From 376d1d69ca753c7e7816ced87ddf83657d50b885 Mon Sep 17 00:00:00 2001 From: daisy-ycguo Date: Tue, 12 Mar 2013 15:23:36 +0800 Subject: [PATCH] Add slicing tool to the master branch This patch added tools used for slicing and merging in translation process. The patch also includes the POT files for each documents. The PO files are not included, which can be downloaded from Transifex. Fixes: bug #1153415 Change-Id: Ia455134c99acb1129e8f10deda0d85867b1ef9a3 --- .tx/config | 49 + .../basic-install/locale/basic-install.pot | 710 + doc/src/docbkx/cli-guide/locale/cli-guide.pot | 879 ++ doc/src/docbkx/common/locale/common.pot | 11333 ++++++++++++++ .../locale/openstack-compute-admin.pot | 12708 ++++++++++++++++ .../openstack-ha/locale/openstack-ha.pot | 32 + .../locale/openstack-install.pot | 3721 +++++ .../openstack-network-connectivity-admin.pot | 4336 ++++++ .../locale/openstack-object-storage-admin.pot | 3288 ++++ .../openstack-ops/locale/openstack-ops.pot | 280 + tools/generatedocbook | 149 + tools/generatepot | 93 + 12 files changed, 37578 insertions(+) create mode 100644 .tx/config create mode 100644 doc/src/docbkx/basic-install/locale/basic-install.pot create mode 100644 doc/src/docbkx/cli-guide/locale/cli-guide.pot create mode 100644 doc/src/docbkx/common/locale/common.pot create mode 100644 doc/src/docbkx/openstack-compute-admin/locale/openstack-compute-admin.pot create mode 100644 doc/src/docbkx/openstack-ha/locale/openstack-ha.pot create mode 100644 doc/src/docbkx/openstack-install/locale/openstack-install.pot create mode 100644 doc/src/docbkx/openstack-network-connectivity-admin/locale/openstack-network-connectivity-admin.pot create mode 100644 doc/src/docbkx/openstack-object-storage-admin/locale/openstack-object-storage-admin.pot create mode 100644 doc/src/docbkx/openstack-ops/locale/openstack-ops.pot create mode 100755 tools/generatedocbook create mode 100755 tools/generatepot diff --git a/.tx/config b/.tx/config new file mode 100644 index 0000000000..5debec1719 --- /dev/null +++ b/.tx/config @@ -0,0 +1,49 @@ +[main] +host = https://www.transifex.net +type = PO + +[openstack-manuals-i18n.common] +file_filter = doc/src/docbkx/common/locale/.po +source_file = doc/src/docbkx/common/locale/common.pot +source_lang = en + +[openstack-manuals-i18n.openstack-compute-admin] +file_filter = doc/src/docbkx/openstack-compute-admin/locale/.po +source_file = doc/src/docbkx/openstack-compute-admin/locale/openstack-compute-admin.pot +source_lang = en + +[openstack-manuals-i18n.openstack-install] +file_filter = doc/src/docbkx/openstack-install/locale/.po +source_file = doc/src/docbkx/openstack-install/locale/openstack-install.pot +source_lang = en + +[openstack-manuals-i18n.openstack-network-connectivity-admin] +file_filter = doc/src/docbkx/openstack-network-connectivity-admin/locale/.po +source_file = doc/src/docbkx/openstack-network-connectivity-admin/locale/openstack-network-connectivity-admin.pot +source_lang = en + +[openstack-manuals-i18n.openstack-object-storage-admin] +file_filter = doc/src/docbkx/openstack-object-storage-admin/locale/.po +source_file = doc/src/docbkx/openstack-object-storage-admin/locale/openstack-object-storage-admin.pot +source_lang = en + +[openstack-manuals-i18n.openstack-ha] +file_filter = doc/src/docbkx/openstack-ha/locale/.po +source_file = doc/src/docbkx/openstack-ha/locale/openstack-ha.pot +source_lang = en + +[openstack-manuals-i18n.basic-install] +file_filter = doc/src/docbkx/basic-install/locale/.po +source_file = doc/src/docbkx/basic-install/locale/basic-install.pot +source_lang = en + +[openstack-manuals-i18n.cli-guide] +file_filter = doc/src/docbkx/cli-guide/locale/.po +source_file = doc/src/docbkx/cli-guide/locale/cli-guide.pot +source_lang = en + +[openstack-manuals-i18n.openstack-ops] +file_filter = doc/src/docbkx/openstack-ops/locale/.po +source_file = doc/src/docbkx/openstack-ops/locale/openstack-ops.pot +source_lang = en + diff --git a/doc/src/docbkx/basic-install/locale/basic-install.pot b/doc/src/docbkx/basic-install/locale/basic-install.pot new file mode 100644 index 0000000000..3e36620339 --- /dev/null +++ b/doc/src/docbkx/basic-install/locale/basic-install.pot @@ -0,0 +1,710 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2013-03-12 15:08+0800\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/src/docbkx/basic-install/src/basic-install_controller.xml:6(title) +msgid "Controller Node" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute.xml:6(title) +msgid "Compute Node" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-operating.xml:6(title) +msgid "Virtual Networking" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-operating.xml:8(title) +msgid "Create Virtual Networking" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-operating.xml:12(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-keystone.xml:44(para) +msgid "Load environment variables :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-operating.xml:16(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-keystone.xml:48(para) +msgid "Create novarc file :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-operating.xml:28(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-keystone.xml:60(para) +msgid "Export the variables :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-operating.xml:35(para) +msgid "Download the Quantum script. We are using the \"Provider Router with Private Networks\" use-case." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-operating.xml:38(para) +msgid "Edit the script belong your networking (public network, floatings IP)." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-operating.xml:41(para) +msgid "Execute the script." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-operating.xml:47(title) +msgid "L3 Configuration" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-operating.xml:50(para) +msgid "Copy the external network ID :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-operating.xml:53(para) ./doc/src/docbkx/basic-install/src/basic-install_network-operating.xml:59(para) +msgid "Edit /etc/quantum/l3_agent.ini and paste the ID :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-operating.xml:56(para) +msgid "Copy the provider router ID :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-operating.xml:62(para) +msgid "Restart L3 Agent :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-quantum.xml:6(title) ./doc/src/docbkx/basic-install/src/basic-install_network-services.xml:30(title) ./doc/src/docbkx/basic-install/src/basic-install_compute-quantum.xml:6(title) ./doc/src/docbkx/basic-install/src/basic-install_compute-quantum.xml:24(title) +msgid "Quantum" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-quantum.xml:10(para) ./doc/src/docbkx/basic-install/src/basic-install_network-services.xml:12(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-glance.xml:10(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-cinder.xml:10(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:111(para) ./doc/src/docbkx/basic-install/src/basic-install_compute-quantum.xml:28(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-keystone.xml:10(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-nova.xml:10(para) ./doc/src/docbkx/basic-install/src/basic-install_compute-nova.xml:10(para) +msgid "Install the packages :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-quantum.xml:14(para) ./doc/src/docbkx/basic-install/src/basic-install_network-services.xml:31(para) +msgid "Configure Quantum services :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-quantum.xml:17(para) ./doc/src/docbkx/basic-install/src/basic-install_network-services.xml:49(para) ./doc/src/docbkx/basic-install/src/basic-install_compute-quantum.xml:31(para) +msgid "Edit /etc/quantum/quantum.conf file and modify :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-quantum.xml:33(para) ./doc/src/docbkx/basic-install/src/basic-install_network-services.xml:69(para) +msgid "It's more handy to choose tunnel mode since you don't have to configure your physical switches for VLANs." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-quantum.xml:24(para) ./doc/src/docbkx/basic-install/src/basic-install_network-services.xml:57(para) +msgid "Edit /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini file and modify :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-quantum.xml:41(para) ./doc/src/docbkx/basic-install/src/basic-install_network-services.xml:42(para) +msgid "Edit /etc/quantum/api-paste.ini file and modify :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-quantum.xml:48(para) ./doc/src/docbkx/basic-install/src/basic-install_network-services.xml:80(para) +msgid "Start the services :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-services.xml:6(title) +msgid "Network Services" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-services.xml:8(title) +msgid "Open-vSwitch" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-services.xml:16(para) +msgid "Start Open vSwitch: " +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-services.xml:20(para) +msgid "Create Virtual Bridging :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-services.xml:34(para) +msgid "Edit /etc/quantum/l3_agent.ini file and modify :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-services.xml:76(para) +msgid "Edit /etc/quantum/dhcp_agent.ini file and add :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_conclusion.xml:6(title) +msgid "Conclusion" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_conclusion.xml:7(para) +msgid "We have built a basic architecture for advanced testing purpose. This kind of architecture is close to the production, without High Availability (HA) and some services such as those for running OpenStack Object Storage. You can of course add as many compute nodes as you want. If you need more specific help, please read the official documentation of each project or write a post to an OpenStack mailing list." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-intro.xml:6(title) ./doc/src/docbkx/basic-install/src/basic-install_intro.xml:6(title) ./doc/src/docbkx/basic-install/src/basic-install_compute-intro.xml:6(title) ./doc/src/docbkx/basic-install/src/basic-install_network-intro.xml:6(title) +msgid "Introduction" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-intro.xml:10(para) +msgid "Databases (with MySQL)" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-intro.xml:13(para) +msgid "Queues (with RabbitMQ)" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-intro.xml:16(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-keystone.xml:6(title) +msgid "Keystone" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-intro.xml:19(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-glance.xml:6(title) +msgid "Glance" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-intro.xml:22(para) +msgid "Nova (without nova-compute)" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-intro.xml:25(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-cinder.xml:6(title) +msgid "Cinder" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-intro.xml:28(para) +msgid "Quantum Server (with Open-vSwitch plugin)" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-intro.xml:31(para) +msgid "Dashboard (with Horizon)" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-intro.xml:7(para) +msgid "The Controller node will provide : " +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_intro.xml:7(para) +msgid "This document helps anyone who wants to deploy OpenStack Folsom for development purposes with Ubuntu 12.04 LTS (using the Ubuntu Cloud Archive)." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_intro.xml:10(para) +msgid "We are going to install a three-node setup with one controller, one network and one compute node." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_intro.xml:12(para) +msgid "Of course, you can setup as many computes nodes as you want. This document is a good start for beginners in OpenStack who want to install a testing infrastructure." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-common.xml:6(title) ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:6(title) ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:6(title) +msgid "Common services" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-common.xml:11(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:13(para) ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:13(para) +msgid "Time zone : UTC" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-common.xml:14(para) +msgid "Hostname : folsom-compute" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-common.xml:17(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:19(para) ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:19(para) +msgid "Packages : OpenSSH-Server" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-common.xml:9(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:11(para) ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:11(para) +msgid "Install Ubuntu with this parameters :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-common.xml:20(para) +msgid "After OS Installation, reboot the server ." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-common.xml:23(para) ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:25(para) +msgid "Since Ubuntu 12.04 LTS has OpenStack Essex by default, we are going to use Cloud Archives for Folsom :Edit /etc/apt/sources.list.d/cloud-archive.list :Upgrade the system (and reboot if you need) :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-common.xml:31(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:36(para) ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:33(para) +msgid "Configure the network :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-common.xml:34(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:39(para) ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:36(para) +msgid "Edit /etc/network/interfaces file :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-common.xml:54(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:59(para) ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:63(para) +msgid "Edit /etc/sysctl.conf :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-common.xml:51(para) +msgid " Then, restart network service :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-common.xml:66(para) ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:76(para) +msgid "Edit the /etc/hosts file and add folsom-controller, folsom-network and folsom-compute hostnames with correct IP." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-common.xml:77(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:87(para) ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:87(para) +msgid "Install the package :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-common.xml:80(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:91(para) ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:90(para) +msgid "Configure /etc/ntp.conf file :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-common.xml:83(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:97(para) ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:118(para) ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:93(para) +msgid "Restart the service :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-common.xml:75(para) +msgid "Install & Configure NTP :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_operate.xml:6(title) +msgid "Create your first VM" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_operate.xml:9(para) +msgid "You can now use OpenStack API or the Dashboard to manage your own IaaS : http://192.168.0.1/horizon with demo / password credentials." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_operate.xml:16(para) +msgid "Edit the security group \"Default\" to allow ICMP and SSH." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_operate.xml:19(para) +msgid "Create a personal keypair." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_operate.xml:22(para) +msgid "In the Dashboard, go to \"Instances\" and click \"Launch Instance\" for spawning a new VM." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_operate.xml:26(para) +msgid "Since Horizon does not manage L3 in Folsom release, we have to configure floating IP from Quantum CLI (using demo tenant). To do that, you need to get the ext_net ID and the port_id of your VM : " +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_operate.xml:32(para) +msgid "Now, we are going to create a floating-IP attached to the virtual port of our VM and routed to the external network : " +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_operate.xml:36(para) +msgid "That's it! You should be able to ping your VM using floating IP." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-intro.xml:10(para) +msgid "Hypervisor (KVM)" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-intro.xml:13(para) +msgid "nova-compute" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-intro.xml:16(para) +msgid "Quantum OVS Agent" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-intro.xml:7(para) +msgid "The Compute node will provide : " +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-glance.xml:13(para) +msgid "Configure Glance :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-glance.xml:16(para) +msgid "Edit /etc/glance/glance-api.conf and /etc/glance/glance-registry.conf files and modify :For glance-api.conf, modify : " +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-glance.xml:25(para) +msgid "Restart Glance services :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-glance.xml:28(para) +msgid "Create Glance tables into the database :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-glance.xml:31(para) +msgid "Download and import Ubuntu 12.04 LTS UEC Image :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-glance.xml:37(para) +msgid "Check if the image has been introduced in the index :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-glance.xml:47(para) +msgid "You can also install Glance Replicator (new in Folsom). More informations about it here." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network.xml:6(title) +msgid "Network Node" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-cinder.xml:14(para) +msgid "Configure & start the iSCSI services :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-cinder.xml:19(para) +msgid "Configure Cinder :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-cinder.xml:22(para) +msgid "Edit /etc/cinder/cinder.conf file and modify :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-cinder.xml:29(para) +msgid "Edit /etc/cinder/api-paste.ini file and modify :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-cinder.xml:34(para) +msgid "Create the volume (on the second disk) :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-cinder.xml:43(para) +msgid "Create Cinder tables into the database :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-cinder.xml:46(para) +msgid "Restart the services :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:6(title) +msgid "Requirements" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:7(para) +msgid "You need at least three machines (virtual or physical) with Ubuntu 12.04 (LTS) installed." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:10(caption) +msgid "Architecture and node information" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:14(para) +msgid "controller" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:15(para) +msgid "network" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:16(para) +msgid "compute" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:23(para) +msgid "Hostname" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:24(para) +msgid "folsom-controller" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:25(para) +msgid "folsom-network" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:26(para) +msgid "folsom-compute" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:31(para) +msgid "Services" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:32(para) +msgid "MySQL, RabbitMQ, Nova, Cinder, Glance, Keystone, Quantum" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:34(para) +msgid "Quantum-L3-agent, Quantum-DHCP-agent, Quantum Agent with Open-vSwitch" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:36(para) +msgid "nova-compute, KVM, nova-api, Quantum Agent with Open-vSwitch" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:42(para) +msgid "Minimum number of disks" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:43(para) ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:77(emphasis) ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:80(emphasis) +msgid "2" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:44(para) ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:45(para) +msgid "1" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:50(para) +msgid "External + API network" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:51(para) +msgid "7.7.7.7/24" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:52(para) +msgid "7.7.7.8/24" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:53(para) ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:67(para) +msgid "-" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:58(para) +msgid "Management network" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:59(para) +msgid "192.168.0.1/24" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:60(para) +msgid "192.168.0.2/24" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:61(para) +msgid "192.168.0.3/24" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:66(para) +msgid "Data network" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:68(para) +msgid "10.10.10.1/24" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:69(para) +msgid "10.10.10.2/24" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:74(emphasis) +msgid "Total number of NIC" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_requirements.xml:79(emphasis) +msgid "3" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/basic-install/src/basic-install_architecture.xml:9(None) ./doc/src/docbkx/basic-install/src/basic-install_architecture.xml:12(None) +msgid "@@image: 'figures/Quantum-PhysNet-Diagram.png'; md5=f94377ebc99eb0f16d417f64730c5d46" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_architecture.xml:6(title) +msgid "Architecture" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_architecture.xml:16(para) +msgid "A standard Quantum setup has up to four distinct physical data center networks:" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_architecture.xml:19(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/src/docbkx/basic-install/src/basic-install_architecture.xml:26(para) +msgid "Data network. Used for VM data communication within the cloud deployment. The IP addressing requirements of this network depend on the Quantum plugin in use. " +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_architecture.xml:33(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/src/docbkx/basic-install/src/basic-install_architecture.xml:40(para) +msgid "API network. Exposes all OpenStack APIs, including the Quantum 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 quantum 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 "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:8(title) ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:8(title) +msgid "Operating System" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:16(para) +msgid "Hostname : controller" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:22(para) ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:22(para) +msgid "After OS Installation, reboot the server." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:25(para) +msgid "Since Ubuntu 12.04 LTS has OpenStack Essex by default, we are going to use the Ubuntu Cloud Archive for Folsom :Edit /etc/apt/sources.list.d/cloud-archive.list :Upgrade the system (and reboot if you need) :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:56(para) ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:60(para) +msgid " Then, restart network service : " +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:71(para) +msgid "Edit the /etc/hosts file and add controller, networknode and compute1 hostnames with correct IP." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:85(para) ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:85(para) +msgid "Install Configure NTP :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:106(title) +msgid "MySQL Database Service" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:114(para) +msgid "Allow connection from the network :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:122(para) +msgid "Create Databases, Users, Rights : " +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:156(title) +msgid "RabbitMQ Messaging Service" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:160(para) +msgid "Install the packages :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-common.xml:164(para) +msgid "Change the default password :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-quantum.xml:8(title) +msgid "Open vSwitch" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-quantum.xml:12(para) +msgid "Install the packages:" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-quantum.xml:15(para) +msgid "Start Open vSwitch service" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-quantum.xml:18(para) +msgid "Configure Virtual Bridging" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-quantum.xml:39(para) +msgid "Edit /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini file and modify :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-quantum.xml:53(para) +msgid "Start the Agent :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-hypervisor.xml:6(title) +msgid "Hypervisor" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-hypervisor.xml:10(para) +msgid "Install the packages that we need :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-hypervisor.xml:14(para) +msgid "Configure libvirt :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-hypervisor.xml:17(para) +msgid "Edit /etc/libvirt/qemu.conf file and add :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-hypervisor.xml:25(para) +msgid "Disable KVM default virtual bridge to avoid any confusion :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-hypervisor.xml:29(para) +msgid "Allow Live Migrations :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-hypervisor.xml:30(para) +msgid "Edit /etc/libvirt/libvirtd.conf file :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-hypervisor.xml:34(para) +msgid "Modify libvirtd_opts variable in /etc/init/libvirt-bin.conf file :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-hypervisor.xml:35(para) +msgid "Edit /etc/default/libvirt-bin file :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-hypervisor.xml:40(para) +msgid "Restart libvirt :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-common.xml:16(para) +msgid "Hostname : folsom-network" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-keystone.xml:14(para) +msgid "Edit /etc/keystone/keystone.conf :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-keystone.xml:39(para) +msgid "Restart Keystone and create the tables in the database :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-keystone.xml:67(para) +msgid "Download the data script and fill Keystone database with data (users, tenants, services) :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-keystone.xml:74(para) +msgid "Download the endpoint script and create the endpoints (for projects) : If an IP address of the management network on the controller node is different from this example, please use the following:" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/bk-basic-install.xml:8(title) +msgid "OpenStack Basic Install" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-dashboard.xml:6(title) +msgid "Dashboard (Horizon)" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-dashboard.xml:7(para) +msgid "Install the packages : OpenStack Dashboard is now available at http://<controller_node>/horizon. We can login with admin / password credentials or demo / password." +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-nova.xml:6(title) ./doc/src/docbkx/basic-install/src/basic-install_compute-nova.xml:6(title) +msgid "Nova" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-nova.xml:15(para) ./doc/src/docbkx/basic-install/src/basic-install_compute-nova.xml:13(para) +msgid "Configure Nova :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-nova.xml:18(para) +msgid "Edit /etc/nova/api-paste.ini file and modify :Since we are going to use Cinder for volumes, we should also delete each part concerning \"nova-volume\" : " +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-nova.xml:55(para) ./doc/src/docbkx/basic-install/src/basic-install_compute-nova.xml:32(para) +msgid "Edit /etc/nova/nova.conf file and modify :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-nova.xml:116(para) +msgid "Create Nova tables into the database :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_controller-nova.xml:119(para) ./doc/src/docbkx/basic-install/src/basic-install_compute-nova.xml:99(para) +msgid "Restart Nova services :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-nova.xml:16(para) +msgid "Edit /etc/nova/api-paste.ini file and modify :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_compute-nova.xml:23(para) +msgid "Edit /etc/nova/nova-compute.conf file and modify :" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-intro.xml:10(para) +msgid "Virtual Bridging (Open-vSwitch + Quantum Agent) with tunneling" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-intro.xml:13(para) +msgid "DHCP Server (Quantum DHCP Agent)" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-intro.xml:16(para) +msgid "Virtual Routing (Quantum L3 Agent)" +msgstr "" + +#: ./doc/src/docbkx/basic-install/src/basic-install_network-intro.xml:7(para) +msgid "The Network node will provide : " +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/src/docbkx/basic-install/src/basic-install_network-intro.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/src/docbkx/cli-guide/locale/cli-guide.pot b/doc/src/docbkx/cli-guide/locale/cli-guide.pot new file mode 100644 index 0000000000..3ab41ffa4e --- /dev/null +++ b/doc/src/docbkx/cli-guide/locale/cli-guide.pot @@ -0,0 +1,879 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2013-03-12 15:08+0800\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/src/docbkx/cli-guide/src/nova_cli_commands.xml:6(title) +msgid "Command List for nova Client" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_install.xml:6(title) +msgid "Install the keystone Client" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_install.xml:7(para) +msgid "This example walks through installing the keystone client. After you install a client, you must configure environment variables for authentication." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_install.xml:11(title) +msgid "To install the keystone client:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_install.xml:13(title) +msgid "Install Python" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_install.xml:14(para) +msgid "Install Python 2.6 or later. Currently, the keystone client does not support Python 3." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_install.xml:18(title) +msgid "Install the keystone client package" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_install.xml:22(emphasis) +msgid "Recommended method:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_install.xml:52(para) +msgid "There is a packaged version so you can use dpkg or aptitude to install python-keystoneclient." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_install.xml:25(para) +msgid "Install through the package manager for your system:SystemCommandMac OS XUbuntu 11.10 and earlierUbuntu 12.04RHEL, CentOS, or Fedora:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_install.xml:64(para) +msgid "Run the following command to install the keystone client package: " +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_install.xml:71(emphasis) +msgid "easy_install" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_install.xml:72(para) +msgid "Run the following command to install the keystone client package:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_install.xml:19(para) +msgid "Choose one of the following methods to install the keystone client package. " +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_install.xml:80(title) +msgid "Test the keystone client" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_install.xml:81(para) +msgid "To verify that you can talk to the API server, run the following commands:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_install.xml:84(para) +msgid "The keystone discover command shows the keystone servers available." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/swift_cli_commands.xml:6(title) +msgid "swift Command Reference" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/swift_cli_howto.xml:9(title) +msgid "swift Client" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/swift_cli_howto.xml:10(para) +msgid "This chapter describes how to use the swift client." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/swift_cli_howto.xml:11(para) ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:11(para) ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:11(para) ./doc/src/docbkx/cli-guide/src/cinder_cli_howto.xml:11(para) ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:11(para) ./doc/src/docbkx/cli-guide/src/keystone_cli_howto.xml:12(para) +msgid "To install the client, see ." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:9(title) +msgid "nova Client" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:10(para) +msgid "This chapter describes how to use the nova client." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:31(title) +msgid "List Instances, Images, and Flavors" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:32(para) +msgid "Before you can go about the business of building your cloud, you want to know what images are available to you by asking the image service what kinds of configurations are available. The image service could be compared to iTunes for your cloud - you can view the playlist of images before using your favorite image to create a new instance in the cloud. To get the list of images, their names, status, and ID, use this command: " +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:51(para) +msgid "Next you need to know the relative sizes of each of these." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:65(para) ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:26(para) +msgid "You can also narrow down the list by using grep to find only the CentOS images with a command like this:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:77(title) +msgid "Launch an Instance" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:78(para) +msgid "Launching a new instance on OpenStack." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:80(title) +msgid "Commands Used" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:81(para) ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:38(para) +msgid "This process uses the following commands: " +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:94(title) +msgid "Before Launch" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:96(para) +msgid "With the information about what is available to you, you can choose the combination of image and flavor to create your virtual servers and launch instances." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:116(title) +msgid "Rebooting an instance" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:117(para) +msgid " performs a reboot of a running instance. By default, this is a \"soft\" reboot, which will attempt a graceful shutdown and restart of the instance. To perform a \"hard\" reboot (i.e., a power cycle of the instance), pass the --hard flag as an argument." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:129(title) +msgid "Manage Images" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:130(para) +msgid "Adding images and setting the access to them can be managed in Glance, but you can create images by taking a snapshot of a running instance and view available images, set or delete image metadata, and delete an image, using the nova CLI." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:140(title) +msgid "Get an Instance Console" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:141(para) +msgid "When you need to get a VNC console directly to a server, you can use the nova get-vnc-console command to connect." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:146(title) +msgid "Managing Baremetal Nodes" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:147(para) +msgid "If you are using the Baremetal driver, you must inform each Nova Compute host of the physical hardware that it should manage. This is done via the baremetal admin extension." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/nova_cli_howto.xml:150(para) +msgid "Create a node with , and then add network interface information to it with . Nodes and interfaces can be listed and deleted. When a node is in use, its status includes the UUID of the Nova instance that is running on it. " +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_commands.xml:6(title) +msgid "keystone Command Reference" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:9(title) +msgid "glance Client" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:10(para) +msgid "This chapter describes how to use the glance client." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:14(title) +msgid "List Images" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:15(para) +msgid "To see what images are available to you, use this command: " +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:36(title) +msgid "Add a New Image" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:37(para) +msgid "Adding a new image to your OpenStack cloud." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:55(title) +msgid "Before You Add an Image" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:57(para) +msgid "Ensure you have created an image that is OpenStack compatible. For details, see the Image Management chapter in the OpenStack Compute Administration Manual." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:66(title) +msgid "Upload an image to glance" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:67(para) +msgid "Assuming you had a CentOS 6.3 image in qcow2 format called centos63.qcow2, the following example will upload it to glance and configure it for public access." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:77(title) +msgid "Update an image" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:78(para) +msgid "To update an image, use the following command:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:80(para) +msgid "Where image is the name or ID of the image that you want to update. You can use the following optional arguments to modify the following image properties:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:125(para) +msgid "To annotate an image with a property that describes the required VIF model, use the argument." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:128(para) ./doc/src/docbkx/cli-guide/src/cli_install.xml:152(para) +msgid "For example:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:146(para) +msgid "virtio" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:149(para) ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:170(para) +msgid "ne2k_pci" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:152(para) ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:173(para) +msgid "pcnet" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:155(para) ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:176(para) +msgid "rtl8139" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:158(para) ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:179(para) +msgid "e1000" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:167(para) +msgid "netfront" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:129(para) +msgid "Valid model values vary depending on the libvirt_type setting: libvirt_type settingSupported model valuesqemu or kvmxen" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:187(para) +msgid "Requesting an unsupported VIF model causes the guest instance to fail to launch." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:194(title) +msgid "Managing Images" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_howto.xml:195(para) +msgid "Adding images and setting the access to them can be managed in glance, but you can create images by taking a snapshot of a running instance and view available images, set or delete image metadata, and delete an image, using the nova client." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cinder_cli_howto.xml:9(title) +msgid "cinder Client" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cinder_cli_howto.xml:10(para) +msgid "This chapter describes how to use the cinder client." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_help.xml:6(title) +msgid "Get Help for Client Commands" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_help.xml:7(para) +msgid "Use the command to get help for commands, parameters, and subcommands for any OpenStack client." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_help.xml:10(para) +msgid "The syntax is:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_help.xml:12(para) +msgid "For example, to get help for glance client commands, run the following command:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_help.xml:15(para) +msgid "The command lists the available commands for the specified client." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_help.xml:18(para) +msgid "Depending on your credentials, you might not have permission to use every command." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_help.xml:21(para) +msgid "To get help for a specific command, enter the command name after the command, as follows:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_help.xml:24(para) +msgid "For example, to get help for the glance command, enter the following command:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_help.xml:29(para) +msgid "The command shows the command usage, a description of the command, and descriptions of any positional and optional arguments, as follows:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_version.xml:6(title) +msgid "Get the Version for a Client" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_version.xml:8(para) +msgid "Search for the version number." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_version.xml:15(para) +msgid "You can also use the yolk -l command to see what version of the CLI you have installed." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:34(title) ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:189(title) +msgid "Authenticate" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:35(para) +msgid "To authenticate a tenant to run commands for the OpenStack clients, you issue an authentication request to the OpenStack Identity Service v2.0. To issue this request, you must first set and source environment variables and install the nova client. Then, you issue an authentication request through the nova command." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:42(title) +msgid "To authenticate:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:46(title) +msgid "Set environment variables" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:47(para) +msgid "Before you can issue client commands, you must set environment variables to authenticate." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:51(para) +msgid "You can either edit your bash profile to add and set environment variables or use an openrc file downloaded from an OpenStack Dashboard." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:55(para) +msgid "Either edit your .bash_profile file:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:57(para) +msgid "Add the following lines to the bash profile. Edit the values for the , , and variables:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:62(varname) ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:88(varname) +msgid "username" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:63(varname) +msgid "password" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:64(varname) ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:84(varname) +msgid "tenant" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:68(para) +msgid "Or download an openrc file from the OpenStack Dashboard:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:94(para) +msgid "Source the file:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:96(para) +msgid "Enter your OpenStack password when prompted." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:128(para) +msgid "Your tenant ID, usually provided with your username." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:135(para) +msgid "Your tenant name, usually provided with your username." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:142(para) +msgid "The endpoint for the Identity Service (keystone), which the nova client uses for authentication. Include the trailing forward slash (/) in the URL. Otherwise, you receive a 404 error." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:97(para) +msgid "The following table describes the environment variables:
OpenStack Clients Environment Variables
Environment VariableDescription
OS_USERNAMEYour OpenStack username.
OS_PASSWORDYour OpenStack user password.
OS_TENANT_ID
OS_TENANT_NAME
OS_AUTH_URL
NOVACLIENT_DEBUGSet to 1 to show the underlying cURL commands with embedded API requests in the command responses. Otherwise, omit this variable.
NOVA_VERSIONThe version of the API. Set to 2.
" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:174(para) +msgid "After you set the variables, save the file." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:177(title) +msgid "Set permissions on and source the bash profile" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:179(para) +msgid "Because the bash profile contains a password, set permissions on it so other people cannot read it:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:183(para) +msgid "To source the variables to make them available in your current shell, run the following command:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:190(para) +msgid "To authenticate, you must install the nova client. To install the nova client, see ." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:193(para) +msgid "To verify that you can talk to the API server, authenticate and list images:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:197(para) +msgid "Then, list networks: " +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:217(title) ./doc/src/docbkx/cli-guide/src/cli_troubleshooting.xml:6(title) +msgid "Troubleshooting" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:220(para) +msgid "If you cannot run commands successfully, make sure that you entered your user name, password, and account number correctly in the bash profile file." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:226(para) ./doc/src/docbkx/cli-guide/src/cli_troubleshooting.xml:28(para) +msgid "If you change any environment variables, either log out and back in or source your bash profile again." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:231(para) +msgid "To override some environment variable settings, you can use the options that are listed at the end of the output. For example, you can override the OS_PASSWORD setting in the bash profile by specifying a password on a nova command, as follows:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_credentials.xml:240(para) +msgid "Where password is your password." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:34(title) ./doc/src/docbkx/cli-guide/src/cli_install.xml:162(title) +msgid "Install the OpenStack Clients" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:35(para) +msgid "To manage your servers, images, volumes, isolated networks, and other cloud resources from the command line, install and use the open-source clients." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:38(para) +msgid "To install the clients, first install some prerequisite software. Then, install the Python packages. Each Python package is an OpenStack client." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:43(title) +msgid "Before You Begin" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:59(para) +msgid "Python 2.6 or later" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:62(para) +msgid "Currently, the clients do not support Python 3." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:68(para) +msgid " package" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:72(para) +msgid "Installed by default on Mac OS X." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:73(para) +msgid "Many Linux distributions provide packages to make easy to install." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:77(para) +msgid "Search your package manager for to find an installation package. If you cannot find one, download the package directly from http://pypi.python.org/pypi/setuptools." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:92(para) +msgid "To install the clients on a Mac OS X or Linux system, use . It is easy to use and ensures that you get the latest version of the clients from the Python Package Index. Also, it lets you update or remove the packages later on." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:105(para) +msgid "Mac OS X " +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:109(para) +msgid "Ubuntu 11.10 and earlier" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:116(para) +msgid "Ubuntu 12.04" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:117(para) ./doc/src/docbkx/cli-guide/src/cli_install.xml:148(para) +msgid "A packaged version enables you to use or to install the python-novaclient." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:125(para) +msgid "Ubuntu " +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:129(para) +msgid "RHEL, CentOS, or Fedora " +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:133(para) +msgid "openSUSE 12.2 and earlier" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:135(para) +msgid "A packaged version available in the Open Build Service enables you to use or to install the the python-novaclient." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:143(para) +msgid "Alternatively, you can still use ." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:147(para) +msgid "openSUSE 12.3" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:102(para) +msgid "Install through the package manager for your system:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:44(para) +msgid "Before you begin, install the following prerequisite software:
OpenStack Clients Prerequisite Software
PrerequisiteDescription
package
" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:166(title) +msgid "To install the OpenStack clients:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:168(title) +msgid "Install or update the client packages" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:169(para) +msgid "You must install each client separately." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:170(para) +msgid "Run the following command to install or update a client package:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:173(para) +msgid "Where <project> is the project name and is one of the following values:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:177(para) +msgid "nova. Compute API." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:181(para) +msgid "quantum. Networking API." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:185(para) +msgid "keystone. Identity service API." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:189(para) +msgid "glance. Image service API." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:193(para) +msgid "swift. Object storage API." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:197(para) +msgid "cinder. Block storage API." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:201(para) +msgid "For example, to install the nova client, run the following command:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:204(para) +msgid "To update the nova client, run the following command:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:207(para) +msgid "To remove the nova client, run the following command:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:213(title) +msgid "Set environment variables and authenticate" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_install.xml:215(para) +msgid "Before you can issue client commands, you must set environment variables and authenticate. See ." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:9(title) +msgid "quantum Client" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:10(para) +msgid "This chapter describes how to use the quantum client." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:15(title) +msgid "Overview" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:18(title) +msgid "Argument parts of API 2.0 command" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:19(para) +msgid "In general, quantum client command arguments divide into three parts:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:22(title) +msgid "Known options" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:23(para) +msgid "These options are following command name. They can be after positional arguments if the command does not support unknown options. Known options are used to represent optional values in API resource. Some options have default value if not specified." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:31(title) +msgid "Positional arguments" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:32(para) +msgid "Positional arguments are mandatory information for an API resource. They must be given in the order." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:37(title) +msgid "Unknown options" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:38(para) +msgid "Unknown options are at the end part of the command line. They must be after a positional argument. If there is no positional argument for the command, pseudo argument ‘--’ should be used. To define an unknown option, the format is --optionname [type=int|bool|list...] [optionvalue]*. There can be multiple option values for a certain optionname. When there is no optionvalue given, the option is regarded as a bool one and value is true. The type is python built-in type, such as int, bool, float and list, defaulted to string if not given. Most of time, quantum server will convert the value into wanted type. Unknown options are used to provides values for update_command, implement new features of API v2.0. It can also be used to provide information for API extension." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:55(para) +msgid "the usage text for a command can tell if it supports unknown options:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:66(para) +msgid "Note the “...” after positional argument name, which is the indicator for unknown options." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:71(title) +msgid "Features from cliff" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:73(title) +msgid "Interactive mode" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:74(para) +msgid "If there is no command specified, the quantum client will enter into interactive mode:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:117(title) +msgid "Output format" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:118(para) +msgid "We can use -h after each command to show the usage of each command:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:154(para) +msgid "We can see the output formatters cliff provides to each command. By default, the output format is table. Now we choose csv output to run the command net-list:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:168(title) +msgid "Column selection" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:169(para) +msgid "We can see -c COLUMN in previous usage output. It can be used to limit the output fields:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:185(title) +msgid "Features from API" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:187(title) +msgid "Fields selection" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:188(para) +msgid "If there are ‘fields’ in request URL, V2.0 API will extract the list of fields to return. A sample of such URLs is http://localhost:9696/v2.0/networks.json?fields=id&fields=name" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:192(para) +msgid "quantumv2 client supports this feature by -F option in known options part and --fields in unknown options part. For example, quantum -F id net-list -- --fields name. Only xx-list and xx-show commands support this feature." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:199(title) +msgid "Value filtering" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/quantum_cli_howto.xml:200(para) +msgid "Any other fields except the ‘fields’ are used as value filtering. A sample of such URLs is http://localhost:9696/v2.0/networks.json?name=test1&name=test2&tag=a. By the current quantum server's sample DB plugin, the filtering has the same meaning as a SQL clause: name in [‘test1’, ‘test2’]. Quantum client supports this feature by any key options in unknown option part. For example quantum net-list -- --name test1 test2 --tag a. Only xx-list and xx-show commands support this feature." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_howto.xml:9(title) +msgid "keystone Client" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/keystone_cli_howto.xml:10(para) +msgid "This chapter describes how to use the keystone client." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:45(title) ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:47(titleabbrev) +msgid "OpenStack Clients Guide" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:55(orgname) ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:64(holder) +msgid "OpenStack LLC" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:59(year) +msgid "2009" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:60(year) +msgid "2010" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:61(year) +msgid "2011" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:62(year) +msgid "2012" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:63(year) +msgid "2013" +msgstr "" + +#. API v2 +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:67(productname) +msgid "OpenStack Clients" +msgstr "" + +#. ... continue addding more revisions here as you change this document using the markup shown below... +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:69(pubdate) ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:90(date) +msgid "2013-02-25" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:72(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:77(para) +msgid "The OpenStack clients are command-line interfaces (CLIs) that let you run simple commands to make OpenStack API calls. These open-source Python clients are easy to learn and use. The OpenStack APIs are RESTful APIs that use all aspects of the HTTP protocol, including methods, URIs, media types, and response codes. To request OpenStack services, you must first issue an authentication request to the OpenStack Identity Service v2.0." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:94(para) +msgid "Updated the description of glance command." +msgstr "" + +#. ... continue addding more revisions here as you change this document using the markup shown below... +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:104(date) +msgid "2013-02-17" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:108(para) +msgid "Added front matter to and reorganized the book." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:112(para) +msgid "Moved authentication to the installation chapter." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:116(para) +msgid "Added the cinder client." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/bk-cli-guide.xml:119(para) +msgid "Consolidated installation into one chapter." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_overview.xml:42(title) +msgid "OpenStack Clients Overview" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_overview.xml:43(para) +msgid "The OpenStack clients are command-line interfaces (CLIs) that let you run simple commands to make OpenStack API calls. These open-source Python clients are easy to learn and use." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_overview.xml:46(para) +msgid "The OpenStack APIs are RESTful APIs that use all aspects of the HTTP protocol, including methods, URIs, media types, and response codes. Internally, each client command runs cURL commands that embed API requests." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_overview.xml:50(para) +msgid "To install an OpenStack client, see ." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_overview.xml:52(para) +msgid "To request OpenStack services either through the clients or through the APIs directly, you must first issue an authentication request to the OpenStack Identity Service v2.0. To do so, you can run the command, which is a nova client command." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_overview.xml:57(para) +msgid "For example, to use the OpenStack Compute API from the command line, complete these steps:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_overview.xml:62(para) +msgid "Install the nova client." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_overview.xml:65(para) +msgid "Issue the nova command." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_overview.xml:69(para) +msgid "Issue other nova client commands, such as , , and so on." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_overview.xml:76(para) +msgid "An OpenStack common client is in development." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_overview.xml:78(para) +msgid "To install the OpenStack clients on a Mac OS X or Linux system, use because it is easy and ensures that you get the latest version of the client from the Python Package Index. Also, lets you update or remove a package later on." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_overview.xml:84(para) +msgid "Use the following OpenStack clients to access the CLIs:
OpenStack Clients
ClientAssocated APIDescriptionSee
cinderBlock storageCreate and delete volumes, attach volumes to and detach volumes from servers, create and delete snapshots, create volumes from snapshots, and get volume statistics.
glanceImage serviceManage images. For example, add and set permissions on images.
keystoneIdentity serviceCreate and manage users, tenants, roles, endpoints, and credentials.
novaCompute, Compute extensionsAuthenticate, launch servers, set security groups, control IP addresses on servers, control volumes, and create images.
quantumNetworkingConfigure networks for guest servers.
swiftObject storageGather 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/src/docbkx/cli-guide/src/quantum_cli_commands.xml:6(title) +msgid "quantum Client Reference" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_troubleshooting.xml:7(para) +msgid "The CLI clients are considered to be software in development." +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_troubleshooting.xml:11(para) +msgid "If you cannot run commands successfully, make sure that you entered your user name, password, and account number correctly in the bash profile file or have sourced the openrc.sh file correctly. To view your environment variables on Mac OSX or Linux, grep to search for OS_ like so: " +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cli_troubleshooting.xml:33(para) +msgid "To override some environment variable settings, you can use the options that are listed at the end of the output. For example, you can override the setting in the bash profile by specifying a password on a nova command, as follows:" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/cinder_cli_commands.xml:6(title) +msgid "cinder Command Reference" +msgstr "" + +#: ./doc/src/docbkx/cli-guide/src/glance_cli_commands.xml:6(title) +msgid "glance Command Reference" +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/src/docbkx/cli-guide/src/glance_cli_commands.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/src/docbkx/common/locale/common.pot b/doc/src/docbkx/common/locale/common.pot new file mode 100644 index 0000000000..9bc891f096 --- /dev/null +++ b/doc/src/docbkx/common/locale/common.pot @@ -0,0 +1,11333 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2013-03-12 15:09+0800\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/src/docbkx/common/nova_cli_fileinjection.xml:8(title) +msgid "Injecting Files into Instances" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_fileinjection.xml:9(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 for some reason you can use the following command:" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:7(title) +msgid "KVM" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:9(para) +msgid "There are several sections about hypervisor selection in this document. If you are reading this document linearly, you do not want to load the KVM module prior to installing 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/src/docbkx/common/kvm.xml:8(para) +msgid "KVM is configured as the default hypervisor for Compute. " +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:26(para) ./doc/src/docbkx/common/qemu.xml:42(para) ./doc/src/docbkx/common/introduction-to-xen.xml:29(para) +msgid "Raw" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:29(para) ./doc/src/docbkx/common/qemu.xml:45(para) +msgid "QEMU Copy-on-write (qcow2)" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:32(para) ./doc/src/docbkx/common/qemu.xml:48(para) +msgid "VMWare virtual machine disk format (vmdk)" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:19(para) +msgid "To enable KVM explicitly, add the following configuration options /etc/nova/nova.conf: The KVM hypervisor supports the following virtual machine image formats:" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:38(para) +msgid "Fedora: Getting started with virtualization from the Fedora project wiki." +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:44(para) +msgid "Ubuntu: KVM/Installation from the Community Ubuntu documentation." +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:48(para) +msgid "Debian: Virtualization with KVM from the Debian handbook." +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/kvm.xml:62(para) +msgid "openSUSE: Installing KVM from the openSUSE Virtualization with KVM manual." +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:68(para) +msgid "SLES: Installing KVM from the SUSE Linux Enterprise Server Virtualization with KVM manual." +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:35(para) +msgid "The rest of this section describes how to enable KVM on your system. You may also wish to consult distribution-specific documentation:" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:76(title) +msgid "Checking for hardware virtualization support" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:77(para) +msgid "The processors of your compute host need to support virtualization technology (VT) to use KVM." +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:79(para) +msgid "If you are running on Ubuntu, use the command to check if your processor has VT support, it is enabled in the BIOS, and KVM is installed properly, as root:" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:82(para) +msgid "If KVM is enabled, the output should look something like:" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:85(para) +msgid "If KVM is not enabled, the output should look something like:" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:88(para) +msgid "In the case that KVM acceleration is not supported, Compute should be configured to use a different hypervisor, such as QEMU or Xen." +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:91(para) +msgid "On distributions that don't have , you can check if your processor has VT support by looking at the processor flags in the /proc/cpuinfo file. For Intel processors, look for the vmx flag, and for AMD processors, look for the svm flag. A simple way to check is to run the following command and see if there is any output:" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:98(para) +msgid "Some systems require that you enable VT support in the system BIOS. If you believe your processor supports hardware acceleration but the above command produced no output, you may need to reboot your machine, enter the system BIOS, and enable the VT option." +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:105(title) +msgid "Enabling KVM" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:106(para) +msgid "KVM requires the kvm and either kvm-intel or kvm-amd modules to be loaded. This may have been configured automatically on your distribution when KVM is installed." +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:109(para) +msgid "You can check that they have been loaded using , as follows, with expected output for Intel-based processors:The following sections describe how to load the kernel modules for Intel-based and AMD-based processors if they were not loaded automatically by your distribution's KVM installation process." +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:119(title) +msgid "Intel-based processors" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:120(para) +msgid "If your compute host is Intel-based, run the following as root to load the kernel modules: Add the following lines to /etc/modules so that these modules will load on reboot:" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:128(title) +msgid "AMD-based processors" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:129(para) +msgid "If your compute host is AMD-based, run the following as root to load the kernel modules: Add the following lines to /etc/modules so that these modules will load on reboot:" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:138(title) +msgid "Specifying the CPU model of KVM guests" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:142(para) +msgid "To maximise performance of virtual machines by exposing new host CPU features to the guest" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:146(para) +msgid "To ensure a consistent default CPU across all machines, removing reliance of variable QEMU defaults" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:139(para) +msgid "The Compute service allows you to control the guest CPU model that is exposed to KVM virtual machines. Use cases include:" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:150(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. Examples of model names include:" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:154(literal) +msgid "\"486\", \"pentium\", \"pentium2\", \"pentiumpro\", \"coreduo\", \"n270\", \"pentiumpro\", \"qemu32\", \"kvm32\", \"cpu64-rhel5\", \"cpu64-rhel5\", \"kvm64\", \"pentiumpro\", \"Conroe\" \"Penryn\", \"Nehalem\", \"Westmere\", \"pentiumpro\", \"cpu64-rhel5\", \"cpu64-rhel5\", \"Opteron_G1\", \"Opteron_G2\", \"Opteron_G3\", \"Opteron_G4\"" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:158(para) +msgid "These models are defined in the file /usr/share/libvirt/cpu_map.xml. Check this file to determine which models are supported by your local installation." +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:161(para) +msgid "There are two Compute configuration options that determine the type of CPU model exposed to the hypervisor when using KVM, libvirt_cpu_mode and libvirt_cpu_model." +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:164(para) +msgid "The libvirt_cpu_mode option can take one of four values: none, host-passthrough, host-model and custom." +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:168(title) +msgid "Host model (default for KVM & QEMU)" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:169(para) +msgid "If your nova.conf contains libvirt_cpu_mode=host-model, libvirt will identify the CPU model in /usr/share/libvirt/cpu_map.xml which most closely matches the host, and then request additional CPU flags to complete the match. This should give close to maximum functionality/performance, which maintaining good reliability/compatibility if the guest is migrated to another host with slightly different host CPUs." +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:178(title) +msgid "Host passthrough" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:179(para) +msgid "If your nova.conf contains libvirt_cpu_mode=host-passthrough, libvirt will tell KVM to passthrough 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/src/docbkx/common/kvm.xml:188(title) +msgid "Custom" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:189(para) +msgid "If your nova.conf 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 should contain:" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:199(title) +msgid "None (default for all libvirt-driven hypervisors other than KVM & QEMU)" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:201(para) +msgid "If your nova.conf contains libvirt_cpu_mode=none, then libvirt will not specify any CPU model at all. It will leave it up to the hypervisor to choose the default model. This setting is equivalent to the Compute service behavior prior to the Folsom release." +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:208(title) ./doc/src/docbkx/common/ch_image_mgmt.xml:1180(emphasis) +msgid "Troubleshooting" +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:209(para) +msgid "Trying to launch a new virtual machine instance fails with the ERROR state, and the following error appears in /var/log/nova/nova-compute.log This is a symptom that the KVM kernel modules have not been loaded." +msgstr "" + +#: ./doc/src/docbkx/common/kvm.xml:215(para) +msgid "If you cannot start VMs after installation without rebooting, it's possible the permissions are not correct. This can happen if you load the KVM module before you've installed nova-compute. To check the permissions, run to see whether the group is set to kvm. If not, run ." +msgstr "" + +#: ./doc/src/docbkx/common/baremetal.xml:6(title) +msgid "Bare Metal Driver" +msgstr "" + +#: ./doc/src/docbkx/common/baremetal.xml:9(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 via Openstack's API, using pluggable sub-drivers to deliver machine imaging (PXE) and power control (IPMI). With this, provisioning and management of physical hardware is accomplished using common cloud APIs and tools, such as Heat 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/src/docbkx/common/baremetal.xml:24(para) +msgid "Some OpenStack Compute features are not implemented by the baremetal hypervisor driver. See the hypervisor support matrix for details." +msgstr "" + +#: ./doc/src/docbkx/common/baremetal.xml:30(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/src/docbkx/common/baremetal.xml:44(para) +msgid "There are many configuration options specific to the Baremetal driver. Also, some additional steps will be required, such as building the baremetal deploy ramdisk. See the main wiki page for details and implementation suggestions." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:8(title) +msgid "SSL and Keystone Configuration" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:9(para) +msgid "Keystone may be configured to support 2-way SSL out-of-the-box. The x509 certificates used by Keystone must be obtained externally and configured for use with Keystone as described in this section. However, a set of sample certficates is provided in the examples/pki/certs and examples/pki/private directories with the Keystone distribution for testing. Here is the description of each of them and their purpose:" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:19(title) +msgid "Types of certificates" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:22(term) +msgid "cacert.pem" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:26(para) +msgid "Certificate Authority chain to validate against." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:32(term) +msgid "ssl_cert.pem" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:36(para) +msgid "Public certificate for Keystone server." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:42(term) +msgid "middleware.pem" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:46(para) +msgid "Public and private certificate for Keystone middleware/client." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:53(term) +msgid "cakey.pem" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:57(para) +msgid "Private key for the CA." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:63(term) +msgid "ssl_key.pem" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:67(para) +msgid "Private key for the Keystone server." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:73(para) +msgid "Note that you may choose whatever names you want for these certificates, or combine the public/private keys in the same file if you wish. These certificates are just provided as an example." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:81(title) +msgid "SSL Configuration" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:82(para) +msgid "To enable SSL with client authentication, modify the etc/keystone.conf file accordingly under the [ssl] section. SSL configuration example using the included sample certificates:" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:97(para) +msgid "enable: True enables SSL. Defaults to False." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:103(para) +msgid "certfile: Path to Keystone public certificate file." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:109(para) +msgid "keyfile: Path to Keystone private certificate file. If the private key is included in the certfile, the keyfile maybe omitted." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:116(para) +msgid "ca_certs: Path to CA trust chain." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-ssl-config.xml:121(para) +msgid "cert_required: Requires client certificate. Defaults to False." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_floatingip.xml:8(title) +msgid "Manage Floating IP Addresses" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_floatingip.xml:9(para) +msgid "A floating IP address is an IP address (typically public) that can be dynamically assigned to an instance. Pools of floating IP addresses are created outside of python-novaclient with the commands. Refer to \"Configuring Public (Floating) IP Addresses\" in the OpenStack Compute Administration Manual for more information." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_floatingip.xml:18(para) +msgid "Before you begin, use to determine what floating IP pools are available. In this example, the only available pool is nova." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_floatingip.xml:30(title) +msgid "Reserve and associate floating IP addresses" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_floatingip.xml:31(para) +msgid "You can reserve floating IP addresses with the command. This command reserves the addresses for the tenant, but does not immediately associate that address with an instance. " +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_floatingip.xml:45(para) +msgid "The floating IP address has been reserved, and can now be associated with an instance with the command. For this example, we'll associate this IP address with an image called smallimage. After the command is complete, you can confirm that the IP address has been associated with the and commands. The first table shows that the 50.56.12.232 is now associated with the smallimage instance ID, and the second table shows the IP address included under smallimage's public IP addresses." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_floatingip.xml:76(title) +msgid "Remove and de-allocate a floating IP address" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_floatingip.xml:78(para) +msgid "To remove a floating IP address from an instance, use the command. After the command is complete, you can confirm that the IP address has been associated with the and commands. You can now de-allocate the floating IP address, returning it to the pool so that it can be used by another tenant. In this example, 50.56.12.232 was the only IP address allocated to this tenant. Running after the de-allocation is complete will return no results." +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:6(title) +msgid "Host aggregates" +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:8(title) ./doc/src/docbkx/common/compute-options.xml:8(title) ./doc/src/docbkx/common/trusted-compute-pools.xml:10(title) +msgid "Overview" +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:9(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 started out as a way to use Xen hypervisor resource pools, but has been generalized to 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 aggregate. This information can be used in the scheduler to enable advanced scheduling, to set up Xen hypervisor resources pools or to define logical groups for migration." +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:19(title) +msgid "Command-line interface" +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:25(para) +msgid "Print a list of all aggregates." +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:29(replaceable) ./doc/src/docbkx/common/host_aggregates.xml:79(replaceable) +msgid "<name>" +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:30(replaceable) +msgid "<availability-zone>" +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:32(para) +msgid "Create a new aggregate named <name> in availability zone <availability-zone>. Returns the ID of the newly created aggregate." +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:39(replaceable) ./doc/src/docbkx/common/host_aggregates.xml:46(replaceable) ./doc/src/docbkx/common/host_aggregates.xml:53(replaceable) ./doc/src/docbkx/common/host_aggregates.xml:61(replaceable) ./doc/src/docbkx/common/host_aggregates.xml:69(replaceable) ./doc/src/docbkx/common/host_aggregates.xml:78(replaceable) +msgid "<id>" +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:41(para) +msgid "Delete an aggregate with id <id>." +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:48(para) +msgid "Show details of the aggregate with id <id>." +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:54(replaceable) ./doc/src/docbkx/common/host_aggregates.xml:62(replaceable) +msgid "<host>" +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:56(para) +msgid "Add host with name <host> to aggregate with id <id>." +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:64(para) +msgid "Remove the host with name <host> from the aggregate with id <id>." +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:70(replaceable) ./doc/src/docbkx/common/host_aggregates.xml:71(replaceable) +msgid "<key=value>" +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:73(para) +msgid "Add or update metadata (key-value pairs) associated with the aggregate with id <id>." +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:80(replaceable) +msgid "<availability_zone>" +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:82(para) +msgid "Update the aggregate's name and optionally availability zone." +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:88(para) +msgid "List all hosts by service." +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:95(para) +msgid "Put/resume host into/from maintenance." +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:20(para) +msgid "The command-line tool supports the following aggregate-related commands. " +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:100(para) +msgid "These commands are only accessible to administrators. If the username and tenant you are using to access the Compute service do not have the admin role, or have not been explicitly granted the appropriate privileges, you will see one of the following errors when trying to use these commands:" +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:110(title) +msgid "Configure scheduler to support host aggregates" +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:111(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/src/docbkx/common/host_aggregates.xml:116(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/src/docbkx/common/host_aggregates.xml:126(title) +msgid "Example: specify compute hosts with SSDs" +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:127(para) +msgid "In this example, we configure the Compute service to allow users to request nodes that have solid-state drives (SSDs). We create a new host aggregate called fast-io in the availability zone called nova, we add the key-value pair ssd=true to the aggregate, and then we add compute nodes node1, and node2 to it." +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:157(para) +msgid "Next, we use the command to create a new flavor called ssd.large with an ID of 6, 8GB of RAM, 80GB root disk, and 4 vCPUs. " +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:166(para) +msgid "Once the flavor has been created, we specify one or more key-value pair that must match the key-value pairs on the host aggregates. In this case, there's only one key-value pair, ssd=true. Setting a key-value pair on a flavor is done using the command." +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:171(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/src/docbkx/common/host_aggregates.xml:190(para) +msgid "Now, when a user requests an instance with the ssd.large flavor, the scheduler will only consider hosts with the ssd=true key-value pair. In this example, that would only be node1 and node2." +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:196(title) +msgid "XenServer hypervisor pools to support live migration" +msgstr "" + +#: ./doc/src/docbkx/common/host_aggregates.xml:197(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. See Configuring Migrations for details on how to create these kinds of host aggregates to support live migration." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/common/getstart.xml:227(None) +msgid "@@image: 'figures/openstack-conceptual-arch-folsom.png'; md5=9b22f153302dea17875567db7ee98758" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/common/getstart.xml:284(None) +msgid "@@image: 'figures/openstack-logical-arch-folsom.png'; md5=bb9674b8194b6eb9b60edacc75dd9707" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/common/getstart.xml:325(None) +msgid "@@image: 'figures/horizon-screenshot.jpg'; md5=9471047adf0d93713be7f54b9db2b53c" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:6(title) +msgid "Getting Started with OpenStack" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:7(para) +msgid "OpenStack is a collection of open source technologies that provides massively scalable cloud computing software. OpenStack can be used by corporations, service providers, VARS, SMBs, researchers, and global data centers looking to deploy large-scale cloud deployments for private or public clouds." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:13(title) +msgid "Why Cloud?" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:14(para) +msgid "In data centers today, many computers suffer the same underutilization in computing power and networking bandwidth. For example, projects may need a large amount of computing capacity to complete a computation, but no longer need the computing power after completing the computation. You want cloud computing when you want a service that's available on-demand with the flexibility to bring it up or down through automation or with little intervention. The phrase \"cloud computing\" is often represented with a diagram that contains a cloud-like shape indicating a layer where responsibility for service goes from user to provider. The cloud in these types of diagrams contains the services that afford computing power harnessed to get work done. Much like the electrical power we receive each day, cloud computing provides subscribers or 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/src/docbkx/common/getstart.xml:31(para) +msgid "These are the compelling features of a cloud:" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:34(para) +msgid "On-demand self-service: Users can provision servers and networks with little human intervention." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:38(para) +msgid "Network access: Any computing capabilities are available over the network. Many different devices are allowed access through standardized mechanisms." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:43(para) +msgid "Resource pooling: Multiple users can access clouds that serve other consumers according to demand." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:47(para) +msgid "Elasticity: Provisioning is rapid and scales out or in based on need." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:51(para) +msgid "Metered or measured service: Just like utilities that are paid for by the hour, clouds should optimize resource use and control it for the level of service or type of servers such as storage or processing." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:57(para) +msgid "Cloud computing offers different service models depending on the capabilities a consumer may require." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:61(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/src/docbkx/common/getstart.xml:66(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/src/docbkx/common/getstart.xml:73(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/src/docbkx/common/getstart.xml:79(para) +msgid "When you hear terms such as public cloud or private cloud, these 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. The NIST also defines community cloud as shared by several organizations supporting a specific community with shared concerns." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:87(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/src/docbkx/common/getstart.xml:91(para) +msgid "What have people done with cloud computing? 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. People also use cloud computing 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/src/docbkx/common/getstart.xml:103(para) +msgid "For a more detailed discussion of cloud computing's essential characteristics and its models of service and deployment, see http://www.nist.gov/itl/cloud/, published by the US National Institute of Standards and Technology." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:112(title) +msgid "What is OpenStack?" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:113(para) +msgid "OpenStack is on a mission: to provide scalable, elastic cloud computing for both public and private clouds, large and small. At the heart of our mission is a pair of basic requirements: clouds must be simple to implement and massively scalable." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:118(para) +msgid "If you are new to OpenStack, you will undoubtedly have questions about installation, deployment, and usage. It can seem overwhelming at first. But don't fear, there are places to get information to guide you and to help resolve any issues you may run into during the on-ramp process. Because the project is so new and constantly changing, be aware of the revision time for all information. If you are reading a document that is a few months old and you feel that it isn't entirely accurate, then please let us know through the mailing list at https://launchpad.net/~openstack or by filing a bug at https://bugs.launchpad.net/openstack-manuals/+filebug so it can be updated or removed." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:134(title) +msgid "Components of OpenStack" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:135(para) +msgid "There are currently seven core components of OpenStack: Compute, Object Storage, Identity, Dashboard, Block Storage, Network and Image Service. Let's look at each in turn." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:140(para) +msgid "Object Store (codenamed \"Swift\") provides object storage. It allows you to store or retrieve files (but not mount directories like a fileserver). Several companies provide commercial storage services based on Swift. These include KT, Rackspace (from which Swift originated) and Internap. Swift is also used internally at many large companies to store their data." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:150(para) +msgid "Image (codenamed \"Glance\") provides a catalog and repository for virtual disk images. These disk images are mostly commonly used in OpenStack Compute. While this service is technically optional, any cloud of size will require it." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:157(para) +msgid "Compute (codenamed \"Nova\") provides virtual servers upon demand. Rackspace and HP provide commercial compute services built on Nova and it is used internally at companies like Mercado Libre and NASA (where it originated)." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:166(para) +msgid "Dashboard (codenamed \"Horizon\") provides a modular web-based user interface for all the OpenStack services. With this web GUI, you can perform most operations on your cloud like launching an instance, assigning IP addresses and setting access controls." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:174(para) +msgid "Identity (codenamed \"Keystone\") provides authentication and authorization for all the OpenStack services. It also provides a service catalog of services within a particular OpenStack cloud." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:182(para) +msgid "Network (codenamed \"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. Quantum has a pluggable architecture to support many popular networking vendors and technologies." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:193(para) +msgid "Block Storage (codenamed \"Cinder\") provides persistent block storage to guest VMs." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:199(para) +msgid "In addition to these core projects, there are also a number of \"incubation\" projects that are being considered for future integration into the OpenStack release." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:205(title) +msgid "Conceptual Architecture" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:207(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/src/docbkx/common/getstart.xml:219(para) +msgid "Conceptually, you can picture the relationships between the services as so:" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:234(para) +msgid "Dashboard (\"Horizon\") provides a web front end to the other OpenStack services" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:238(para) +msgid "Compute (\"Nova\") stores and retrieves virtual disks (\"images\") and associated metadata in Image (\"Glance\")" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:242(para) +msgid "Network (\"Quantum\") provides virtual networking for Compute." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:246(para) +msgid "Block Storage (\"Cinder\") provides storage volumes for Compute." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:250(para) +msgid "Image (\"Glance\") can store the actual virtual disk files in the Object Store(\"Swift\")" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:254(para) +msgid "All the services authenticate with Identity (\"Keystone\")" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:259(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/src/docbkx/common/getstart.xml:268(title) +msgid "Logical Architecture" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:270(para) +msgid "As you can imagine, the logical architecture is far more complicated than the conceptual architecture shown above. As with any service-oriented architecture, diagrams quickly become \"messy\" trying to illustrate all the possible combinations of service communications. The diagram below, illustrates the most common architecture of an OpenStack-based cloud. However, as OpenStack supports a wide variety of technologies, it does not represent the only architecture possible." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:289(para) +msgid "This picture is consistent with the conceptual architecture above in that:" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:294(para) +msgid "End users can interact through a common web interface (Horizon) or directly to each service through their API" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:299(para) +msgid "All services authenticate through a common source (facilitated through Keystone)" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:303(para) +msgid "Individual services interact with each other through their public APIs (except where privileged administrator commands are necessary)" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:310(para) +msgid "In the sections below, we'll delve into the architecture for each of the services." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:313(title) +msgid "Dashboard" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:315(para) +msgid "Horizon is a modular Django web application that provides an end user and administrator interface to OpenStack services." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:330(para) +msgid "As with most web applications, the architecture is fairly simple:" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:335(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/src/docbkx/common/getstart.xml:344(para) +msgid "A database (configurable as to which one). As it relies mostly on the other services for data, it stores very little data of its own." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:350(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/src/docbkx/common/getstart.xml:358(title) +msgid "Compute" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:360(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/src/docbkx/common/getstart.xml:367(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." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:376(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/src/docbkx/common/getstart.xml:387(para) +msgid "The nova-network worker daemon is very similar to nova-compute. 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." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:396(para) +msgid "The nova-schedule process is conceptually the simplest piece of code in OpenStack Nova: take 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/src/docbkx/common/getstart.xml:403(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/src/docbkx/common/getstart.xml:412(para) +msgid "The SQL database stores most of the build-time and run-time 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/src/docbkx/common/getstart.xml:422(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/src/docbkx/common/getstart.xml:430(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/src/docbkx/common/getstart.xml:437(title) +msgid "Object Store" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:439(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/src/docbkx/common/getstart.xml:445(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/src/docbkx/common/getstart.xml:455(para) +msgid "Account servers manage accounts defined with the object storage service." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:459(para) +msgid "Container servers manage a mapping of containers (i.e folders) within the object store service." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:463(para) +msgid "Object servers manage actual objects (i.e. files) on the storage nodes." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:467(para) +msgid "There are also a number of periodic process 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/src/docbkx/common/getstart.xml:476(para) +msgid "Authentication is handled through configurable WSGI middleware (which will usually be Keystone)." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:480(title) +msgid "Image Store" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:482(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/src/docbkx/common/getstart.xml:490(para) +msgid "glance-api accepts Image API calls for image discovery, image retrieval and image storage." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:494(para) +msgid "glance-registry stores, processes and retrieves metadata about images (size, type, etc.)." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:498(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/src/docbkx/common/getstart.xml:503(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/src/docbkx/common/getstart.xml:512(para) +msgid "There are also a number of periodic process 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/src/docbkx/common/getstart.xml:518(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/src/docbkx/common/getstart.xml:526(title) +msgid "Identity" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:528(para) +msgid "Keystone provides a single point of integration for OpenStack policy, catalog, token and authentication." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:533(para) +msgid "keystone handles API requests as well as providing configurable catalog, policy, token and identity services." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:538(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/src/docbkx/common/getstart.xml:545(para) +msgid "Most people will use this as a point of customization for their current authentication services." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:549(title) +msgid "Network" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:551(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/src/docbkx/common/getstart.xml:563(para) +msgid "quantum-server accepts API requests and then routes them to the appropriate quantum plugin for action." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:566(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, Open vSwitch, Linux bridging and the Ryu Network Operating System." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:567(para) +msgid "The common agents are L3 (layer 3), DHCP (dynamic host IP addressing) and the specific plug-in agent." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:570(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/src/docbkx/common/getstart.xml:573(para) +msgid "Quantum will interact mainly with Nova, where it will provide networks and connectivity for its instances." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:579(title) +msgid "Block Storage" +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:581(para) +msgid "Cinder separates out the persistent block storage functionality that was previously part of Openstack Compute 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/src/docbkx/common/getstart.xml:585(para) +msgid "cinder-api accepts API requests and routes them to cinder-volume for action." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:588(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/src/docbkx/common/getstart.xml:591(para) +msgid "Much like nova-scheduler, the cinder-scheduler daemon picks the optimal block storage provider node to create the volume on." +msgstr "" + +#: ./doc/src/docbkx/common/getstart.xml:594(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/src/docbkx/common/getstart.xml:597(para) +msgid "Like Quantum, Cinder will mainly interact with Nova, providing volumes for its instances." +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:8(title) +msgid "Adding images with glance image-create" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:9(para) +msgid "Use the command to add a new virtual machine image to glance, and use to modify properties of an image that has been updated. The image-create command takes several optional arguments, but you should specify a name for your image using the --name flag, as well as the disk format with --disk-format and container format with --container_format. Pass in the file via standard input or using the file command. For example:" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:17(replaceable) ./doc/src/docbkx/common/adding-images.xml:19(replaceable) +msgid "/path/to/file.img" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:16(para) +msgid " or " +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:22(title) +msgid "Image metadata" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:27(replaceable) +msgid "img-uuid" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:33(term) +msgid "architecture" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:43(literal) +msgid "alpha" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:47(link) +msgid "DEC 64-bit RISC" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:52(literal) +msgid "armv7l" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:56(link) +msgid "ARM Cortex-A7 MPCore" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:61(literal) +msgid "cris" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:65(link) +msgid "Ethernet, Token Ring, AXis - Code Reduced Instruction Set" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:70(literal) +msgid "i686" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:72(para) +msgid "Intel sixth-generation x86 (P6 microarchitecture)" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:80(literal) +msgid "ia64" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:84(link) +msgid "Itanium" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:89(literal) +msgid "lm32" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:93(link) +msgid "Lattice Micro32" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:98(literal) +msgid "m68k" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:102(link) +msgid "Motorola 68000" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:107(literal) +msgid "microblaze" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:111(link) +msgid "Xilinx 32-bit FPGA (Big Endian)" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:116(literal) +msgid "microblazeel" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:120(link) +msgid "Xilinx 32-bit FPGA (Little Endian)" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:125(literal) +msgid "mips" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:129(link) +msgid "MIPS 32-bit RISC (Big Endian)" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:134(literal) +msgid "mipsel" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:138(link) +msgid "MIPS 32-bit RISC (Little Endian)" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:143(literal) +msgid "mips64" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:147(link) +msgid "MIPS 64-bit RISC (Big Endian)" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:152(literal) +msgid "mips64el" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:156(link) +msgid "MIPS 64-bit RISC (Little Endian)" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:161(literal) +msgid "openrisc" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:165(link) +msgid "OpenCores RISC" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:170(literal) +msgid "parisc" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:174(link) +msgid "HP Precision Architecture RISC" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:179(literal) +msgid "parisc64" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:183(link) +msgid "HP Precision Architecture 64-bit RISC" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:188(literal) +msgid "ppc" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:192(link) +msgid "PowerPC 32-bit" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:197(literal) +msgid "ppc64" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:201(link) +msgid "PowerPC 64-bit" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:206(literal) +msgid "ppcemb" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:210(link) +msgid "PowerPC (Embedded 32-bit)" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:215(literal) +msgid "s390" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:219(link) +msgid "IBM Enterprise Systems Architecture/390" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:224(literal) +msgid "s390x" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:228(link) +msgid "S/390 64-bit" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:233(literal) +msgid "sh4" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:237(link) +msgid "SuperH SH-4 (Little Endian)" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:242(literal) +msgid "sh4eb" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:246(link) +msgid "SuperH SH-4 (Big Endian)" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:251(literal) +msgid "sparc" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:255(link) +msgid "Scalable Processor Architecture, 32-bit" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:260(literal) +msgid "sparc64" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:264(link) +msgid "Scalable Processor Architecture, 64-bit" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:269(literal) +msgid "unicore32" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:273(link) +msgid "Microprocessor Research and Development Center RISC Unicore32" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:279(literal) +msgid "x86_64" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:283(link) +msgid "64-bit extension of IA-32" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:288(literal) +msgid "xtensa" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:292(link) +msgid "Tensilica Xtensa configurable microprocessor core" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:297(literal) +msgid "xtensaeb" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:301(link) +msgid "Tensilica Xtensa configurable microprocessor core (Big Endian)" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:35(para) +msgid "The CPU architecture that must be supported by the hypervisor, e.g. x86_64, arm, 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/src/docbkx/common/adding-images.xml:311(term) +msgid "hypervisor_type" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:313(para) +msgid "The hypervisor type. Allowed values include: xen, qemu, kvm, lxc, uml, vmware, hyperv, powervm." +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:321(term) +msgid "vm_mode" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:327(literal) +msgid "hvm" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:329(para) +msgid "Fully virtualized. This is the mode used by QEMU and KVM." +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:334(literal) +msgid "xen" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:336(para) +msgid "Xen 3.0 paravirtualized." +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:340(literal) +msgid "uml" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:342(para) +msgid "User Mode Linux paravirtualized." +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:346(literal) +msgid "exe" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:348(para) +msgid "Executables in containers. This is the mode used by LXC." +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:323(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/src/docbkx/common/adding-images.xml:357(term) +msgid "auto_disk_config" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:359(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/src/docbkx/common/adding-images.xml:368(term) +msgid "os_type" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:370(para) +msgid "The operating system installed on the image, e.g. linux, 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 will create a FAT32-based swap partition instead of a Linux swap partition, and it will limit the injected hostname to less than 16 characters." +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:23(para) +msgid "You can associate metadata with an image using the --property key=value argument to or .For example: 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: The following metadata properties are specific to the XenAPI driver:" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:383(term) +msgid "vmware_adaptertype" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:385(para) +msgid "Indicates the virtual SCSI or IDE controller used by the hypervisor. Allowed values: lsiLogic, busLogic, ide" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:391(term) +msgid "vmware_ostype" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:393(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/src/docbkx/common/adding-images.xml:402(term) +msgid "vmware_image_version" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:404(para) +msgid "Currently unused, set it to 1." +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:380(para) +msgid "The following metadata properties are specific to the VMware API driver: " +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:414(term) +msgid "instance_uuid" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:416(para) +msgid "For snapshot images, this is the UUID of the server used to create this image." +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:422(term) +msgid "kernel_id" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:424(para) +msgid "The ID of image stored in Glance that should be used as the kernel when booting an AMI-style image." +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:431(term) +msgid "ramdisk_id" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:433(para) +msgid "The ID of image stored in Glance that should be used as the ramdisk when booting an AMI-style image." +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:440(term) +msgid "os_version" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:442(para) +msgid "The operating system version as specified by the distributor." +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:448(term) +msgid "os_distro" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:461(literal) +msgid "arch" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:463(para) +msgid "This is: Arch Linux" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:466(para) +msgid "Do not use: archlinux, or org.archlinux" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:474(literal) +msgid "centos" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:476(para) +msgid "This is: Community Enterprise Operating System" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:479(para) +msgid "Do not use: org.centosCentOS" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:487(literal) +msgid "debian" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:489(para) +msgid "This is: Debian" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:492(para) +msgid "Do not use: Debian, or org.debian" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:500(literal) +msgid "fedora" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:502(para) +msgid "This is: Fedora" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:505(para) +msgid "Do not use: Fedora, org.fedora, or org.fedoraproject" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:514(literal) +msgid "freebsd" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:516(para) +msgid "This is: FreeBSD" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:519(para) +msgid "Do not use: org.freebsd, freeBSD, or FreeBSD" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:528(literal) +msgid "gentoo" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:530(para) +msgid "This is: Gentoo Linux" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:533(para) +msgid "Do not use: Gentoo, or org.gentoo" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:541(literal) +msgid "mandrake" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:543(para) +msgid "This is: Mandrakelinux (MandrakeSoft)" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:546(para) +msgid "Do not use: mandrakelinux, or MandrakeLinux" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:554(literal) +msgid "mandriva" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:556(para) +msgid "This is: Mandriva Linux" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:559(para) +msgid "Do not use: mandrivalinux" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:566(literal) +msgid "mes" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:568(para) +msgid "This is: Mandriva Enterprise Server" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:571(para) +msgid "Do not use: mandrivaent, or mandrivaES" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:579(literal) +msgid "msdos" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:581(para) +msgid "This is: Microsoft Disc Operating System" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:584(para) +msgid "Do not use: ms-dos" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:591(literal) +msgid "netbsd" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:593(para) +msgid "This is: NetBSD" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:596(para) +msgid "Do not use: NetBSD, or org.netbsd" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:604(literal) +msgid "netware" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:606(para) +msgid "This is: Novell NetWare" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:609(para) +msgid "Do not use: novell, or NetWare" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:617(literal) +msgid "openbsd" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:619(para) +msgid "This is: OpenBSD" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:622(para) +msgid "Do not use: OpenBSD, or org.openbsd" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:630(literal) +msgid "opensolaris" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:632(para) +msgid "Do not use: OpenSolaris,or org.opensolaris" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:640(literal) +msgid "opensuse" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:642(para) +msgid "This is: openSUSE" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:645(para) +msgid "Do not use: suse, SuSE, or org.opensuse" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:654(literal) +msgid "rhel" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:656(para) +msgid "This is: Red Hat Enterprise Linux" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:659(para) +msgid "Do not use: redhat, RedHat, or com.redhat" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:668(literal) +msgid "sled" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:670(para) +msgid "This is: SUSE Linux Enterprise Desktop" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:673(para) +msgid "Do not use: com.suse" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:680(literal) ./doc/src/docbkx/common/nova_cli_usage_statistics.xml:54(replaceable) +msgid "ubuntu" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:682(para) +msgid "This is: Ubuntu" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:685(para) +msgid "Do not use: Ubuntu, com.ubuntu, org.ubuntu, or canonical" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:695(literal) +msgid "windows" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:697(para) +msgid "This is: Microsoft Windows" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:700(para) +msgid "Do not use: com.microsoft.server, or windoze" +msgstr "" + +#: ./doc/src/docbkx/common/adding-images.xml:450(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/src/docbkx/common/adding-images.xml:408(para) +msgid "In order 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 below. " +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:8(title) +msgid "Manage Security Groups" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:9(para) +msgid "A security group is a named collection of network access rules that can be used to limit the types of traffic that have access to instances. When you spawn an instance, you can assign it to one or more groups. For each security group, the associated rules permit you to manage the allowed traffic to instances within the group. Any incoming traffic which is not matched by a rule is denied by default. At any time, it is possible to add or remove rules within a security group. Rules are automatically enforced as soon as they are created." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:16(para) +msgid "Before you begin, use to view the available security groups (specify --all-tenants if you are a cloud administrator wanting to view all tenants' groups) . You can also view the rules for a security group with . 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/src/docbkx/common/nova_cli_secgroups.xml:38(title) +msgid "Add or delete a security group" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:39(para) +msgid "Security groups can be added with ." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:41(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/src/docbkx/common/nova_cli_secgroups.xml:66(para) +msgid "All the traffic originated by the instances (outbound traffic) is allowed" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:70(para) +msgid "All the traffic destined to instances (inbound traffic) is denied" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:74(para) +msgid "All the instances inside the group are allowed to talk to each other" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:79(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/src/docbkx/common/nova_cli_secgroups.xml:62(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/src/docbkx/common/nova_cli_secgroups.xml:83(para) +msgid "In the following example, the group secure1 is deleted. When you view the security group list, it no longer appears." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:100(title) +msgid "Modify security group rules" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:103(para) +msgid "It is not possible to change the default outbound behaviour." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:112(para) ./doc/src/docbkx/common/nova_cli_secgroups.xml:130(para) ./doc/src/docbkx/common/nova_cli_secgroups.xml:199(para) +msgid "<secgroup> ID of security group." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:115(para) ./doc/src/docbkx/common/nova_cli_secgroups.xml:202(para) +msgid "<ip_proto> IP protocol (icmp, tcp, udp)." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:118(para) ./doc/src/docbkx/common/nova_cli_secgroups.xml:205(para) +msgid "<from_port> Port at start of range." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:121(para) ./doc/src/docbkx/common/nova_cli_secgroups.xml:208(para) +msgid "<to_port> Port at end of range." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:124(para) ./doc/src/docbkx/common/nova_cli_secgroups.xml:211(para) +msgid "<cidr> CIDR for address range." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:101(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/src/docbkx/common/nova_cli_secgroups.xml:133(para) +msgid "<ip_proto> IP protocol (with icmp specified)." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:136(para) +msgid "<ICMP_code> The ICMP code." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:139(para) +msgid "<ICMP_type> The ICMP type." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:142(para) +msgid "<cidr> CIDR for the source address range." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:146(para) +msgid "Entering \"-1\" for both code and type indicates that all ICMP codes and types should be allowed." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:127(para) +msgid "For ICMP rules, instead of specifying a begin and end port, you specify the allowed ICMP code and ICMP type: " +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:153(title) +msgid "The CIDR notation" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:154(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/src/docbkx/common/nova_cli_secgroups.xml:164(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/src/docbkx/common/nova_cli_secgroups.xml:175(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/src/docbkx/common/nova_cli_secgroups.xml:196(para) +msgid "In order to delete a rule, you need to specify the exact same arguments you used to create it:" +msgstr "" + +#: ./doc/src/docbkx/common/monitoring.xml:5(title) ./doc/src/docbkx/common/ch_identity_mgmt.xml:215(title) +msgid "Monitoring" +msgstr "" + +#: ./doc/src/docbkx/common/monitoring.xml:8(title) +msgid "Different aspects of cloud monitoring" +msgstr "" + +#: ./doc/src/docbkx/common/monitoring.xml:9(para) +msgid "In cloud environments, we can identify three distinct areas for monitoring: 1. Cloud hardware and services: These are different hardware and software pieces of the cluster running on bare metal, including hypervisors and storage and controller nodes. The problem is well-known and a number of tools exist to deal with it. Some of most popular are Nagios, Ganglia, Cacti, and Zabbix. 2. User’s cloud ecosystem: This is everything that makes up a user’s cloud account. In case of OpenStack it is instances, persistent volumes, floating IPs, security groups, etc. For all these components, the user needs reliable and clear information on their status. This info generally should come from the internals of the cloud software. 3. Performance of cloud resources: This is the performance of tenants’ cloud infrastructures running on top of a given OpenStack installation. This specifically boils down to determining what prevents tenants’ resources from functioning properly and how these problematic resources affect other cloud resources." +msgstr "" + +#: ./doc/src/docbkx/common/monitoring.xml:25(title) +msgid "Monitoring the status of user's resources" +msgstr "" + +#: ./doc/src/docbkx/common/monitoring.xml:27(para) +msgid "When it comes to users, their primary expectation is usually about consistent feedback from OpenStack about their instance states. There is nothing more annoying than having an instance reported as “ACTIVE” by the dashboard, even though it’s been gone for several minutes. OpenStack tries to prevent such discrepancies by running several checks in a cron-like manner (they are called “periodic tasks” in OpenStack code) on each compute node. These checks are simply methods of the ComputeManager class located in compute/manager.py or directly in drivers for different hypervisors (some of these checks are available for certain hypervisors only), e.g. _check_instance_build_time, _cleanup_running_deleted_instances, _sync_power_states." +msgstr "" + +#: ./doc/src/docbkx/common/monitoring.xml:39(title) +msgid "Monitoring performance of cloud resources" +msgstr "" + +#: ./doc/src/docbkx/common/monitoring.xml:41(para) +msgid "While monitoring farms of physical servers is a standard task even on a large scale, monitoring virtual infrastructure (“cloud scale”) is much more daunting. Cloud introduces a lot of dynamic resources, which can behave unpredictably and move between different hardware components. So it is usually quite hard to tell which of the thousands of VMs has problems (without even having root access to it) and how the problem affects other resources. Standards like sFlow try to tackle this problem, by providing efficient monitoring for a high volume of events (based on probing) and determining relationships between different cloud resources." +msgstr "" + +#: ./doc/src/docbkx/common/monitoring.xml:49(para) +msgid "sFlow is worked on by a consortium of mainstream network device vendors, including ExtremeNetworks, HP, Hitachi, etc. Since it’s embedded in their devices, it provides a consistent way to monitor traffic across different networks. However, from the standpoint of a number of open source projects, It’s also built into OpenvSwitch virtual switch (which is a more robust alternative to a Linux bridge)." +msgstr "" + +#: ./doc/src/docbkx/common/monitoring.xml:55(para) +msgid "To provide end-to-end packet flow analysis, sFlow agents need to be deployed on all devices across the network. The agents simply collect sample data on network devices (including packet headers and forwarding/routing table state), and send them to the sFlow Collector. The collector gathers data samples from all the sFlow agents and produces meaningful statistics out of them, including traffic characteristics and network topology (how packets traverse the network between two endpoints)." +msgstr "" + +#: ./doc/src/docbkx/common/monitoring.xml:61(para) +msgid "While sFlow itself is defined as a standard to monitor networks, it also comes with a “host sFlow agent.” Per the website: \"The Host sFlow agent exports physical and virtual server performance metrics using the sFlow protocol. The agent provides scalable, multi-vendor, multi-OS performance monitoring with minimal impact on the systems being monitored.\"" +msgstr "" + +#: ./doc/src/docbkx/common/monitoring.xml:67(para) +msgid "sFlow agents are available for mainstream hypervisors, including Xen, KVM/libvirt, and Hyper-V (VMWare to be added soon) and can be installed on a number of operating systems (FreeBSD, Linux, Solaris, Windows) to monitor applications running on them. For the IaaS clouds based on these hypervisors, it means that it’s now possible to sample different metrics of an instance (including I/O, CPU, RAM, interrupts/sec etc.) without even logging into it. To make it even better, one can combine the “network” and “host” parts of sFlow data to provide a complex monitoring solution" +msgstr "" + +#: ./doc/src/docbkx/common/monitoring.xml:75(para) +msgid "With the advent of Quantum in the Folsom release, the virtual network device moved from Linux bridge to OpenvSwitch. If we add KVM or Xen to the mix, we will have sFlow as an applicable framework to monitor instances themselves and their virtual network topologies as well. There are a number of sFlow collectors available. The most widely used seem to be Ganglia and sFlowTrend, which are free. While Ganglia is focused mainly on monitoring the performance of clustered hosts or instance pools, sFlowTrend seems to be more robust, adding network metrics and topologies on top of that." +msgstr "" + +#: ./doc/src/docbkx/common/monitoring.xml:86(title) +msgid "Monitoring Openstack services" +msgstr "" + +#: ./doc/src/docbkx/common/monitoring.xml:88(para) +msgid "The table below shows which Nagios checks can be used to monitor different openstack services. ===================== ========================= Service Nagios check ===================== ========================= Database check_mysql/check_pgsql --------------------- ------------------------- RabbitMQ nagios rabbitmq plugin --------------------- ------------------------- libvirt check_libvirt --------------------- ------------------------- dnsmasq check_dhcp --------------------- ------------------------- nova-api check_http --------------------- ------------------------- nova-scheduler check_procs --------------------- ------------------------- nova-compute check_procs --------------------- ------------------------- nova-network check_procs --------------------- ------------------------- keystone-api check_http --------------------- ------------------------- glance-api check_http --------------------- ------------------------- glance-registry check_http --------------------- ------------------------- server availability check_ping ===================== =========================" +msgstr "" + +#: ./doc/src/docbkx/common/qemu.xml:7(title) +msgid "QEMU" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/qemu.xml:15(para) +msgid "Running on older hardware that lacks virtualization support." +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/qemu.xml:13(para) +msgid "The typical uses cases for QEMU are" +msgstr "" + +#: ./doc/src/docbkx/common/qemu.xml:25(para) +msgid "KVM requires hardware support for acceleration. If hardware support is not available (e.g., if you are running Compute inside of a VM and the hypervisor does not expose the required hardware support), you can use QEMU instead. KVM and QEMU have the same level of support in OpenStack, but KVM will provide better performance. To enable QEMU:" +msgstr "" + +#: ./doc/src/docbkx/common/qemu.xml:31(para) +msgid "For some operations you may also have to install the utility:" +msgstr "" + +#: ./doc/src/docbkx/common/qemu.xml:39(para) +msgid "The QEMU hypervisor supports the following virtual machine image formats:" +msgstr "" + +#: ./doc/src/docbkx/common/qemu.xml:51(title) +msgid "Tips and fixes for QEMU on RHEL" +msgstr "" + +#: ./doc/src/docbkx/common/qemu.xml:52(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 2 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/src/docbkx/common/qemu.xml:62(para) +msgid "The second command, , may take a while." +msgstr "" + +#: ./doc/src/docbkx/common/colocating-services.xml:7(title) +msgid "Co-locating services" +msgstr "" + +#: ./doc/src/docbkx/common/colocating-services.xml:8(para) +msgid "While in a best-practice deployment, each OpenStack project's services would live on a different machine, this is not always practical. For example, in small deployments there might be too few machines available, or a limited number of public IP addresses. Components from different OpenStack projects are not necessarily engineered to be able to be co-located, however many users report success with a variety of deployment scenarios." +msgstr "" + +#: ./doc/src/docbkx/common/colocating-services.xml:21(para) +msgid "Ensure dependencies aren't in conflict. The OpenStack Continuous Integration team does attempt to ensure there is no conflict - so if you see issues during package installation, consider filing a bug." +msgstr "" + +#: ./doc/src/docbkx/common/colocating-services.xml:25(para) +msgid "Monitor your systems and ensure they are not overloaded. Some parts of OpenStack use a lot of CPU time (eg Swift Proxy Servers), while others are IO focused (eg Swift Object Server). Try to balance these so they complement each other." +msgstr "" + +#: ./doc/src/docbkx/common/colocating-services.xml:30(para) +msgid "Beware of security. Different parts of OpenStack assume different security models. For example, Swift assumes the storage nodes will be on a private network and does not provide additional security between nodes in the cluster." +msgstr "" + +#: ./doc/src/docbkx/common/colocating-services.xml:34(para) +msgid "Ensure the ports you are running the services on don't conflict. Most ports used by OpenStack are configurable." +msgstr "" + +#: ./doc/src/docbkx/common/colocating-services.xml:16(para) +msgid "The following is a series of pointers to be used when co-location of services from different OpenStack projects on the same machine is a must: " +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:8(title) +msgid "Certificates for PKI" +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:9(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 Keystone configuration file as specified in the above section. Additionally, the private key should only be readable by the system user that will run Keystone. The values that specify where to read the certificates are under the [signing] section of the configuration file. The configuration values are:" +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:26(para) +msgid "token_format - Determines the algorithm used to generate tokens. Can be either UUID or PKI. Defaults to PKI." +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:33(para) +msgid "certfile - Location of certificate used to verify tokens. Default is /etc/keystone/ssl/certs/signing_cert.pem." +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:39(para) +msgid "keyfile - Location of private key used to sign tokens. Default is /etc/keystone/ssl/private/signing_key.pem." +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:45(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/src/docbkx/common/certificates-for-pki.xml:52(para) +msgid "key_size - Default is 1024." +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:57(para) +msgid "valid_days - Default is 3650." +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:62(para) +msgid "ca_password - Password required to read the ca_file. Default is None." +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:69(title) +msgid "Signing Certificate Issued by External CA" +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:70(para) +msgid "You may 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/src/docbkx/common/certificates-for-pki.xml:77(para) +msgid "all certificate and key files must be in Privacy Enhanced Mail (PEM) format" +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:83(para) +msgid "private key files must not be protected by a password" +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:88(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/src/docbkx/common/certificates-for-pki.xml:94(para) +msgid "The basic workflow for using a signing certificate issued by an external CA involves:" +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:98(para) ./doc/src/docbkx/common/certificates-for-pki.xml:110(title) +msgid "Request Signing Certificate from External CA" +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:101(para) +msgid "Convert certificate and private key to PEM if needed" +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:105(para) ./doc/src/docbkx/common/certificates-for-pki.xml:160(title) +msgid "Install External Signing Certificate" +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:111(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/src/docbkx/common/certificates-for-pki.xml:116(para) +msgid "First create a certificate request configuration file (e.g. cert_req.conf):" +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:138(para) +msgid "Then generate a CRS with OpenSSL CLI. Do not encrypt the generated private key. Must use the -nodes option." +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:143(para) +msgid "For example:" +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:149(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/src/docbkx/common/certificates-for-pki.xml:161(para) +msgid "Assuming you have the following already:" +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:166(para) +msgid "signing_cert.pem - (Keystone token) signing certificate in PEM format" +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:172(para) +msgid "signing_key.pem - corresponding (non-encrypted) private key in PEM format" +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:178(para) +msgid "cacert.pem - trust CA certificate chain in PEM format" +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:184(para) +msgid "Copy the above to your certificate directory. For example:" +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:194(para) +msgid "Make sure the certificate directory is only accessible by root." +msgstr "" + +#: ./doc/src/docbkx/common/certificates-for-pki.xml:197(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/src/docbkx/common/support.xml:6(title) +msgid "Support" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:7(para) +msgid "Online resources aid in supporting OpenStack and the community members are willing and able to 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. Here are some ideas for supporting OpenStack and troubleshooting your existing installations." +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:9(title) +msgid "Community Support" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:9(para) +msgid "Here are some places you can locate others who want to help." +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:10(title) +msgid "The Launchpad Answers area" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:11(para) +msgid "During setup or testing, you may have questions about how to do something, or end up in a situation where you can't seem to get a feature to work correctly. One place to look for help is the Answers section on Launchpad. Launchpad is the \"home\" for the project code and its developers and thus is a natural place to ask about the project. When visiting the Answers section, it is usually good to at least scan over recently asked questions to see if your question has already been answered. If that is not the case, then proceed to adding a new question. Be sure you 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, link to screenshots, and so on. The Launchpad Answers areas are available here:" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:22(para) +msgid "OpenStack Compute: https://answers.launchpad.net/nova" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:25(para) +msgid "OpenStack Object Storage: https://answers.launchpad.net/swift" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:28(para) +msgid "OpenStack Image Delivery and Registration: https://answers.launchpad.net/glance" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:31(para) +msgid "OpenStack Identity: https://answers.launchpad.net/keystone" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:34(para) +msgid "OpenStack Dashboard: https://answers.launchpad.net/horizon" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:37(para) +msgid "OpenStack Network Connectivity: https://answers.launchpad.net/quantum" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:42(title) +msgid "OpenStack mailing list" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:43(para) +msgid "Posting your question or scenario to the OpenStack mailing list is a great way to get answers and insights. You can learn from and help others who may have the same scenario as you. Go to https://launchpad.net/~openstack and click \"Subscribe to mailing list\" or view the archives at https://lists.launchpad.net/openstack/. You may be interested in the other mailing lists for specific projects or development - these can be found on the wiki." +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:51(title) +msgid "The OpenStack Wiki search" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:52(para) +msgid "The OpenStack wiki contains content on a broad range of topics, but some of it sits a bit below the surface. Fortunately, the wiki search feature is very powerful in that it can do both searches by title and by content. If you are searching for specific information, say about \"networking\" or \"api\" for nova, you can find lots of content using the search feature. More is being added all the time, so be sure to check back often. You can find the search box in the upper right hand corner of any OpenStack wiki page." +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:59(title) +msgid "The Launchpad Bugs area" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:60(para) +msgid "So you think you've found a bug. That's great! Seriously, it is. The OpenStack community values your setup and testing efforts and wants your feedback. To log a bug you must have a Launchpad account, so sign up at https://launchpad.net/+login if you do not already have a Launchpad ID. You can view existing bugs and report your bug in the Launchpad Bugs area. It is suggested that you first use the search facility to see if the bug you found has already been reported (or even better, already fixed). If it still seems like your bug is new or unreported then it is time to fill out a bug report." +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:68(para) +msgid "Some tips:" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:69(para) +msgid "Give a clear, concise summary!" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:70(para) +msgid "Provide as much detail as possible in the description. Paste in your command output or stack traces, link to screenshots, etc." +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:73(para) +msgid "Be sure to include what version of the software you are using. This is especially critical if you are using a development branch eg. \"Folsom release\" vs git commit bc79c3ecc55929bac585d04a03475b72e06a3208." +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:76(para) +msgid "Any deployment specific info is helpful as well. eg. Ubuntu 12.04, multi-node install." +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:79(para) +msgid "The Launchpad Bugs areas are available here - OpenStack Compute:" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:82(para) +msgid "OpenStack Compute: https://bugs.launchpad.net/nova" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:85(para) +msgid "OpenStack Object Storage: https://bugs.launchpad.net/swift" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:88(para) +msgid "OpenStack Image Delivery and Registration: https://bugs.launchpad.net/glance" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:91(para) +msgid "OpenStack Identity: https://bugs.launchpad.net/keystone" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:94(para) +msgid "OpenStack Dashboard: https://bugs.launchpad.net/horizon" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:97(para) +msgid "OpenStack Network Connectivity: https://bugs.launchpad.net/quantum" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:103(title) +msgid "The OpenStack IRC channel" +msgstr "" + +#: ./doc/src/docbkx/common/support.xml:104(para) +msgid "The OpenStack community lives and breathes in the #openstack IRC channel on the Freenode network. You can come by to hang out, ask questions, or get immediate feedback for urgent and pressing issues. To get into the IRC channel you need to install an IRC client or use a browser-based client by going to http://webchat.freenode.net/. You can also use Colloquy (Mac OS X, http://colloquy.info/) or 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 then paste into the channel. The OpenStack IRC channel is: #openstack on irc.freenode.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/src/docbkx/common/keystone-concepts.xml:177(None) ./doc/src/docbkx/common/keystone-concepts.xml:182(None) +msgid "@@image: 'figures/SCH_5002_V00_NUAC-Keystone.png'; md5=9b963136b10282119cfad907dcfc1e7b" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:7(title) +msgid "Basic Concepts" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:8(para) +msgid "The Identity service has two primary functions:" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:13(para) +msgid "User management: keep track of users and what they are permitted to do" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:19(para) +msgid "Service catalog: Provide a catalog of what services are available and where their API endpoints are located" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:25(para) +msgid "The Identity Service has several definitions which are important to understand." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:31(term) +msgid "User" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:33(para) +msgid "A 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/src/docbkx/common/keystone-concepts.xml:45(term) +msgid "Credentials" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:47(para) +msgid "Data that belongs to, is owned by, and generally only known by a user that the user can present to prove they are who they are (since nobody else should know that data)." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:52(para) +msgid "Examples are:" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:57(para) +msgid "a matching username and password" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:62(para) +msgid "a matching username and API key" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:67(para) +msgid "yourself and a driver's license with a picture of you" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:73(para) +msgid "a token that was issued to you that nobody else knows of" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:82(term) +msgid "Authentication" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:84(para) +msgid "In the context of the identity service, authentication is the act of confirming the identity of a user or the truth of a claim. The identity service will confirm that incoming request are being made by the user who claims to be making the call by validating a set of claims that the user is making. These claims are initially in the form of a set of credentials (username & password, or username and API key). After initial confirmation, the identity service will issue the user a token which the user can then provide to demonstrate that their identity has been authenticated when making subsequent requests." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:100(term) +msgid "Token" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:102(para) +msgid "A token is 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/src/docbkx/common/keystone-concepts.xml:108(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 a aspire to be a full-fledged identity store and management solution." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:119(term) +msgid "Tenant" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:121(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/src/docbkx/common/keystone-concepts.xml:130(term) +msgid "Service" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:132(para) +msgid "An OpenStack service, such as Compute (Nova), Object Storage (Swift), or Image Service (Glance). A service provides one or more endpoints through which users can access resources and perform (presumably useful) operations." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:142(term) +msgid "Endpoint" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:144(para) +msgid "An network-accessible address, usually described by URL, where a service may be accessed. 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/src/docbkx/common/keystone-concepts.xml:154(term) +msgid "Role" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:156(para) +msgid "A personality that a user assumes when performing a specific set of operations. A role includes a set of right and privileges. A user assuming that role inherits those rights and privileges." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:162(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 roles grants access to." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:187(title) +msgid "User management" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:192(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:522(title) +msgid "Users" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:195(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:422(title) +msgid "Tenants" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:198(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:693(title) +msgid "Roles" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:188(para) +msgid "The three main concepts of Identity user management are: " +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:202(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/src/docbkx/common/keystone-concepts.xml:208(para) +msgid "A tenant can be thought of as 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 will receive a list of all of the running instances in the tenant you specified in your query. This example creates a tenant named \"acme\":" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:218(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/src/docbkx/common/keystone-concepts.xml:227(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/src/docbkx/common/keystone-concepts.xml:234(para) +msgid "It is up to individual services such as the Compute service and Image service to assign meaning to these roles. As far as the Identity service is concerned, a role is simply a name." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:240(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/src/docbkx/common/keystone-concepts.xml:272(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/src/docbkx/common/keystone-concepts.xml:278(para) +msgid "The /etc/[SERVICE_CODENAME]/policy.json 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/src/docbkx/common/keystone-concepts.xml:289(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/src/docbkx/common/keystone-concepts.xml:296(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/src/docbkx/common/keystone-concepts.xml:302(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/src/docbkx/common/keystone-concepts.xml:312(para) +msgid "If we wished to restrict creation of volumes to users who had the compute-user role in a particular tenant, we would add \"role:compute-user\", like so:" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:320(para) +msgid "If we wished to restrict all Compute service requests to require this role, the resulting file would look like:" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:427(title) +msgid "Service management" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:428(para) +msgid "The two main concepts of Identity service management are:" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:433(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:818(title) +msgid "Services" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:436(para) +msgid "Endpoints" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:439(para) +msgid "The Identity service also maintains a user that corresponds to each service (e.g., a user named nova, for the Compute service) and a special service tenant, which is called service." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-concepts.xml:445(para) +msgid "The commands for creating services and endpoints are described in a later section." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-external-auth.xml:5(title) +msgid "Using External Authentication with OpenStack Identity" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-external-auth.xml:6(para) +msgid "When Keystone is executed in apache-httpd it is possible to use external authentication methods different from the authentication provided by the identity store backend. For example, this makes possible to use a SQL identity backend together with X.509 authentication, Kerberos, etc. instead of using the username/password combination." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-external-auth.xml:14(title) +msgid "Using HTTPD authentication" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-external-auth.xml:15(para) +msgid "Webservers like Apache HTTP support many methods of authentication. Keystone can profit from this feature and let the authentication be done in the webserver, that will pass down the authenticated user to Keystone using the REMOTE_USER environment variable. This user must exist in advance in the identity backend so as to get a token from the controller. To use this method, OpenStack Identity should be running on apache-httpd." +msgstr "" + +#: ./doc/src/docbkx/common/keystone-external-auth.xml:26(title) +msgid "Using X.509" +msgstr "" + +#: ./doc/src/docbkx/common/keystone-external-auth.xml:27(para) +msgid "The following snippet for the Apache conf will authenticate the user based on a valid X.509 certificate from a known CA: " +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_metadata.xml:8(title) +msgid "Insert metadata during launch" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_metadata.xml:9(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/src/docbkx/common/nova_cli_metadata.xml:18(para) +msgid "When viewing the server information, you can see the metadata included on the metadata line: " +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_startstop.xml:8(title) +msgid "Stop and Start an Instance" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_startstop.xml:11(para) ./doc/src/docbkx/common/nova_cli_startstop.xml:12(para) +msgid " / " +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_startstop.xml:9(para) +msgid "There are two methods for stopping and starting an instance: " +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_startstop.xml:15(title) +msgid "Pause and Unpause" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_startstop.xml:16(para) +msgid " stores the state of the VM in RAM. A paused instance continues to run, albeit in a \"frozen\" state." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_startstop.xml:21(title) +msgid "Suspend and Resume" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_startstop.xml:22(para) +msgid " initiates a hypervisor-level suspend operation. Suspending an instance stores the state of the VM on disk; all memory is written to disk and the virtual machine is stopped. Suspending an instance is thus similar to placing a device in hibernation, and makes memory and vCPUs available. Administrators may want to suspend an instance for system maintenance, or if the instance is not frequently used." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_resizerebuild.xml:8(title) +msgid "Change Server Configuration" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_resizerebuild.xml:9(para) +msgid "After you have created a server, you may need to increase its size, change the image used to build it, or perform other configuration changes." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_resizerebuild.xml:13(title) +msgid "Commands Used" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_resizerebuild.xml:14(para) +msgid "This process uses the following commands: " +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_resizerebuild.xml:23(title) +msgid "Increase or Decrease Server Size" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_resizerebuild.xml:24(para) +msgid "Server size is changed by applying a different flavor to the server. Before you begin, use nova flavor-list to review the flavors available to you." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_resizerebuild.xml:40(para) +msgid "In this example, we'll take a server originally configured with the m1.tiny flavor and resize it to m1.small." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_resizerebuild.xml:70(para) +msgid "Use the resize command with the server's ID (6beefcf7-9de6-48b3-9ba9-e11b343189b3) and the ID of the desired flavor (2):" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_resizerebuild.xml:74(para) +msgid "While the server is rebuilding, its status will be displayed as RESIZING." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_resizerebuild.xml:83(para) +msgid "When the resize operation is completed, the status displayed is VERIFY_RESIZE. This prompts the user to verify that the operation has been successful; to confirm:" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_resizerebuild.xml:88(para) +msgid "However, if the operation has not worked as expected, you can revert it by doing:" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_resizerebuild.xml:92(para) +msgid "In both cases, the server status should go back to ACTIVE." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_volumes.xml:8(title) +msgid "Manage Volumes" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_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/src/docbkx/common/nova_cli_terminate.xml:8(title) +msgid "Terminate an Instance" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_terminate.xml:9(para) +msgid "When you no longer need an instance, use the command to terminate it. You can use the instance name or the ID string. You will not receive a notification indicating that the instance has been deleted, but if you run the command, the instance will no longer appear in the list." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_terminate.xml:15(para) +msgid "In this example, we will delete the instance tinyimage, which is experiencing an error condition." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:6(title) +msgid "OpenStack Dashboard Session Storage" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:7(para) +msgid "Horizon uses Django’s sessions framework for handling user session data; however that’s not the end of the story. There are numerous session backends available, which are controlled through the SESSION_ENGINE setting in your local_settings.py file. What follows is a quick discussion of the pros and cons of each of the common options as they pertain to deploying Horizon specifically." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:16(title) +msgid "Local Memory Cache" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:17(para) +msgid "Local memory storage is the quickest and easiest session backend to set up, as it has no external dependencies whatsoever. However, it has two significant drawbacks:" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:21(para) +msgid "No shared storage across processes or workers." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:22(para) +msgid "No persistence after a process terminates." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:24(para) +msgid "The local memory backend 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/src/docbkx/common/dashboard_sessions.xml:36(title) +msgid "Memcached" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:37(para) +msgid "External caching using an application such as memcached offers persistence and shared storage, and can be very useful for small-scale deployment and/or development. However, for distributed and high-availability scenarios memcached has inherent problems which are beyond the scope of this documentation." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:42(para) +msgid "Memcached is an extremely fast and efficient cache backend for cases where it fits the deployment need, but it’s not appropriate for all scenarios." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:45(para) +msgid "Requirements:" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:47(para) +msgid "Memcached service running and accessible." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:48(para) +msgid "Python memcached module installed." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:50(para) +msgid "Enabled by:" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:60(title) +msgid "Database" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:61(para) +msgid "Database-backed sessions are scalable (using an appropriate database strategy), persistent, and can be made high-concurrency and highly-available." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:65(para) +msgid "The downside to this approach is that 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. To enable, follow the below steps to initialise the database and configure it for use" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:72(para) +msgid "Start the mysql command line client by running:" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:74(para) +msgid "Enter the MySQL root user's password when prompted." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:75(para) +msgid "To configure the MySQL database, create the dash database." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:77(para) +msgid "Create a MySQL user for the newly-created dash database that has full control of the database." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:81(para) +msgid "Enter quit at the mysql> prompt to exit MySQL." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:83(para) +msgid "In the /etc/openstack-dashboard/local_settings.py file, change these options:" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:100(para) +msgid "After configuring the local_settings.py as shown, you can run the command to populate this newly-created database." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:104(para) +msgid "As a result, you should see the following at the end of what returns:" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:109(para) +msgid "If you want to avoid a warning when restarting apache2, create a blackhole directory in the dashboard directory like so:" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:111(para) +msgid "Restart Apache to pick up the default site and symbolic link settings." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:114(para) +msgid "Restart the nova-api service to ensure the API server can connect to the Dashboard and to avoid an error displayed in the Dashboard." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:120(title) +msgid "Cached Database" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:121(para) +msgid "To mitigate the performance issues of database queries, you can also consider using Django’s cached_db session backend which utilizes both your database and caching infrastructure to perform write-through caching and efficient retrieval. You can enable this hybrid setting by configuring both your database and cache as discussed above and then using:" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:133(title) +msgid "Cookies" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:134(para) +msgid "If you’re using Django 1.4 or later, a new session backend is available to you which avoids server load and scaling problems: the signed_cookies backend!" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:137(para) +msgid "This backend stores session data in a cookie which is stored by the user’s browser. The backend 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/src/docbkx/common/dashboard_sessions.xml:142(para) +msgid "The pros of this session engine are that it doesn’t require any 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/src/docbkx/common/dashboard_sessions.xml:146(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 which can be stored." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_sessions.xml:149(para) +msgid "For a thorough discussion of the security implications of this session backend, please read the Django documentation on cookie-based sessions." +msgstr "" + +#: ./doc/src/docbkx/common/tenant-specific-image-storage.xml:6(title) +msgid "Configuring Tenant-specific Storage Locations for Images with Object Storage" +msgstr "" + +#: ./doc/src/docbkx/common/tenant-specific-image-storage.xml:8(para) +msgid "For some deployers, storing all images in a single place for all tenants and users to access is not ideal. To enable access control to specific images for cloud users, you can configure the Image service with the ability to store image data in the image owner-specific locations." +msgstr "" + +#: ./doc/src/docbkx/common/tenant-specific-image-storage.xml:13(para) +msgid "These are the relevant configuration options in the glance-api.conf file:" +msgstr "" + +#: ./doc/src/docbkx/common/tenant-specific-image-storage.xml:17(para) +msgid "swift_store_multi_tenant: this must be set to 'True' to enable tenant-specific storage locations (it defaults to 'False')." +msgstr "" + +#: ./doc/src/docbkx/common/tenant-specific-image-storage.xml:22(para) +msgid "swift_store_admin_tenants: this is a list of tenants, referenced by id, that should be granted read and write access to all Object Storage containers created by the Image service." +msgstr "" + +#: ./doc/src/docbkx/common/tenant-specific-image-storage.xml:28(para) +msgid "Assuming you configured 'swift' as your default_store in glance-api.conf and you enable this feature as described above, images will be stored in an Object Storage service (swift) endpoint pulled from the authenticated user's service_catalog. The created image data will only be accessible through the Image service by the tenant that owns it and any tenants defined in swift_store_admin_tenants that are identified as having admin-level accounts." +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:6(title) +msgid "File format for nova.conf" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:9(para) +msgid "The Compute service supports a large number of configuration options. These options are specified in a configuration file whose default location in /etc/nova/nova.conf." +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:12(para) +msgid "The configuration file is in INI file format, with options specified as key=value pairs, grouped into sections. Almost all of the configuration options are in the DEFAULT section. Here's a brief example:" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:25(title) +msgid "Types of configuration options" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:29(term) +msgid "BoolOpt" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:31(para) +msgid "Boolean option. Value must be either true or false . Example:" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:37(term) +msgid "StrOpt" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:39(para) +msgid "String option. Value is an arbitrary string. Example:" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:44(term) +msgid "IntOption" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:46(para) +msgid "Integer option. Value must be an integer. Example: " +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:51(term) +msgid "MultiStrOpt" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:53(para) +msgid "String option. Same as StrOpt, except that it can be declared multiple times to indicate multiple values. Example:" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:60(term) +msgid "ListOpt" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:62(para) +msgid "List option. Value is a list of arbitrary strings separated by commas. Example:" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:67(term) +msgid "FloatOpt" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:69(para) +msgid "Floating-point option. Value must be a floating-point number. Example:" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:26(para) +msgid "Each configuration option has an associated type that indicates what values can be set. The supported option types are as follows:" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:77(para) +msgid "Nova options should not be quoted." +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:82(title) +msgid "Sections" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:86(literal) +msgid "[DEFAULT]" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:88(para) +msgid "Almost all of the configuration options are organized into this section. If the documentation for a configuration option does not specify its section, assume that it should be placed in this one." +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:94(literal) +msgid "[cells]" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:96(para) +msgid "The cells section is used for options for configuring cells functionality. See the Cells section for more details." +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:102(literal) +msgid "[baremetal]" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:104(para) +msgid "This section is used for options that relate to the baremetal hypervisor driver." +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:109(literal) +msgid "[conductor]" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:111(para) +msgid "The conductor section is used for options for configuring the nova-conductor service." +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:116(literal) +msgid "[trusted_computing]" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:118(para) +msgid "The trusted_computing section is used for options that relate to the trusted computing pools functionality. Options in this section describe how to connect to a remote attestation service." +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:83(para) +msgid "Configuration options are grouped by section. The Compute config file supports the following sections." +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:127(title) +msgid "Variable substition" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:128(para) +msgid "The configuration file supports variable substitution. Once a configuration option is set, it can be referenced in later configuration values when preceded by $. Consider the following example where my_ip is defined and then $my_ip is used as a variable." +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:135(para) +msgid "If you need a value to contain the $ symbol, escape it by doing $$. For example, if your LDAP DNS password was $xkj432, you would do:" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:139(para) +msgid "The Compute code uses Python's string.Template.safe_substitute() method to implement variable substitution. For more details on how variable substitution is resolved, see Python documentation on template strings and PEP 292." +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:147(title) +msgid "Whitespace" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:148(para) +msgid "To include whitespace in a configuration value, use a quoted string. For example:" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:152(title) +msgid "Specifying an alternate location for nova.conf" +msgstr "" + +#: ./doc/src/docbkx/common/compute-options.xml:153(para) +msgid "The configuration file is loaded by all of the nova-* services, as well as the command-line tool. To specify an alternate location for the configuration file, pass the --config-file /path/to/nova.conf argument when starting a nova-* service or calling ." +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:6(title) +msgid "Hyper-V Virtualization Platform" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:15(emphasis) +msgid "Windows Server 2008r2" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:20(emphasis) +msgid "Windows Server 2012" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:21(para) +msgid "Server and Core (with the Hyper-V role enabled), and Hyper-V Server" +msgstr "" + +#: ./doc/src/docbkx/common/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 32bit 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/src/docbkx/common/hyper-v.xml:26(title) +msgid "Hyper-V Configuration" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:30(emphasis) +msgid "Local Storage Considerations" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:37(title) +msgid "Configure NTP" +msgstr "" + +#: ./doc/src/docbkx/common/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 will need to run the following commands" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:52(title) +msgid "Configuring Hyper-V Virtual Switching" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:67(title) +msgid "Enable iSCSI Initiator Service" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:68(para) +msgid "To prepare the Hyper-V node to be able to attach to volumes provided by nova-volume or cinder you must first make sure the Windows iSCSI initiator service is running and started automatically." +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:79(title) +msgid "Configuring Shared Nothing Live Migration" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:83(para) +msgid "The following outlines the steps of shared nothing live migration." +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:86(para) +msgid "The target hosts ensures that live migration is enabled and properly configured in Hyper-V." +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:94(para) +msgid "The source hosts ensures that live migration is enabled and properly configured in Hyper-V." +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:98(para) +msgid "The source hosts initiates a Hyper-V live migration." +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:101(para) +msgid "The source hosts communicates to the manager the outcome of the operation." +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:109(literal) +msgid "instances_shared_storage=False" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:114(literal) +msgid "limit_cpu_features=True" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:121(literal) +msgid "instances_path=DRIVELETTER:\\PATH\\TO\\YOUR\\INSTANCES" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:125(para) +msgid "Additional Requirements:" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:128(para) +msgid "Hyper-V 2012 RC or Windows Server 2012 RC with Hyper-V role enabled" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:131(para) +msgid "A Windows domain controller with the Hyper-V compute nodes as domain members" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:135(para) +msgid "The instances_path command line option/flag needs to be the same on all hosts" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:145(emphasis) +msgid "How to setup live migration on Hyper-V" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:152(replaceable) ./doc/src/docbkx/common/hyper-v.xml:338(replaceable) ./doc/src/docbkx/common/hyper-v.xml:339(replaceable) ./doc/src/docbkx/common/hyper-v.xml:341(replaceable) +msgid "IP_ADDRESS" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:161(emphasis) +msgid "Additional Reading" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:162(para) +msgid "Here's an article that clarifies the various live migration options in Hyper-V:" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:166(link) +msgid "http://ariessysadmin.blogspot.ro/2012/04/hyper-v-live-migration-of-windows.html" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:170(title) +msgid "\"Python Requirements\">" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:171(emphasis) ./doc/src/docbkx/common/glossary/glossary-terms.xml:3447(glossterm) +msgid "Python" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:177(link) +msgid "http://www.python.org/ftp/python/2.7.3/python-2.7.3.msi" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:181(para) +msgid "Install the MSI accepting the default options." +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:184(para) +msgid "The installation will put python in C:/python27." +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:188(emphasis) +msgid "Setuptools" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:194(link) +msgid "http://pypi.python.org/packages/2.7/s/setuptools/setuptools-0.6c11.win32-py2.7.exe" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:197(emphasis) +msgid "Python Dependencies" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:198(para) +msgid "The following packages need to be downloaded and manually installed onto the Compute Node" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:202(emphasis) +msgid "MySQL-python" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:205(link) +msgid "http://codegood.com/download/10/" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:209(emphasis) +msgid "pywin32" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:210(para) +msgid "Download and run the installer from the following location" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:214(link) +msgid "http://sourceforge.net/projects/pywin32/files/pywin32/Build%20217/pywin32-217.win32-py2.7.exe" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:218(emphasis) +msgid "greenlet" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:219(para) +msgid "Select the link below:" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:221(link) +msgid "http://www.lfd.uci.edu/~gohlke/pythonlibs/" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:222(para) +msgid "You will need to scroll down to the greenlet section for the following file: greenlet-0.4.0.win32-py2.7.‌exe" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:224(para) +msgid "Click on the file, to initiate the download. Once the download is complete, run the installer." +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:228(para) +msgid "The following python packages need to be installed via easy_install or pip. Run the following replacing PACKAGENAME with the packages below:" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:231(replaceable) +msgid "PACKAGE_NAME" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:235(para) +msgid "amqplib" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:238(para) +msgid "anyjson" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:241(para) +msgid "distribute" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:244(para) +msgid "eventlet" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:247(para) +msgid "httplib2" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:250(para) +msgid "iso8601" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:253(para) +msgid "jsonschema" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:256(para) +msgid "kombu" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:259(para) +msgid "netaddr" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:262(para) +msgid "paste" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:265(para) +msgid "paste-deploy" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:268(para) +msgid "prettytable" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:271(para) +msgid "python-cinderclient" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:274(para) +msgid "python-glanceclient" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:277(para) +msgid "python-keystoneclient" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:280(para) +msgid "repoze.lru" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:283(para) +msgid "routes" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:286(para) +msgid "sqlalchemy" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:289(para) +msgid "simplejson" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:292(para) +msgid "warlock" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:295(para) +msgid "webob" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:298(para) +msgid "wmi" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:303(title) +msgid "Installing Nova-compute" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:304(emphasis) +msgid "Using git on Windows to retrieve source" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:310(link) +msgid "http://code.google.com/p/msysgit/downloads/list?q=full+installer+official+git" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:315(para) +msgid "Once installed you may run the following to clone the Nova code." +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:321(title) +msgid "Configuring Nova.conf" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/hyper-v.xml:349(title) +msgid "Preparing Images for use with Hyper-V" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:350(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/src/docbkx/common/hyper-v.xml:354(link) +msgid "http://technet.microsoft.com/en-us/library/cc772480.aspx" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:355(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/src/docbkx/common/hyper-v.xml:358(replaceable) +msgid "VM_IMAGE_NAME" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:362(title) +msgid "Running Compute with Hyper-V" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:363(para) +msgid "To start the nova-compute service, run this command from a console in the Windows server:" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:370(title) +msgid "Troubleshooting Hyper-V Configuration" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:373(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/src/docbkx/common/hyper-v.xml:378(link) +msgid "here" +msgstr "" + +#: ./doc/src/docbkx/common/hyper-v.xml:376(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 "" + +#: ./doc/src/docbkx/common/nova_cli_boot.xml:8(title) +msgid "Create Your Server with the nova Client" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_boot.xml:10(title) +msgid "To create and boot your server with the nova client:" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_boot.xml:13(para) +msgid "Issue the following command. In the command, specify the server name, flavor ID, and image ID:" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_boot.xml:18(para) +msgid "The command returns a list of server properties. The status field indicates whether the server is being built or is active. A status of BUILD indicates that your server is being built." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_boot.xml:49(para) +msgid "Copy the server ID value from the id field in the output. You use this ID to get details for your server to determine if it built successfully." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_boot.xml:53(para) +msgid "Copy the administrative password value from the adminPass field. You use this value to log into your 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/src/docbkx/common/introduction-to-xen.xml:169(None) +msgid "@@image: 'figures/XenServer-dom0-domU.png'; md5=be393a6f0c70762ea76b995c12044ebf" +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:7(title) +msgid "Xen, XenAPI, XenServer and XCP" +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:9(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: The above 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. Note these settings are generally unique to each hypervisor host as the use of the host internal management network IP address (169.254.0.1) will cause features such as live-migration to break." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:32(para) +msgid "VHD (in a gzipped tarball)" +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:25(para) +msgid "OpenStack with XenAPI supports the following virtual machine image formats: " +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:37(para) +msgid "It is possible to manage Xen using libvirt. This would be necessary for any Xen-based system that isn't using the XCP toolstack, such as SUSE Linux or Oracle Linux. Unfortunately, this is not well-tested or supported as of the Essex release. To experiment using Xen through libvirt add the following configuration options /etc/nova/nova.conf: " +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:47(para) +msgid "The rest of this section describes Xen, XCP, and XenServer, the differences between them, and how to use them with OpenStack. Xen's architecture is different from KVM's in important ways, and we discuss those differences and when each might make sense in your OpenStack cloud." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:53(title) +msgid "Xen terminology" +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:55(para) +msgid "Xen is a hypervisor. It provides the fundamental isolation between virtual machines. Xen is open source (GPLv2) and is managed by Xen.org, an cross-industry organization." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:59(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/src/docbkx/common/introduction-to-xen.xml:66(para) +msgid "Xen Cloud Platform (XCP) is an open source (GPLv2) tool stack for Xen. It is designed specifically as 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/src/docbkx/common/introduction-to-xen.xml:78(para) +msgid "Citrix XenServer is 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/src/docbkx/common/introduction-to-xen.xml:91(para) +msgid "Both XenServer and XCP include Xen, Linux, and the primary control daemon known as xapi." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:94(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/src/docbkx/common/introduction-to-xen.xml:108(title) +msgid "Privileged and unprivileged domains" +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:110(para) +msgid "A Xen host will run 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/src/docbkx/common/introduction-to-xen.xml:126(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/src/docbkx/common/introduction-to-xen.xml:141(title) +msgid "Paravirtualized versus hardware virtualized domains" +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:143(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 have the advantage that there is no need to modify the guest operating system, which is essential when running Windows." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:153(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/src/docbkx/common/introduction-to-xen.xml:162(title) +msgid "XenAPI deployment architecture" +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:164(para) +msgid "When you deploy OpenStack on XCP or XenServer you will get something similar to this: " +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:175(para) +msgid "The hypervisor: Xen" +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:177(para) +msgid "Domain 0: runs xapi and some small pieces from OpenStack (some xapi plugins and network isolation rules). The majority of this is provided by XenServer or XCP (or yourself using Kronos)." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:181(para) +msgid "OpenStack domU: 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/src/docbkx/common/introduction-to-xen.xml:188(para) +msgid "Nova uses the XenAPI Python library to talk to xapi, and it uses the Host Internal Management Network to reach from the domU to dom0 without leaving the host." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:172(para) +msgid "Key things to note: " +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:198(para) +msgid "The above diagram assumes FlatDHCP networking (the DevStack default)." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:201(para) +msgid "There are three main OpenStack networks: Management traffic (RabbitMQ, MySQL, etc), Tenant network traffic (controlled by nova-network) and Public traffic (floating IPs, public API end points)." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:206(para) +msgid "Each network that leaves the host has been put through a separate physical network interface. This is the simplest model, but it's not the only one possible. You may choose to isolate this traffic using VLANs instead, for example." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:194(para) +msgid "Some notes on the networking: " +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:216(title) +msgid "XenAPI pools" +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:218(para) +msgid "The host-aggregates feature allows you to create pools of XenServer hosts (configuring shared storage is still an out of band activity), to enable live migration when using shared storage." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:226(title) +msgid "Installing XenServer and XCP" +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:228(para) +msgid "When you want to run OpenStack with XCP or XenServer, you first need to install the software on an appropriate server. Please note, Xen is a type 1 hypervisor. This means when your server starts the first software that runs is Xen. This means the software you install on your compute host is XenServer or XCP, not the operating system you wish to run the OpenStack code on. The OpenStack services will run in a VM you install on top of XenServer." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:246(link) +msgid "http://www.citrix.com/XenServer/download" +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:250(link) +msgid "http://www.xen.org/download/xcp/index.html" +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:238(para) +msgid "Before you can install your system you must decide if you want to install Citrix XenServer (either the free edition, or one of the paid editions) or Xen Cloud Platform from Xen.org. You can download the software from the following locations: When installing many servers, you may find it easier to perform PXE boot installations of XenServer or XCP. You can also package up any post install changes you wish to make to your XenServer by creating your own XenServer supplimental pack." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:262(para) +msgid "It is also possible to get XCP by installing the xcp-xenapi package on Debian based distributions. However, this is not as mature or feature complete as above distributions. This will modify your boot loader to first boot Xen, then boot your existing OS on top of Xen as Dom0. It is in Dom0 that the xapi daemon will run. You can find more details on the Xen.org wiki: http://wiki.xen.org/wiki/Project_Kronos " +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:274(title) +msgid "Post install steps" +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:280(para) +msgid "Ensure you are using 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 using the LVM SR. Storage repository (SR) is a XenAPI specific term relating to the physical storage on which virtual disks are stored." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:290(para) +msgid "For resize and migrate functionality, please perform the changes described in the Configuring Resize section of the OpenStack Compute Administration Manual." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:276(para) +msgid "Now you have installed XenServer or XCP, it is time to start running OpenStack. Before you can start running OpenStack you must ensure: " +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:302(para) +msgid "Install the VIF isolation rules to help prevent mac and ip address spoofing." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:306(para) +msgid "Install the XenAPI plugins." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:309(para) +msgid "Create a Paravirtualised virtual machine that can run the OpenStack compute code." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:313(para) +msgid "Install and configure the nova-compute in the above virtual machine." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:298(para) +msgid "You are now ready to install OpenStack onto your XenServer system. This process involves the following steps: For further information on how to perform these steps look at how DevStack performs the last three steps when doing developer deployments. For more information on DevStack, take a look at the DevStack and XenServer Readme. More information on the first step can be found in the XenServer mutli-tenancy protection doc. More information on how to install the XenAPI plugins can be found in the XenAPI plugins Readme." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:336(title) +msgid "Xen Boot from ISO" +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:337(para) +msgid "XenServer, through the XenAPI integration with OpenStack provides a feature to boot instances from an ISO file. In order to activate the \"Boot From ISO\" feature, the SR elements on XenServer host must be configured that way." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:342(para) +msgid "First, create an ISO-typed SR, such as an NFS ISO library, for instance. For this, using XenCenter is a simple method. You need to export an NFS volume from a remote NFS server. Make sure it is exported in read-write mode." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:346(para) +msgid "Second, on the compute host, find the uuid of this ISO SR and write it down. " +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:350(para) +msgid "Next, locate the uuid of the NFS ISO library: " +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:354(para) +msgid "Set the uuid and configuration. Even if an NFS mount point isn't local storage, you must specify \"local-storage-iso\". " +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:358(para) +msgid "Now, make sure the host-uuid from \"xe pbd-list\" equals the uuid of the host you found earlier " +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:363(para) +msgid "You should now be able to add images via the OpenStack Image Registry, with disk_format=iso, and boot them in OpenStack Compute. " +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:374(title) +msgid "Further reading" +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:379(para) +msgid "Citrix XenServer official documentation: http://docs.vmd.citrix.com/XenServer." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:386(para) +msgid "What is Xen? by Xen.org: http://xen.org/files/Marketing/WhatisXen.pdf." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:392(para) +msgid "Xen Hypervisor project: http://xen.org/products/xenhyp.html." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:398(para) +msgid "XCP project: http://xen.org/products/cloudxen.html." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:404(para) +msgid "Further XenServer and OpenStack information: http://wiki.openstack.org/XenServer." +msgstr "" + +#: ./doc/src/docbkx/common/introduction-to-xen.xml:376(para) +msgid "Here are some of the resources available to learn more about Xen: " +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:6(title) +msgid "Identity Management" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:7(para) +msgid "The default identity management system for OpenStack is the OpenStack Identity Service, code-named Keystone. Once Identity is installed, it is configured via a primary configuration file (etc/keystone.conf), possibly a separate logging configuration file, and initializing data into keystone using the command line client." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:16(title) +msgid "Memcached and System Time" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:17(para) +msgid "If using memcached with Keystone - e.g. using the memcache token driver or the auth_token middleware - ensure that the system time of memcached hosts is set to UTC. Memcached uses the host's system time in determining whether a key has expired, whereas Keystone sets key expiry in UTC. The timezone used by Keystone and memcached must match if key expiry is to behave as expected." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:29(title) +msgid "User CRUD" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:30(para) +msgid "Keystone provides a user CRUD filter that can be added to the public_api pipeline. This user crud filter allows 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 app in the public_api WSGI pipeline in keystone.conf e.g.:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:46(para) +msgid "Each user can then change their own password with a HTTP PATCH" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:53(para) +msgid "In addition to changing their password all of the users current tokens will be deleted (if the backend used is kvs or sql)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:59(title) +msgid "Configuration Files" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:60(para) +msgid "The Identity configuration file is an 'ini' file format with sections, extended from Paste, a common system used to configure python WSGI based applications. In addition to the paste config entries, general configuration values are stored under [DEFAULT], [sql], [ec2] and then drivers for the various services are included under their individual sections." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:71(para) +msgid "The services include:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:74(para) +msgid "[DEFAULT] - general configuration" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:79(para) +msgid "[sql] - optional storage backend configuration" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:85(para) +msgid "[ec2] - Amazon EC2 authentication driver configuration" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:91(para) +msgid "[s3] - Amazon S3 authentication driver configuration." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:97(para) +msgid "[identity] - identity system driver configuration" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:103(para) +msgid "[catalog] - service catalog driver configuration" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:109(para) +msgid "[token] - token driver configuration" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:114(para) +msgid "[policy] - policy system driver configuration for RBAC" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:120(para) +msgid "[signing] - cryptographic signatures for PKI based tokens" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:126(para) +msgid "[ssl] - SSL configuration" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:131(para) +msgid "The configuration file is expected to be named keystone.conf. When starting Identity, you can specify a different configuration file to use with --config-file. If you do not specify a configuration file, keystone will look in the following directories for a configuration file, in order:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:143(literal) +msgid "~/.keystone" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:148(literal) +msgid "~/" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:153(literal) +msgid "/etc/keystone" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:158(literal) +msgid "/etc" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:164(title) +msgid "Logging" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:165(para) +msgid "Logging is configured externally to the rest of Identity, the file specifying the logging configuration is in the [DEFAULT] section of the keystone.conf file under log_config. If you wish to route all your logging through syslog, set use_syslog=true option in the [DEFAULT] section." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:172(para) +msgid "A sample logging file is available with the project in the directory etc/logging.conf.sample. Like other OpenStack projects, Identity uses the `python logging module`, which includes extensive configuration options for choosing the output levels and formats." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:179(para) +msgid "In addition to this documentation page, you can check the etc/keystone.conf sample configuration files distributed with keystone for example configuration files for each server application." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:185(para) +msgid "For services which have separate paste-deploy ini file, auth_token middleware can be alternatively configured in [keystone_authtoken] section in the main config file, such as nova.conf. For example in Nova, all middleware parameters can be removed from api-paste.ini like these:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:195(para) +msgid "and set in nova.conf like these:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:210(para) +msgid "Note that middleware parameters in paste config take priority, they must be removed to use values in [keystone_authtoken] section." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:216(para) +msgid "Keystone provides some basic request/response monitoring statistics out of the box." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:220(para) +msgid "Enable data collection by defining a stats_monitoring filter and including it at the beginning of any desired WSGI pipelines:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:232(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/src/docbkx/common/ch_identity_mgmt.xml:246(para) +msgid "Query the admin API for statistics using:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:252(para) +msgid "Reset collected data using:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:261(title) +msgid "Sample Configuration Files" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:265(filename) +msgid "etc/keystone.conf" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:270(literal) +msgid "etc/logging.conf.sample" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:277(title) +msgid "Running" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:278(para) +msgid "Running Identity is simply starting the services by using the command:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:285(para) +msgid "Invoking this command starts up two wsgi.Server instances, configured by the keystone.conf file as described above. One of these wsgi 'servers' is admin (the administration API) and the other is main (the primary/public API interface). Both of these run in a single process." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:295(title) +msgid "Initializing Keystone" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:296(para) +msgid " is designed to execute commands that cannot be administered through the normal REST api. At the moment, the following calls are supported:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:303(para) +msgid "db_sync: Sync the database." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:308(para) +msgid "import_nova_auth: Load auth data from a dump created with keystone-manage." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:314(para) +msgid "Generally, the following is the first step after a source installation:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:321(para) +msgid "Invoking keystone-manage by itself will give you additional usage information." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:328(title) +msgid "Adding Users, Tenants, and Roles with python-keystoneclient" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:330(para) +msgid "User, tenants, and roles must be administered using admin credentials. There are two ways to configure python-keystoneclient to use admin credentials, using the token auth method, or password auth method." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:337(title) +msgid "Token Auth Method" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:338(para) +msgid "To use keystone client using token auth, set the following flags" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:343(para) +msgid "--endpoint SERVICE_ENDPOINT : allows you to specify the keystone endpoint to communicate with. The default endpoint is http://localhost:35357/v2.0'" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:351(para) +msgid "--token SERVICE_TOKEN : your administrator service token." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:359(title) +msgid "Password Auth Method" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:362(para) +msgid "--username OS_USERNAME : allows you to specify the administrator username" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:368(para) +msgid "--password OS_PASSWORD : Your administrator password" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:374(para) +msgid "--tenant_name OS_TENANT_NAME : Name of your tenant" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:380(para) +msgid "--auth_url OS_AUTH_URL : url of your keystone auth server, for example http://localhost:5000/v2.0'" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:390(title) +msgid "Example usage" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:391(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/src/docbkx/common/ch_identity_mgmt.xml:423(para) +msgid "Tenants are the high level grouping within Keystone that represent groups of users. A tenant is the grouping that owns virtual machines within Nova, or containers within Swift. A tenant can have zero or more users, Users can be associated with more than one tenant, and each tenant - user pairing can have a role associated with it." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:432(literal) +msgid "tenant-create" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:433(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:821(para) +msgid "keyword arguments" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:438(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:528(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:701(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:826(para) +msgid "name" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:443(para) +msgid "description (optional, defaults to None)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:448(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:548(para) +msgid "enabled (optional, defaults to True)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:453(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:475(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:494(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:513(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:553(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:573(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:596(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:622(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:641(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:660(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:684(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:706(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:723(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:730(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:747(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:774(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:806(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:841(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:863(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:882(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:901(para) +msgid "example:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:459(para) +msgid "creates a tenant named \"demo\"." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:464(literal) +msgid "tenant-delete" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:465(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:484(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:503(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:586(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:605(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:631(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:650(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:669(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:696(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:713(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:737(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:754(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:786(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:853(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:872(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:891(para) +msgid "arguments" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:470(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:489(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:508(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:769(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:801(para) +msgid "tenant_id" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:483(literal) +msgid "tenant-enable" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:502(literal) +msgid "tenant-disable" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:524(literal) +msgid "user-create" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:525(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:565(para) +msgid "keyword arguments:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:533(para) +msgid "pass" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:538(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:615(para) +msgid "email" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:543(para) +msgid "default_tenant (optional, defaults to None)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:564(literal) +msgid "user-delete" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:568(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:4621(glossterm) +msgid "user" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:581(literal) +msgid "user-list" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:582(para) +msgid "list users in the system, optionally by a specific tenant (identified by tenant_id)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:591(para) +msgid "tenant_id (optional, defaults to None)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:604(literal) +msgid "user-update --email" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:610(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:636(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:655(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:674(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:764(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:796(para) +msgid "user_id" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:630(literal) +msgid "user-enable" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:649(literal) +msgid "user-disable" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:668(literal) +msgid "user-update --password" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:679(para) +msgid "password" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:695(literal) +msgid "role-create" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:712(literal) +msgid "role-delete" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:718(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:742(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:759(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:791(para) +msgid "role_id" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:729(literal) +msgid "role-list" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:736(literal) +msgid "role-get" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:753(literal) +msgid "add-user-role" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:785(literal) +msgid "remove-user-role" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:820(literal) +msgid "service-create" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:831(para) ./doc/src/docbkx/common/boot_from_volume.xml:64(literal) +msgid "type" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:836(para) +msgid "description" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:852(literal) +msgid "service-list" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:858(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:877(para) ./doc/src/docbkx/common/ch_identity_mgmt.xml:896(para) +msgid "service_id" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:871(literal) +msgid "service-get" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:890(literal) +msgid "service-delete" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:911(title) +msgid "Configuring Services to work with Keystone" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:912(para) +msgid "Once Keystone is installed and running, services need to be configured to work with it. To do this, we primarily install and configure middleware for the OpenStack service to handle authentication tasks or otherwise interact with Keystone." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:918(para) +msgid "In general:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:923(para) +msgid "Clients making calls to the service will pass in an authentication token." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:929(para) +msgid "The Keystone middleware will look for and validate that token, taking the appropriate action." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:935(para) +msgid "It will also retrieve additional information from the token such as user name, id, tenant name, id, roles, etc..." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:941(para) +msgid "The middleware will pass those data down to the service as headers." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:947(title) +msgid "Setting up credentials" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:948(para) +msgid "To ensure services that you add to the catalog know about the users, tenants, and roles, you must create an admin token and create service users. These sections walk through those requirements." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:954(title) +msgid "Admin Token" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:955(para) +msgid "For a default installation of Keystone, before you can use the REST API, you need to define an authorization token. This is configured in keystone.conf file under the section [DEFAULT]. In the sample file provided with the keystone project, the line defining this token is" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:962(para) +msgid "[DEFAULT] admin_token = ADMIN" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:966(para) +msgid "This configured token is a \"shared secret\" between keystone and other OpenStack services, and is used by the client to communicate with the API to create tenants, users, roles, etc." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:972(title) +msgid "Setting up tenants, users, and roles" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:973(para) +msgid "You need to minimally define a tenant, user, and role to link the tenant and user as the most basic set of details to get other services authenticating and authorizing with keystone." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:978(para) +msgid "You will also want to create service users for Compute (nova), Image (glance), Object Storage (swift), etc. to be able to use to authenticate users against the Identity service (keystone). The auth_token middleware supports using either the shared secret described above as `admin_token` or users for each service." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:985(para) +msgid "See the configuration section for a walk through on how to create tenants, users, and roles." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:992(title) +msgid "Setting up services" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:996(title) +msgid "Creating Service Users" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:997(para) +msgid "To configure the OpenStack services with service users, we need to create a tenant for all the services, and then users for each of the services. We then assign those service users an Admin role on the service tenant. This allows them to validate tokens - and authenticate and authorize other user requests." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1004(para) +msgid "Create a tenant for the services, typically named 'service' (however, the name can be whatever you choose):" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1011(para) +msgid "This returns a UUID of the tenant - keep that, you'll need it when creating the users and specifying the roles." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1015(para) +msgid "Create service users for nova, glance, swift, and quantum (or whatever subset is relevant to your deployment):" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1025(para) +msgid "Repeat this for each service you want to enable. Email is a required field in keystone right now, but not used in relation to the service accounts. Each of these commands will also return a UUID of the user. Keep those to assign the Admin role." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1031(para) +msgid "For adding the Admin role to the service accounts, you'll need to know the UUID of the role you want to add. If you don't have them handy, you can look it up quickly with:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1039(para) +msgid "Once you have it, assign the service users to the Admin role. This is all assuming that you've already created the basic roles and settings as described in the configuration section:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1051(title) +msgid "Defining Services" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1052(para) +msgid "Keystone also acts as a service catalog to let other OpenStack systems know where relevant API endpoints exist for OpenStack Services. The OpenStack Dashboard, in particular, uses this heavily - and this must be configured for the OpenStack Dashboard to properly function." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1059(para) +msgid "The endpoints for these services are defined in a template, an example of which is in the project as the file etc/default_catalog.templates. When keystone uses a template file backend, then changes made to the endpoints are kept in memory and don't persist if you restart the service or reboot the machine. Use the SQL backend when deploying a system for production." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1066(para) +msgid "Keystone supports two means of defining the services, one is the catalog template, as described above - in which case everything is detailed in that template." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1071(para) +msgid "The other is a SQL backend for the catalog service, in which case after keystone is online, you need to add the services to the catalog:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1096(title) +msgid "Setting Up Middleware" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1098(title) +msgid "Keystone Auth-Token Middleware" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1099(para) +msgid "The Keystone auth_token middleware is a WSGI component that can be inserted in the WSGI pipeline to handle authenticating tokens with Keystone." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1106(title) +msgid "Configuring Nova to use Keystone" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1107(para) +msgid "When configuring Nova, it is important to create a nova user in the service tenant and include the nova user's login information in /etc/nova/nova.conf" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1111(title) +msgid "Configuring Swift to use Keystone" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1112(para) +msgid "Similar to Nova, swift can be configured to use Keystone for authentication rather than its built in 'tempauth'." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1118(para) +msgid "Add a service endpoint for Swift to Keystone" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1123(para) +msgid "Configure the paste file for swift-proxy, /etc/swift/proxy-server.conf." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1128(para) +msgid "Reconfigure Swift's proxy server to use Keystone instead of TempAuth. Here's an example `/etc/swift/proxy-server.conf`:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1173(para) +msgid "Restart swift services." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1178(para) +msgid "Verify that the Identity service, Keystone, is providing authentication to Object Storage (Swift)." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1190(title) +msgid "Configuring Swift with S3 emulation to use Keystone" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1191(para) +msgid "Keystone support validating S3 tokens using the same tokens as the generated EC2 tokens. When you have generated a pair of EC2 access token and secret you can access your swift cluster directly with the S3 API." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1199(para) +msgid "Configure the paste file for swift-proxy (`/etc/swift/proxy-server.conf`) to use S3token and Swift3 middleware. You must have the s3token middleware in the pipeline when using keystone and swift3." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1204(para) +msgid "Here's an example:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1253(para) +msgid "You can then access directly your Swift via the S3 API, here's an example with the `boto` library:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1273(title) +msgid "Configuring Keystone for an LDAP backend" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1274(para) +msgid "As an alternative to the SQL Database backing store, Keystone can use a directory server to provide the Identity service. An example Schema for OpenStack would look like this:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1301(para) +msgid "The corresponding entries in the Keystone configuration file are:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1322(para) +msgid "The default object classes and attributes are intentionally simplistic. They reflect the common standard objects according to the LDAP RFCs. However, in a live deployment, the correct attributes can be overridden to support a preexisting, more 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/src/docbkx/common/ch_identity_mgmt.xml:1340(para) +msgid "There is a set of allowed actions per object type that you can modify depending on your specific deployment. For example, the users are managed by another tool and you have only read access, in such case the configuration is:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1360(para) +msgid "There are some configuration options for filtering users, tenants and roles, if the backend is providing too much output, in such case the configuration will look like:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1371(para) +msgid "In case that the directory server does not have an attribute enabled of type boolean for the user, there are several configuration parameters that can be used to extract the value from an integer attribute like in Active Directory:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1383(para) +msgid "In this case the attribute is an integer and the enabled attribute is listed in bit 1, so the if the mask configured user_enabled_mask is different from 0, it gets the value from the field user_enabled_attribute and it makes an ADD operation with the value indicated on user_enabled_mask and if the value matches the mask then the account is disabled." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1392(para) +msgid "It also saves the value without mask to the user identity in the attribute enabled_nomask. This is needed in order to set it back in case that we need to change it to enable/disable a user because it contains more information than the status like password expiration. Last setting user_enabled_mask is needed in order to create a default value on the integer attribute (512 = NORMAL ACCOUNT on AD)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1402(para) +msgid "In case of Active Directory the classes and attributes could not match the specified classes in the LDAP module so you can configure them like so:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1432(title) +msgid "Reference for LDAP Configuration Options in keystone.conf" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1436(title) +msgid "Auth-Token Middleware with Username and Password" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1437(para) +msgid "It is also possible to configure Keystone's auth_token middleware using the 'admin_user' and 'admin_password' options. When using the 'admin_user' and 'admin_password' options the 'admin_token' parameter is optional. If 'admin_token' is specified it will by used only if the specified token is still valid." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1445(para) +msgid "Here is an example paste config filter that makes use of the 'admin_user' and 'admin_password' parameters:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1460(para) +msgid "It should be noted that when using this option an admin tenant/role relationship is required. The admin user is granted access to the 'Admin' role on the 'admin' tenant." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1469(title) +msgid "Configuring Keystone SSL support" +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1478(para) +msgid "ca.pem - Certificate Authority chain to validate against." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1482(para) +msgid "keystone.pem - Public certificate for Keystone server." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1486(para) +msgid "middleware.pem - Public and private certificate for Keystone middleware/client." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1490(para) +msgid "cakey.pem - Private key for the CA." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1494(para) +msgid "keystonekey.pem - Private key for the Keystone server." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1470(para) +msgid "Keystone may be configured to support 2-way SSL out-of-the-box. The x509 certificates used by Keystone must be obtained externally and configured for use with Keystone as described in this section. However, a set of sample certificates is provided in the examples/ssl directory with the Keystone distribution for testing. Here is the description of each of them and their purpose: Note that you may choose whatever names you want for these certificates, or combine the public/private keys in the same file if you wish. These certificates are just provided as an example." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1501(para) +msgid "To enable SSL with client authentication, modify the etc/keystone.conf file accordingly under the [ssl] section. SSL configuration example using the included sample certificates: Example: " +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1522(para) +msgid "enable: True enables SSL. Defaults to False." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1523(para) +msgid "certfile: Path to Keystone public certificate file." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1524(para) +msgid "keyfile: Path to Keystone private certificate file. If the private key is included in the certfile, the keyfile may be omitted." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1527(para) +msgid "ca_certs: Path to CA trust chain." +msgstr "" + +#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1528(para) +msgid "cert_required: Requires client certificate. Defaults to False." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/common/dashboard_customizing.xml:21(None) ./doc/src/docbkx/common/dashboard_customizing.xml:26(None) +msgid "@@image: 'figures/Login-–-OpenStack-Dashboard.png'; md5=6b3389c5c4fc122b29abcd5bf4d7983d" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/common/dashboard_customizing.xml:33(None) ./doc/src/docbkx/common/dashboard_customizing.xml:38(None) +msgid "@@image: 'figures/Flavors-–-TGen-Cloud-Dashboard.png'; md5=7ee18997b5febe17014ace389d03c051" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:6(title) +msgid "How To Custom Brand The OpenStack Dashboard (Horizon)" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:7(para) +msgid "Adapted from a blog post by Preston Lee." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:8(para) +msgid "When deploying OpenStack on Ubuntu Server 12.04, you can have the openstack-dashboard package installed to provide the web-based “Horizon” GUI component. Canonical also provides an openstack-dashboard-ubuntu-theme package that brands the Python-based Django GUI." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:14(para) +msgid "The Horizon documents briefly mention branding customization to give you a head start, but here are more specific steps. Here’s a custom-branded Horizon dashboard with custom colors, logo, and site title:" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:41(para) +msgid "Once you know where to make the appropriate changes, it’s super simple. Step-by-step:" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:44(para) +msgid "Create a graphical logo with a transparent background. The text “TGen Cloud” in this example is actually rendered via .png files of multiple sizes created with a graphics program. Use a 200×27 for the logged-in banner graphic, and 365×50 for the login screen graphic." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:48(para) +msgid "Set the HTML title (shown at the top of the browser window) by adding the following line to /etc/openstack-dashboard/local_settings.py: SITE_BRANDING = \"Example, Inc. Cloud\"" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:51(para) +msgid "Upload your new graphic files to: " +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:54(para) +msgid "Create a new CSS stylesheet — we’ll call ours custom.css — in the directory: " +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:57(para) +msgid "Edit your CSS file using the following as a starting point for customization, which simply overrides the Ubuntu customizations made in the ubuntu.css file." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:60(para) +msgid "Change the colors and image file names as appropriate, though the relative directory paths should be the same. " +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:94(para) +msgid "Open the following HTML template in an editor: " +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:100(emphasis) +msgid "<link href='{{ STATIC_URL }}dashboard/css/custom.css' media='screen' rel='stylesheet' />" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:96(para) +msgid "Add a line to include your new stylesheet pointing to custom.css: (I’ve highlighted the new line in bold.) " +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:103(para) +msgid "Restart apache just for good measure: sudo service apache2 restartsudo service httpd restart" +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:105(para) +msgid "Reload the dashboard in your browser and fine tune your CSS appropriate." +msgstr "" + +#: ./doc/src/docbkx/common/dashboard_customizing.xml:106(para) +msgid "You’re done!" +msgstr "" + +#: ./doc/src/docbkx/common/powervm.xml:6(title) +msgid "PowerVM" +msgstr "" + +#: ./doc/src/docbkx/common/powervm.xml:9(title) ./doc/src/docbkx/common/user-data.xml:10(title) ./doc/src/docbkx/common/vmware.xml:9(title) ./doc/src/docbkx/common/config-drive.xml:6(title) +msgid "Introduction" +msgstr "" + +#: ./doc/src/docbkx/common/powervm.xml:10(para) +msgid "PowerVM compute driver connects to an Integrated Virtualization Manager (IVM) to perform PowerVM Logical Partition (LPAR) deployment and management. The driver supports file-based deployment using images from Glance." +msgstr "" + +#: ./doc/src/docbkx/common/powervm.xml:14(para) +msgid "Hardware Management Console (HMC) is not yet supported." +msgstr "" + +#: ./doc/src/docbkx/common/powervm.xml:15(para) +msgid "For more detailed information about PowerVM Virtualization system, refer to the IBM Redbook publication: IBM PowerVM Virtualization Introduction and Configuration." +msgstr "" + +#: ./doc/src/docbkx/common/powervm.xml:21(title) +msgid "Configuration" +msgstr "" + +#: ./doc/src/docbkx/common/powervm.xml:22(para) +msgid "To enable the PowerVM compute driver, add the following configuration options /etc/nova/nova.conf: " +msgstr "" + +#: ./doc/src/docbkx/common/lxc.xml:6(title) +msgid "LXC (Linux containers)" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/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 need to access to specialized hardware (e.g., GPUs), this may be easier to achieve with LXC than other hypervisors." +msgstr "" + +#: ./doc/src/docbkx/common/lxc.xml:22(para) +msgid "Some OpenStack Compute features may be missing when running with LXC as the hypervisor. See the hypervisor support matrix for details." +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/lxc.xml:30(para) +msgid "On Ubuntu 12.04, enable LXC support in OpenStack by installing the nova-compute-lxc package." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_userdata.xml:8(title) +msgid "Providing User Data to Instances" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_userdata.xml:9(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 the cloudinit system is an open source package from Ubuntu that handles early initialization of a cloud instance that makes use of this user data." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_userdata.xml:17(para) +msgid "This user-data can be put in a file on your local system and then passed in at instance creation with the flag --user-data <user-data-file> for example:" +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:8(title) +msgid "Configuring instances at boot time" +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:11(para) +msgid "Users often want to do some configuration to their instances after booting. For example, you may want to install some packages, start services, or manage the instance using a Puppet or Chef server. When launching instances in an OpenStack cloud, there are two technologies that work together to support automated configuration of instances at boot time: user data and cloud-init." +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:18(title) ./doc/src/docbkx/common/config-drive.xml:181(title) +msgid "User data" +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:19(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/src/docbkx/common/user-data.xml:22(para) +msgid "User data is sent using the --user-data /path/to/filename option when calling . The following example creates a text file and then send the contents of that file as user data to the instance." +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:30(para) +msgid "The instance can retrieve user data by querying the metadata service at using either the OpenStack metadata API or the EC2 compatibility API:" +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:38(para) +msgid "Note that the Compute service treats user data as a blob. While the example above used a text file, user data can be in any format." +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:42(title) +msgid "Cloud-init" +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:43(para) +msgid "To do something useful with the user data, the virtual machine image must be configured to run a service on boot that retrieves the user data from the metadata service and take some action based on the contents of the data. The cloud-init package was designed to do exactly this. In particular, cloud-init is compatible with the Compute metadata service as well as the Compute config drive." +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:48(para) +msgid "Note that cloud-init is not an OpenStack technology. Rather, it is a package that is designed to support multiple cloud providers, so that the same virtual machine image can be used in different clouds without modification. Cloud-init is an open source project, and the source code is available on Launchpad. It is maintained by Canonical, the company which 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 Fedora." +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:56(para) +msgid "We recommend installing cloud-init on images that you create to simplify the task of configuring your instances on boot. Even if you do not wish to use user data to configure instance behavior at boot time, cloud-init provides useful functionality such as copying the public key to an account (the ubuntu account by default on Ubuntu instances, the ec2-user by default in Fedora instances)." +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:62(para) +msgid "If you do not have cloud-init installed, you will need to manually configure your image to retrieve the public key from the metadata service on boot and copy it to the appropriate account." +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:67(title) +msgid "Cloud-init supported formats and documentation" +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:68(para) +msgid "We recommend taking a look at the cloud-init doc/userdata.txt file the examples directory as well as the Ubuntu community documentation for details on how to use cloud-init. We provide some basic examples here." +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:79(para) +msgid "Shell scripts (starts with #!)" +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:82(para) +msgid "Cloud config files (starts with #cloud-config)" +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:76(para) +msgid "Cloud-init supports several different input formats for user data. We briefly discuss two commonly used formats:" +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:87(title) +msgid "Running a shell script on boot" +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:88(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. Here's an example of a script that creates an account called clouduser." +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:93(para) +msgid "Sending a shell script as user data has a similar effect to writing an /etc/rc.local script: it will be executed very late in the boot sequence as root." +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:99(title) +msgid "Cloud-config format" +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:100(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/src/docbkx/common/user-data.xml:106(title) +msgid "Example: Setting hostname" +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:107(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/src/docbkx/common/user-data.xml:117(title) +msgid "Example: Configuring instances with Puppet" +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:118(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/src/docbkx/common/user-data.xml:145(title) +msgid "Example: Configuring instances with Chef" +msgstr "" + +#: ./doc/src/docbkx/common/user-data.xml:146(para) +msgid "This cloud-init user data example, based on doc/examples/cloud-config/chef.txt, and intended for use in an Ubuntu image, would add the Chef apt repository, install Chef, connect to a Chef server at https://chefserver.example.com:4000 and install Apache." +msgstr "" + +#: ./doc/src/docbkx/common/support-object-storage.xml:5(title) +msgid "Troubleshooting OpenStack Object Storage" +msgstr "" + +#: ./doc/src/docbkx/common/support-object-storage.xml:6(para) +msgid "For OpenStack 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/src/docbkx/common/support-object-storage.xml:8(title) +msgid "Handling Drive Failure" +msgstr "" + +#: ./doc/src/docbkx/common/support-object-storage.xml:9(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 OpenStack 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/src/docbkx/common/support-object-storage.xml:10(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/src/docbkx/common/support-object-storage.xml:11(para) +msgid "Rackspace has seen hints at drive failures by looking at error messages in /var/log/kern.log - do consider checking this in your monitoring" +msgstr "" + +#: ./doc/src/docbkx/common/support-object-storage.xml:17(title) +msgid "Handling Server Failure" +msgstr "" + +#: ./doc/src/docbkx/common/support-object-storage.xml:19(para) +msgid "If a server is having hardware issues, it is a good idea to make sure the OpenStack Object Storage services are not running. This will allow OpenStack Object Storage to work around the failure while you troubleshoot." +msgstr "" + +#: ./doc/src/docbkx/common/support-object-storage.xml:21(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 OpenStack 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/src/docbkx/common/support-object-storage.xml:23(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/src/docbkx/common/support-object-storage.xml:26(title) +msgid "Detecting Failed Drives" +msgstr "" + +#: ./doc/src/docbkx/common/support-object-storage.xml:28(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 OpenStack Object Storage can work around it. The script takes a configuration file with the following settings:" +msgstr "" + +#: ./doc/src/docbkx/common/support-object-storage.xml:39(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/src/docbkx/common/support-object-storage.xml:43(title) +msgid "Emergency Recovery of Ring Builder Files" +msgstr "" + +#: ./doc/src/docbkx/common/support-object-storage.xml:44(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/src/docbkx/common/support-object-storage.xml:47(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/src/docbkx/common/support-object-storage.xml:51(title) +msgid "Warning" +msgstr "" + +#: ./doc/src/docbkx/common/support-object-storage.xml:52(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/src/docbkx/common/support-object-storage.xml:54(para) +msgid "First, load the ring and a new ringbuilder object in a Python REPL:" +msgstr "" + +#: ./doc/src/docbkx/common/support-object-storage.xml:59(para) +msgid "Now, start copying the data we have in the ring into the builder." +msgstr "" + +#: ./doc/src/docbkx/common/support-object-storage.xml:77(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/src/docbkx/common/support-object-storage.xml:83(para) +msgid "Try some validation: if this doesn't raise an exception, you may feel some hope. Not too much, though." +msgstr "" + +#: ./doc/src/docbkx/common/support-object-storage.xml:88(para) +msgid "Save the builder." +msgstr "" + +#: ./doc/src/docbkx/common/support-object-storage.xml:93(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/src/docbkx/common/support-object-storage.xml:101(para) +msgid "Next, repeat the procedure for container.ring.gz and object.ring.gz, and you might get usable builder files." +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:8(title) +msgid "Launch from a Volume" +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:9(para) +msgid "The Compute service has preliminary support for booting an instance from a volume." +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:12(title) +msgid "Creating a bootable volume" +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:13(para) +msgid "To create a bootable volume, mount the volume to an existing instance, and then build a volume-backed image. Here is an example based on exercises/boot_from_volume.sh. This example assumes that you have a running instance with a 1GB volume mounted at /dev/vdc. These commands will make the mounted volume bootable using a CirrOS image. As root:" +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:33(para) +msgid "Detach the volume once you are done." +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:36(title) +msgid "Booting an instance from the volume" +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:37(para) +msgid "To boot a new instance from the volume, use the command with use the --block-device-mapping flag. The output for shows the following documentation about this flag:" +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:49(literal) +msgid "dev-name" +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:51(para) +msgid "A device name where the volume will be attached in the system at /dev/dev_name. This value is typically vda." +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:57(literal) +msgid "id" +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:59(para) +msgid "The ID of the volume to boot from, as shown in the output of ." +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:66(para) +msgid "This is either snap, which means that the volume was created from a snapshot, or anything other than snap (a blank string is valid). In the example above, the volume was not created from a snapshot, so we will leave this field blank in our example below." +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:74(literal) +msgid "size (GB)" +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:76(para) +msgid "The size of the volume, in GB. It is safe to leave this blank and have the Compute service infer the size." +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:81(literal) +msgid "delete-on-terminate" +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:83(para) +msgid "A boolean to indicate whether the volume should be deleted when the instance is terminated. True can be specified as True or 1. False can be specified as False or 0." +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:47(para) +msgid "The command arguments are:" +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:92(para) +msgid "Because of bug #1008622, you must specify an image when booting from a volume, even though this image will not be used." +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:100(replaceable) +msgid "f4addd24-4e8a-46bb-b15d-fae2591f1a35" +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:100(replaceable) +msgid "mykey" +msgstr "" + +#: ./doc/src/docbkx/common/boot_from_volume.xml:91(para) +msgid "The following example will attempt boot from volume with ID=13, it will not delete on terminate. Replace the --image flag with a valid image on your system, and the --key-name with a valid keypair name:" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_evacuate.xml:5(title) +msgid "Instance evacuation" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_evacuate.xml:6(para) +msgid "As cloud administrator, while you are managing your cloud, you may get to the point where one of the cloud compute nodes fails. For example, due to hardware malfunction. At that point you may use server evacuation in order to make managed instances available again." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_evacuate.xml:14(title) +msgid "Before Evacuation" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_evacuate.xml:16(para) +msgid "With the information about instance configuration, like if it is running on shared storage, you can choose the required evacuation parameters for your case. Use the command to list the hosts and find new host for the evacuated instance. In order to preserve user data on server disk, target host has to have preconfigured shared storage with down host. As well, you have to validate that the current vm host is down. Otherwise the evacuation will fail with error." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_evacuate.xml:31(title) +msgid "To evacuate your server without shared storage:" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_evacuate.xml:32(para) +msgid " performs an instance evacuation from down host to specified host. The instance will be booted from a new disk, but will preserve the configuration, e.g. id, name, uid, ip...etc. New instance password can be passed to the command using the --password <pwd> option. If not given it will be generated and printed after the command finishes successfully." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_evacuate.xml:41(replaceable) ./doc/src/docbkx/common/nova_cli_evacuate.xml:70(replaceable) +msgid "evacuated_server_name" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_evacuate.xml:41(replaceable) ./doc/src/docbkx/common/nova_cli_evacuate.xml:70(replaceable) +msgid "host_b" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_evacuate.xml:43(para) +msgid "The command returns a new server password. " +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_evacuate.xml:60(title) +msgid "Evacuate server to specified host and preserve user data" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_evacuate.xml:61(para) +msgid "In order to preserve the user disk data on the evacuated server the OpenStack Compute should be deployed with shared filesystem. Refer to the shared storage section in the Configure migrations guide in order to configure your system. In this scenario the password will remain unchanged." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_sshkeys.xml:8(title) +msgid "Associating ssh keys with instances" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_sshkeys.xml:11(title) +msgid "Creating New Keys" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_sshkeys.xml:12(para) +msgid "The command: will create a key named mykey which you can associate with instances. Save the file mykey.pem to a secure location as it will allow root access to instances the mykeykey is associated with." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_sshkeys.xml:23(title) +msgid "Uploading Existing Keys" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_sshkeys.xml:24(para) +msgid "The command: will upload the existing public key mykey.pub and associate it with the name mykey. You will need to have the matching private key to access instances associated with this key." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_sshkeys.xml:34(title) +msgid "Adding Keys to Your Instance" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_sshkeys.xml:35(para) +msgid "To associate a key with an instance on boot add --key_name mykey to your command line for example:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:6(title) +msgid "Image Management" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:7(para) +msgid "You can use OpenStack Image Services for discovering, registering, and retrieving virtual machine images. The service includes a RESTful API that allows users to query VM image metadata and retrieve the actual image with HTTP requests, or you can use a client class in your Python code to accomplish the same tasks." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:13(para) +msgid "VM images made available through OpenStack Image Service can be stored in a variety of locations from simple file systems to object-storage systems like the OpenStack Object Storage project, or even use S3 storage either on its own or through an OpenStack Object Storage S3 interface." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:18(para) +msgid "The backend stores that OpenStack Image Service can work with are as follows:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:22(para) +msgid "OpenStack Object Storage - OpenStack Object Storage is the highly-available object storage project in OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:28(para) +msgid "Filesystem - The default backend that OpenStack Image Service uses to store virtual machine images is the filesystem backend. This simple backend writes image files to the local filesystem." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:35(para) +msgid "S3 - This backend allows OpenStack Image Service to store virtual machine images in Amazon’s S3 service." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:41(para) +msgid "HTTP - OpenStack Image Service can read virtual machine images that are available via HTTP somewhere on the Internet. This store is readonly." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:47(para) +msgid "This chapter assumes you have a working installation of the Image Service, with a working endpoint and users created in the Identity service, plus you have sourced the environment variables required by the nova client and glance client." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:55(title) +msgid "Getting virtual machine images" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:58(title) +msgid "CirrOS (test) images" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:59(para) +msgid "Scott Moser maintains a set of small virtual machine images that are designed for testing. These images use cirros as the login user. They are hosted under the CirrOS project on Launchpad andare available for download." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:64(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.0-x86_64-disk.img" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:72(title) +msgid "Ubuntu images" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:73(para) +msgid "Canonical maintains an official set of Ubuntu-based images These accounts use ubuntu as the login user." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:76(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/src/docbkx/common/ch_image_mgmt.xml:83(title) +msgid "Fedora images" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:84(para) +msgid "The Fedora project maintains prebuilt Fedora JEOS (Just Enough OS) images for download at http://berrange.fedorapeople.org/images ." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:88(para) +msgid "A 64-bit QCOW2 image for Fedora 16, f16-x86_64-openstack-sda.qcow2, is available for download." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:93(title) +msgid "openSUSE and SLES 11 images" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:94(para) +msgid "SUSE Studio is an easy way to build virtual appliances for openSUSE and SLES 11 (SUSE Linux Enterprise Server) that are compatible with OpenStack. Free registration is required to download or build images." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:99(para) +msgid "For example, Christian Berendt used openSUSE to create a test openSUSE 12.1 (JeOS) image." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:104(title) +msgid "Rackspace Cloud Builders (multiple distros) images" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:105(para) +msgid "Rackspace Cloud Builders maintains a list of pre-built images from various distributions (RedHat, CentOS, Fedora, Ubuntu) at rackerjoe/oz-image-build on Github." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:113(title) +msgid "Tool support for creating images" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:114(para) +msgid "There are several open-source third-party tools available that simplify the task of creating new virtual machine images." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:117(title) +msgid "Oz (KVM)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:118(para) +msgid "Oz is a command-line tool that has the ability to create images for common Linux distributions. Rackspace Cloud Builders uses Oz to create virtual machines, see rackerjoe/oz-image-build on Github for their Oz templates. For an example from the Fedora Project wiki, see Building an image with Oz." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:128(title) +msgid "VMBuilder (KVM, Xen)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:129(para) +msgid "VMBuilder can be used to create virtual machine images for different hypervisors." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:132(para) +msgid "The Ubuntu 12.04 server guide has documentation on how to use VMBuilder." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:136(title) +msgid "BoxGrinder (KVM, Xen, VMWare)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:137(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/src/docbkx/common/ch_image_mgmt.xml:143(title) +msgid "VeeWee (KVM)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:144(para) +msgid " VeeWee is often used to build Vagrant boxes, but it can also be used to build KVM images." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:148(para) +msgid "See the doc/definition.md and doc/template.md VeeWee documentation files for more details." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:154(title) +msgid "imagefactory" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:155(para) +msgid "imagefactory is a new tool from the Aeolus project designed to automate the building, converting, and uploading images to different cloud providers. It includes support for OpenStack-based clouds." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:164(title) +msgid "Customizing an image for OpenStack" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:165(para) +msgid "This section describes what customizations you should to your image to maximize compatibility with OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:167(title) +msgid "Support metadata service or config drive" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:177(title) +msgid "Support resizing" +msgstr "" + +#. 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 will have a primary disk of 10GB. When an instance's disk +#. is resized up, zeros are just added to the end. +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:185(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/src/docbkx/common/ch_image_mgmt.xml:192(para) +msgid "The image's partition table describes the original size of the image" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:196(para) +msgid "The image's filesystem fills the original size of the image" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:190(para) +msgid "Your image must be configured to deal with two issues:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:199(title) +msgid "Adjusting the partition table on instance boot" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:200(para) +msgid "Your image will need to run a script on boot to modify the partition table. Due to a limitation in the Linux kernel, you cannot modify a partition table of a disk that has partition currently mounted (you can for LVM, but not for \"raw disks\"); this partition adjustment has to happen inside the initramfs before the root volume is mounted, or a reboot has to be done to free the mount of /." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:206(para) +msgid "Ubuntu cloud images and cirros images use a tool called that is part of the cloud-utils package." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:211(title) +msgid "Adjusting the filesystem" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:212(para) +msgid "You will need to resize the file system in addition to the partition table. If you have cloud-init installed, it will do the resize assuming the partition tables have been adjusted properly. Cirros images run resize2fs on the root partition on boot." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:220(para) +msgid "auto_disk_config=True in nova.conf." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:223(para) +msgid "The disk on the image has only one partition." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:226(para) +msgid "The file system on the one partition is ext3 or ext4." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:216(para) +msgid "If you are using XenServer as your hypervisor, the above steps are not needed as 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/src/docbkx/common/ch_image_mgmt.xml:234(title) +msgid "Creating raw or QCOW2 images" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:239(para) +msgid "QCOW2 images are only supported with KVM and QEMU hypervisors." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:235(para) +msgid "This section describes how to create a raw or QCOW2 image from a Linux installation ISO file. Raw images are the simplest image file format and are supported by all of the hypervisors. QCOW2 images have several advantages over raw images. They take up less space than raw images (growing in size as needed), and they support snapshots." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:241(para) +msgid "As an example, this section will describe how to create aa CentOS 6.2 image. 64-bit ISO images of CentOS 6.2 can be downloaded from one of the CentOS mirrors. This example uses the CentOS netinstall ISO, which is a smaller ISO file that downloads packages from the Internet as needed." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:246(title) +msgid "Create an empty image (raw)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:247(para) +msgid "Here we create a a 5GB raw image using the command: " +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:250(title) +msgid "Create an empty image (QCOW2)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:251(para) +msgid "Here we create a a 5GB QCOW2 image using the command: " +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:255(title) +msgid "Boot the ISO using the image" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:256(para) +msgid "First, find a spare vnc display. (Note that vnc display :N correspond to TCP port 5900+N, so that :0 corresponds to port 5900). Check which ones are currently in use with the command, as root:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:263(para) +msgid "This shows that vnc displays :0 and :1 are in use. In this example, we will use VNC display :2." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:265(para) +msgid "Also, we want a temporary file to send power signals to the VM instance. We default to /tmp/file.mon, but make sure it doesn't exist yet. If it does, use a different file name for the MONITOR variable defined below:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:277(title) +msgid "Connect to the instance via VNC" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:278(para) +msgid "VNC is a remote desktop protocol that will give you full-screen display access to the virtual machine instance, as well as let you interact with keyboard and mouse. Use a VNC client (e.g., Vinagre on Gnome, Krdc on KDE, xvnc4viewer from RealVNC, xtightvncviewer from TightVNC) to connect to the machine using the display you specified. You should now see a CentOS install screen." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:288(title) +msgid "Point the installer to a CentOS web server" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:292(para) +msgid "Web site name: mirror.umd.edu (consider using other mirrors as an alternative)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:296(para) +msgid "CentOS directory: centos/6.2/os/x86_64" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:289(para) +msgid "The CentOS net installer requires that the user specify the web site and a CentOS directory that corresponds to one of the CentOS mirrors. " +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:299(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/src/docbkx/common/ch_image_mgmt.xml:304(title) +msgid "Partition the disks" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:305(para) +msgid "There are different options for partitioning the disks. The default installation will use LVM partitions, and will create three partitions (/boot, /, swap). The simplest approach is to create a single ext4 partition, mounted to \"/\"." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:312(title) +msgid "Step through the install" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:313(para) +msgid "The simplest thing to do is to choose the \"Server\" install, which will install an SSH server." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:317(title) +msgid "When install completes, shut down the instance" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:318(para) +msgid "Power down the instance using the monitor socket file to send a power down signal, as root:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:324(title) +msgid "Start the instance again without the ISO" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:335(title) +msgid "Connect to instance via VNC" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:336(para) +msgid "When you boot the first time, it will ask you about authentication tools, you can just choose 'Exit'. Then, log in as root using the root password you specified." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:341(title) +msgid "Edit HWADDR from eth0 config file" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:342(para) +msgid "The operating system records the MAC address of the virtual ethernet card in /etc/sysconfig/network-scripts/ifcfg-eth0 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/src/docbkx/common/ch_image_mgmt.xml:347(para) +msgid "Edit /etc/sysconfig/network-scripts/ifcfg-eth0 and remove the HWADDR= line." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:351(title) +msgid "Configure to fetch metadata" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:356(para) +msgid "Install a cloud-init RPM , which is a port of the Ubuntu cloud-init package. This is the recommended approach." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:363(para) ./doc/src/docbkx/common/ch_image_mgmt.xml:921(para) +msgid "Modify /etc/rc.local to fetch desired information from the metadata service, as described below." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:352(para) +msgid "An instance must perform several steps on startup by interacting with the metada service (e.g., retrieve ssh public key, execute user data script). There are several ways to implement this functionality, including:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:369(title) +msgid "Using cloud-init to fetch the public key" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:370(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 virtual machines, the account is called \"ubuntu\". On Fedora-based virtual machines, the account is called \"ec2-user\"." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:374(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/src/docbkx/common/ch_image_mgmt.xml:380(title) +msgid "Writing a script to fetch the public key" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:381(para) ./doc/src/docbkx/common/ch_image_mgmt.xml:925(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”" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:396(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/src/docbkx/common/ch_image_mgmt.xml:397(para) ./doc/src/docbkx/common/ch_image_mgmt.xml:940(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/src/docbkx/common/ch_image_mgmt.xml:402(para) ./doc/src/docbkx/common/ch_image_mgmt.xml:945(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/src/docbkx/common/ch_image_mgmt.xml:410(title) +msgid "Shut down the instance" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:411(para) +msgid "From inside the instance, as root:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:414(title) +msgid "Modifying the image (raw)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:415(para) +msgid "You can make changes to the filesystem of an image without booting it, by mounting the image as a file system. To mount a raw image, you need to attach it to a loop device (e.g., /dev/loop0, /dev/loop1). To identify the next unused loop device, as root:In the example above, /dev/loop0 is available for use. Associate it to the image using , and expose the partitions as device files using , as root:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:429(para) +msgid "If the image has, say three partitions (/boot, /, /swap), there should be one new device created per partition:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:434(para) ./doc/src/docbkx/common/ch_image_mgmt.xml:470(para) +msgid "To mount the second partition, as root:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:437(para) +msgid "You can now modify the files in the image by going to /mnt/image. When done, unmount the image and release the loop device, as root:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:444(title) +msgid "Modifying the image (qcow2)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:448(para) +msgid "If nbd has already been loaded with max_part=0, you will not be able to mount an image if it has multiple partitions. In this case, you may need to first unload the nbd kernel module, and then load it. To unload it, as root:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:445(para) +msgid "You can make changes to the filesystem of an image without booting it, by mounting the image as a file system. To mount a QEMU image, you need the nbd kernel module to be loaded. Load the nbd kernel module, as root:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:454(para) +msgid "Connect your image to one of the network block devices (e.g., /dev/nbd0, /dev/nbd1). In this example, we use /dev/nbd3. As root:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:465(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/src/docbkx/common/ch_image_mgmt.xml:459(para) +msgid "If the image has, say three partitions (/boot, /, /swap), there should be one new device created per partition:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:473(para) +msgid "You can now modify the files in the image by going to /mnt/image. When done, unmount the image and release the network block device, as root:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:480(title) +msgid "Upload the image to glance (raw)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:488(title) +msgid "Upload the image to glance (qcow2)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:498(title) +msgid "Booting a test image" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:499(para) +msgid "The following assumes you are using QEMU or KVM in your deployment." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:501(para) +msgid "Download a CirrOS test image:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:505(para) +msgid "Add the image to glance:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:511(para) +msgid "Check that adding the image was successful (Status should be ACTIVE when the operation is complete):" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:523(para) +msgid "Create a keypair so you can ssh to the instance:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:529(para) +msgid "In general, you need to use an ssh keypair to log in to a running instance, although some images have built-in accounts created with associated passwords. However, since images are often shared by many users, it is not advised to put passwords into the images. Nova therefore supports injecting ssh keys into instances before they are booted. This allows a user to login to the instances that he or she creates securely. Generally the first thing that a user does when using the system is create a keypair." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:535(para) +msgid "Keypairs provide secure authentication to your instances. As part of the first boot of a virtual image, the private key of your keypair is added to authorized_keys file of the login account. Nova generates a public and private key pair, and sends the private key to the user. The public key is stored so that it can be injected into instances." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:538(para) +msgid "Run (boot) a test instance:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:542(para) +msgid "Here's a description of the parameters used above:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:544(para) +msgid "--image: the name or ID of the image we want to launch, as shown in the output of " +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:548(para) +msgid "--flavor: the name or ID of the size of the instance to create (number of vcpus, available RAM, available storage). View the list of available flavors by running " +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:554(para) +msgid "-key_name: the name of the key to inject in to the instance at launch." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:559(para) +msgid "Check the status of the instance you launched:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:563(para) +msgid "The instance will go from BUILD to ACTIVE in a short time, and you should be able to connect via ssh as 'cirros' user, using the private key you created. If your ssh keypair fails for some reason, you can also log in with the default cirros password: cubswin:)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:571(para) +msgid "The 'cirros' user is part of the sudoers group, so you can escalate to 'root' via the following command when logged in to the instance:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:581(title) +msgid "Tearing down (deleting) Instances" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:583(para) +msgid "When you are done with an instance, you can tear it down using the command, passing either the instance name or instance ID as the argument. You can get a listing of the names and IDs of all running instances using the . For example:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:603(title) +msgid "Pausing and Suspending Instances" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:604(para) +msgid "Since the release of the API in its 1.1 version, it is possible to pause and suspend instances." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:607(para) +msgid "Pausing and Suspending instances only apply to KVM-based hypervisors and XenServer/XCP Hypervisors." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:611(para) +msgid "Pause/ Unpause : Stores the content of the VM in memory (RAM)." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:613(para) +msgid "Suspend/ Resume : Stores the content of the VM on disk." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:615(para) +msgid "It can be interesting for an administrator to suspend instances, if a maintenance is planned; or if the instance are not frequently used. Suspending an instance frees up memory and vCPUS, while pausing keeps the instance running, in a \"frozen\" state. Suspension could be compared to an \"hibernation\" mode." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:622(title) +msgid "Pausing instance" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:623(para) +msgid "To pause an instance :" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:625(para) +msgid "To resume a paused instance :" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:629(title) +msgid "Suspending instance" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:630(para) +msgid "To suspend an instance :" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:632(para) +msgid "To resume a suspended instance :" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:637(title) +msgid "Select a specific host to boot instances on" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:638(para) +msgid "With the Folsom release it is no longer possible to indicate a specific compute host to use to boot an instance with the --force_hosts parameter. See bug 1061665 for further discussion." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:644(title) +msgid "Select a specific zone to boot instances on" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:645(para) +msgid "It is possible to specify which availability zone to run the instance on using the nova client. In order to use such feature, make sure you are using an admin account." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:648(para) +msgid "You can determine the current active zone by looking at the nova.conf file for the compute node and seeing the node_availability_zone=yyyyy where yyyyy is the name of the zone the host is affiliated with." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:652(para) +msgid "We see here our \"server2\" lives in the \"nova\" availabilty zone. You can now select the host on which the instance would be spawned, using the \"--availability-zone\" parameter as an admin." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:656(para) +msgid "The --force_hosts scheduler hint has been replaced with --availability_zone in the Folsom release." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:665(orgname) +msgid "CSS Corp- Open Source Services" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:667(title) +msgid "Creating custom images" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:669(para) +msgid "by CSS Corp Open Source Services" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:672(para) +msgid "There are several pre-built images for OpenStack available from various sources. You can download such images and use them to get familiar with OpenStack. You can refer to http://docs.openstack.org/trunk/openstack-compute/admin/content/starting-images.html for details on using such images." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:679(para) +msgid "For any production deployment, you may like to have the ability to bundle custom images, with a custom set of applications or configuration. This chapter will guide you through the process of creating Linux images of Debian and Redhat based distributions from scratch. We have also covered an approach to bundling Windows images." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:685(para) +msgid "There are some minor differences in the way you would bundle a Linux image, based on the distribution. Ubuntu makes it very easy by providing cloud-init package, which can be used to take care of the instance configuration at the time of launch. cloud-init handles importing ssh keys for password-less login, setting hostname etc. The instance acquires the instance specific configuration from Nova-compute by connecting to a meta data interface running on 169.254.169.254." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:694(para) +msgid "While creating the image of a distro that does not have cloud-init or an equivalent package, you may need to take care of importing the keys etc. by running a set of commands at boot time from rc.local." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:698(para) +msgid "The process used for Ubuntu and Fedora is largely the same with a few minor differences, which are explained below." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:702(para) +msgid "In both cases, the documentation below assumes that you have a working KVM installation to use for creating the images. We are using the machine called ‘client1′ as explained in the chapter on “Installation and Configuration” for this purpose." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:708(para) +msgid "The approach explained below will give you disk images that represent a disk without any partitions. Nova-compute can resize such disks ( including resizing the file system) based on the instance type chosen at the time of launching the instance. These images cannot have ‘bootable’ flag and hence it is mandatory to have associated kernel and ramdisk images. These kernel and ramdisk images need to be used by nova-compute at the time of launching the instance." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:717(para) +msgid "However, we have also added a small section towards the end of the chapter about creating bootable images with multiple partitions that can be used by nova to launch an instance without the need for kernel and ramdisk images. The caveat is that while nova-compute can re-size such disks at the time of launching the instance, the file system size is not altered and hence, for all practical purposes, such disks are not re-sizable." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:726(title) +msgid "Creating a Linux Image – Ubuntu & Fedora" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:729(para) +msgid "The first step would be to create a raw image on Client1. This will represent the main HDD of the virtual machine, so make sure to give it as much space as you will need." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:738(title) +msgid "OS Installation" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:739(para) +msgid "Download the iso file of the Linux distribution you want installed in the image. The instructions below are tested on Ubuntu 11.04 Natty Narwhal 64-bit server and Fedora 14 64-bit. Most of the instructions refer to Ubuntu. The points of difference between Ubuntu and Fedora are mentioned wherever required." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:749(para) +msgid "Boot a KVM Instance with the OS installer ISO in the virtual CD-ROM. This will start the installation process. The command below also sets up a VNC display at port 0" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:756(para) +msgid "Connect to the VM through VNC (use display number :0) and finish the installation." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:758(para) +msgid "For Example, where 10.10.10.4 is the IP address of client1:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:763(para) +msgid "During the installation of Ubuntu, create a single ext4 partition mounted on ‘/’. Do not create a swap partition." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:766(para) +msgid "In the case of Fedora 14, the installation will not progress unless you create a swap partition. Please go ahead and create a swap partition." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:771(para) +msgid "After finishing the installation, relaunch the VM by executing the following command." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:776(para) +msgid "At this point, you can add all the packages you want to have installed, update the installation, add users and make any configuration changes you want in your image." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:780(para) +msgid "At the minimum, for Ubuntu you may run the following commands" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:787(para) +msgid "For Fedora run the following commands as root" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:795(para) +msgid "Also remove the network persistence rules from /etc/udev/rules.d as their presence will result in the network interface in the instance coming up as an interface other than eth0." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:802(para) +msgid "Shutdown the Virtual machine and proceed with the next steps." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:806(title) +msgid "Extracting the EXT4 partition" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:807(para) +msgid "The image that needs to be uploaded to OpenStack needs to be an ext4 filesystem image. Here are the steps to create a ext4 filesystem image from the raw image i.e server.img" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:815(para) ./doc/src/docbkx/common/ch_image_mgmt.xml:827(para) +msgid "You should see an output like this:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:819(para) +msgid "Observe the name of the loop device ( /dev/loop0 in our setup) when $filepath is the path to the mounted .raw file." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:822(para) +msgid "Now we need to find out the starting sector of the partition. Run:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:839(para) +msgid "Make a note of the starting sector of the /dev/loop0p1 partition i.e the partition whose ID is 83. This number should be multiplied by 512 to obtain the correct value. In this case: 2048 x 512 = 1048576" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:844(para) +msgid "Unmount the loop0 device:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:848(para) +msgid "Now mount only the partition(/dev/loop0p1) of server.img which we had previously noted down, by adding the -o parameter with value previously calculated value" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:856(para) +msgid "You’ll see a message like this:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:860(para) +msgid "Make a note of the mount point of our device(/dev/loop0 in our setup) when $filepath is the path to the mounted .raw file." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:863(para) +msgid "Copy the entire partition to a new .raw file" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:868(para) +msgid "Now we have our ext4 filesystem image i.e serverfinal.img" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:871(para) +msgid "Unmount the loop0 device" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:877(title) +msgid "Tweaking /etc/fstab" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:878(para) +msgid "You will need to tweak /etc/fstab to make it suitable for a cloud instance. Nova-compute may resize the disk at the time of launch of instances based on the instance type chosen. This can make the UUID of the disk invalid. Hence we have to use File system label as the identifier for the partition instead of the UUID." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:885(para) +msgid "Loop mount the serverfinal.img, by running" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:890(para) +msgid "Edit /mnt/etc/fstab and modify the line for mounting root partition(which may look like the following)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:897(para) +msgid "to" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:904(title) +msgid "Fetching Metadata in Fedora" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:910(para) +msgid "Install a cloud-initRPM , which is a port of the Ubuntu cloud-init package." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:916(para) +msgid "Install Condenser, an alternate version of cloud-init." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:905(para) +msgid "An instance must perform several steps on startup by interacting with the metadata service (e.g., retrieve ssh public key, execute user data script). When building a Fedora image, there are several options for implementing this functionality, including:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:952(title) +msgid "Kernel and Initrd for OpenStack" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:954(para) +msgid "Copy the kernel and the initrd image from /mnt/boot to user home directory. These will be used later for creating and uploading a complete virtual image to OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:961(para) +msgid "Unmount the Loop partition" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:965(para) +msgid "Change the filesystem label of serverfinal.img to ‘uec-rootfs’" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:970(para) +msgid "Now, we have all the components of the image ready to be uploaded to OpenStack imaging server." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:974(title) +msgid "Registering with OpenStack" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:975(para) +msgid "The last step would be to upload the images to OpenStack Image Service. The files that need to be uploaded for the above sample setup of Ubuntu are: vmlinuz-2.6.38-7-server, initrd.img-2.6.38-7-server, serverfinal.img" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:980(para) +msgid "Run the following command" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:984(para) +msgid "For Fedora, the process will be similar. Make sure that you use the right kernel and initrd files extracted above." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:987(para) +msgid "The uec-publish-image command returns the prompt back immediately. However, the upload process takes some time and the images will be usable only after the process is complete. You can keep checking the status using the command as mentioned below." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:995(title) +msgid "Bootable Images" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:996(para) +msgid "You can register bootable disk images without associating kernel and ramdisk images. When you do not want the flexibility of using the same disk image with different kernel/ramdisk images, you can go for bootable disk images. This greatly simplifies the process of bundling and registering the images. However, the caveats mentioned in the introduction to this chapter apply. Please note that the instructions below use server.img and you can skip all the cumbersome steps related to extracting the single ext4 partition." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1012(title) +msgid "Image Listing" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1013(para) +msgid "The status of the images that have been uploaded can be viewed by using nova image-list command. The output should like this:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1029(title) +msgid "Creating a Windows Image" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1030(para) +msgid "The first step would be to create a raw image on Client1, this will represent the main HDD of the virtual machine, so make sure to give it as much space as you will need." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1037(para) +msgid "OpenStack presents the disk using aVIRTIO interface while launching the instance. Hence the OS needs to have drivers for VIRTIO. By default, the Windows Server 2008 ISO does not have the drivers for VIRTIO. Sso download a virtual floppy drive containing VIRTIO drivers from the following location" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1045(link) +msgid "http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1046(para) +msgid "and attach it during the installation" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1047(para) +msgid "Start the installation by running" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1051(para) +msgid "When the installation prompts you to choose a hard disk device you won’t see any devices available. Click on “Load drivers” at the bottom left and load the drivers from A:\\i386\\Win2008" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1055(para) +msgid "After the Installation is over, boot into it once and install any additional applications you need to install and make any configuration changes you need to make. Also ensure that RDP is enabled as that would be the only way you can connect to a running instance of Windows. Windows firewall needs to be configured to allow incoming ICMP and RDP connections." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1062(para) +msgid "For OpenStack to allow incoming RDP Connections, use commands to open up port 3389." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1064(para) +msgid "Shut-down the VM and upload the image to OpenStack" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1071(title) +msgid "Creating images from running instances with KVM and Xen" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1081(emphasis) +msgid "Pre-requisites (KVM)" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1083(para) +msgid "In order to use the feature properly, you will need 0.14 or greater. The imaging feature uses the copy from a snapshot for image files. (e.g qcow-img convert -f qcow2 -O qcow2 -s $snapshot_name $instance-disk)." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1089(para) +msgid "On Debian-like distros, you can check the version by running : " +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1097(para) +msgid "Images can only be created from running instances if Compute is configured to use qcow2 images, which is the default setting. You can explicitly enable the use of qcow2 images by adding the following line to nova.conf: " +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1109(emphasis) +msgid "Write data to disk" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1111(para) +msgid "Before creating the image, we need to make sure we are not missing any buffered content that wouldn't have been written to the instance's disk. In order to resolve that ; connect to the instance and run then exit." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1120(emphasis) +msgid "Create the image" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1138(para) +msgid "The image that will be created will be flagged as \"Private\" (For glance : --is-public=False). Thus, the image will be available only for the tenant." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1123(para) +msgid "In order to create the image, we first need obtain the server id : Based on the output, we run : The command will then perform the image creation (by creating qemu snapshot) and will automatically upload the image to your repository. " +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1148(emphasis) +msgid "Check image status" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1151(para) +msgid "After a while the image will turn from a \"SAVING\" state to an \"ACTIVE\" one. will allow you to check the progress : " +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1170(emphasis) +msgid "Create an instance from the image" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1173(para) +msgid "You can now create an instance based on this image as you normally do for other images :" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1183(para) +msgid "Mainly, it wouldn't take more than 5 minutes in order to go from a \"SAVING\" to the \"ACTIVE\" state. If this takes longer than five minutes, here are several hints:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1187(para) +msgid "- The feature doesn't work while you have attached a volume (via nova-volume) to the instance. Thus, you should dettach the volume first, create the image, and re-mount the volume." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1192(para) +msgid "- Make sure the version of qemu you are using is not older than the 0.14 version. That would create \"unknown option -s\" into nova-compute.log." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1196(para) +msgid "- Look into nova-api.log and nova-compute.log for extra information." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1073(para) +msgid "It is possible to create an image from a running instance on KVM and Xen. This is a convenient way to spawn pre-configured instances; update them according to your needs ; and re-image the instances. The process to create an image from a running instance is quite simple : " +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1203(title) +msgid "Replicating images across multiple data centers" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1204(para) +msgid "The image service comes with a tool called that can be used to populate a new glance server using the images stored in an existing glance server. The images in the replicated glance server preserve the uuids, metadata, and image data from the original. Running the tool will output a set of commands that it supports:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1244(para) +msgid "The replicator supports the following commands:" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1246(title) +msgid "livecopy: Load the contents of one glance instance into another" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1248(replaceable) ./doc/src/docbkx/common/ch_image_mgmt.xml:1312(replaceable) +msgid "fromserver:port" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1248(replaceable) ./doc/src/docbkx/common/ch_image_mgmt.xml:1312(replaceable) +msgid "toserver:port" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1253(para) +msgid "fromserver:port: the location of the master glance instance" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1257(para) +msgid "toserver:port: the location of the slave glance instance." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1262(para) +msgid "Take a copy of the fromserver, and dump it onto the toserver. Only images visible to the user running the replicator will be copied if glance is configured to use the Identity service (keystone) for authentication. Only images active on fromserver are copied across. The copy is done \"on-the-wire\" so there are no large temporary files on the machine running the replicator to clean up." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1270(title) +msgid "dump: Dump the contents of a glance instance to local disk" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1272(replaceable) +msgid "server:port" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1272(replaceable) +msgid "path" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1276(para) ./doc/src/docbkx/common/ch_image_mgmt.xml:1296(para) ./doc/src/docbkx/common/ch_image_mgmt.xml:1329(para) +msgid "server:port: the location of the glance instance." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1280(para) +msgid "path: a directory on disk to contain the data." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1274(para) +msgid "Do the same thing as , but dump the contents of the glance server to a directory on disk. This includes metadata and image data. Depending on the size of the local glance repository, the resulting dump may consume a large amount of local storage. Therefore, we recommend you use the comamnd first to determine the size of the resulting dump." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1291(title) +msgid "load: Load a directory created by the dump command into a glance server" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1300(para) +msgid "path: a directory on disk containing the data." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1305(para) +msgid "Load the contents of a local directory into glance." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1306(para) +msgid "The and are useful when replicating across two glance servers where a direct connection across the two glance hosts is impossible or too slow." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1311(title) +msgid "compare: Compare the contents of two glance servers" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1314(para) +msgid "fromserver:port: the location of the master glance instance." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1318(para) +msgid " toserver:port: the location of the slave glance instance." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1312(para) +msgid "The command will show you the differences between the two servers, which is effectively a dry run of the command." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1326(title) +msgid "size: Determine the size of a glance instance if dumped to disk" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1327(para) +msgid "The command will tell you how much disk is going to be used by image data in either a or a . Note that this will provide raw number of bytes that would be written to the destination, it has no information about the redundancy costs associated with glance-registry back-ends that use replication for redundancy, such as Swift or Ceph." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1340(title) +msgid "Example using livecopy" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1341(para) +msgid "Assuming you have a primary glance service running on a node called primary.example.com with glance-api service running on port 9292 (the default port) and you want to replicate its contents to a secondary glance service running on a node called secondary.example.com, also on port 9292, you will first need to get authentication tokens from keystone for the primary and secondary glance server and then you can use the glance-replicator livecopy command." +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1360(replaceable) +msgid "8e97fa8bcf4443cfbd3beb9079c7142f" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1371(replaceable) +msgid "29f777ac2c9b41a6b4ee9c3e6b85f98a" +msgstr "" + +#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1348(para) +msgid "The following example assumes that you have a credentials file for your primary cloud called primary.openrc and one for your secondary cloud called secondary.openrc." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/common/vmware.xml:16(None) +msgid "@@image: 'figures/vmwareapi_blockdiagram.jpg'; md5=0621a71746e28754fefa28e7a451eed0" +msgstr "" + +#: ./doc/src/docbkx/common/vmware.xml:6(title) +msgid "VMware ESX/ESXi Server Support" +msgstr "" + +#: ./doc/src/docbkx/common/vmware.xml:10(para) +msgid "OpenStack Compute supports the VMware ESX hypervisor. This section describes the additional configuration required to launch VMWare-based virtual machine images." +msgstr "" + +#: ./doc/src/docbkx/common/vmware.xml:23(title) +msgid "Prerequisites" +msgstr "" + +#: ./doc/src/docbkx/common/vmware.xml:24(para) +msgid "You will need to install the following software:" +msgstr "" + +#: ./doc/src/docbkx/common/vmware.xml:26(para) +msgid "python-suds: This software is needed by the nova-compute service. If not installed, the \"nova-compute\" service shuts down with the message: \"Unable to import suds\"." +msgstr "" + +#: ./doc/src/docbkx/common/vmware.xml:28(para) +msgid "SSH server" +msgstr "" + +#: ./doc/src/docbkx/common/vmware.xml:29(para) +msgid "Tomcat server" +msgstr "" + +#: ./doc/src/docbkx/common/vmware.xml:31(para) +msgid "On ubuntu, these packages can be installed by doing (as root):" +msgstr "" + +#: ./doc/src/docbkx/common/vmware.xml:36(title) +msgid "Configure Tomcat to serve WSDL files" +msgstr "" + +#: ./doc/src/docbkx/common/vmware.xml:37(para) +msgid "Download the the SDK from http://www.vmware.com/support/developer/vc-sdk/ and copy it into /var/lib/tomcat6/webapps. You should ensure that the WSDL is available, in eg /var/lib/tomcat6/webapps/vmware/SDK/wsdl/vim25/vimService.wsdl." +msgstr "" + +#: ./doc/src/docbkx/common/vmware.xml:41(title) +msgid "VMWare configuration options" +msgstr "" + +#: ./doc/src/docbkx/common/vmware.xml:42(para) +msgid "Configure nova.conf with the following VMWare-specific config options:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:42(None) ./doc/src/docbkx/common/trusted-compute-pools.xml:46(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/src/docbkx/common/trusted-compute-pools.xml:125(None) ./doc/src/docbkx/common/trusted-compute-pools.xml:128(None) +msgid "@@image: 'figures/OpenStackTrustedComputePool2.png'; md5=077261c595464638c4b3fcc92b6afb9a" +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:8(title) +msgid "Trusted Compute Pools" +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:11(para) +msgid "Trusted compute pools enables administrators to designate a group of compute hosts as \"trusted\". These hosts use hardware-based security features, such as Intel's Trusted Execution Technology (TXT), to provide an additional level of security. Combined with an external standalone web-based remote attestation server, cloud providers can ensure that the compute node is running software with verified measurements, thus they can establish the foundation for the secure cloud stack. Through the Trusted Computing Pools, cloud subscribers can request services to be run on verified compute nodes." +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:20(para) +msgid "Compute nodes boot with Intel TXT technology enabled." +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:23(para) +msgid "The compute node's BIOS, hypervisor and OS are measured." +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:26(para) +msgid "These measured data is sent to the attestation server when challenged by attestation server." +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:30(para) +msgid "The attestation server verifies those measurements against good/known database to determine nodes' trustworthiness." +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:18(para) +msgid "The remote attestation server performs node verification through the following steps:" +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:34(para) +msgid "A description of how to set up an attestation service is beyond the scope of this document. See the Open Attestation project for an open source project that can be used to implement an attestation service." +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:52(title) +msgid "Configuring the Compute service to use Trusted Compute Pools" +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:58(term) ./doc/src/docbkx/common/glossary/glossary-terms.xml:3997(glossterm) +msgid "server" +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:60(para) +msgid "Hostname or IP address of the host that runs the attestation service" +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:65(term) ./doc/src/docbkx/common/glossary/glossary-terms.xml:3287(glossterm) +msgid "port" +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:67(para) +msgid "HTTPS port for the attestation service" +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:71(term) +msgid "server_ca_file" +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:73(para) +msgid "Certificate file used to verify the attestation server's identity." +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:78(term) +msgid "api_url" +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:80(para) +msgid "The attestation service URL path." +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:84(term) +msgid "auth_blob" +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:86(para) +msgid "An authentication blob, which is required by the attestation service." +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:53(para) +msgid "The Compute service must be configured to with the connection information for the attestation service. The connection information is specified in the trusted_computing section of nova.conf. Specify the following parameters in this section.Add the following lines to /etc/nova/nova.conf in the DEFAULT and trusted_computing sections to enable scheduling support for Trusted Compute Pools, and edit the details of the trusted_computing section based on the details of your attestation service." +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:109(para) +msgid "Restart the nova-compute and nova-scheduler services after making these changes." +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:112(title) +msgid "Specify trusted flavors" +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:113(para) +msgid "One or more flavors must be configured as \"trusted\". Users can then request trusted nodes by specifying one of these trusted flavors when booting a new instance. Use the command to set a flavor as trusted. For example, to set the m1.tiny flavor as trusted:" +msgstr "" + +#: ./doc/src/docbkx/common/trusted-compute-pools.xml:120(para) +msgid "A user can request that their instance runs on a trusted host by specifying a trusted flavor when invoking the command." +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:5(title) +msgid "Troubleshooting OpenStack Compute" +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:6(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 ping or ssh from a compute node to the instances running on that node. Another common problem is trying to run 32-bit images on a 64-bit compute node. This section offers more information about how to troubleshoot Compute." +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:7(title) +msgid "Log files for OpenStack Compute" +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:7(para) +msgid "Log files are stored in /var/log/nova and there is a log file for each service, for example nova-compute.log. You can format the log strings using options for the nova.log module. The options used to set format strings are: logging_context_format_string and logging_default_format_string. 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/src/docbkx/common/support-compute.xml:14(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, and then the nova daemon logs to syslog." +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:18(title) +msgid "Common Errors and Fixes for OpenStack Compute" +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:19(para) +msgid "The Launchpad Answers 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 to Launchpad Answers and IRC. We are constantly fixing bugs, so online resources are a great way to get the most up-to-date errors and fixes." +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:20(para) +msgid "Credential errors, 401, 403 forbidden errors" +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:21(para) +msgid "A 403 forbidden error is caused by missing credentials. Through current installation methods, there are basically two ways to get the novarc file. The manual method requires getting it from within a project zipfile, and the scripted method just generates novarc out of the project zip file and sources it for you. If you do the manual method through a zip file, then the following novarc alone, you end up losing the creds that are tied to the user you created with nova-manage in the steps before." +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:22(para) +msgid "When you run nova-api the first time, it generates the certificate authority information, including openssl.cnf. If it gets started out of order, you may not be able to create your zip file. Once your CA information is available, you should be able to go back to nova-manage to create your zipfile." +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:22(para) +msgid "You may also need to check your proxy settings to see if they are causing problems with the novarc creation." +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:23(para) +msgid "Instance errors" +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:24(para) +msgid "Sometimes a particular instance shows \"pending\" or you cannot SSH to it. Sometimes the image itself is the problem. For example, when using flat manager networking, you do not have a dhcp server, and an ami-tiny image doesn't support interface injection so you cannot connect to it. The fix for this type of problem is to use an Ubuntu image, which should obtain an IP address correctly with FlatManager network settings. To troubleshoot other possible problems with an instance, such as one that stays in a spawning state, first check your instances directory for i-ze0bnh1q dir to make sure it has the following files:" +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:25(para) +msgid "libvirt.xml" +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:26(para) +msgid "disk" +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:27(para) +msgid "disk-raw" +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:28(para) +msgid "kernel" +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:29(para) +msgid "ramdisk" +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:30(para) +msgid "console.log (Once the instance actually starts you should see a console.log.)" +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:32(para) +msgid "Check the file sizes to see if they are reasonable. If any are missing/zero/very small then nova-compute has somehow not completed download of the images from objectstore." +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:33(para) +msgid "Also check nova-compute.log for exceptions. Sometimes they don't show up in the console output." +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:34(para) +msgid "Next, check the /var/log/libvirt/qemu/i-ze0bnh1q.log file to see if it exists and has any useful error messages in it." +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:37(para) +msgid "Finally, from the instances/i-ze0bnh1q directory, try virsh create libvirt.xml and see if you get an error there." +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:40(title) +msgid "Manually reset the state of an instance" +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:41(para) +msgid "If an instance gets stuck in an intermediate state (e.g., \"deleting\"), you can manually reset the state of an instance using the command. This will reset it to an error state, which you can then delete. For example:" +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:47(para) +msgid "You can also use the --active to force the instance back into an active state instead of an error state, for example:" +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:52(title) +msgid "Problems with Injection" +msgstr "" + +#: ./doc/src/docbkx/common/support-compute.xml:53(para) +msgid "If you are diagnosing problems with instances not booting, or booting slowly, consider investigating file injection as a cause. Setting libvirt_injection_partition to -2 disables injection in libvirt. This can be required if you want to make user specified files available from the metadata server (and config drive is not enabled), for performance reasons, and also to avoid boot failure if injection itself fails." +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:8(title) +msgid "Disk and Container Formats for Images" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:10(para) +msgid "When adding an image to the Image service (glance), you may specify what the virtual machine image’s disk format and container format are." +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:12(para) +msgid "This document explains exactly what these formats are." +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:14(title) +msgid "Disk Format" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:15(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/src/docbkx/common/image-formats.xml:18(para) +msgid "You can set your image’s disk format to one of the following:" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:20(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:3602(glossterm) +msgid "raw" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:21(para) +msgid "This is an unstructured disk image format; if you have a file without an extension it is possibly a raw format" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:23(para) +msgid "vhd" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:24(para) +msgid "This is the VHD disk format, a common disk format used by virtual machine monitors from VMWare, Xen, Microsoft, VirtualBox, and others" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:27(para) +msgid "vmdk" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:28(para) +msgid "Another common disk format supported by many common virtual machine monitors" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:30(para) +msgid "vdi" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:31(para) +msgid "A disk format supported by VirtualBox virtual machine monitor and the QEMU emulator" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:34(para) +msgid "iso" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:35(para) +msgid "An archive format for the data contents of an optical disc (e.g. CDROM)" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:37(para) +msgid "qcow2" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:38(para) +msgid "A disk format supported by the QEMU emulator that can expand dynamically and supports Copy on Write" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:41(para) ./doc/src/docbkx/common/image-formats.xml:67(para) +msgid "aki" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:42(para) ./doc/src/docbkx/common/image-formats.xml:68(para) +msgid "This indicates what is stored in Glance is an Amazon kernel image" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:44(para) ./doc/src/docbkx/common/image-formats.xml:70(para) +msgid "ari" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:45(para) ./doc/src/docbkx/common/image-formats.xml:71(para) +msgid "This indicates what is stored in Glance is an Amazon ramdisk image" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:47(para) ./doc/src/docbkx/common/image-formats.xml:73(para) +msgid "ami" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:48(para) ./doc/src/docbkx/common/image-formats.xml:74(para) +msgid "This indicates what is stored in Glance is an Amazon machine image" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:53(title) +msgid "Container Format" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:54(para) +msgid "The container format refers to whether the virtual machine image is in a file format that also contains metadata about the actual virtual machine." +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:56(para) +msgid "Note that the container format string is not currently used by Glance or other OpenStack components, so it is safe to simply specify bare as the container format if you are unsure." +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:59(para) +msgid "You can set your image’s container format to one of the following:" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:61(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:515(glossterm) +msgid "bare" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:62(para) +msgid "This indicates there is no container or metadata envelope for the image" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:64(para) +msgid "ovf" +msgstr "" + +#: ./doc/src/docbkx/common/image-formats.xml:65(para) +msgid "This is the OVF container format" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:6(title) +msgid "Storage Concepts" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:7(para) +msgid "Storage is found in many parts of the OpenStack stack, and the differing types can cause confusion to even experienced cloud engineers. Here's a simple chart to kick-start your understanding:" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:13(caption) +msgid "Types of Storage" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:19(td) +msgid "On-instance / ephemeral" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:20(td) +msgid "Volumes block storage (Cinder)" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:21(td) +msgid "Object Storage (Swift)" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:26(td) +msgid "Used for running Operating System and scratch space" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:27(td) +msgid "Used for adding additional persistent storage to a virtual machine (VM)" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:29(td) +msgid "Used for storing virtual machine images and data" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:32(td) +msgid "Persists until VM is terminated" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:33(td) ./doc/src/docbkx/common/storage-concepts.xml:34(td) +msgid "Persists until deleted" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:37(td) ./doc/src/docbkx/common/storage-concepts.xml:38(td) +msgid "Access associated with a VM" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:39(td) +msgid "Available from anywhere" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:42(td) +msgid "Implemented as a filesystem underlying OpenStack Compute" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:43(td) +msgid "Mounted via OpenStack Block-Storage controlled protocol (for example, iSCSI)" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:45(td) +msgid "REST API" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:48(td) +msgid "Administrator configures size setting, based on flavors" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:50(td) +msgid "Sizings based on need" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:51(td) +msgid "Easily scalable for future growth" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:54(td) +msgid "Example: 10GB first disk, 30GB/core second disk" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:55(td) +msgid "Example: 1TB \"extra hard drive\"" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:56(td) +msgid "Example: 10s of TBs of dataset storage" +msgstr "" + +#: ./doc/src/docbkx/common/storage-concepts.xml:62(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/src/docbkx/common/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/src/docbkx/common/storage-concepts.xml:74(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/src/docbkx/common/storage-concepts.xml:60(para) +msgid "Other points of note include: " +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_usage_statistics.xml:4(title) +msgid "Usage statistics" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_usage_statistics.xml:4(para) +msgid "The nova command-line tool can provide some basic statistics on resource usage for hosts and instances." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_usage_statistics.xml:6(para) +msgid "For more sophisticated monitoring, see the Ceilometer project, which is currently under development. You may also wish to consider installing tools such as Ganglia or Graphite if you require access to more detailed data." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_usage_statistics.xml:12(title) +msgid "Host usage statistics" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_usage_statistics.xml:13(para) +msgid "Use the command to list the hosts and the nova-related services that are running on them:" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_usage_statistics.xml:31(para) +msgid "Use the command to retrieve a summary of resource usage of all of the instances running on the host. The \"cpu\" column is the sum of the virtual CPUs of all of the instances running on the host, the \"memory_mb\" column is the sum of the memory (in MB) allocated to the instances running on the hosts, and the \"disk_gb\" column is the sum of the root and ephemeral disk sizes (in GB) of the instances running on the hosts." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_usage_statistics.xml:40(replaceable) +msgid "c2-compute-01" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_usage_statistics.xml:37(para) +msgid "Note that these values are computed using only information about the flavors of the instances running on the hosts. This command does not query the CPU usage, memory usage, or hard disk usage of the physical host." +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_usage_statistics.xml:51(title) +msgid "Instance usage statistics" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_usage_statistics.xml:52(para) +msgid "Use the command to retrieve CPU, memory, I/O and network statistics from an instance:" +msgstr "" + +#: ./doc/src/docbkx/common/nova_cli_usage_statistics.xml:76(para) +msgid "Use the command to get summary statistics for each tenant:" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:4(title) +msgid "Config drive" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:7(para) +msgid "OpenStack can be configured to write metadata to a special configuration drive that will be attached to the instance when it boots. The instance can retrieve any information that would normally be available through the metadata service by mounting this disk and reading files from it." +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:11(para) +msgid "One use case for the config drive is to pass networking configuration (e.g., IP address, netmask, gateway) when DHCP is not being used to assign IP addresses to instances. The instance's IP configuration can be transmitted using the config drive, which can be mounted and accessed before the instance's network settings have been configured." +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:15(para) +msgid "The config drive can be used by any guest operating system that is capable of mounting an ISO9660 or VFAT file system. This functionality should be available on all modern operating systems." +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:18(para) +msgid "In addition, an image that has been built with a recent version of the cloud-init package will be able to automatically access metadata passed via config drive. The current version of cloud-init as of this writing (0.7.1) has been confirmed to work with Ubuntu, as well as Fedora-based images such as RHEL." +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:22(para) +msgid "If an image does not have the cloud-init package installed, the image must be customized to run a script that mounts the config drive on boot, reads the data from the drive, and takes appropriate action such as adding the public key to an account. See below for details on how data is organized on the config drive." +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:28(title) +msgid "Enabling the config drive" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:29(para) +msgid "To enable the config drive, pass the --config-drive=true parameter when calling . Here is a complex example that enables the config drive as well as passing user data, two files, and two key/value metadata pairs, all of which will be accessible from the config drive as described below." +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:36(para) +msgid "You can also configure the Compute service to always create a config drive by setting the following option in /etc/nova/nova.conf: " +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:39(para) +msgid "As of this writing, there is no mechanism for an administrator to disable use of the config drive if a user passes the --config-drive=true flag to the command." +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:44(title) +msgid "Accessing the config drive from inside an instance" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:45(para) +msgid "The config drive will have a volume label of config-2. If your guest OS supports accessing disk by label, you should be able to mount the config drive as the /dev/disk/by-label/config-2 device. For example:" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:52(para) +msgid "The cirros 0.3.0 test image does not have support for the config drive. Support will be added in version 0.3.1." +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:57(para) +msgid "If your guest operating system does not use udev, then the /dev/disk/by-label directory will not be present. The command can be used to identify the block device that corresponds to the config drive. For example, when booting the cirros image with the m1.tiny flavor, the device will be /dev/vdb:" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:62(para) +msgid "Once identified, the device can then be mounted:" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:71(title) +msgid "Contents of the config drive" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:72(para) +msgid "The files that will be present in the config drive will vary depending on the arguments that were passed to . Based on the example above, the contents of the config drive would be:" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:90(title) +msgid "Guidelines for accessing config drive data" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:91(para) +msgid "Do not rely on the presence of the EC2 metadata present in the config drive (i.e., files under the ec2 directory), as this content may be removed in a future release." +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:94(para) +msgid "When creating images that access config drive data, if there are multiple directories under the openstack directory, always select the highest API version by date that your consumer supports. For example, if your guest image can support versions 2012-03-05, 2012-08-05, 2013-04-13. It is best to try 2013-04-13 first and fall back to an earlier version if it 2013-04-13 isn't present." +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:101(title) +msgid "Format of OpenStack metadata" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:102(para) +msgid "Here is an example of the contents of openstack/2012-08-10/meta_data.json, openstack/latest/meta_data.json (these two files are identical), formatted to improve readability:" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:132(para) +msgid "Note the effect of the --file /etc/network/interfaces=/home/myuser/instance-interfaces argument passed to the original command. The contents of this file are contained in the file openstack/content/0000 file on the config drive, and the path is specified as /etc/network/interfaces in the meta_data.json file." +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:140(title) +msgid "Format of EC2 metadata" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:141(para) +msgid "Here is an example of the contents of ec2/2009-04-04/meta-data.json, latest/meta-data.json (these two files are identical) formatted to improve readbility:" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:182(para) +msgid "The files openstack/2012-08-10/user_data, openstack/latest/user_data, ec2/2009-04-04/user-data, and ec2/latest/user-data, will only be present if the --user-data flag was passed to and will contain the contents of the user data file passed as the argument." +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:190(title) +msgid "Format of the config drive" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:191(para) +msgid "The default format of the config drive as an ISO 9660 filesystem. To explicitly specify the ISO 9660 format, add the following line to /etc/nova/nova.conf:" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:197(para) +msgid "For legacy reasons, the config drive can be configured to use VFAT format instead of ISO 9660. It is unlikely that you would require VFAT format, since ISO 9660 is widely supported across operating systems. However, if you wish to use the VFAT format, add the following line to /etc/nova/nova.conf instead:" +msgstr "" + +#: ./doc/src/docbkx/common/config-drive.xml:204(para) +msgid "If VFAT is chosen, the config drive will be 64MB in size." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:26(None) ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:31(None) +msgid "@@image: 'figures/Security-Group.png'; md5=4ea3cad296134b457249b2a6f582786a" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:54(None) ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:58(None) +msgid "@@image: 'figures/KeyPair.png'; md5=2e9dd4638d380ae7b7eb0152a9cd05d6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:73(None) ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:77(None) +msgid "@@image: 'figures/Images.png'; md5=23597afdea00fe180aad420d706082bc" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:91(None) ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:96(None) +msgid "@@image: 'figures/LaunchInstance.png'; md5=bd9c57187d4604a8b6ecbf71816507c4" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:106(None) ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:110(None) +msgid "@@image: 'figures/InstanceReady.png'; md5=1b77cf84bb5b4de6a1055235df2df515" +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:8(title) +msgid "Launching Instances using Dashboard" +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:10(para) +msgid "The Dashboard can be used to launch instances. This section explains the various steps to be followed to launch a instance." +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:14(title) +msgid "Modify Security Groups" +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:15(para) +msgid "Before launching a VM, first modify the Security Groups rules to allow us to ping and SSH to the instances. This is done by editing the default security group or adding a new security group. For ease of understanding, modify the default security group." +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:35(para) +msgid "Select IP protocol TCP and enter 22 in \"From Port\" and \"To Port\" and CIDR 0.0.0.0/0. This opens port 22 for requests from any IP. If you want requests from particular range of IP, provide it in CIDR field." +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:40(para) +msgid "Select IP protocol ICMP and enter -1 in \"From Port\" and \"To Port\" and CIDR 0.0.0.0/0. This allows ping from any IP. If you want ping requests from particular range of IP, provide it in CIDR field." +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:46(title) +msgid "Adding Keypair" +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:47(para) +msgid "Next add a Keypair. Once a Keypair is added, the public key would be downloaded. This key can be used to SSH to the launched instance." +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:62(para) +msgid "Once this is done, we are now all set to launch an Instance" +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:66(title) +msgid "Launching Instance" +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:67(para) +msgid "Click Images & Snapshots and launch a required instance from the list of images available." +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:81(para) +msgid "Click launch on the required image. Provide a Server Name, select the flavor, the keypair added above and the default security group. Provide the number of instances required. Once these details are provided, click Launch Instance." +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:100(para) +msgid "Once the status is Active, the instance is ready and we can ping and SSH to the instance." +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:116(title) +msgid "Make a secure connection to the launched instance" +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:117(para) +msgid "Here are the steps to SSH into an instance using the downloaded keypair file. The username is ubuntu for the Ubuntu cloud images on TryStack." +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:124(para) +msgid "Download the MyKey.pem file from the OpenStack Dashboard." +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:128(para) +msgid "In a command line interface, modify the access to the .pem file:" +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:134(para) +msgid "Use the command to ensure that the keypair is known to SSH:" +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:138(para) +msgid "Copy the IP address from the MyFirstInstance." +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:142(para) +msgid "Use the SSH command to make a secure connection to the instance:" +msgstr "" + +#: ./doc/src/docbkx/common/dashboardlaunchinginstances.xml:145(para) +msgid "You should see a prompt asking \"Are you sure you want to continue connection (yes/no)?\" Type yes and you have successfully connected." +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:4(caption) +msgid "Description of keystone.conf file configuration options for LDAP" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:10(td) +msgid "Configuration option=Default value" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:11(td) +msgid "(Type) Description" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:16(td) +msgid "url=ldap://localhost" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:17(td) +msgid "The location for the ldap server." +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:20(td) +msgid "user = dc=Manager,dc=example,dc=com" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:22(td) +msgid "(StrOpt) User for the LDAP server to use as default." +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:25(td) +msgid "password = None" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:26(td) +msgid "(StrOpt) Password for LDAP server to connect to." +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:29(td) +msgid "suffix = cn=example,cn=com" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:31(td) +msgid "(StrOpt) Default suffix for your LDAP server." +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:33(td) +msgid "use_dumb_member = False" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:34(td) +msgid "(Bool) Indicates whether dumb_member settings are in use." +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:36(td) +msgid "allow_subtree_delete = False" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:38(td) +msgid "(Bool) Determine whether to delete LDAP subtrees." +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:41(td) +msgid "dumb_member = cn=dumb,dc=example,dc=com" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:43(td) +msgid "Mockup member as placeholder, for testing purposes." +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:45(td) +msgid "query_scope = one" +msgstr "" + +#: ./doc/src/docbkx/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/src/docbkx/common/tables/ldap-keystone-conf.xml:49(td) +msgid "user_tree_dn = ou=Users,dc=example,dc=com" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:53(td) +msgid "user_filter =" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:57(td) +msgid "user_objectclass = inetOrgPerson" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:61(td) +msgid "user_id_attribute = cn" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:65(td) +msgid "user_name_attribute = sn" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:69(td) +msgid "user_mail_attribute = email" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:73(td) +msgid "user_pass_attribute = userPassword" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:77(td) +msgid "user_enabled_attribute = enabled" +msgstr "" + +#: ./doc/src/docbkx/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/src/docbkx/common/tables/ldap-keystone-conf.xml:82(td) +msgid "user_enabled_mask = 0" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:86(td) +msgid "user_enabled_default = True" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:90(td) +msgid "user_attribute_ignore = tenant_id,tenants" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:94(td) +msgid "user_allow_create = True" +msgstr "" + +#: ./doc/src/docbkx/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/src/docbkx/common/tables/ldap-keystone-conf.xml:98(td) +msgid "user_allow_update = True" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:102(td) +msgid "user_allow_delete = True" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:107(td) +msgid "tenant_tree_dn = ou=Groups,dc=example,dc=com" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:112(td) +msgid "tenant_filter =" +msgstr "" + +#: ./doc/src/docbkx/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/src/docbkx/common/tables/ldap-keystone-conf.xml:116(td) +msgid "tenant_objectclass = groupOfNames" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:120(td) +msgid "tenant_id_attribute = cn" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:124(td) +msgid "tenant_member_attribute = member" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:128(td) +msgid "tenant_name_attribute = ou" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:132(td) +msgid "tenant_desc_attribute = desc" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:136(td) +msgid "tenant_enabled_attribute = enabled" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:140(td) +msgid "tenant_attribute_ignore =" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:144(td) +msgid "tenant_allow_create = True" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:148(td) +msgid "tenant_allow_update = True" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:153(td) +msgid "tenant_allow_delete = True" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:158(td) +msgid "role_tree_dn = ou=Roles,dc=example,dc=com" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:163(td) +msgid "role_filter =" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:168(td) +msgid "role_objectclass = organizationalRole" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:173(td) +msgid "role_id_attribute = cn" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:178(td) +msgid "role_name_attribute = ou" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:183(td) +msgid "role_member_attribute = roleOccupant" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:188(td) +msgid "role_attribute_ignore =" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:193(td) +msgid "role_allow_create = True" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:198(td) +msgid "role_allow_update = True" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:203(td) +msgid "role_allow_delete = True" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:208(td) +msgid "group_tree_dn =" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:213(td) +msgid "group_filter =" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:218(td) +msgid "group_objectclass = groupOfNames" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:223(td) +msgid "group_id_attribute = cn" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:228(td) +msgid "group_name_attribute = ou" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:233(td) +msgid "group_member_attribute = member" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:238(td) +msgid "group_desc_attribute = desc" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:243(td) +msgid "group_attribute_ignore =" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:248(td) +msgid "group_allow_create = True" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:253(td) +msgid "group_allow_update = True" +msgstr "" + +#: ./doc/src/docbkx/common/tables/ldap-keystone-conf.xml:258(td) +msgid "group_allow_delete = True" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:5(title) +msgid "Glossary" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/glossary/glossary-terms.xml:15(link) +msgid "http://www.apache.org/licenses/LICENSE-2.0" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/glossary/glossary-terms.xml:26(title) +msgid "A" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:29(glossterm) +msgid "absolute limit" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/glossary/glossary-terms.xml:37(glossterm) +msgid "access key" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:39(para) +msgid "Alternative term for an Amazon EC2 access key." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:44(glossterm) +msgid "account" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:46(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/src/docbkx/common/glossary/glossary-terms.xml:53(glossterm) +msgid "accounting" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:55(para) +msgid "Nova provides accounting information through the event notification and system usage data facilities." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:61(glossterm) +msgid "account auditor" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/glossary/glossary-terms.xml:70(glossterm) +msgid "account database" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/glossary/glossary-terms.xml:78(glossterm) +msgid "account reaper" +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/glossary/glossary-terms.xml:86(glossterm) +msgid "account server" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:88(para) +msgid "Lists containers in swift and stores container information in the account database." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:93(glossterm) +msgid "account service" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:95(para) +msgid "Component of swift that provides account services such as list, create, modify, and audit. Do not confuse with keystone, OpenLDAP, or similar user account services." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:102(glossterm) +msgid "Active Directory" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:104(para) +msgid "Authentication and Identity Service by Microsoft, based on LDAP. Supported in OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:110(glossterm) +msgid "address pool" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:112(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/src/docbkx/common/glossary/glossary-terms.xml:119(glossterm) +msgid "admin API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:121(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/src/docbkx/common/glossary/glossary-terms.xml:129(glossterm) +msgid "admin server" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:131(para) +msgid "In the context of keystone, the worker process that provides access to the admin API." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:136(glossterm) +msgid "Advanced Message Queuing Protocol (AMQP)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:139(para) +msgid "The open standard messaging protocol used by nova for intra-service communications, provided by RabbitMQ (the default), Qpid, or ZeroMQ." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:145(glossterm) +msgid "Advanced RISC Machine (ARM)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:147(para) +msgid "Lower power consumption CPU often found in mobile and embedded devices. Supported by OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:153(glossterm) +msgid "alert" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:155(para) +msgid "Nova 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/src/docbkx/common/glossary/glossary-terms.xml:162(glossterm) +msgid "allocate" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:164(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/src/docbkx/common/glossary/glossary-terms.xml:171(glossterm) +msgid "Amazon Kernel Image (AKI)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:173(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:180(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:187(para) +msgid "Both a VM container format and a VM disk format. Supported by glance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:178(glossterm) +msgid "Amazon Machine Image (AMI)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:185(glossterm) +msgid "Amazon Ramdisk Image (ARI)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:192(glossterm) +msgid "Anvil" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:194(para) +msgid "A project that ports the shell script-based project named devstack to Python." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:199(glossterm) +msgid "Apache" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:201(para) +msgid "The most common web server software currently used on the Internet." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:206(glossterm) +msgid "Apache License 2.0" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:208(para) +msgid "All OpenStack core projects are provided under the terms of the Apache License 2.0 license." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:214(glossterm) +msgid "API endpoint" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:216(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/src/docbkx/common/glossary/glossary-terms.xml:225(glossterm) +msgid "API extension" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:227(para) +msgid "A feature of nova and quantum that allows custom modules to extend the core APIs." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:232(glossterm) +msgid "API extension plug-in" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:234(para) +msgid "Alternative term for a quantum plug-in or quantum API extension." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:239(glossterm) +msgid "API key" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:241(para) +msgid "Alternative term for an API token." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:245(glossterm) +msgid "API server" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:247(para) +msgid "Any node running a daemon or worker that provides an API endpoint." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:252(glossterm) +msgid "API token" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:254(para) +msgid "Passed to API requests and used by OpenStack to verify that the client is authorized to run the requested operation." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:260(glossterm) +msgid "API version" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:262(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/src/docbkx/common/glossary/glossary-terms.xml:268(glossterm) +msgid "applet" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:270(para) +msgid "A Java program that can be embedded into a web page." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:275(glossterm) +msgid "Application Programming Interface (API)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:278(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/src/docbkx/common/glossary/glossary-terms.xml:287(glossterm) +msgid "application server" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:289(para) +msgid "A piece of software that makes available another piece of software over a network." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:294(glossterm) +msgid "Application Service Provider (ASP)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:296(para) +msgid "Companies that rent specialized applications that help businesses and organizations provide additional services with less cost." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:302(glossterm) +msgid "arptables" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:304(para) +msgid "Used along with iptables, ebtables, and ip6tables in nova to provide firewall services." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:311(glossterm) +msgid "associate" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:313(para) +msgid "The process associating a nova floating IP address to a fixed IP address." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:318(glossterm) +msgid "Asynchronous JavaScript and XML (AJAX)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:321(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/src/docbkx/common/glossary/glossary-terms.xml:328(glossterm) +msgid "ATA over Ethernet (AoE)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:330(para) +msgid "A disk storage protocol tunneled within Ethernet. Currently not supported in nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:335(glossterm) +msgid "attach" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:337(para) +msgid "The process of connecting a VIF or vNIC to a L2 network in quantum. In the context of nova, this process connects a storage volume to an instance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:344(glossterm) +msgid "attachment (network)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:346(para) +msgid "Association of an interface ID to a logical port. Plugs an interface into a port." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:351(glossterm) +msgid "auditing" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:353(para) +msgid "Provided in nova through the system usage data facility." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:358(glossterm) +msgid "auditor" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:360(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/src/docbkx/common/glossary/glossary-terms.xml:368(glossterm) +msgid "Austin" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:370(para) +msgid "Project name for the initial release of OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:375(glossterm) +msgid "auth node" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:377(para) +msgid "Alternative term for a swift authorization node." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:382(glossterm) +msgid "authentication" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:384(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/src/docbkx/common/glossary/glossary-terms.xml:391(glossterm) +msgid "authentication token" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:393(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/src/docbkx/common/glossary/glossary-terms.xml:400(glossterm) +msgid "AuthN" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:402(para) +msgid "The keystone component that provides authentication services." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:407(glossterm) +msgid "authorization" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:409(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/src/docbkx/common/glossary/glossary-terms.xml:417(glossterm) +msgid "authorization node" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:419(para) +msgid "A swift node that provides authorization services." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:424(glossterm) +msgid "AuthZ" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:426(para) +msgid "The keystone component that provides high-level authorization services." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:431(glossterm) +msgid "Auto ACK" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:433(para) +msgid "Configuration setting within RabbitMQ that enables or disables message acknowledgment. Enabled by default." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:439(glossterm) +msgid "auto declare" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:441(para) +msgid "A nova RabbitMQ setting that determines if a message exchange is automatically created when the program starts." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:447(glossterm) +msgid "availability zone" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:449(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/src/docbkx/common/glossary/glossary-terms.xml:463(title) +msgid "B" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:474(glossterm) +msgid "back-end" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:476(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/src/docbkx/common/glossary/glossary-terms.xml:483(glossterm) +msgid "back-end catalog" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:485(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/src/docbkx/common/glossary/glossary-terms.xml:493(glossterm) +msgid "back-end store" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:495(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/src/docbkx/common/glossary/glossary-terms.xml:505(glossterm) +msgid "bandwidth" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:507(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/src/docbkx/common/glossary/glossary-terms.xml:517(para) +msgid "A glance container format that indicates that no container exists for the VM image." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:522(glossterm) +msgid "Bexar" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:524(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/src/docbkx/common/glossary/glossary-terms.xml:531(glossterm) +msgid "binary" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:533(para) +msgid "Information that consists solely of ones and zeroes, which is the language of computers." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:538(glossterm) +msgid "bit" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:540(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/src/docbkx/common/glossary/glossary-terms.xml:546(glossterm) +msgid "bit-per-second (BPS)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:549(para) +msgid "The universal measurement of how quickly data is transferred from place to place." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:555(glossterm) +msgid "block device" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:557(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/src/docbkx/common/glossary/glossary-terms.xml:564(glossterm) +msgid "block migration" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:566(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/src/docbkx/common/glossary/glossary-terms.xml:574(glossterm) +msgid "bootable disk image" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:576(para) +msgid "A type of VM image that exists as a single, bootable file." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:581(glossterm) +msgid "Bootstrap Protocol (BOOTP)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:583(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/src/docbkx/common/glossary/glossary-terms.xml:592(glossterm) +msgid "browser" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:594(para) +msgid "Any client software that allows a computer or device to access the Internet." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:599(glossterm) +msgid "builder file" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:601(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/src/docbkx/common/glossary/glossary-terms.xml:608(glossterm) +msgid "button class" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:610(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/src/docbkx/common/glossary/glossary-terms.xml:619(glossterm) +msgid "byte" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:621(para) +msgid "Set of bits that make up a single character; there are usually 8 bits to a byte." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:634(title) +msgid "C" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:636(glossterm) +msgid "cache pruner" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:638(para) +msgid "An executable program that is used to keep a glance VM image cache at or below its configured maximum size." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:644(glossterm) +msgid "cactus" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:646(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/src/docbkx/common/glossary/glossary-terms.xml:653(glossterm) +msgid "CALL" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:655(para) +msgid "One of the RPC primitives used by the OpenStack message queue software. Sends a message and waits for a response." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:661(glossterm) +msgid "capability" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:663(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/src/docbkx/common/glossary/glossary-terms.xml:669(glossterm) +msgid "capacity cache" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:671(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/src/docbkx/common/glossary/glossary-terms.xml:678(glossterm) +msgid "capacity updater" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:680(para) +msgid "A notification driver that monitors VM instances and updates the capacity cache as needed." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:685(glossterm) +msgid "CAST" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:687(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/src/docbkx/common/glossary/glossary-terms.xml:693(glossterm) +msgid "catalog" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:695(para) +msgid "Contains a list of available API endpoints to a user after they authenticate to keystone." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:700(glossterm) +msgid "catalog service" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:702(para) +msgid "A keystone service that provides a list of available API endpoints to a user after they authenticate to keystone." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:709(glossterm) +msgid "ceilometer" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:712(para) +msgid "An incubated project that provides metering and billing facilities for OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:717(glossterm) +msgid "cell" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:719(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/src/docbkx/common/glossary/glossary-terms.xml:727(glossterm) +msgid "cell forwarding" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:729(para) +msgid "A nova option that allows parent cells to pass resource requests to child cells if the parent cannot provide the requested resource." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:735(glossterm) +msgid "cell manager" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:737(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/src/docbkx/common/glossary/glossary-terms.xml:743(glossterm) +msgid "CentOS" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:745(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:1235(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:3121(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:3682(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:4398(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:4595(para) +msgid "A Linux distribution that is compatible with OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:750(glossterm) +msgid "Ceph" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:752(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/src/docbkx/common/glossary/glossary-terms.xml:759(glossterm) +msgid "CephFS" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:761(para) +msgid "The POSIX-compliant file system provided by Ceph." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:766(glossterm) +msgid "certificate authority" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:768(para) +msgid "A simple certificate authority provided by nova for cloudpipe VPNs and VM image decryption." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:773(glossterm) +msgid "Challenge-Handshake Authentication Protocol (CHAP)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:776(para) +msgid "An iSCSI authentication method supported by nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:781(glossterm) +msgid "chance scheduler" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:783(para) +msgid "A scheduling method used by nova that randomly chooses an available host from the pool." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:788(glossterm) +msgid "changes since" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:790(para) +msgid "A nova API parameter that allows you to download 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/src/docbkx/common/glossary/glossary-terms.xml:798(glossterm) +msgid "Chef" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:800(para) +msgid "An operating system configuration management tool supporting OpenStack deployments." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:805(glossterm) +msgid "child cell" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:807(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/src/docbkx/common/glossary/glossary-terms.xml:816(glossterm) +msgid "cinder" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:818(para) +msgid "A core OpenStack project that maintains the nova Volume Service for VMs." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:823(glossterm) +msgid "Cisco quantum plug-in" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:825(para) +msgid "A quantum plug-in for Cisco devices and technologies including UCS and Nexus." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:830(glossterm) +msgid "cloud architect" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:833(para) +msgid "A person who plans, designs, and oversees the creation of clouds." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:838(glossterm) +msgid "cloud computing" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:840(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/src/docbkx/common/glossary/glossary-terms.xml:849(glossterm) +msgid "cloud controller" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:851(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/src/docbkx/common/glossary/glossary-terms.xml:859(glossterm) +msgid "cloud controller node" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:861(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/src/docbkx/common/glossary/glossary-terms.xml:868(glossterm) +msgid "Cloud Data Management Interface (CDMI)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:871(para) +msgid "SINA standard that defines a RESTful API for managing objects in the cloud, currently unsupported in OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:877(glossterm) +msgid "Cloud Infrastructure Management Interface (CIMI)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:880(para) +msgid "An in-progress specification for cloud management. Currently unsupported in OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:886(glossterm) +msgid "cloud-init" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:888(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/src/docbkx/common/glossary/glossary-terms.xml:896(glossterm) +msgid "cloudadmin" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:898(para) +msgid "One of the default roles in the nova RBAC system. Allows for complete system access." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:903(glossterm) +msgid "cloudpipe" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:905(para) +msgid "A service in nova used to create VPNs on a per-project basis." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:910(glossterm) +msgid "cloudpipe image" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:912(para) +msgid "A pre-made VM image that serves as a cloudpipe server. Essentially, OpenVPN running on Linux." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:919(glossterm) +msgid "command filter" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:922(para) +msgid "Lists allowed commands within the nova rootwrap facility." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:927(glossterm) +msgid "community project" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:929(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/src/docbkx/common/glossary/glossary-terms.xml:937(glossterm) +msgid "compression" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:939(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/src/docbkx/common/glossary/glossary-terms.xml:946(glossterm) +msgid "Compute API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:948(para) +msgid "The nova-api daemon that provides access to the nova services. Can also communicate with some outside APIs such as the Amazons EC2 API." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:954(glossterm) +msgid "Compute API extension" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:956(para) +msgid "Alternative term for a nova API extension." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:962(glossterm) +msgid "compute controller" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:964(para) +msgid "The nova component that chooses suitable hosts on which to start VM instances." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:969(glossterm) +msgid "compute host" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:972(para) +msgid "Physical host dedicated to running compute nodes." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:977(glossterm) +msgid "compute node" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:979(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/src/docbkx/common/glossary/glossary-terms.xml:985(glossterm) +msgid "compute service" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:987(para) +msgid "Alternative term for the nova component that manages VMs." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:993(glossterm) +msgid "compute worker" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:996(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/src/docbkx/common/glossary/glossary-terms.xml:1004(glossterm) +msgid "concatenated object" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1006(para) +msgid "A segmented large object within swift that is put back together again and then sent to the client." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1012(glossterm) +msgid "consistency window" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1014(para) +msgid "The amount of time it takes for a new swift object to become accessible to all clients." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1019(glossterm) +msgid "console log" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1021(para) +msgid "Contains the output from a Linux VM console in nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1026(glossterm) +msgid "container" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1028(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/src/docbkx/common/glossary/glossary-terms.xml:1035(glossterm) +msgid "container auditor" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1037(para) +msgid "Checks for missing replicas or incorrect objects in the specified swift containers through queries to the SQLite back-end database." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1043(glossterm) +msgid "container database" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1045(para) +msgid "A SQLite database that contains swift containers and related metadata and is accessed by the container server" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1051(glossterm) +msgid "container format" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1053(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/src/docbkx/common/glossary/glossary-terms.xml:1059(glossterm) +msgid "container server" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1061(para) +msgid "Component of swift that manages containers." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1066(glossterm) +msgid "container service" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1068(para) +msgid "The swift component that provides container services, such as create, delete, list, and so on." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1080(glossterm) +msgid "controller node" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1082(para) +msgid "Alternative term for a cloud controller node." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1088(glossterm) +msgid "core API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1091(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, quantum, glance, and so on." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1098(glossterm) +msgid "core project" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1100(para) +msgid "An official OpenStack project. Currently consists of Compute (nova), Object Storage (swift), Image Service (glance), Identity (keystone), Dashboard (horizon), Networking (quantum), and Volume (cinder)." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1108(glossterm) +msgid "cost" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1110(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/src/docbkx/common/glossary/glossary-terms.xml:1117(glossterm) +msgid "credentials" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1119(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/src/docbkx/common/glossary/glossary-terms.xml:1128(glossterm) +msgid "Crowbar" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1130(para) +msgid "An open source community project by Dell that aims to provide all necessary services to quickly deploy clouds." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1136(glossterm) +msgid "current workload" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1138(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/src/docbkx/common/glossary/glossary-terms.xml:1145(glossterm) +msgid "customer" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1147(para) +msgid "Alternative term for tenant." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1151(glossterm) +msgid "customization module" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1153(para) +msgid "A user-created Python module that is loaded by horizon to change the look and feel of the dashboard." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1168(title) +msgid "D" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1170(glossterm) +msgid "daemon" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1172(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/src/docbkx/common/glossary/glossary-terms.xml:1178(glossterm) +msgid "dashboard" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1180(para) +msgid "The web-based management interface for OpenStack. An alternative name for horizon." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1191(glossterm) +msgid "database ID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1193(para) +msgid "A unique ID given to each replica of a swift database." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1198(glossterm) +msgid "database replicator" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1200(para) +msgid "The component of swift that copies changes in the account, container, and object databases to other nodes." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1206(glossterm) +msgid "data encryption" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1208(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/src/docbkx/common/glossary/glossary-terms.xml:1224(glossterm) +msgid "deallocate" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1226(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/src/docbkx/common/glossary/glossary-terms.xml:1233(glossterm) +msgid "Debian" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1246(glossterm) +msgid "deduplication" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1248(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/src/docbkx/common/glossary/glossary-terms.xml:1255(glossterm) +msgid "default panel" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1257(para) +msgid "The default panel that is displayed when a user accesses the horizon dashboard." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1262(glossterm) +msgid "default tenant" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1264(para) +msgid "New users are assigned to this keystone tenant if no tenant is specified when a user is created." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1270(glossterm) +msgid "default token" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1272(para) +msgid "A keystone token that is not associated with a specific tenant and is exchanged for a scoped token." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1278(glossterm) +msgid "delayed delete" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1280(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/src/docbkx/common/glossary/glossary-terms.xml:1286(glossterm) +msgid "delivery mode" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1288(para) +msgid "Setting for the nova RabbitMQ message delivery mode, can be set to either transient or persistent." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1294(glossterm) +msgid "deprecated auth" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1296(para) +msgid "An option within nova that allows administrators to create and manage users through the nova-manage command as opposed to using keystone." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1302(glossterm) +msgid "developer" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1304(para) +msgid "One of the default roles in the nova RBAC system and is the default role assigned to a new user." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1310(glossterm) +msgid "device" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1312(para) +msgid "In the context of swift this refers to the underlying storage device." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1317(glossterm) +msgid "device ID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1319(para) +msgid "Maps swift partitions to physical storage devices." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1324(glossterm) +msgid "device weight" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1326(para) +msgid "Used to distribute the partitions among swift devices. The distribution is usually proportional to the storage capacity of the device." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1332(glossterm) +msgid "DevStack" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1334(para) +msgid "Community project that uses shell scripts to quickly build complete OpenStack development environments." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1341(glossterm) +msgid "Dynamic HyperText Markup Language (DHTML)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1344(para) +msgid "Used to refer to pages that use HTML, JavaScript, and CCS to allow users to interact with a web page or show simple animation." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1350(glossterm) +msgid "Diablo" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1352(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/src/docbkx/common/glossary/glossary-terms.xml:1360(glossterm) +msgid "direct consumer" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1362(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/src/docbkx/common/glossary/glossary-terms.xml:1369(glossterm) +msgid "direct exchange" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1371(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/src/docbkx/common/glossary/glossary-terms.xml:1377(glossterm) +msgid "direct publisher" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1379(para) +msgid "Element of RabbitMQ that provides a response to an incoming MQ message." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1384(glossterm) +msgid "disassociate" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1386(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/src/docbkx/common/glossary/glossary-terms.xml:1393(glossterm) +msgid "disk encryption" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1395(para) +msgid "The ability to encrypt data at the file system, disk partition or whole disk level. Supported within nova VMs." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1401(glossterm) +msgid "disk format" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1403(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/src/docbkx/common/glossary/glossary-terms.xml:1409(glossterm) +msgid "dispersion" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1411(para) +msgid "In swift, tools to test and ensure dispersion of objects and containers to ensure fault tolerance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1417(glossterm) +msgid "Django" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1419(para) +msgid "A web framework used extensively in horizon." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1424(glossterm) +msgid "dnsmasq" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1426(para) +msgid "Daemon that provides DNS, DHCP, BOOTP, and TFTP services, used by the nova VLAN manager and FlatDHCP manager." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1432(glossterm) +msgid "Domain Name Service (DNS)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1434(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/src/docbkx/common/glossary/glossary-terms.xml:1443(glossterm) +msgid "Domain Name System (DNS)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1445(para) +msgid "A system by which Internet domain name-to-address and address-to-name resolutions are determined." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1448(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/src/docbkx/common/glossary/glossary-terms.xml:1452(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/src/docbkx/common/glossary/glossary-terms.xml:1464(glossterm) +msgid "download" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1466(para) +msgid "The transfer of data, usually in the form of files, from one computer to another." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1471(glossterm) +msgid "DNS record" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1473(para) +msgid "A record that specifies information about a particular domain and belongs to the domain." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1479(glossterm) +msgid "domain" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1481(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/src/docbkx/common/glossary/glossary-terms.xml:1485(para) +msgid "A domain is an entity or container of all DNS-related information containing one or more records." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1493(glossterm) +msgid "durable exchange" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1495(para) +msgid "The nova RabbitMQ message exchange that remains active when the server restarts." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1500(glossterm) +msgid "durable queue" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1502(para) +msgid "A nova RabbitMQ message queue that will remain active when the server restarts." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1507(glossterm) +msgid "Dynamic Host Configuration Protocol (DHCP)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1510(para) +msgid "A method to automatically configure networking for a host at boot time. Provided by both quantum and nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1519(title) +msgid "E" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1521(glossterm) +msgid "EBS boot volume" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1523(para) +msgid "An Amazon EBS storage volume that contains a bootable VM image, currently unsupported in OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1529(glossterm) +msgid "ebtables" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1531(para) +msgid "Used in nova along with arptables, iptables, and ip6tables to create firewalls and to ensure isolation of network communications." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1537(glossterm) +msgid "EC2" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1539(para) +msgid "The Amazon commercial compute product, similar to nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1544(glossterm) +msgid "EC2 access key" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1546(para) +msgid "Used along with an EC2 secret key to access the nova EC2 API." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1551(glossterm) +msgid "EC2 API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1553(para) +msgid "OpenStack supports accessing the Amazon EC2 API through nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1558(glossterm) +msgid "EC2 Compatibility API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1560(para) +msgid "A nova component that allows OpenStack to communicate with Amazon EC2" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1565(glossterm) +msgid "EC2 secret key" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1567(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/src/docbkx/common/glossary/glossary-terms.xml:1573(glossterm) +msgid "Elastic Block Storage (EBS)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1575(para) +msgid "The Amazon commercial block storage product." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1582(glossterm) +msgid "encryption" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1584(para) +msgid "OpenStack supports encryption technologies such as HTTPS, SSH, SSL, TLS, digital certificates, and data encryption." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1590(glossterm) +msgid "endpoint" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1592(para) +msgid "See API endpoint." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1596(glossterm) +msgid "endpoint registry" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1598(para) +msgid "Alternative term for a keystone catalog." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1602(glossterm) +msgid "endpoint template" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1604(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/src/docbkx/common/glossary/glossary-terms.xml:1611(glossterm) +msgid "entity" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1613(para) +msgid "Any piece of hardware or software that wants to connect to the network services provided by quantum, the Network Connectivity service. An entity can make use of quantum by implementing a VIF." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1621(glossterm) +msgid "ephemeral image" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1623(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/src/docbkx/common/glossary/glossary-terms.xml:1629(glossterm) +msgid "ephemeral volume" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1631(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/src/docbkx/common/glossary/glossary-terms.xml:1638(glossterm) +msgid "Essex" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1640(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/src/docbkx/common/glossary/glossary-terms.xml:1649(glossterm) +msgid "ESX" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1651(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:1657(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:2526(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:2598(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:4648(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:4679(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:4930(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:5006(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:5020(para) +msgid "An OpenStack-supported hypervisor." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1655(glossterm) +msgid "ESXi" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1661(glossterm) +msgid "ETag" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1663(para) +msgid "MD5 hash of an object within swift, used to ensure data integrity." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1668(glossterm) +msgid "euca2ools" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1670(para) +msgid "A collection of command line tools for administering VMs, most are compatible with OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1676(glossterm) +msgid "Eucalyptus Kernel Image (EKI)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1678(para) +msgid "Used along with an ERI to create an EMI." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1682(glossterm) +msgid "Eucalyptus Machine Image (EMI)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1684(para) +msgid "VM image container format supported by glance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1689(glossterm) +msgid "Eucalyptus Ramdisk Image (ERI)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1691(para) +msgid "Used along with an EKI to create an EMI." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1695(glossterm) +msgid "evacuate" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1697(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/src/docbkx/common/glossary/glossary-terms.xml:1704(glossterm) +msgid "exchange" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1706(para) +msgid "Alternative term for a RabbitMQ message exchange." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1712(glossterm) +msgid "exchange type" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1715(para) +msgid "A routing algorithm in the nova RabbitMQ." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1720(glossterm) +msgid "exclusive queue" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1723(para) +msgid "Connected to by a direct consumer in RabbitMQ / nova, the message can only be consumed by the current connection." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1730(glossterm) +msgid "extended attributes (xattrs)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1733(para) +msgid "File system option that allows for storage of additional information beyond owner, group, permissions, modification time, and so on. The underlying swift file system must support extended attributes." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1741(glossterm) +msgid "extension" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1743(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/src/docbkx/common/glossary/glossary-terms.xml:1750(glossterm) +msgid "extra specs" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1752(para) +msgid "Allows additional requirements to be specified when nova determines where to start a new instance, examples include a minimum amount of network bandwidth or a GPU." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1762(title) +msgid "F" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1764(glossterm) +msgid "FakeLDAP" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1766(para) +msgid "An easy method to create a local LDAP directory for testing keystone and nova. Requires Redis." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1772(glossterm) +msgid "fan-out exchange" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1774(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/src/docbkx/common/glossary/glossary-terms.xml:1781(glossterm) +msgid "Fedora" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1783(para) +msgid "A Linux distribution compatible with OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1788(glossterm) +msgid "Fibre Channel" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1790(para) +msgid "Storage protocol similar in concept to TCP/IP, encapsulates SCSI commands and data." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1795(glossterm) +msgid "Fibre Channel over Ethernet (FCoE)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1797(para) +msgid "The fibre channel protocol tunneled within Ethernet." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1802(glossterm) +msgid "fill-first scheduler" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1804(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/src/docbkx/common/glossary/glossary-terms.xml:1810(glossterm) +msgid "filter" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1812(para) +msgid "The step of the nova scheduling process where hosts that cannot run the VMs are eliminated and will not be chosen." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1830(glossterm) +msgid "firewall" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1832(para) +msgid "Used to restrict communications between hosts and/or nodes, implemented in nova using iptables, arptables, ip6tables and etables." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1838(glossterm) +msgid "fixed IP address" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1840(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/src/docbkx/common/glossary/glossary-terms.xml:1848(glossterm) +msgid "FlatDHCP Manager" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1850(para) +msgid "The nova component that provides dnsmasq (DHCP, DNS, BOOTP, TFTP) and radvd (routing) services." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1856(glossterm) +msgid "Flat Manager" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1858(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/src/docbkx/common/glossary/glossary-terms.xml:1865(glossterm) ./doc/src/docbkx/common/glossary/glossary-terms.xml:1900(glossterm) +msgid "flat mode injection" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1868(para) +msgid "A nova networking method where the OS network configuration information is injected into the VM (VM) image before the instance starts." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1874(glossterm) ./doc/src/docbkx/common/glossary/glossary-terms.xml:1909(glossterm) +msgid "flat network" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1876(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:1911(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/src/docbkx/common/glossary/glossary-terms.xml:1886(glossterm) ./doc/src/docbkx/common/glossary/glossary-terms.xml:1921(glossterm) +msgid "flavor" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1888(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:1923(para) +msgid "Alternative term for a VM instance type." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1892(glossterm) ./doc/src/docbkx/common/glossary/glossary-terms.xml:1927(glossterm) +msgid "flavor ID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1894(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:1929(para) +msgid "UUID for each nova or glance VM flavor or instance type." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1903(para) +msgid "A nova networking method where the OS network configuration information is injected into the VM image before the instance starts." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1934(glossterm) +msgid "floating IP address" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1936(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/src/docbkx/common/glossary/glossary-terms.xml:1946(glossterm) +msgid "Folsom" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1948(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 (quantum), Image service (glance) and Volumes or Block Storage (cinder)." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1959(glossterm) +msgid "form" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1961(para) +msgid "horizon fixfixfix" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1965(glossterm) +msgid "FormPost" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1967(para) +msgid "swift middleware that allows users to upload (post) an image through a form on a web page." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1974(glossterm) +msgid "front-end" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1976(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/src/docbkx/common/glossary/glossary-terms.xml:1990(title) +msgid "G" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1992(glossterm) +msgid "gateway" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1994(para) +msgid "Hardware or software that translates between two different protocols." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:1999(glossterm) +msgid "GIF" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2001(para) +msgid "Stands for Graphic Interchange Format, a type of image file that is commonly used for animated images on web pages." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2007(glossterm) +msgid "glance" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2009(para) +msgid "A core project that provides the OpenStack Image Service." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2014(glossterm) +msgid "glance API server" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2016(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/src/docbkx/common/glossary/glossary-terms.xml:2023(glossterm) +msgid "glance registry" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2025(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:3711(para) +msgid "Alternative term for the glance image registry." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2030(glossterm) +msgid "global endpoint template" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2032(para) +msgid "The keystone endpoint template that contains services available to all tenants." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2037(glossterm) +msgid "GlusterFS" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2039(para) +msgid "A file system designed to aggregate NAS hosts, compatible with OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2046(glossterm) +msgid "golden image" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2048(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/src/docbkx/common/glossary/glossary-terms.xml:2054(glossterm) +msgid "Graphics Processing Unit (GPU)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2056(para) +msgid "Choosing a host based on the existence of a GPU is currently unsupported in OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2061(glossterm) +msgid "Green Threads" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2063(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/src/docbkx/common/glossary/glossary-terms.xml:2070(glossterm) +msgid "Grizzly" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2072(para) +msgid "Project name for the seventh release of OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2077(glossterm) +msgid "guest OS" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2079(para) +msgid "An operating system instance running under the control of a hypervisor." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2087(title) +msgid "H" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2089(glossterm) +msgid "handover" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2091(para) +msgid "An object state in swift where a new replica of the object is automatically created due to a drive failure." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2097(glossterm) +msgid "hard reboot" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2099(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/src/docbkx/common/glossary/glossary-terms.xml:2105(glossterm) +msgid "heat" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2107(para) +msgid "An integrated project that aims to orchestrate multiple cloud applications for OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2112(glossterm) +msgid "horizon" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2114(para) +msgid "The project that provides the OpenStack Dashboard." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2119(glossterm) +msgid "horizon plugin" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2122(para) +msgid "A plugin for the OpenStack Dashboard (horizon)." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2127(glossterm) +msgid "host" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2129(para) +msgid "A physical computer, not a VM instance (node)." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2134(glossterm) +msgid "host aggregate" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2136(para) +msgid "A method to further subdivide availability zones into hypervisor pools, a collection of common hosts." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2142(glossterm) +msgid "Host Bus Adapter (HBA)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2144(para) +msgid "Device plugged into a PCI slot such as a fibre channel or network card." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2149(glossterm) +msgid "HyperText Transfer Protocol (HTTP)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2151(para) +msgid "The protocol that tells browsers where to go to find information." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2156(glossterm) +msgid "Hypertext Transfer Protocol Secure (HTTPS)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2159(para) +msgid "Encrypted HTTP communications using SSL or TLS, most OpenStack API endpoints and many inter-component communications support HTTPS communication." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2166(glossterm) +msgid "Hyper-V" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2168(para) +msgid "One of the hypervisors supported by OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2173(glossterm) +msgid "hypervisor" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2175(para) +msgid "Software that arbitrates and controls VM access to the actual underlying hardware." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2180(glossterm) +msgid "hypervisor pool" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2182(para) +msgid "A collection of hypervisors grouped together through host aggregates." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2188(glossterm) +msgid "hypertext" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2190(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/src/docbkx/common/glossary/glossary-terms.xml:2205(title) +msgid "I" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2207(glossterm) +msgid "ID number" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2209(para) +msgid "Unique numeric ID associated with each user in keystone, conceptually similar to a Linux or LDAP UID." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2215(glossterm) +msgid "Identity API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2217(para) +msgid "Alternative term for the Identity Service API." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2222(glossterm) +msgid "Identity back-end" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2224(para) +msgid "The source used by keystone to retrieve user information an OpenLDAP server for example." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2229(glossterm) +msgid "Identity Service" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2232(para) +msgid "The identity service provided by the keystone project." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2237(glossterm) +msgid "Identity Service API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2239(para) +msgid "The API used to access the OpenStack Identity Service provided through keystone." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2244(glossterm) +msgid "image" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2246(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/src/docbkx/common/glossary/glossary-terms.xml:2256(glossterm) +msgid "Image API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2258(para) +msgid "The glance API endpoint for management of VM images." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2263(glossterm) +msgid "image cache" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2265(para) +msgid "Used by glance to allow images on the local host to be used rather than re-downloading them from the image server each time one is requested." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2272(glossterm) +msgid "image ID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2274(para) +msgid "Combination of URI and UUID used to access glance VM images through the image API." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2279(glossterm) +msgid "image membership" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2281(para) +msgid "A list of tenants that can access a given VM image within glance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2286(glossterm) +msgid "image owner" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2288(para) +msgid "The keystone tenant who owns a glance virtual machine image." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2293(glossterm) +msgid "image registry" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2295(para) +msgid "A list of VM images that are available through glance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2300(glossterm) +msgid "Image Service API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2302(para) +msgid "Alternative name for the glance image API." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2307(glossterm) +msgid "image status" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2309(para) +msgid "The current status of a VM image in glance, not to be confused with the status of a running instance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2315(glossterm) +msgid "image store" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2317(para) +msgid "The back-end store used by glance to store VM images, options include swift, local file system, S3, or HTTP." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2323(glossterm) +msgid "image UUID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2325(para) +msgid "UUID used by glance to uniquely identify each VM image." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2330(glossterm) +msgid "incubated project" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2332(para) +msgid "A community project may be elevated to this status and is then promoted to a core project." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2338(glossterm) +msgid "ingress filtering" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2340(para) +msgid "The process of filtering incoming network traffic. Supported by nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2345(glossterm) +msgid "injection" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2347(para) +msgid "The process of putting a file into a virtual machine image before the instance is started." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2354(glossterm) +msgid "instance" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2356(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/src/docbkx/common/glossary/glossary-terms.xml:2362(glossterm) +msgid "instance ID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2364(para) +msgid "Unique ID that is specific to each running nova VM instance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2369(glossterm) +msgid "instance state" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2371(para) +msgid "The current state of a nova VM image." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2375(glossterm) +msgid "instance type" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2377(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/src/docbkx/common/glossary/glossary-terms.xml:2384(glossterm) +msgid "instance type ID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2386(para) +msgid "Alternative term for a flavor ID." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2390(glossterm) +msgid "instance UUID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2392(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:4016(para) +msgid "Unique ID assigned to each nova VM instance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2397(glossterm) +msgid "interface ID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2399(para) +msgid "Unique ID for a quantum VIF or vNIC in the form of a UUID." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2404(glossterm) +msgid "Internet Service Provider (ISP)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2406(para) +msgid "Any business that provides Internet access to individuals or businesses." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2412(glossterm) +msgid "IP Address" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2414(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/src/docbkx/common/glossary/glossary-terms.xml:2422(glossterm) +msgid "IP Address Management (IPAM)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2424(para) +msgid "The process of automating IP address allocation, deallocation, and management. Currently provided by nova, Melange, and quantum but will eventually be folded into quantum." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2432(glossterm) +msgid "ip6tables" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2434(para) +msgid "Used along with arptables, ebtables, and iptables to create firewalls in nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2439(glossterm) +msgid "iptables" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2441(para) +msgid "Used along with arptables, ebtables, and ip6tables to create firewalls in nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2446(glossterm) +msgid "IPv6" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2448(para) +msgid "Supported by nova, quantum, and other components of OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2453(glossterm) +msgid "iSCSI" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2455(para) +msgid "The SCSI disk protocol tunneled within Ethernet, supported by nova, swift, and glance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2460(glossterm) +msgid "ISO9960" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2462(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:3462(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:4693(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:4700(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:4802(para) +msgid "One of the VM image disk formats supported by glance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2468(glossterm) +msgid "itsec" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2470(para) +msgid "A default roles in the nova RBAC system that allows the user to quarantine an instance in any project." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2484(title) +msgid "J" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2486(glossterm) +msgid "Java" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2488(para) +msgid "A programming language that is used to create systems that involve more than one computer by way of a network." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2494(glossterm) +msgid "JavaScript" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2496(para) +msgid "A scripting language used in web pages." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2500(glossterm) +msgid "JavaScript Object Notation (JSON)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2502(para) +msgid "One of the supported response formats in OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2507(glossterm) +msgid "Jenkins" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2509(para) +msgid "Tool used for OpenStack development to run jobs automatically." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2522(title) +msgid "K" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2524(glossterm) +msgid "kernel-based VM (KVM)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2530(glossterm) +msgid "keystone" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2532(para) +msgid "The project that provides OpenStack Identity services." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2537(glossterm) +msgid "Kickstart" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2539(para) +msgid "A tool to automate system configuration and installation on Red Hat, Fedora, and CentOS based Linux distributions." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2548(title) +msgid "L" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2550(glossterm) +msgid "large object" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2552(para) +msgid "An object within swift that is larger than 5 GBs." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2557(glossterm) +msgid "Launchpad" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2559(para) +msgid "The collaboration site for OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2564(glossterm) +msgid "Layer-2 network" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2567(para) +msgid "Term used for OSI network architecture for the data link layer." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2573(glossterm) +msgid "libvirt" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2575(para) +msgid "Virtualization API library used by OpenStack to interact with many of its supported hypervisors." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2581(glossterm) +msgid "Linux bridge" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2583(para) +msgid "Software used to allow multiple VMs to share a single physical NIC within nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2588(glossterm) +msgid "Linux bridge quantum plug-in" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2590(para) +msgid "Plugin that allows a Linux bridge to understand a quantum port, interface attachment, and other abstractions." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2596(glossterm) +msgid "Linux containers (LXC)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2602(glossterm) +msgid "live migration" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2604(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/src/docbkx/common/glossary/glossary-terms.xml:2612(glossterm) +msgid "load balancer" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2614(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/src/docbkx/common/glossary/glossary-terms.xml:2622(glossterm) +msgid "load balancing" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2624(para) +msgid "The process of spreading client requests between two or more nodes to improve performance and availability." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2639(title) +msgid "M" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2641(glossterm) +msgid "management API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2643(para) +msgid "Alternative term for an admin API." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2647(glossterm) +msgid "management network" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2649(para) +msgid "A network segment used for administration, not accessible to the public internet." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2655(glossterm) +msgid "manager" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2658(para) +msgid "Logical groupings of related code such as the nova volume manager or network manager." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2663(glossterm) +msgid "manifest" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2665(para) +msgid "Used to track segments of a large object within swift." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2670(glossterm) +msgid "manifest object" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2672(para) +msgid "A special swift object that contains the manifest for a large object." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2678(glossterm) +msgid "Melange" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2680(para) +msgid "Project name for OpenStack Network Information Service. To be merged with quantum." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2685(glossterm) +msgid "membership" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2687(para) +msgid "The association between a glance VM image and a tenant, allows images to be shared with specified tenant(s)." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2693(glossterm) +msgid "membership list" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2695(para) +msgid "Contains a list of tenants that can access a given VM image within glance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2700(glossterm) +msgid "memcached" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2702(para) +msgid "A distributed memory object caching system, used by swift for caching." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2707(glossterm) +msgid "memory overcommit" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2709(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/src/docbkx/common/glossary/glossary-terms.xml:2717(glossterm) +msgid "message broker" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2719(para) +msgid "The software package used to provide AMQP messaging capabilities within nova, default is RabbitMQ." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2725(glossterm) +msgid "message bus" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2727(para) +msgid "The main virtual communication line used by all AMQP messages for inter-cloud communications within nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2739(glossterm) +msgid "message queue" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2741(para) +msgid "Passes requests from clients to the appropriate workers and returns the output to the client once the job is complete." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2747(glossterm) +msgid "Meta-Data Server (MDS)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2749(para) +msgid "Stores CephFS metadata." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2753(glossterm) +msgid "migration" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2755(para) +msgid "The process of moving a VM instance from one host to another." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2760(glossterm) +msgid "Monitor (Mon)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2762(para) +msgid "Component of Ceph that communicates with external clients, checks data state and consistency, and performs quorum functions." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2768(glossterm) +msgid "multi-factor authentication" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2770(para) +msgid "Authentication using two or more sources such as a password and a private key, currently unsupported in keystone." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2776(glossterm) +msgid "MultiNic" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2778(para) +msgid "Facility in nova that allows each virtual machine instance to have more than one VIF connected to it." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2793(title) +msgid "N" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2795(glossterm) +msgid "Nebula" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2797(para) +msgid "Released as open source by NASA in 2010 and is the basis for nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2802(glossterm) +msgid "netadmin" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2804(para) +msgid "One of the default roles in the nova RBAC system, allows the user to allocate publicly accessible IP addresses to instances and change firewall rules." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2811(glossterm) +msgid "NetApp volume driver" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2813(para) +msgid "Allows nova to communicate with NetApp storage devices through the NetApp OnCommand Provisioning Manager." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2820(glossterm) +msgid "network" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2822(para) +msgid "A virtual network providing connectivity between entities. For example, a collection of virtual ports that share network connectivity. In quantum terminology, a network is always a Layer-2 network." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2832(glossterm) +msgid "Network Address Translation (NAT)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2834(para) +msgid "The process of modifying IP address information while in-transit. Supported by nova and quantum." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2840(glossterm) +msgid "network controller" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2842(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/src/docbkx/common/glossary/glossary-terms.xml:2849(glossterm) +msgid "Network File System (NFS)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2851(para) +msgid "A method for making file systems available over the network. Supported by OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2856(glossterm) +msgid "network ID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2858(para) +msgid "Unique ID assigned to each network segment within quantum." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2863(glossterm) +msgid "network manager" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2865(para) +msgid "The nova component that manages various network components, such as firewall rules, IP address allocation, and so on." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2871(glossterm) +msgid "network node" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2873(para) +msgid "Any nova node that runs the network worker daemon." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2878(glossterm) +msgid "network segment" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2880(para) +msgid "Represents a virtual, isolated OSI layer 2 subnet in quantum." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2885(glossterm) +msgid "Network Time Protocol (NTP)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2887(para) +msgid "A method of keeping a clock for a host or node correct through communications with a trusted, accurate time source." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2893(glossterm) +msgid "network UUID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2895(para) +msgid "Unique ID for a quantum network segment." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2899(glossterm) +msgid "network worker" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2901(para) +msgid "The nova-network worker daemon, provides services such as giving an IP address to a booting nova instance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2907(glossterm) +msgid "Nexenta volume driver" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2909(para) +msgid "Provides support for NexentaStor devices in nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2914(glossterm) +msgid "Nicira NVP quantum plugin" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2916(para) +msgid "Provides support for the Nicira Network Virtualization Platform (NVP) in quantum." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2921(glossterm) +msgid "No ACK" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2923(para) +msgid "Disables server-side message acknowledgment in the nova RabbitMQ. Increases performance but decreases reliability." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2929(glossterm) +msgid "node" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2931(para) +msgid "A VM instance that runs on a host." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2935(glossterm) +msgid "non-durable exchange" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2937(para) +msgid "Message exchange that is cleared when the service restarts. Its data is not written to persistent storage." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2943(glossterm) +msgid "non-durable queue" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2945(para) +msgid "Message queue that is cleared when the service restarts. Its data is not written to persistent storage." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2951(glossterm) +msgid "non-persistent volume" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2953(para) +msgid "Alternative term for an ephemeral volume." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2958(glossterm) +msgid "nova" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2960(para) +msgid "The OpenStack project that provides compute services." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2965(glossterm) +msgid "nova API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2967(para) +msgid "Alternative term for the nova Compute API." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2972(glossterm) +msgid "nova network" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2974(para) +msgid "A nova component that manages IP address allocation, firewalls, and other network-related tasks." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2980(glossterm) +msgid "nova volume" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2982(para) +msgid "The nova component that manages storage volumes, currently being split off into a separate project named cinder." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2991(title) +msgid "O" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2993(glossterm) +msgid "object" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:2995(para) +msgid "A BLOB of data held by swift, can be in any format." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3000(glossterm) +msgid "Object API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3002(para) ./doc/src/docbkx/common/glossary/glossary-terms.xml:3055(para) +msgid "Alternative term for the swift object API." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3007(glossterm) +msgid "object auditor" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3009(para) +msgid "Opens all objects for an object server and verifies the MD5 hash, size, and metadata for each object." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3015(glossterm) +msgid "object expiration" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3017(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/src/docbkx/common/glossary/glossary-terms.xml:3024(glossterm) +msgid "object hash" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3026(para) +msgid "Uniquely ID for a swift object." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3030(glossterm) +msgid "object path hash" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3032(para) +msgid "Used by swift to determine the location of an object in the ring. Maps objects to partitions." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3038(glossterm) +msgid "object replicator" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3040(para) +msgid "Component of swift that copies and object to remote partitions for fault tolerance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3046(glossterm) +msgid "object server" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3048(para) +msgid "Component of swift that is responsible for managing objects." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3053(glossterm) +msgid "Object Service API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3061(glossterm) +msgid "object storage" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3063(para) +msgid "Provides eventually consistent and redundant storage and retrieval of fixed digital content." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3069(glossterm) +msgid "Object Storage Device (OSD)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3071(para) +msgid "The Ceph storage daemon." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3075(glossterm) +msgid "object versioning" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3077(para) +msgid "Allows a user to set a flag on a swift container so all objects within the container are versioned." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3083(glossterm) +msgid "Oldie" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3085(para) +msgid "Term for a swift process that has been running for a long time, may be an indication of a hung process." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3091(glossterm) +msgid "Open Cloud Computing Interface (OCCI)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3094(para) +msgid "A standardized interface for managing compute, data, and network resources, currently unsupported in OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3100(glossterm) +msgid "OpenID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3102(para) +msgid "Currently unsupported in OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3106(glossterm) +msgid "OpenLDAP" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3108(para) +msgid "An open source LDAP server. Supported by both nova and keystone." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3113(glossterm) +msgid "OpenStack API (OSAPI)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3115(para) +msgid "The core OpenStack API." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3119(glossterm) +msgid "openSUSE" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3127(glossterm) +msgid "Open Virtualization Format (OVF)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3129(para) +msgid "Standard for packaging VM images. Supported in OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3140(glossterm) +msgid "Open vSwitch quantum Plug-in" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3142(para) +msgid "A plugin for quantum used to provide support for Open vSwitch." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3147(glossterm) +msgid "operator" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3150(para) +msgid "The person responsible for planning and maintaining an OpenStack installation." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3155(glossterm) +msgid "orphan" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3158(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/src/docbkx/common/glossary/glossary-terms.xml:3168(title) +msgid "P" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3182(glossterm) +msgid "parent cell" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3184(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/src/docbkx/common/glossary/glossary-terms.xml:3191(glossterm) +msgid "partition" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3193(para) +msgid "A unit of storage within swift used to store objects, exists on top of devices, replicated for fault tolerance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3199(glossterm) +msgid "partition index" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3201(para) +msgid "Contains the locations of all swift partitions within the ring." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3212(glossterm) +msgid "partition shift value" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3214(para) +msgid "Used by swift to determine which partition data should reside on." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3219(glossterm) +msgid "pause" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3221(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/src/docbkx/common/glossary/glossary-terms.xml:3227(glossterm) +msgid "PCI passthrough" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3229(para) +msgid "Allows guest VMs to have exclusive access to a PCI device, currently unsupported in OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3235(glossterm) +msgid "persistent message" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3237(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/src/docbkx/common/glossary/glossary-terms.xml:3243(glossterm) +msgid "persistent volume" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3245(para) +msgid "Changes to these types of disk volumes are saved." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3250(glossterm) +msgid "personality file" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3252(para) +msgid "A file used to customize a nova instance, can be used to inject SSH keys or a specific network configuration." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3265(glossterm) +msgid "plugin" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3267(para) +msgid "Software component providing the actual implementation for quantum APIs, or for Compute APIs, depending on the context." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3279(glossterm) +msgid "policy service" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3281(para) +msgid "Component of keystone that provides a rule management interface and a rule based authorization engine." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3289(para) +msgid "A virtual network port within quantum, VIFs / vNICs are connected to a port." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3294(glossterm) +msgid "port UUID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3296(para) +msgid "Unique ID for a quantum port." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3300(glossterm) +msgid "preseed" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3302(para) +msgid "A tool to automate system configuration and installation on Debian based Linux distributions." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3314(glossterm) +msgid "private image" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3316(para) +msgid "A glance VM image that is only available to specified tenants." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3321(glossterm) +msgid "private IP address" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3323(para) +msgid "An IP address used for management and administration, not available to the public internet." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3329(glossterm) +msgid "private network" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3331(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/src/docbkx/common/glossary/glossary-terms.xml:3350(glossterm) +msgid "project" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3352(para) +msgid "A logical grouping of users within nova, used to define quotas and access to VM images." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3357(glossterm) +msgid "project ID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3359(para) +msgid "User defined alpha-numeric string in nova, the name of a project." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3364(glossterm) +msgid "project VPN" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3366(para) +msgid "Alternative term for a cloudpipe." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3370(glossterm) +msgid "provider" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3372(para) +msgid "An administrator who has access to all hosts and instances." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3377(glossterm) +msgid "proxy node" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3379(para) +msgid "A node that provides the swift proxy service." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3384(glossterm) +msgid "proxy server" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3386(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/src/docbkx/common/glossary/glossary-terms.xml:3393(glossterm) +msgid "public API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3395(para) +msgid "An API endpoint used for both service to service communication and end user interactions." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3400(glossterm) +msgid "public image" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3403(para) +msgid "A glance VM image that is available to all tenants." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3409(glossterm) +msgid "public IP address" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3411(para) +msgid "An IP address that is accessible to end-users." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3416(glossterm) +msgid "public network" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3418(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/src/docbkx/common/glossary/glossary-terms.xml:3440(glossterm) +msgid "Puppet" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3442(para) +msgid "An operating system configuration management tool supported by OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3449(para) +msgid "Programming language used extensively in OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3458(title) +msgid "Q" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3460(glossterm) +msgid "QEMU Copy On Write 2 (QCOW2)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3467(glossterm) +msgid "Qpid" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3469(para) +msgid "Message queue software supported by OpenStack, an alternative to RabbitMQ." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3474(glossterm) +msgid "quantum" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3476(para) +msgid "A core OpenStack project that provides a network connectivity abstraction layer to OpenStack Compute." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3482(glossterm) +msgid "quantum API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3484(para) +msgid "API used to access quantum, provides and extensible architecture to allow custom plugin creation." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3490(glossterm) +msgid "quantum manager" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3492(para) +msgid "Allows nova and quantum integration thus allowing quantum to perform network management for nova VMs." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3498(glossterm) +msgid "quantum plugin" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3500(para) +msgid "Interface within quantum that allows organizations to create custom plugins for advanced features such as QoS, ACLs, or IDS." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3507(glossterm) +msgid "quarantine" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3509(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/src/docbkx/common/glossary/glossary-terms.xml:3528(glossterm) +msgid "Quick EMUlator (QEMU)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3530(para) +msgid "One of the hypervisors supported by OpenStack, generally used for development purposes." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3535(glossterm) +msgid "quota" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3537(para) +msgid "In nova, the ability to set resource limits on a per-project basis." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3545(title) +msgid "R" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3547(glossterm) +msgid "RabbitMQ" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3549(para) +msgid "The default message queue software used by OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3554(glossterm) +msgid "Rackspace Cloud Files" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3556(para) +msgid "Released as open source by Rackspace in 2010, the basis for swift." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3561(glossterm) +msgid "RADOS Block Device (RBD)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3563(para) +msgid "Component of Ceph that allows a Linux block device to be striped over multiple distributed data stores." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3569(glossterm) +msgid "radvd" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3571(para) +msgid "The router advertisement daemon, used by the nova VLAN manager and FlatDHCP manager to provide routing services for VM instances." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3577(glossterm) +msgid "RAM filter" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3579(para) +msgid "The nova setting that allows or disallows RAM overcommitment." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3584(glossterm) +msgid "RAM overcommit" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3586(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/src/docbkx/common/glossary/glossary-terms.xml:3594(glossterm) +msgid "rate limit" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3596(para) +msgid "Configurable option within swift to limit database writes on a per-account and/or per-container basis." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3604(para) +msgid "One of the VM image disk formats supported by glance, an unstructured disk image." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3610(glossterm) +msgid "rebalance" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3612(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/src/docbkx/common/glossary/glossary-terms.xml:3620(glossterm) +msgid "reboot" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3622(para) +msgid "Either a soft or hard reboot of a server. With a soft reboot, the operating system is signaled to restart, which allows for 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/src/docbkx/common/glossary/glossary-terms.xml:3634(glossterm) +msgid "rebuild" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3636(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/src/docbkx/common/glossary/glossary-terms.xml:3642(glossterm) +msgid "Recon" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3644(para) +msgid "A component of swift used to collect metrics." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3651(glossterm) +msgid "record" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3653(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/src/docbkx/common/glossary/glossary-terms.xml:3665(glossterm) +msgid "record ID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3667(para) +msgid "A number within a database that is incremented each time a change is made. Used by swift when replicating." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3673(glossterm) +msgid "Red Dwarf Lite" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3675(para) +msgid "Community project that aims to provide database as a service." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3680(glossterm) +msgid "Red Hat Enterprise Linux (RHEL)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3700(glossterm) +msgid "reference architecture" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3703(para) +msgid "A recommended architecture for an OpenStack cloud." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3708(glossterm) +msgid "registry" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3716(glossterm) +msgid "registry server" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3718(para) +msgid "A glance service that provides VM image metadata information to clients." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3723(glossterm) +msgid "Reliable, Autonomic Distributed Object Store (RADOS)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3726(para) +msgid "A collection of components that provides object storage within Ceph. Similar to swift." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3731(glossterm) +msgid "Remote Procedure Call (RPC)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3733(para) +msgid "The method used by the nova RabbitMQ for intra-service communications." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3738(glossterm) +msgid "replica" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3740(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/src/docbkx/common/glossary/glossary-terms.xml:3747(glossterm) +msgid "replica count" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3749(para) +msgid "The number of replicas of the data in a swift ring." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3754(glossterm) +msgid "replication" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3756(para) +msgid "The process of copying data to a separate physical device for fault tolerance and performance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3764(glossterm) +msgid "replicator" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3766(para) +msgid "The swift back-end process that creates and manages object replicas." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3772(glossterm) +msgid "request ID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3774(para) +msgid "Unique ID assigned to each request sent to nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3791(glossterm) +msgid "rescue image" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3793(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/src/docbkx/common/glossary/glossary-terms.xml:3801(glossterm) +msgid "resize" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3803(para) +msgid "Converts an existing server to a different flavor, in essence, scaling the server up or down. The original server is saved to allow rollback if if there is a problem. All resizes must be tested and explicitly confirmed, at which time the original server is removed." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3813(glossterm) +msgid "RESTful" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3815(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/src/docbkx/common/glossary/glossary-terms.xml:3823(glossterm) +msgid "ring" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3825(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/src/docbkx/common/glossary/glossary-terms.xml:3831(glossterm) +msgid "ring builder" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3833(para) +msgid "Builds and manages rings within swift, assigns partitions to devices, and pushes the configuration to other storage nodes." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3839(glossterm) +msgid "Role Based Access Control (RBAC)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3841(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/src/docbkx/common/glossary/glossary-terms.xml:3849(glossterm) +msgid "role ID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3851(para) +msgid "Alpha-numeric ID assigned to each keystone role." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3856(glossterm) +msgid "rootwrap" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3858(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/src/docbkx/common/glossary/glossary-terms.xml:3864(glossterm) +msgid "round-robin scheduler" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3866(para) +msgid "Type of nova scheduler that evenly distributes instances among available hosts." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3871(glossterm) +msgid "routing key" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3873(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/src/docbkx/common/glossary/glossary-terms.xml:3880(glossterm) +msgid "RPC driver" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3882(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/src/docbkx/common/glossary/glossary-terms.xml:3889(glossterm) +msgid "rsync" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3891(para) +msgid "Used by swift to push object replicas." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3895(glossterm) +msgid "RXTX cap" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3897(para) +msgid "Absolute limit on the amount of network traffic a nova VM instance can send and receive." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3902(glossterm) +msgid "RXTX quota" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3904(para) +msgid "Soft limit on the amount of network traffic a nova VM instance can send and receive." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3909(glossterm) +msgid "Ryu quantum plugin" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3911(para) +msgid "Allows the Ryu Network Operating System to function as a quantum OpenFlow controller." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3920(title) +msgid "S" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3922(glossterm) +msgid "S3" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3924(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/src/docbkx/common/glossary/glossary-terms.xml:3930(glossterm) +msgid "scheduler manager" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3932(para) +msgid "A nova component that determines where VM instances should start. Uses modular design to support a variety of scheduler types." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3944(glossterm) +msgid "scoped token" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3946(para) +msgid "A keystone API access token that is associated with a specific tenant." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3951(glossterm) +msgid "scrubber" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3953(para) +msgid "Checks for and deletes unused VM, the component of glance that implements delayed delete." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3958(glossterm) +msgid "secret key" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3960(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/src/docbkx/common/glossary/glossary-terms.xml:3966(glossterm) +msgid "secure shell (SSH)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3968(para) +msgid "Open source tool used to access remote hosts through an encrypted communications channel, SSH key injection is supported by nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3981(glossterm) +msgid "security group" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3983(para) +msgid "A set of network traffic filtering rules that are applied to a nova instance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3988(glossterm) +msgid "segmented object" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3990(para) +msgid "A swift large object that has been broken up into pieces, the re-assembled object is called a concatenated object." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:3999(para) +msgid "Computer that provides explicit services to the client software running on that system, often managing a variety of computer operations." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4002(para) +msgid "A server is a VM instance in the compute system. Flavor and image are requisite elements when creating a server." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4008(glossterm) +msgid "server image" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4010(para) +msgid "Alternative term for a VM image." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4014(glossterm) +msgid "server UUID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4021(glossterm) +msgid "service catalog" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4023(para) +msgid "Alternative term for the keystone catalog." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4028(glossterm) +msgid "service ID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4030(para) +msgid "Unique ID assigned to each service that is available in the keystone catalog." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4035(glossterm) +msgid "service registration" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4037(para) +msgid "A keystone feature that allows services such as nova to automatically register with the catalog." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4043(glossterm) +msgid "service tenant" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4045(para) +msgid "Special keystone tenant that contains all services that are listed in the catalog." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4050(glossterm) +msgid "service token" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4052(para) +msgid "An administrator defined token used by nova to communicate securely with keystone." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4057(glossterm) +msgid "session back-end" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4059(para) +msgid "The method of storage used by horizon to track client sessions such as local memory, cookies, a database, or memcached." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4065(glossterm) +msgid "session persistence" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4067(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/src/docbkx/common/glossary/glossary-terms.xml:4074(glossterm) +msgid "session storage" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4076(para) +msgid "A horizon component that stores and tracks client session information. Implemented through the Django sessions framework." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4089(glossterm) +msgid "shared IP address" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4091(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 allow 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/src/docbkx/common/glossary/glossary-terms.xml:4107(glossterm) +msgid "shared IP group" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4109(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/src/docbkx/common/glossary/glossary-terms.xml:4126(glossterm) +msgid "shared storage" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4128(para) +msgid "Block storage that is simultaneously accessible by multiple clients. For example, NFS." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4133(glossterm) +msgid "Sheepdog" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4135(para) +msgid "Distributed block storage system for QEMU, supported by OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4140(glossterm) +msgid "Single-root I/O Virtualization (SR-IOV)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4143(para) +msgid "Alternative term for PCI pass-through. Currently unsupported in OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4148(glossterm) +msgid "Simple Cloud Identity Management (SCIM)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4151(para) +msgid "Specification for managing identity in the cloud, currently unsupported by OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4163(glossterm) +msgid "SmokeStack" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4165(para) +msgid "Runs automated tests against the core OpenStack API, written in Rails." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4170(glossterm) +msgid "snapshot" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4172(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/src/docbkx/common/glossary/glossary-terms.xml:4181(glossterm) +msgid "soft reboot" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4183(para) +msgid "A controlled reboot where a VM instance is properly restarted through operating system commands." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4189(glossterm) +msgid "SolidFire Volume Driver" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4191(para) +msgid "The nova volume driver for the SolidFire iSCSI storage appliance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4196(glossterm) +msgid "spread-first scheduler" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4198(para) +msgid "The nova VM scheduling algorithm that attempts to start new VM on the host with the least amount of load." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4204(glossterm) +msgid "SQL-Alchemy" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4206(para) +msgid "An open source SQL toolkit for Python, used in OpenStack." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4211(glossterm) +msgid "SQLite" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4213(para) +msgid "A lightweight SQL database, used as the default persistent storage method in many OpenStack services." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4219(glossterm) +msgid "StackTach" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4221(para) +msgid "Community project that captures nova AMQP communications, useful for debugging." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4227(glossterm) +msgid "static IP address" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4229(para) +msgid "Alternative term for a fixed IP address." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4233(glossterm) +msgid "StaticWeb" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4235(para) +msgid "WSGI middleware component of swift that serves container data as a static web page." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4240(glossterm) +msgid "storage back-end" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4242(para) +msgid "The method that a service uses for persistent storage such as iSCSI, NFS, or local disk." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4247(glossterm) +msgid "storage node" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4249(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/src/docbkx/common/glossary/glossary-terms.xml:4256(glossterm) +msgid "storage manager" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4258(para) +msgid "Component of XenAPI that provides a pluggable interface to support a wide variety of persistent storage back-ends." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4264(glossterm) +msgid "storage manager back-end" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4266(para) +msgid "A persistent storage method supported by XenAPI such as iSCSI or NFS." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4272(glossterm) +msgid "storage services" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4274(para) +msgid "Collective name for the swift object services, container services, and account services." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4279(glossterm) +msgid "strategy" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4281(para) +msgid "Specifies the authentication source used by glance or keystone." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4286(glossterm) +msgid "suspend" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4288(para) +msgid "Alternative term for a paused VM instance." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4293(glossterm) +msgid "swap" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4295(para) +msgid "Disk-based virtual memory, used by operating systems to provide more memory than is actually available on the system." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4301(glossterm) +msgid "swawth" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4303(para) +msgid "An authentication and authorization service for swift, implemented through WSGI middleware, uses swift itself as the persistent backing store." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4310(glossterm) +msgid "swift" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4312(para) +msgid "An OpenStack core project that provides object storage services." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4317(glossterm) +msgid "swift All in One (SAIO)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4319(para) +msgid "Creates a full swift development environment within a single VM." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4324(glossterm) +msgid "swift middleware" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4326(para) +msgid "Collective term for components within swift that allows for additional functionality." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4331(glossterm) +msgid "swift proxy server" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4333(para) +msgid "Acts as the gatekeeper to swift and is responsible for authenticating the user." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4338(glossterm) +msgid "swift storage node" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4340(para) +msgid "A node that runs swift account, container, and object services." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4345(glossterm) +msgid "sync point" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4347(para) +msgid "Point in time since the last container and accounts database sync among nodes within swift." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4353(glossterm) +msgid "sysadmin" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4355(para) +msgid "One of the default roles in the nova RBAC system, allows the user add other users to his or her project, interact with VM images that are associated with the project, and start and stop VM (VM) instances." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4375(glossterm) +msgid "system usage" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4377(para) +msgid "A nova component that along with the notification system collects metrics and usage information, can be used for billing." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4384(glossterm) +msgid "subdomain" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4386(para) +msgid "A domain within a parent domain. Subdomains cannot be registered. Subdomains allow 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/src/docbkx/common/glossary/glossary-terms.xml:4396(glossterm) +msgid "SUSE Linux Enterprise Server (SLES)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4406(title) +msgid "T" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4426(glossterm) +msgid "TempAuth" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4428(para) +msgid "An authentication facility within swift that allows swift itself to perform authentication and authorization, frequently used in testing and development." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4435(glossterm) +msgid "Tempest" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4437(para) +msgid "Automated software test suite designed to run against the trunk of the OpenStack core project." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4455(glossterm) +msgid "TempURL" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4457(para) +msgid "A swift middleware component that allows a user to create URLs for temporary object access." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4463(glossterm) +msgid "tenant" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4465(para) +msgid "A group of users, used to isolate access to nova resources. An alternative term for a nova project." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4471(glossterm) +msgid "Tenant API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4473(para) +msgid "An API that is accessible to tenants." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4477(glossterm) +msgid "tenant endpoint" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4479(para) +msgid "A keystone API endpoint that is associated with one or more tenants." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4484(glossterm) +msgid "tenant ID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4486(para) +msgid "Unique ID assigned to each tenant within keystone, the nova project IDs map to the keystone tenant IDs." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4492(glossterm) +msgid "token" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4494(para) +msgid "An alpha-numeric string of text used to access OpenStack APIs and resources." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4499(glossterm) +msgid "token services" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4501(para) +msgid "A keystone component that manages and validates tokens after a user or tenant has been authenticated." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4507(glossterm) +msgid "tombstone" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4509(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/src/docbkx/common/glossary/glossary-terms.xml:4533(glossterm) +msgid "topic publisher" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4535(para) +msgid "A process that is created when a RPC call is executed, used to push the message to the topic exchange." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4541(glossterm) +msgid "Torpedo" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4543(para) +msgid "Community project used to run automated tests against the OpenStack API." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4548(glossterm) +msgid "transaction ID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4550(para) +msgid "Unique ID assigned to each swift request, used for debugging and tracing." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4555(glossterm) +msgid "transient" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4557(para) +msgid "Alternative term for non-durable." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4561(glossterm) +msgid "transient exchange" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4563(para) +msgid "Alternative term for a non-durable exchange." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4568(glossterm) +msgid "transient message" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4570(para) +msgid "A message that is stored in memory and is lost after the server is restarted." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4576(glossterm) +msgid "transient queue" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4578(para) +msgid "Alternative term for a non-durable queue." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4591(title) +msgid "U" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4593(glossterm) +msgid "Ubuntu" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4606(glossterm) +msgid "unscoped token" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4608(para) +msgid "Alternative term for a keystone default token." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4613(glossterm) +msgid "updater" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4615(para) +msgid "Collective term for a group of swift components that process queued and failed updates for containers and objects." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4623(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/src/docbkx/common/glossary/glossary-terms.xml:4629(glossterm) +msgid "user data" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4631(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/src/docbkx/common/glossary/glossary-terms.xml:4646(glossterm) +msgid "User Mode Linux (UML)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4661(title) +msgid "V" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4669(glossterm) +msgid "VIF UUID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4671(para) +msgid "Unique ID assigned to each quantum VIF." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4677(glossterm) +msgid "VirtualBox" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4683(glossterm) +msgid "Virtual Central Processing Unit (vCPU)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4686(para) +msgid "Allows physical CPUs to be sub-divided and those divisions are then used by instances." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4691(glossterm) +msgid "Virtual Disk Image (VDI)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4698(glossterm) +msgid "Virtual Hard Disk (VHD)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4705(glossterm) +msgid "Virtual IP" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4707(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/src/docbkx/common/glossary/glossary-terms.xml:4716(glossterm) +msgid "Virtual Machine (VM)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4718(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/src/docbkx/common/glossary/glossary-terms.xml:4724(glossterm) +msgid "virtual network" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4726(para) +msgid "An L2 network segment within quantum." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4730(glossterm) +msgid "Virtual Network Computing (VNC)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4732(para) +msgid "Open source GUI and CLI tools used for remote console access to VMs. Supported by nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4737(glossterm) +msgid "Virtual Network InterFace (VIF)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4739(para) +msgid "An interface that is plugged into a port in a quantum network. Typically a virtual network interface belonging to a VM." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4745(glossterm) +msgid "virtual port" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4747(para) +msgid "Attachment point where a virtual interface connects to a virtual network." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4752(glossterm) +msgid "virtual private network (VPN)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4754(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/src/docbkx/common/glossary/glossary-terms.xml:4760(glossterm) +msgid "virtual server" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4762(para) +msgid "Alternative term for a VM or guest." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4766(glossterm) +msgid "virtual switch (vSwitch)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4768(para) +msgid "Software that runs on a host or node and provides the features and functions of a hardware based network switch." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4774(glossterm) +msgid "virtual VLAN" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4776(para) +msgid "Alternative term for a virtual network." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4780(glossterm) +msgid "VLAN manager" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4782(para) +msgid "The nova component that provides dnsmasq, radvd, and sets up forwarding to and from cloudpipe instances." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4788(glossterm) +msgid "VLAN network" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4790(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/src/docbkx/common/glossary/glossary-terms.xml:4800(glossterm) +msgid "VM disk (VMDK)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4807(glossterm) +msgid "VM image" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4809(para) +msgid "Alternative term for an image." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4829(glossterm) +msgid "VM Remote Control (VMRC)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4831(para) +msgid "Method to access VM instance consoles using a web browser. Supported by nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4839(glossterm) +msgid "VMware API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4841(para) +msgid "Supports interaction with VMware products in nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4846(glossterm) +msgid "VNC proxy" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4848(para) +msgid "A nova component that provides users access to the consoles of their VM instances through VNC or VMRC." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4854(glossterm) +msgid "volume" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4856(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/src/docbkx/common/glossary/glossary-terms.xml:4863(glossterm) +msgid "Volume API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4865(para) +msgid "An API on a separate endpoint for attaching, detaching, and creating block storage for compute VMs." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4871(glossterm) +msgid "volume controller" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4873(para) +msgid "A nova component that oversees and coordinates storage volume actions." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4878(glossterm) +msgid "volume driver" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4880(para) +msgid "Alternative term for a volume plugin." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4884(glossterm) +msgid "volume ID" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4886(para) +msgid "Unique ID applied to each storage volume under the nova control." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4891(glossterm) +msgid "volume manager" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4893(para) +msgid "A nova component that creates, attaches, and detaches persistent storage volumes." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4898(glossterm) +msgid "volume node" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4900(para) +msgid "A nova node that runs the nova-volume daemon." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4905(glossterm) +msgid "volume plugin" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4907(para) +msgid "A plugin for the nova volume manager. Provides support for a new and specialized types of back-end storage." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4913(glossterm) +msgid "Volume Service API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4915(para) +msgid "Alternative term for the nova volume API." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4919(glossterm) +msgid "volume worker" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4921(para) +msgid "The nova component that interacts with back-end storage to manage the creation and deletion of volumes and the creation of compute volumes, provided by the nova-volume daemon." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4928(glossterm) +msgid "vSphere" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4943(title) +msgid "W" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4945(glossterm) +msgid "weight" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4947(para) +msgid "Used by swift storage devices to determine which storage devices are suitable for the job. Devices are weighted by size." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4953(glossterm) +msgid "weighted cost" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4955(para) +msgid "The sum of each cost used when deciding where to start a new VM instance in nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4960(glossterm) +msgid "weighing" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4962(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/src/docbkx/common/glossary/glossary-terms.xml:4976(glossterm) +msgid "worker" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4978(para) +msgid "A daemon that carries out tasks. For example, the nova-volume worker attaches storage to an VM instance. Workers listen to a queue and take action when new messages arrive." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4994(title) +msgid "X" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4997(glossterm) +msgid "Xen API" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:4999(para) +msgid "The Xen administrative API. Supported by nova." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:5004(glossterm) +msgid "Xen Cloud Platform (XCP)" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:5010(glossterm) +msgid "Xen Storage Manager Volume Driver" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:5012(para) +msgid "A nova volume plugin that allows for communication with the Xen Storage Manager API." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:5018(glossterm) +msgid "XenServer" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:5033(title) +msgid "Y" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:5043(title) +msgid "Z" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:5045(glossterm) +msgid "ZeroMQ" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:5047(para) +msgid "Message queue software supported by OpenStack, an alternative to RabbitMQ. Also spelled 0MQ." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:5053(glossterm) +msgid "Zuul" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/glossary-terms.xml:5055(para) +msgid "Tool used in OpenStack development to ensure correctly ordered testing of changes in parallel." +msgstr "" + +#: ./doc/src/docbkx/common/glossary/openstack-glossary.xml:9(title) ./doc/src/docbkx/common/glossary/openstack-glossary.xml:12(title) +msgid "OpenStack Glossary" +msgstr "" + +#: ./doc/src/docbkx/common/glossary/openstack-glossary.xml:13(para) +msgid "Use this glossary to get definitions of OpenStack-related words and phrases." +msgstr "" + +#: ./doc/src/docbkx/common/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/src/docbkx/common/glossary/openstack-glossary.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/src/docbkx/openstack-compute-admin/locale/openstack-compute-admin.pot b/doc/src/docbkx/openstack-compute-admin/locale/openstack-compute-admin.pot new file mode 100644 index 0000000000..f3fea4def4 --- /dev/null +++ b/doc/src/docbkx/openstack-compute-admin/locale/openstack-compute-admin.pot @@ -0,0 +1,12708 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2013-03-12 15:09+0800\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/src/docbkx/openstack-compute-admin/computevolumes.xml:135(None) +msgid "@@image: 'figures/ceph/ceph-architecture.png'; md5=f7e854c9dbfb64534c47c3583e774c81" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:6(title) +msgid "Volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:8(title) +msgid "Cinder Versus Nova-Volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:9(para) +msgid "You now have two options in terms of Block Storage. Currently (as of the Folsom release) both are nearly identical in terms of functionality, API's and even the general theory of operation. Keep in mind however that Nova-Volumes is deprecated and will be removed at the release of Grizzly." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:15(para) +msgid "See the Cinder section of the Folsom Install Guide for Cinder-specific information." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:21(title) +msgid "Managing Volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:22(para) +msgid "Nova-volume is the 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). However, nova-volume is not the same implementation that EC2 uses today. Nova-volume 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." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:29(para) +msgid "Before going any further; let's discuss the nova-volume implementation in OpenStack:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:30(para) +msgid "The nova-volumes service uses iSCSI-exposed LVM volumes to the compute nodes which run instances. Thus, there are two components involved:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:35(para) +msgid "lvm2, which works with a VG called \"nova-volumes\" (Refer to http://en.wikipedia.org/wiki/Logical_Volume_Manager_(Linux) for further details)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:41(para) +msgid "open-iscsi, the iSCSI implementation which manages iSCSI sessions on the compute nodes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:46(para) +msgid "Here is what happens from the volume creation to its attachment:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:49(para) +msgid "The volume is created via ; which creates an LV into the volume group (VG) \"nova-volumes\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:53(para) +msgid "The volume is attached to an instance via ; which creates a unique iSCSI IQN that will be exposed to the compute node" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:57(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/src/docbkx/openstack-compute-admin/computevolumes.xml:61(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/src/docbkx/openstack-compute-admin/computevolumes.xml:65(para) +msgid "For this particular walk through, there is one cloud controller running nova-api, nova-scheduler, nova-objectstore, nova-network and nova-volume services. There are two additional compute nodes running nova-compute. The walk through uses a custom partitioning scheme that carves out 60GB of space and labels it as LVM. The network is a /28 .80-.95, and FlatManger is the NetworkManager setting for OpenStack Compute (Nova)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:70(para) +msgid "Please note that the network mode doesn't interfere at all with the way nova-volume works, but networking must be set up for nova-volumes to work. Please refer to Networking for more details." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:75(para) +msgid "To set up Compute to use volumes, ensure that nova-volume is installed along with lvm2. The guide will be split in four parts :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:80(para) +msgid "Installing the nova-volume service on the cloud controller." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:83(para) +msgid "Configuring the \"nova-volumes\" volume group on the compute nodes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:87(para) +msgid "Troubleshooting your nova-volume installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:90(para) +msgid "Backup your nova volumes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:101(title) +msgid "Volume drivers" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:102(para) +msgid "The default nova-volume behaviour can be altered by using different volume drivers that are included in Nova codebase. To set volume driver, use volume_driver flag. The default is as follows:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:113(title) +msgid "Ceph RADOS block device (RBD)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:114(para) +msgid "By Sebastien Han from http://www.sebastien-han.fr/blog/2012/06/10/introducing-ceph-to-openstack/" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:115(para) +msgid "If you are using KVM or QEMU as your hypervisor, the Compute service can be configured to use Ceph's RADOS block devices (RBD) for volumes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:130(title) +msgid "Ceph-architecture.png" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:119(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 is capable of auto-scaling to the exabyte level and beyond, it runs on commodity hardware, it 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. As a result of its open source nature, this portable storage platform may be installed and used in public or private clouds." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:140(title) +msgid "RADOS?" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:141(para) +msgid "You can easily get confused by the denomination: Ceph? RADOS?" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:143(para) +msgid "RADOS: Reliable Autonomic Distributed Object Store is an object storage. RADOS takes care of distributing the objects across the whole storage cluster and replicating them for fault tolerance. It is built with 3 major components:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:151(para) +msgid "Object Storage Device (ODS): the storage daemon - RADOS service, the location of your data. You must have this daemon running on each server of your cluster. For each OSD you can have an associated hard drive disks. For performance purpose it’s usually better to pool your hard drive disk with raid arrays, LVM or btrfs pooling. With that, for one server your will have one daemon running. By default, three pools are created: data, metadata and RBD." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:166(para) +msgid "Meta-Data Server (MDS): this is where the metadata are stored. MDSs builds POSIX file system on top of objects for Ceph clients. However if you are not using the Ceph File System, you do not need a meta data server." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:175(para) +msgid "Monitor (MON): this lightweight daemon handles all the communications with the external applications and the 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 will at least run 3 ceph-mon daemons on separate servers. Quorum decisions and calculus are elected by a majority vote, we expressly need odd number." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:192(para) +msgid "Ceph developers recommend to use btrfs as a file system for the storage. Using XFS is also possible and might be a better alternative for production environments. Neither Ceph nor Btrfs are ready for production. It could be really risky to put them together. This is why XFS is an excellent alternative to btrfs. The ext4 file system is also compatible but doesn’t take advantage of all the power of Ceph." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:203(para) +msgid "We recommend configuring Ceph to use the XFS file system in the near term, and btrfs in the long term once it is stable enough for production." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:209(para) +msgid "See ceph.com/docs/master/rec/file system/ for more information about usable file systems." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:213(title) +msgid "Ways to store, use and expose data" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:214(para) +msgid "There are several ways to store and access your data." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:217(para) +msgid "RADOS: as an object, default storage mechanism." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:220(para) +msgid "RBD: 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/src/docbkx/openstack-compute-admin/computevolumes.xml:226(para) +msgid "CephFS: as a file, POSIX-compliant file system." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:229(para) +msgid "Ceph exposes its distributed object store (RADOS) and it can be accessed via multiple interfaces:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:231(para) +msgid "RADOS Gateway: Swift and Amazon-S3 compatible RESTful interface. See RADOS_Gateway for further information." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:235(para) +msgid "librados and the related C/C++ bindings." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:237(para) +msgid "rbd and QEMU-RBD: Linux kernel and QEMU block devices that stripe data across multiple objects." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:242(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/src/docbkx/openstack-compute-admin/computevolumes.xml:249(title) +msgid "IBM Storwize family and SVC volume driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:250(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/src/docbkx/openstack-compute-admin/computevolumes.xml:255(title) +msgid "Configuring the Storwize family and SVC system" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:258(title) +msgid "iSCSI configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:259(para) +msgid "The Storwize family or SVC system must be configured for iSCSI. Each Storwize family or SVC node should have at least one iSCSI IP address. The 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; there is no need to provide these iSCSI IP addresses directly to the driver." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:273(para) +msgid "You should make sure that the compute nodes have iSCSI network access to the Storwize family or SVC system." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:279(title) +msgid "Configuring storage pools" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:280(para) +msgid "The 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 flag. Details about the configuration flags and how to provide the flags to the driver appear in the next section." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:292(title) +msgid "Configuring user authentication for the driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:294(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/src/docbkx/openstack-compute-admin/computevolumes.xml:307(para) +msgid "Make sure the compute node running the nova-volume management driver has SSH network access to the storage system." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:312(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/src/docbkx/openstack-compute-admin/computevolumes.xml:327(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/src/docbkx/openstack-compute-admin/computevolumes.xml:332(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/src/docbkx/openstack-compute-admin/computevolumes.xml:339(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/src/docbkx/openstack-compute-admin/computevolumes.xml:357(title) +msgid "Creating a SSH key pair using OpenSSH" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:358(para) +msgid "You can create an SSH key pair using OpenSSH, by running:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:364(para) +msgid "The command prompts for a file to save the key pair. For example, if you select 'key' as the filename, two files will be created: key and key.pub. The key file holds the private SSH key and key.pub holds the public SSH key." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:375(para) +msgid "The command also prompts for a passphrase, which should be empty." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:377(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/src/docbkx/openstack-compute-admin/computevolumes.xml:387(title) +msgid "Configuring the Storwize family and SVC driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:390(title) +msgid "Enabling the Storwize family and SVC driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:392(para) +msgid "Set the volume driver to the Storwize family and SVC driver by setting the volume_driver option in nova.conf as follows:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:401(title) +msgid "Configuring options for the Storwize family and SVC driver in nova.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:403(para) +msgid "The following options apply to all volumes and cannot be changed for a specific volume." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:406(caption) +msgid "List of configuration flags for Storwize storage and SVC driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:414(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:980(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1123(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1228(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1372(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1519(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1618(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1721(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1823(td) +msgid "Flag name" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:415(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:981(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1124(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1229(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1373(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1520(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1619(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1722(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1824(td) +msgid "Type" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:416(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:982(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1125(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1230(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1374(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1521(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1620(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1723(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1825(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1349(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1412(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1511(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1610(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1703(td) +msgid "Default" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:417(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:983(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1126(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1231(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1375(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1522(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1621(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1724(td) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1826(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1351(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1414(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1513(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1612(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1705(td) +msgid "Description" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:422(literal) +msgid "san_ip" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:424(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:440(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:482(para) +msgid "Required" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:426(para) +msgid "Management IP or host name" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:430(literal) +msgid "san_ssh_port" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:433(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:491(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:508(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:533(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:544(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:570(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:582(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:605(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:625(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1032(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1041(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1053(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1063(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1283(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1295(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1309(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1319(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1428(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1439(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1452(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1552(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1775(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1879(para) +msgid "Optional" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:434(para) +msgid "22" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:435(para) +msgid "Management port" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:438(literal) +msgid "san_login" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:442(para) +msgid "Management login username" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:446(literal) +msgid "san_password" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:451(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 will use only the SSH private key." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:449(para) +msgid "Required " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:462(para) +msgid "Management login password" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:466(literal) +msgid "san_private_key" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:469(para) +msgid "Required " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:473(para) +msgid "Management login SSH private key" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:479(literal) +msgid "storwize_svc_volpool_name" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:484(para) +msgid "Pool name for volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:488(literal) +msgid "storwize_svc_vol_vtype" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:492(para) +msgid "Striped" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:495(para) +msgid "More details on this configuration option are available in the Storwize family and SVC command line documentation under the mkvdisk command." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:493(para) +msgid "Volume virtualization type " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:505(literal) +msgid "storwize_svc_vol_rsize" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:509(para) +msgid "2%" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:512(para) +msgid "The driver creates thin-provisioned volumes by default. The storwize_svc_vol_rsize flag defines the initial physical allocation size 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/src/docbkx/openstack-compute-admin/computevolumes.xml:510(para) +msgid "Initial physical allocation " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:530(literal) +msgid "storwize_svc_vol_warning" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:534(para) +msgid "0 (disabled)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:535(para) +msgid "Space allocation warning threshold " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:541(literal) +msgid "storwize_svc_vol_autoexpand" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:545(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:606(para) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1586(literal) +msgid "True" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:548(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/src/docbkx/openstack-compute-admin/computevolumes.xml:546(para) +msgid "Enable or disable volume auto expand " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:567(literal) +msgid "storwize_svc_vol_grainsize" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:571(para) +msgid "256" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:572(para) +msgid "Volume grain size in KB" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:578(literal) +msgid "storwize_svc_vol_compression" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:583(para) +msgid "False" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:587(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/src/docbkx/openstack-compute-admin/computevolumes.xml:584(para) +msgid "Enable or disable Real-Time Compression " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:602(literal) +msgid "storwize_svc_vol_easytier" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:609(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/src/docbkx/openstack-compute-admin/computevolumes.xml:607(para) +msgid "Enable or disable Easy Tier " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:621(literal) +msgid "storwize_svc_flashcopy_timeout" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:626(para) +msgid "120" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:629(para) +msgid "The driver wait timeout threshold when creating an OpenStack snapshot. This is actually the maximum amount of time the driver will wait 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/src/docbkx/openstack-compute-admin/computevolumes.xml:627(para) +msgid "FlashCopy timeout threshold (seconds)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:645(title) +msgid "Nexenta" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:646(para) +msgid "NexentaStor Appliance is NAS/SAN software platform designed for building reliable and fast network storage arrays. The NexentaStor is based on the OpenSolaris and uses ZFS as a disk management system. NexentaStor can serve as a storage node for the OpenStack and provide block-level volumes for the virtual servers via iSCSI protocol." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:649(para) +msgid "The Nexenta driver allows you to use Nexenta SA to store Nova volumes. Every Nova volume is represented by a single zvol in a predefined Nexenta volume. 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/src/docbkx/openstack-compute-admin/computevolumes.xml:655(para) +msgid "To use Nova with Nexenta Storage Appliance, you should:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:657(para) +msgid "set volume_driver=nova.volume.nexenta.volume.NexentaDriver." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:659(para) +msgid "set --nexenta_host flag to the hostname or IP of your NexentaStor" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:661(para) +msgid "set --nexenta_user and --nexenta_password to the username and password of the user with all necessary privileges on the appliance, including the access to REST API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:666(para) +msgid "set --nexenta_volume to the name of the volume on the appliance that you would like to use in Nova, or create a volume named nova (it will be used by default)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:672(para) +msgid "Nexenta driver has a lot of tunable flags. Some of them you might want to change:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:674(para) +msgid "nexenta_target_prefix defines the prefix that will be prepended to volume id to form target name on Nexenta" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:677(para) +msgid "nexenta_target_group_prefix defines the prefix for target groups" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:679(para) +msgid "nexenta_blocksize can be set to the size of the blocks in newly created zvols on appliance, with the suffix; for example, the default 8K means 8 kilobytes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:683(para) +msgid "nexenta_sparse is boolean and can be set to use sparse zvols to save space on appliance" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:687(para) +msgid "Some flags that you might want to keep with the default values:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:690(para) +msgid "nexenta_rest_port is the port where Nexenta listens for REST requests (the same port where the NMV works)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:693(para) +msgid "nexenta_rest_protocol can be set to http or https, but the default is auto which makes the driver try to use HTTP and switch to HTTPS in case of failure" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:699(para) +msgid "nexenta_iscsi_target_portal_port is the port to connect to Nexenta over iSCSI" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:705(title) +msgid "Using the XenAPI Storage Manager Volume Driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:706(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, etc. The list below shows some of the storage plugins already supported in Citrix XenServer and Xen Cloud Platform (XCP):" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:718(para) +msgid "NFS VHD: Storage repository (SR) plugin which stores disks as Virtual Hard Disk (VHD) files on a remote Network File System (NFS)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:723(para) +msgid "Local VHD on LVM: SR plugin which represents disks as VHD disks on Logical Volumes (LVM) within a locally-attached Volume Group." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:728(para) +msgid "HBA LUN-per-VDI driver: SR plugin which represents Logical Units (LUs) as Virtual Disk Images (VDIs) sourced by host bus adapters (HBAs). E.g. hardware-based iSCSI or FC support." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:734(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/src/docbkx/openstack-compute-admin/computevolumes.xml:739(para) +msgid "LVHD over FC: SR plugin which represents disks as VHDs on Logical Volumes within a Volume Group created on an HBA LUN. E.g. hardware-based iSCSI or FC support." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:744(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/src/docbkx/openstack-compute-admin/computevolumes.xml:749(para) +msgid "LVHD over iSCSI: SR plugin which represents disks as Logical Volumes within a Volume Group created on an iSCSI LUN." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:754(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/src/docbkx/openstack-compute-admin/computevolumes.xml:760(title) +msgid "Design and Operation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:762(title) +msgid "Definitions" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:765(para) +msgid "Backend: A term for a particular storage backend. This could be iSCSI, NFS, Netapp etc." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:771(para) +msgid "Backend-config: All the parameters required to connect to a specific backend. For e.g. For NFS, this would be the server, path, etc." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:778(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 will use a backend where backups are possible. A flavor can be associated with multiple backends. The volume scheduler, with the help of the driver, will decide which backend will be used to create a volume of a particular flavor. Currently, the driver uses a simple \"first-fit\" policy, where the first backend that can successfully create this volume is the one that is used." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:799(title) +msgid "Operation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:800(para) +msgid "The admin uses the nova-manage command detailed below to add flavors and backends." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:802(para) +msgid "One or more nova-volume service instances will be deployed per availability zone. When an instance is started, it will create storage repositories (SRs) to connect to the backends available within that zone. All nova-volume instances within a zone can see all the available backends. These instances are completely symmetric and hence should be able to service any create_volume request within the zone." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:814(title) +msgid "On XenServer, PV guests required" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:816(para) +msgid "Note that when using XenServer you can only attach a volume to a PV guest." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:822(title) +msgid "Configuring XenAPI Storage Manager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:824(title) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:657(emphasis) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:881(emphasis) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:957(emphasis) +msgid "Prerequisites" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:828(para) +msgid "xensm requires that you use either Citrix XenServer or XCP as the hypervisor. The NetApp and EqualLogic backends are not supported on XCP." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:833(para) +msgid "Ensure all hosts running volume and compute services have connectivity to the storage system." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:841(title) +msgid "Configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:846(emphasis) +msgid "Set the following configuration options for the nova volume service: (nova-compute also requires the volume_driver configuration option.)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:857(emphasis) +msgid "The backend configurations that the volume driver uses need to be created before starting the volume service." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:873(para) +msgid "Example: For the NFS storage manager plugin, the steps below may be used." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:888(emphasis) +msgid "Start nova-volume and nova-compute with the new configuration options." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:895(title) +msgid "Creating and Accessing the volumes from VMs" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:896(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 backends." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:900(para) +msgid "The standard euca-* or OpenStack API commands (such as volume extensions) should be used for creating, destroying, attaching, or detaching volumes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:907(title) +msgid "Configuring Cinder or Nova-Volumes to use a SolidFire Cluster" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:908(para) +msgid "The SolidFire Cluster is a high performance all SSD iSCSI storage device, providing 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 per volume basis. The SolidFire cluster offers all of these things along with de-duplication, compression and an architecture that takes full advantage of SSD's." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:914(para) +msgid "To configure and use a SolidFire cluster with Nova-Volumes modify your nova.conf or cinder.conf file as shown below:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:922(para) +msgid "To configure and use a SolidFire cluster with Cinder, modify your cinder.conf file similarly to how you would a nova.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:933(title) +msgid "NetApp drivers" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:934(para) +msgid "NetApp drivers for 7-Mode and clustered Data ONTAP® have been written in two variants namely iSCSI and NFS drivers. Both variants provide OpenStack with access to NetApp 7-Mode controllers and clustered Data ONTAP for provisioning and managing OpenStack volumes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:941(title) +msgid "NetApp iSCSI drivers for 7-Mode and clustered Data ONTAP" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:943(para) +msgid "The NetApp iSCSI drivers for 7-Mode and clustered Data ONTAP systems provide OpenStack compute instances with access to NetApp 7-Mode storage controllers and clustered Data ONTAP storage systems." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:949(title) +msgid "NetApp iSCSI driver for 7-Mode storage controller" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:950(para) +msgid "The NetApp iSCSI driver for 7-Mode is a driver interface from OpenStack to the NetApp 7-Mode storage controllers for provisioning and managing the SAN block storage entity, that is, NetApp LUN using iSCSI protocol." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:956(para) +msgid "The NetApp iSCSI driver for 7-Mode requires additional NetApp management software, namely OnCommand™, installed and configured for using 7-Mode storage controllers before configuring the 7-Mode driver on OpenStack." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:962(title) +msgid "Configuration options available for the 7-Mode system driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:964(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1502(para) +msgid "Set the volume driver to the NetApp 7-Mode driver by setting the volume_driver option in cinder.conf as follows:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:972(caption) +msgid "List of configuration flags for NetApp 7-Mode iSCSI driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:988(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1131(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1527(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1626(literal) +msgid "netapp_wsdl_url" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:990(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1004(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1013(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1023(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1133(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1151(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1161(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1170(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1180(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1239(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1248(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1262(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1272(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1383(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1393(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1407(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1417(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1529(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1543(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1560(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1569(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1628(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1644(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1654(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1663(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1673(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1732(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1741(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1754(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1764(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1834(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1844(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1858(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1868(para) +msgid "Mandatory" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:992(para) +msgid "WSDL URL for NetApp OnCommand services running on an OnCommand installation. OnCommand is used as intermediate management software between OpenStack and 7-Mode storage systems." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1002(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1168(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1260(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1405(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1558(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1661(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1752(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1856(literal) +msgid "netapp_login" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1006(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1562(para) +msgid "Login user name for OnCommand installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1011(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1178(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1270(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1415(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1567(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1671(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1762(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1866(literal) +msgid "netapp_password" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1015(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1571(para) +msgid "Login password for OnCommand installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1020(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1148(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1236(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1380(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1540(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1641(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1729(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1831(literal) +msgid "netapp_server_hostname" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1025(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1545(para) +msgid "OnCommand server host name/IP address." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1030(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1159(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1246(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1391(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1550(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1652(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1739(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1842(literal) +msgid "netapp_server_port" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1033(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1553(para) +msgid "8088" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1034(para) +msgid "OnCommand server port." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1038(literal) +msgid "netapp_storage_service" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1043(para) +msgid "Storage service to use while provisioning. Storage service is configured on OnCommand." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1049(literal) +msgid "netapp_storage_service_prefix" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1055(para) +msgid "Storage service prefix to use on OnCommand if using volume_types." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1061(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1307(literal) +msgid "netapp_vfiler" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1065(para) +msgid "The vFiler® unit name if using vFiler to host OpenStack volumes. MultiStore® must be enabled before using vFiler for provisioning." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1075(para) +msgid "Make sure that at least one of the flags netapp_storage_service or netapp_storage_service_prefix is specified in configuration." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1080(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1189(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1332(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1461(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1577(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1682(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1785(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1889(para) +msgid "Refer to OpenStack NetApp community for detailed information." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1087(title) +msgid "NetApp iSCSI driver for clustered Data ONTAP" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1089(para) +msgid "The NetApp iSCSI driver for clustered Data ONTAP is a driver interface from OpenStack to clustered Data ONTAP storage systems that allows the provisioning and managing the SAN block storage entity, that is, NetApp LUN using iSCSI protocol." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1095(para) +msgid "The NetApp iSCSI driver for clustered Data ONTAP requires additional NetApp management software namely OnCommand, WFA and the NetApp Cloud Web Service application to be installed and configured for using clustered Data ONTAP systems before configuring ONTAP cluster driver on OpenStack." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1103(title) +msgid "Configuration options for the clustered Data ONTAP driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1105(para) +msgid "Set the volume driver to the clustered Data ONTAP driver by setting the volume_driver option in cinder.conf as follows:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1114(caption) +msgid "List of configuration flags for clustered Data ONTAP iSCSI driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1135(para) +msgid "WSDL URL for NetApp Cloud Web Service application serving as management software. NetApp Cloud Web Service is an intermediate service for propagating requests from the OpenStack driver to different NetApp softwares installed in the environment and the clustered Data ONTAP systems." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1153(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1646(para) +msgid "The host name/IP address of NetApp Cloud Web Service installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1163(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1656(para) +msgid "The port on which NetApp Cloud Web Service listens." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1172(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1665(para) +msgid "Login user name for NetApp Cloud Web Service installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1182(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1675(para) +msgid "Login password for NetApp Cloud Web Service installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1196(title) +msgid "NetApp iSCSI direct driver for 7-Mode storage controller" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1198(para) +msgid "The NetApp iSCSI direct driver for 7-Mode is a driver interface from OpenStack to the NetApp 7-Mode storage controllers for the provisioning and managing the SAN block storage entity, that is, NetApp LUN using iSCSI protocol." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1204(para) +msgid "The NetApp iSCSI direct driver for 7-Mode does not require any additional management software to achieve the desired functionality. It uses NetApp APIs to interact with the 7-Mode storage controller." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1210(title) +msgid "Configuration options for the 7-Mode direct driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1212(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1705(para) +msgid "Set the volume driver to the NetApp 7-Mode direct driver by setting the volume_driver option in cinder.conf as follows:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1219(caption) +msgid "List of configuration flags for NetApp 7-Mode iSCSI direct driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1241(para) +msgid "The management IP address for the 7-Mode storage controller." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1250(para) +msgid "The 7-Mode controller port to use for communication. As a custom 80 is used for http and 443 is used for https communication. The default ports can be changed if other ports are used for ONTAPI® on 7-Mode controller." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1264(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1756(para) +msgid "Login user name for 7-Mode controller management." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1274(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1766(para) +msgid "Login password for 7-Mode controller management." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1280(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1425(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1772(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1876(literal) +msgid "netapp_transport_type" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1284(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1429(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1776(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1880(para) +msgid "http" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1285(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1777(para) +msgid "Transport protocol to use for communicating with 7-Mode controller. Supported protocols include http and https." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1292(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1436(literal) +msgid "netapp_size_multiplier" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1296(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1440(para) +msgid "1.2" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1297(para) +msgid "The quantity to be multiplied by the requested OpenStack volume size which then is used to make sure that the final size is available on the 7-Mode controller before creating the OpenStack volume on the same controller." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1311(para) +msgid "The vFiler unit to be used for provisioning of OpenStack volumes. Use this only if using MultiStore®." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1317(literal) +msgid "netapp_volume_list" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1321(para) +msgid "Comma separated list of NetApp volumes to be used for provisioning on 7-Mode controller. This option is used to restrict provisioning to the specified NetApp controller volumes. In case this option is not specified all NetApp controller volumes except the controller root volume are used for provisioning OpenStack volumes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1339(title) +msgid "NetApp iSCSI direct driver for clustered Data ONTAP" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1340(para) +msgid "The NetApp iSCSI direct driver for clustered Data ONTAP is a driver interface from OpenStack to clustered Data ONTAP storage systems for provisioning and managing the SAN block storage entity, that is, NetApp LUN using iSCSI protocol." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1346(para) +msgid "The NetApp iSCSI direct driver for clustered Data ONTAP does not require additional management software to achieve the desired functionality. It uses NetApp APIs to interact with the clustered Data ONTAP." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1352(title) +msgid "Configuration options for the clustered Data ONTAP direct driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1355(para) +msgid "Set the volume driver to the clustered Data ONTAP direct driver by setting the volume_driver option in cinder.conf as follows:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1363(caption) +msgid "List of configuration flags for clustered Data ONTAP iSCSI direct driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1385(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1836(para) +msgid "The cluster management IP address for the clustered Data ONTAP." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1395(para) +msgid "The clustered Data ONTAP port to use for communication. As a custom 80 is used for http and 443 is used for https communication. The default ports can be changed if other ports are used for ONTAPI on clustered Data ONTAP." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1409(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1860(para) +msgid "Login user name for clustered Data ONTAP management." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1419(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1870(para) +msgid "Login password for clustered Data ONTAP management." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1430(para) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1881(para) +msgid "Transport protocol for communicating with clustered Data ONTAP. Supported protocols include http and https." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1441(para) +msgid "The quantity to be multiplied to the requested OpenStack volume size which then is used to make sure that the final size is available on clustered Data ONTAP Vserver before creating OpenStack volume on the same." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1450(literal) +msgid "netapp_vserver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1453(para) +msgid "openstack" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1454(para) +msgid "The Vserver on the cluster on which provisioning of OpenStack volumes will be done." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1469(title) +msgid "NetApp NFS drivers for 7-Mode and clustered Data ONTAP systems" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1472(para) +msgid "The NetApp NFS drivers for 7-Mode and clustered Data ONTAP systems provide OpenStack compute instances with access to NetApp 7-Mode storage controllers and clustered Data ONTAP storage systems for provisioning and managing entities on NFS exports on NetApp storage controllers." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1479(para) +msgid "The NFS exports are mounted on the OpenStack nodes after which the OpenStack volumes can be created and managed using the NetApp NFS drivers on the NFS exports. The OpenStack compute instances get the required block storage device as files on NFS exports managed by OpenStack." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1486(title) +msgid "NetApp NFS driver for 7-Mode storage controller" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1487(para) +msgid "The NetApp NFS driver for 7-Mode is a driver interface from OpenStack to NetApp 7-Mode storage controllers for provisioning and managing OpenStack volumes on NFS exports provided by the 7-Mode storage controller." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1493(para) +msgid "The NetApp NFS driver for 7-Mode requires additional NetApp management software namely OnCommand which needs installed and configured for using 7-Mode storage controllers before configuring 7-Mode NFS driver on OpenStack." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1500(title) +msgid "Configuration options available for the 7-Mode NFS driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1510(caption) +msgid "List of configuration flags for NetApp 7-Mode NFS driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1531(para) +msgid "WSDL URL for NetApp OnCommand Webservices running on an OnCommand installation. OnCommand is used as an intermediate management software between OpenStack and 7-Mode storage systems." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1554(para) +msgid "OnCommand server port to connect to." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1584(title) +msgid "NetApp NFS driver for clustered Data ONTAP" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1585(para) +msgid "The NetApp NFS driver for clustered Data ONTAP is a driver interface from OpenStack to clustered Data ONTAP systems for provisioning and managing OpenStack volumes on NFS exports provided by the clustered Data ONTAP system." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1591(para) +msgid "The NetApp NFS driver for clustered Data ONTAP requires additional NetApp management software namely OnCommand, WFA and NetApp Cloud Web Service application to be installed and configured for using clustered Data ONTAP systems before configuring clustered Data ONTAP NFS driver on OpenStack." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1598(title) +msgid "Configuration options for the clustered Data ONTAP NFS driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1601(para) +msgid "Set the volume driver to the clustered Data ONTAP NFS driver by setting the volume_driver option in cinder.conf as follows:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1610(caption) +msgid "List of configuration flags for clustered Data ONTAP NFS driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1630(para) +msgid "WSDL URL for NetApp Cloud Web Service serving as management software. NetApp Cloud Web Service is an intermediate service used for propagating requests from the OpenStack driver to different NetApp softwares installed in the environment and the ONTAP cluster systems." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1689(title) +msgid "NetApp NFS direct driver for 7-Mode storage controller" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1691(para) +msgid "The NetApp NFS direct driver for 7-Mode is a driver interface from OpenStack to NetApp 7-Mode storage controllers for provisioning and managing OpenStack volumes on NFS exports provided by the 7-Mode storage controller." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1697(para) +msgid "The NetApp NFS direct driver for 7-Mode does not require any additional management software to achieve the desired functionality. It uses NetApp APIs to interact with the 7-Mode storage controller." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1703(title) +msgid "Configuration options for the 7-Mode NFS direct driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1713(caption) +msgid "List of configuration flags for NetApp 7-Mode NFS direct driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1734(para) +msgid "The management IP address for the NetApp 7-Mode storage controller." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1743(para) +msgid "The 7-Mode controller port to use for communication. As a custom 80 is used for http and 443 is used for https communication. The default ports can be changed if other ports are for ONTAPI on 7-Mode controller." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1792(title) +msgid "NetApp NFS direct driver for clustered Data ONTAP" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1793(para) +msgid "The NetApp NFS direct driver for clustered Data ONTAP is a driver interface from OpenStack to clustered Data ONTAP system for provisioning and managing OpenStack volumes on NFS exports provided by the clustered Data ONTAP system." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1799(para) +msgid "The NetApp NFS direct driver for clustered Data ONTAP does not require any additional management software to achieve the desired functionality. It uses NetApp APIs to interact with the clustered Data ONTAP." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1805(title) +msgid "Configuration options for the clustered Data ONTAP NFS direct driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1807(para) +msgid "Set the volume driver to the NetApp clustered Data ONTAP direct driver by setting the volume_driver option in cinder.conf as follows:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1815(caption) +msgid "List of configuration flags for NetApp clustered Data ONTAP NFS direct driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1846(para) +msgid "The clustered Data ONTAP port for communication. As a custom 80 is used for http and 443 is used for https communication. The default ports can be changed if other ports are used for ONTAPI on clustered Data ONTAP." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1899(title) +msgid "HP / LeftHand SAN" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1900(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 (Xen, KVM, OpenVZ etc) by exposing the volumes via ISCSI to connect to the instances." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1906(para) +msgid "The HpSanISCSIDriver allows you to use a HP/Lefthand SAN that supports the Cliq interface. Every supported volume operation translates into a cliq call in the backend." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1910(para) +msgid "To use Nova with HP/Lefthand SAN, you should set the following required parameters in nova.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1913(para) +msgid "set volume_driver=nova.volume.san.HpSanISCSIDriver." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1915(para) +msgid "set san_ip flag to the hostname or VIP of your Virtual Storage Appliance (VSA)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1918(para) +msgid "set san_login and san_password to the username and password of the ssh user with all necessary privileges on the appliance." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1924(para) +msgid "set san_ssh_port=16022 the default is set to 22, but the default for the VSA is usually 16022." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1928(para) +msgid "set san_clustername to the name of the cluster on which the associated volumes will be created." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1932(para) +msgid "Some of the optional settings with their default values:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1935(para) +msgid "san_thin_provision=True set it to False to disable thin provisioning." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1937(para) +msgid "san_is_local=False This is almost always False for this driver. Setting it to True will try and run the cliq commands locally instead of over ssh." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1943(title) +msgid "Configuring the VSA" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1944(para) +msgid "In addition to configuring the nova-volume service some pre configuration has to happen on the VSA for proper functioning in an Openstack environment." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1951(para) +msgid "Configure Chap on each of the nova-compute nodes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1955(para) +msgid "Add Server associations on the VSA with the associated Chap and initiator information. Note that the name should correspond to the 'hostname' of the nova-compute node. For Xen this will be the hypervisor hostname. This can either be done through Cliq or the Centralized Management Console." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1971(title) +msgid "EMC SMI-S iSCSI Driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1972(para) +msgid "The EMCSMISISCSIDriver is based on the existing ISCSIDriver, with the ability to create/delete and attach/detach volumes and create/delete snapshots, etc." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1975(para) +msgid "The EMCSMISISCSIDriver executes the volume operations by communicating with the backend EMC storage. It uses a CIM client in python called PyWBEM to make CIM operations over HTTP." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1978(para) +msgid "The EMC CIM Object Manager (ECOM) is packaged with the EMC SMI-S Provider. It is a CIM server that allows CIM clients to make CIM operations over HTTP, using SMI-S in the backend for EMC storage operations." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1982(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/src/docbkx/openstack-compute-admin/computevolumes.xml:1986(title) ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:19(title) +msgid "Requirements" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1987(para) +msgid "EMC SMI-S Provider V4.5.1 and higher is required. SMI-S can be downloaded from EMC's Powerlink web site. Refer to the EMC SMI-S Provider release notes for installation instructions." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1991(para) +msgid "EMC storage VMAX Family and VNX Series are supported." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1994(title) +msgid "Supported Operations" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1995(para) +msgid "The following operations will be supported on both VMAX and VNX arrays:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1998(para) +msgid "Create volume" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:1999(para) +msgid "Delete volume" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2000(para) +msgid "Attach volume" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2001(para) +msgid "Detach volume" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2002(para) +msgid "Create snapshot" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2003(para) +msgid "Delete snapshot" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2004(para) +msgid "Create cloned volume" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2005(para) +msgid "Copy image to volume" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2006(para) +msgid "Copy volume to image" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2008(para) +msgid "The following operations will be supported on VNX only:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2010(para) +msgid "Create volume from snapshot" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2012(para) +msgid "Only thin provisioning is supported." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2015(title) +msgid "Preparation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2017(para) +msgid "Install python-pywbem package. For example:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2019(para) +msgid "Setup SMI-S. Download SMI-S from PowerLink and install it following the instructions of SMI-S release notes. Add your VNX/VMAX/VMAXe arrays to SMI-S following the SMI-S release notes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2023(para) +msgid "Register with VNX." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2024(para) +msgid "Create Masking View on VMAX." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2028(title) +msgid "Register with VNX" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2029(para) +msgid "For a VNX volume to be exported to a Compute node, the node needs to be registered with VNX first." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2031(para) +msgid "On the Compute node 1.1.1.1, do the following (assume 10.10.61.35 is the iscsi target):" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2038(literal) ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2052(literal) +msgid "10.10.61.35" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2049(para) +msgid "Log in to VNX from the Compute node using the target corresponding to the SPA port:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2052(literal) +msgid "iqn.1992-04.com.emc:cx.apm01234567890.a0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2054(para) +msgid "Assume iqn.1993-08.org.debian:01:1a2b3c4d5f6g is the initiator name of the Compute node. Login 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/src/docbkx/openstack-compute-admin/computevolumes.xml:2058(para) +msgid "Click the \"Register\" button, select \"CLARiiON/VNX\" and enter the host name myhost1 and IP address myhost1. Click Register. Now host 1.1.1.1 will appear under Hosts->Host List as well." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2061(para) +msgid "Log out of VNX on the Compute node:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2065(para) +msgid "Log in to VNX from the Compute node using the target corresponding to the SPB port:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2069(para) +msgid "In Unisphere register the initiator with the SPB port." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2070(para) +msgid "Log out:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2076(title) +msgid "Create Masking View on VMAX" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2077(para) +msgid "For VMAX, user needs to do initial setup on the Unisphere for VMAX server first. On the Unisphere for VMAX server, create initiator group, storage group, port group, and put them in a masking view. Initiator group contains the initiator names of the openstack hosts. Storage group should have at least 6 gatekeepers." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2083(title) +msgid "Config file cinder.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2084(para) +msgid "Make the following changes in /etc/cinder/cinder.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2085(para) +msgid "For VMAX, we have the following entries where 10.10.61.45 is the IP address of the VMAX iscsi target." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2093(para) +msgid "For VNX, we have the following entries where 10.10.61.35 is the IP address of the VNX iscsi target." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2101(para) +msgid "Restart the cinder-volume service." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2104(title) +msgid "Config file cinder_emc_config.xml" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2105(para) +msgid "Create the file /etc/cinder/cinder_emc_config.xml. We don't need to restart service for this change." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2107(para) +msgid "For VMAX, we have the following in the xml file:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2119(para) +msgid "For VNX, we have the following in the xml file:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2130(para) +msgid "MaskingView is required for attaching VMAX volumes to an OpenStack VM. A Masking View can be created using Unisphere for VMAX. The Masking View needs to have an Initiator Group that contains the initiator of the OpenStack compute node that hosts the VM." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2134(para) +msgid "StorageType is the thin pool where user wants to create volume from. Only thin LUNs are supported by the plugin. is required for both VMAX and VNX. Thin pools can be created using Unisphere for VMAX and VNX." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2137(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/src/docbkx/openstack-compute-admin/computevolumes.xml:2143(title) +msgid "Boot From Volume" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2144(para) +msgid "The Compute service has preliminary support for booting an instance from a volume." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2147(title) +msgid "Creating a bootable volume" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2148(para) +msgid "To create a bootable volume, mount the volume to an existing instance, and then build a volume-backed image. Here is an example based on exercises/boot_from_volume.sh. This example assumes that you have a running instance with a 1GB volume mounted at /dev/vdc. These commands will make the mounted volume bootable using a CirrOS image. As root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2168(para) +msgid "Detach the volume once you are done." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2171(title) +msgid "Booting an instance from the volume" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2172(para) +msgid "To boot a new instance from the volume, use the command with the --block_device_mapping flag. The output for shows the following documentation about this flag:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2183(literal) +msgid "dev_name" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2185(para) +msgid "A device name where the volume will be attached in the system at /dev/dev_name. This value is typically vda." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2191(literal) +msgid "id" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2193(para) +msgid "The ID of the volume to boot from, as shown in the output of ." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2198(literal) +msgid "type" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2200(para) +msgid "This is either snap, which means that the volume was created from a snapshot, or anything other than snap (a blank string is valid). In the example above, the volume was not created from a snapshot, so we will leave this field blank in our example below." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2208(literal) +msgid "size (GB)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2210(para) +msgid "The size of the volume, in GB. It is safe to leave this blank and have the Compute service infer the size." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2215(literal) +msgid "delete_on_terminate" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2217(para) +msgid "A boolean to indicate whether the volume should be deleted when the instance is terminated. True can be specified as True or 1. False can be specified as False or 0." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2181(para) +msgid "The command arguments are:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2226(para) +msgid "Because of bug #1008622, you must specify an image when booting from a volume, even though this image will not be used." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2234(replaceable) +msgid "f4addd24-4e8a-46bb-b15d-fae2591f1a35" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2234(replaceable) +msgid "mykey" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computevolumes.xml:2225(para) +msgid "The following example will attempt boot from volume with ID=13, it will not delete on terminate. Replace the --image flag with a valid image on your system, and the --key_name with a valid keypair name:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-cinder.xml:5(title) +msgid "Troubleshoot your cinder installation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-cinder.xml:6(para) +msgid "This section is intended to help solve some basic and common errors that are encountered during setup and configuration of Cinder. The focus here is on failed creation of volumes. The most important thing to know is where to look in case of a failure. There are two log files that are especially helpful in the case of a volume creation failure. The first is the cinder-api log, and the second is the cinder-volume log." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-cinder.xml:11(para) +msgid "The cinder-api log is useful in determining if you have endpoint or connectivity issues. If you send a request to create a volume and it fails, it's a good idea to look here first and see if the request even made it to the Cinder service. If the request seems to be logged, and there are no errors or trace-backs then you can move to the cinder-volume log and look for errors or trace-backs there." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-cinder.xml:18(para) +msgid "There are some common issues with both nova-volumes and Cinder on Folsom to look out for, the following refers to Cinder only, but is applicable to both Nova-Volume and Cinder unless otherwise specified." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-cinder.xml:22(emphasis) +msgid "Create commands are in cinder-api log with no error" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-cinder.xml:27(emphasis) +msgid "state_path and volumes_dir settings" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-cinder.xml:28(para) +msgid "As of Folsom Cinder is using tgtd 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/src/docbkx/openstack-compute-admin/troubleshoot-cinder.xml:34(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, Cinder uses a state_path variable, which if installing via 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/src/docbkx/openstack-compute-admin/troubleshoot-cinder.xml:40(para) +msgid "While this should all be handled for you by you installer, it can go wrong. If you're having 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 doesn't exist, and it should give you information to specify what path exactly it was looking for." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-cinder.xml:47(emphasis) +msgid "persistent tgt include file" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-cinder.xml:48(para) +msgid "Along with the volumes_dir mentioned above, 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 /etc/tgt/conf.d, and you should have created this when you went through the install guide. If you haven't or you're running into issues, verify that you have a file /etc/tgt/conf.d/cinder.conf (for Nova-Volumes, this will be /etc//tgt/conf.d/nova.conf)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-cinder.xml:54(para) +msgid "If the files not there, you can create it easily by doing the following:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-cinder.xml:61(emphasis) +msgid "No sign of create call in the cinder-api log" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-cinder.xml:63(para) +msgid "This is most likely going to be a minor adjustment to you nova.conf file. Make sure that your nova.conf has the following entry:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-cinder.xml:69(para) +msgid "And make certain that you EXPLICITLY set enabled_apis as the default will include osapi_volume:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:57(None) +msgid "@@image: 'figures/novnc/SCH_5009_V00_NUAC-VNC_OpenStack.png'; md5=182dc38019a220c851e1c94aa50f4565" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:7(title) +msgid "Overview of VNC Proxy" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:10(para) +msgid "The VNC Proxy is an OpenStack component that allows users of the Compute service to access their instances through VNC clients." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:12(para) +msgid "The VNC console connection works as follows:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:15(para) +msgid "User connects to API and gets an access_url like http://ip:port/?token=xyz." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:19(para) +msgid "User pastes URL in browser or as client parameter." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:22(para) +msgid "Browser/Client connects to proxy." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:25(para) +msgid "Proxy talks to nova-consoleauth to authorize the user's token, and then maps the token to the private host and port of an instance's VNC server. The compute host specifies the address the proxy should use to connect via the nova.conf option vncserver_proxyclient_address. In this way, the vnc proxy works as a bridge between the public network, and the private host network." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:32(para) +msgid "Proxy initiates connection to VNC server, and continues proxying until the session ends." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:36(para) +msgid "The proxy also performs the required function of tunneling the VNC protocol over Websockets so that the noVNC client has a way to talk VNC. Note that in general, the VNC proxy performs multiple functions:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:42(para) +msgid "Bridges between public network (where clients live) and private network (where vncservers live)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:46(para) +msgid "Mediates token authentication." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:52(title) +msgid "NoVNC Process" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:49(para) +msgid "Transparently deals with hypervisor-specific connection details to provide a uniform client experience. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:66(title) +msgid "About nova-consoleauth" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:69(para) +msgid "Both client proxies leverage a shared service to manage token auth called nova-consoleauth. This service must be running in order 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/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:73(para) +msgid "The nova-consoleauth shared service should not be confused with nova-console, which is a XenAPI-specific service that is not used by the most recent VNC proxy architecture." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:80(title) +msgid "Typical Deployment" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:83(para) +msgid "A typical deployment will consist of the following components:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:88(para) +msgid "One nova-consoleauth process. Typically this runs on the controller host." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:91(para) +msgid "One or more nova-novncproxy services. This supports browser-based novnc clients. For simple deployments, this service typically will run on the same machine as nova-api, since it proxies between the public network and the private compute host network." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:96(para) +msgid "One or more nova-xvpvncproxy services. This supports the special Java client discussed in this document. For simple deployments, this service typically will run on the same machine as nova-api, since it proxies between the public network and the private compute host network." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:102(para) +msgid "One or more compute hosts. These compute hosts must have correctly configured configuration options, as described below." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:109(title) +msgid "Getting an Access URL" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:112(para) +msgid "Nova provides the ability to create access_urls through the os-consoles extension. Support for accessing this URL is provided by novaclient:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:116(replaceable) ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:123(replaceable) ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:172(replaceable) ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:228(replaceable) +msgid "[server_id]" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:116(replaceable) +msgid "[novnc|xvpvnc]" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:118(para) +msgid "Specify 'novnc' to retrieve a URL suitable for pasting into a web browser. Specify 'xvpvnc' for a URL suitable for pasting into the Java client." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:121(para) +msgid "So to request a web browser URL:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:128(title) +msgid "VNC Configuration Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:130(para) +msgid "If you intend to support live migration, you cannot specify a specific IP address for vncserver_listen, because that IP address will not exist on the destination host." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:133(para) +msgid "vncserver_proxyclient_address - Defaults to 127.0.0.1. This is the address of the compute host that nova will instruct proxies to use when connecting to instance servers. For all-in-one XenServer domU deployments this can be set to 169.254.0.1. For multi-host XenServer domU deployments this can be set to a dom0 management ip on the same network as the proxies. For multi-host libvirt deployments this can be set to a host management IP on the same network as the proxies." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:145(title) +msgid "Accessing VNC Consoles with a Java client" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:148(para) +msgid "To enable support for the OpenStack Java VNC client in Compute, we provide the service, which you should run to enable this feature." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:153(para) +msgid "xvpvncproxy_port=[port] - port to bind (defaults to 6081)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:157(para) +msgid "xvpvncproxy_host=[host] - host to bind (defaults to 0.0.0.0)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:161(para) +msgid "As a client, you will need a special Java client, which is a version of TightVNC slightly modified to support our token auth:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:169(para) +msgid "Then, to create a session, first request an access URL using and then run the client like so. To retrieve access URL:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:174(para) +msgid "To run client:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:175(replaceable) +msgid "[access_url]" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:180(title) +msgid "nova-novncproxy (novnc)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:183(para) +msgid "You will need the novnc package installed, which contains the nova-novncproxy service. As root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:186(para) +msgid "The service should start automatically on install. To restart it:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:188(para) +msgid "The configuration option parameter should point to your nova.conf configuration file that includes the message queue server address and credentials." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:191(para) +msgid "By default, binds on 0.0.0.0:6080." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:193(para) +msgid "In order to connect the service to your nova deployment, add the two following configuration options into your nova.conf file :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:197(para) +msgid "vncserver_listen=0.0.0.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:198(para) +msgid "This configuration option allow you to specify the address for the vnc service to bind on, make sure it is assigned one of the compute node interfaces. This address will be the one used by your domain file." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:206(para) +msgid "In order to have the live migration working, make sure to use the 0.0.0.0address." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:211(para) +msgid "vncserver_ proxyclient_ address =127.0.0.1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:214(para) +msgid "This is the address of the compute host that nova will instruct proxies to use when connecting to instance vncservers." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:218(para) +msgid "The previous vnc proxy implementation, called nova-vncproxy, has been deprecated." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:223(title) +msgid "Accessing a VNC console through a web browser" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:225(para) +msgid "Retrieving an access_url for a web browser is similar to the flow for the Java client. To retrieve the access URL:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:229(para) +msgid "Then, paste the URL into your web browser." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:231(para) +msgid "Additionally, you can use the OpenStack Dashboard (codenamed Horizon), to access browser-based VNC consoles for instances." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:237(title) +msgid "Frequently asked questions about VNC access to VMs" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:242(emphasis) +msgid "Q: What is the difference between nova-xvpvncproxy and nova-novncproxy?" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:245(para) +msgid "A: nova-xvpvncproxy which ships with nova, is a new proxy that supports a simple Java client. nova-novncproxy uses noVNC to provide vnc support through a web browser." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:249(emphasis) +msgid "Q: I want VNC support in the Dashboard. What services do I need?" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:251(para) +msgid "A: You need nova-novncproxy, nova-consoleauth, and correctly configured compute hosts." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:255(emphasis) +msgid "Q: When I use or click on the VNC tab of the Dashboard, it hangs. Why?" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:257(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 will wait for a reply from them until a timeout is reached." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:262(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/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:264(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/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:271(para) +msgid "Your nova-compute configuration file would need the following values:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:282(para) +msgid "Note that novncproxy_base_url and novncproxy_base_url use a public ip; this is the url that is ultimately returned to clients, who generally will not have access to your private network. Your PROXYSERVER must be able to reach vncserver_proxyclient_address, as that is the address over which the vnc connection will be proxied." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:286(para) +msgid "See \"Important nova-compute Options\" for more information." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:290(emphasis) +msgid "Q: My noVNC does not work with recent versions of web browsers. Why?" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:293(para) +msgid "A: Make sure you have python-numpy installed, which is required to support a newer version of the WebSocket protocol (HyBi-07+). Also, if you are using Diablo's nova-vncproxy, note that support for this protocol is not provided." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:302(emphasis) +msgid "Q: How do I adjust the dimensions of the VNC window image in horizon?" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:304(para) +msgid "A: These values are hard-coded in a Django HTML template. To alter them, you must edit the template file _detail_vnc.html. The location of this file will vary based on Linux distribution. On Ubuntu 12.04, the file can be found at /usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-vnc-console.xml:308(para) +msgid "Modify the width and height parameters:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-spice-console.xml:8(title) +msgid "Spice Console" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-spice-console.xml:9(para) +msgid "OpenStack Compute has long had support for VNC consoles to guests. The VNC protocol is fairly limited, lacking support for multiple monitors, bi-directional audio, reliable cut+paste, video streaming and more. SPICE is a new protocol which aims to address all the limitations in VNC, to provide good remote desktop support." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-spice-console.xml:15(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 using SPICE-over-websockets. The nova-spicehtml5proxy service communicates directly with the hypervisor process using SPICE." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-spice-console.xml:22(para) +msgid "Options for configuring SPICE as the console for OpenStack Compute can be found below." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:67(None) +msgid "@@image: '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/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:83(None) +msgid "@@image: 'figures/xenapinfs/remote_config.png'; md5=eab22f6aa5413c2043936872ea44e459" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:6(title) +msgid "XenAPINFS" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:7(para) +msgid "XenAPINFS is a Block Storage (Cinder) driver which is using an NFS share through XenAPI's Storage Manager to store virtual disk images and exposing those virtual disks as volumes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:11(para) +msgid "This driver is not accessing the NFS share directly, it is only accessing the share through XenAPI Storage Manager. This driver should be considered as a reference implementation for using XenAPI's storage manager in OpenStack ( present in XenServer and XCP)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:22(para) +msgid "A XenServer/XCP installation acting as Storage Controller. I will refer to this hypervisor as Storage Controller in this document." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:28(para) +msgid "Use XenServer/XCP as your hypervisor for compute nodes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:32(para) +msgid "An NFS share, that is configured for XenServer/XCP. For the specific requirements, export options, please refer to the administration guide of your specific XenServer version. It is also requirement, that the NFS share is accessible by all the XenServers components within your cloud." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:39(para) +msgid "For creating volumes from XenServer type images (vhd tgz files), XenServer Nova plugins are also required on the Storage Controller." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:46(para) +msgid "It is possible to use a XenServer as a Storage Controller and as a compute node in the same time, thus the minimal configuration consists of a XenXerver/XCP box and an NFS share." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:54(title) +msgid "Configuration Patterns" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:62(title) +msgid "Local configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:57(para) +msgid "Local configuration (Recommended): The driver is running in a virtual machine on top of the storage controller. With this configuration, it is possible to create volumes from other formats supported by qemu-img. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:78(title) +msgid "Remote configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:74(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/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:93(title) +msgid "Configuration Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:94(para) +msgid "Assuming the following setup:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:96(para) +msgid "XenServer box at 10.2.2.1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:97(para) +msgid "XenServer password is r00tme" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:98(para) +msgid "NFS server is nfs.example.com" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:99(para) +msgid "NFS export is at /volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/cinder-xenapinfs.xml:102(para) +msgid "In order to use XenAPINFS as your cinder driver, the following configuration options needs to be set in cinder.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:7(title) +msgid "Troubleshoot your nova-volume installation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:8(para) +msgid "This section will help if you are able to successfully create volumes with either Cinder or Nova-Volume, however you can't attach them to an instance. If you are having trouble creating volumes, go to the cinder troubleshootingsection." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:14(para) +msgid "If the volume attachment doesn't work, you should be able to perform different checks in order to see where the issue is. The nova-volume.log and nova-compute.log will help you to diagnosis the errors you could encounter:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:18(emphasis) +msgid "nova-compute.log / nova-volume.log" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:22(para) +msgid "ERROR \"Cannot resolve host\"This error happens when the compute node is unable to resolve the nova-volume server name. You could either add a record for the server if you have a DNS server; or add it into the /etc/hosts file of the nova-compute." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:42(para) +msgid "ERROR \"No route to host\" This error could be caused by several things, but it means only one thing : openiscsi is unable to establish a communication with your nova-volumes server." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:49(para) +msgid "The first thing you could do is running a telnet session in order to see if you are able to reach the nova-volume server. From the compute-node, run :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:55(para) +msgid "If the session times out, check the server firewall; or try to ping it. You could also run a tcpdump session which may also provide extra information:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:62(para) +msgid "Again, try to manually run an iSCSI discovery via:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:69(emphasis) +msgid "\"Lost connectivity between nova-volumes and node-compute ; how to restore a clean state ?\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:72(para) +msgid "Network disconnection can happens, from an \"iSCSI view\", losing connectivity could be seen as a physical removal of a server's disk. If the instance runs a volume while you loose the network between them, you won't be able to detach the volume. You would encounter several errors. Here is how you could clean this :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:77(para) +msgid "First, from the nova-compute, close the active (but stalled) iSCSI session, refer to the volume attached to get the session, and perform the following command :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:83(para) +msgid "Here is an session output:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:95(para) +msgid "For example, to free volume 9, close the session number 9." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:97(para) +msgid "The cloud-controller is actually unaware of the iSCSI session closing, and will keeps the volume state as in-use: You now have to inform the cloud-controller that the disk can be used. Nova stores the volumes info into the \"volumes\" table. You will have to update four fields into the database nova uses (eg. MySQL). First, connect to the database:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:114(para) +msgid "Using the volume id, you will have to run the following sql queries:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:122(para) +msgid "Now if you run again from the cloud controller, you should see an available volume now:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/troubleshoot-nova-volume.xml:132(para) +msgid "You can now proceed to the volume attachment again!" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:8(title) +msgid "Reference Information for Securing with Root Wrappers" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:10(para) +msgid "The goal of the root wrapper is to allow the nova unprivileged user to run a number of actions as the root user, in the safest manner possible. Historically, Nova used a specific sudoers file listing every command that the nova user was allowed to run, and just used sudo to run that command as root. However this was difficult to maintain (the sudoers file was in packaging), and did not allow for complex filtering of parameters (advanced filters). The rootwrap was designed to solve those issues." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:19(para) +msgid "How rootwrap works:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:20(para) +msgid "Instead of just calling sudo make me a sandwich, Compute services starting with nova- call sudo nova-rootwrap /etc/nova/rootwrap.conf make me a sandwich. A generic sudoers entry lets the nova 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/src/docbkx/openstack-compute-admin/rootwrap.xml:29(title) +msgid "Security model" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:31(para) +msgid "The escalation path is fully controlled by the root user. A sudoers entry (owned by root) allows nova 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 nova user itself is not in control of the configuration or modules used by the nova-rootwrap executable." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:44(title) +msgid "Details of rootwrap.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:45(para) +msgid "The rootwrap.conf file is used to influence how nova-rootwrap works. Since it's in the trusted security path, it needs to be owned and writeable only by 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/src/docbkx/openstack-compute-admin/rootwrap.xml:49(para) +msgid "It uses an INI file format with the following sections and parameters:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:51(caption) ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:82(caption) +msgid "Description of rootwrap.conf configuration options" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:57(para) ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:88(para) ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:10(td) ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:10(para) ./doc/src/docbkx/openstack-compute-admin/tables/live-migration-nova-conf.xml:10(td) ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:10(td) ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:10(para) ./doc/src/docbkx/openstack-compute-admin/tables/config-drive-nova-conf.xml:10(para) ./doc/src/docbkx/openstack-compute-admin/tables/nova-policies-nova-conf.xml:10(para) ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:10(para) ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:10(para) ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:10(td) ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:10(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:10(td) ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:10(para) ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:10(para) ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:10(para) ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:10(td) ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:10(para) ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:11(para) ./doc/src/docbkx/openstack-compute-admin/tables/spice-guests-nova-conf.xml:10(para) ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:10(td) ./doc/src/docbkx/openstack-compute-admin/tables/ipv6-nova-conf.xml:10(td) ./doc/src/docbkx/openstack-compute-admin/tables/s3-nova-conf.xml:10(td) ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:11(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:11(para) ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:10(para) +msgid "Configuration option=Default value" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:58(para) ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:89(para) ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:11(td) ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:11(para) ./doc/src/docbkx/openstack-compute-admin/tables/live-migration-nova-conf.xml:11(td) ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:11(td) ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:11(para) ./doc/src/docbkx/openstack-compute-admin/tables/config-drive-nova-conf.xml:11(para) ./doc/src/docbkx/openstack-compute-admin/tables/nova-policies-nova-conf.xml:11(para) ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:11(para) ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:11(para) ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:11(td) ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:11(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:11(td) ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:11(para) ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:11(para) ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:11(para) ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:11(td) ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:11(para) ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:12(para) ./doc/src/docbkx/openstack-compute-admin/tables/spice-guests-nova-conf.xml:11(para) ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:11(td) ./doc/src/docbkx/openstack-compute-admin/tables/ipv6-nova-conf.xml:11(td) ./doc/src/docbkx/openstack-compute-admin/tables/s3-nova-conf.xml:11(td) ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:12(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:12(para) ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:11(para) +msgid "(Type) Description" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:62(para) +msgid "[DEFAULT]" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:64(para) +msgid "filters_path=/etc/nova/rootwrap.d,/usr/share/nova/rootwrap" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:66(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 writeable only by the root user." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:76(title) +msgid "Details of .filters files" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:77(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 writeable only by the root user. Their location is specified in the rootwrap.conf file." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:79(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 you define):" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:93(para) +msgid "[Filters]" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:95(para) +msgid "filter_name=kpartx: CommandFilter, /sbin/kpartx, root" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/rootwrap.xml:97(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 "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:165(None) +msgid "@@image: 'figures/instance-life-1.png'; md5=88c0e9edb6e2245fa75d537f40cc57e6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:186(None) +msgid "@@image: 'figures/instance-life-2.png'; md5=30ed5e5b35fe6392f4474a5cf534e2d0" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:228(None) +msgid "@@image: 'figures/instance-life-3.png'; md5=8f69499a1ef7364430c10e226e571dd5" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:6(title) +msgid "Introduction to OpenStack Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:7(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/src/docbkx/openstack-compute-admin/aboutcompute.xml:17(title) ./doc/src/docbkx/openstack-compute-admin/computehypervisors.xml:6(title) +msgid "Hypervisors" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:19(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://wiki.openstack.org/HypervisorSupportMatrix for a detailed list of features and support across the hypervisors." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:27(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/src/docbkx/openstack-compute-admin/aboutcompute.xml:32(para) +msgid "KVM - Kernel-based Virtual Machine" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:36(para) +msgid "LXC - Linux Containers (through libvirt)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:40(para) +msgid "QEMU - Quick EMUlator" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:44(para) +msgid "UML - User Mode Linux" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:48(para) +msgid "VMWare ESX/ESXi 4.1 update 1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:53(para) +msgid "Xen - Xen, Citrix XenServer and Xen Cloud Platform (XCP)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:57(para) +msgid " Bare Metal - Provisions physical hardware via pluggable sub-drivers." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:63(title) +msgid "Users and Tenants (Projects)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:74(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 when a tenant ID is expected." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:64(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/src/docbkx/openstack-compute-admin/aboutcompute.xml:78(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/src/docbkx/openstack-compute-admin/aboutcompute.xml:87(para) +msgid "Number of volumes which may be created" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:90(para) +msgid "Total size of all volumes within a project as measured in GB" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:93(para) +msgid "Number of instances which may be launched" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:96(para) +msgid "Number of processor cores which may be allocated" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:99(para) +msgid "Publicly accessible IP addresses" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:85(para) +msgid "For tenants, quota controls are available to limit the:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:104(title) +msgid "Images and Instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:106(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 preform the actions described are presented in the Image Management and Volume Management chapters." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:118(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/src/docbkx/openstack-compute-admin/aboutcompute.xml:123(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/src/docbkx/openstack-compute-admin/aboutcompute.xml:132(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/src/docbkx/openstack-compute-admin/aboutcompute.xml:140(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 nova-volume service which provide persistent block storage as opposed to the ephemeral storage provided by the instance flavor." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:146(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/src/docbkx/openstack-compute-admin/aboutcompute.xml:151(title) +msgid "Initial State" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:153(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 nova-volume service." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:162(title) +msgid "Base image state with no running instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:172(title) +msgid "Launching an instance" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:174(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 nova-volume store to the third virtual disk, vdc, on this instance." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:183(title) +msgid "Instance creation from image and run time state" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:191(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). The compute node attaches to the requested nova-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 dive. The instance runs and changes data on the disks indicated in red in the diagram." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:205(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/src/docbkx/openstack-compute-admin/aboutcompute.xml:216(title) +msgid "End State" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.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 through out." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:225(title) +msgid "End state of image and volume after instance exits" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:235(title) +msgid "System Architecture" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:235(para) +msgid "OpenStack Compute consists of several main components. A \"cloud controller\" contains many of these components, and it represents the global state and interacts with all other components. An API Server acts as the web services front end for the cloud controller. The compute controller provides compute server resources and typically contains the compute service, The Object Store component optionally provides storage services. An auth manager provides authentication and authorization services when used with the Compute system, or you can use the Identity Service (keystone) as a separate authentication service. A volume controller provides fast and permanent block-level storage for the compute servers. A network controller provides virtual networks to enable compute servers to interact with each other and with the public network. A scheduler selects the most suitable compute controller to host an instance." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:245(para) +msgid "OpenStack Compute is built on a shared-nothing, messaging-based architecture. You can run all of the major components on multiple servers including a compute controller, volume controller, network controller, and object store (or image service). A cloud controller communicates with the internal object store via HTTP (Hyper Text Transfer Protocol), but it communicates with a scheduler, network controller, and volume controller via AMQP (Advanced Message Queue Protocol). To avoid blocking each component while waiting for a response, OpenStack Compute uses asynchronous calls, with a call-back that gets triggered when a response is received." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:254(para) +msgid "To achieve the shared-nothing property with multiple copies of the same component, OpenStack Compute keeps all the cloud system state in a database." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:256(title) +msgid "Block Storage and OpenStack Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:258(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/src/docbkx/openstack-compute-admin/aboutcompute.xml:270(title) +msgid "Ephemeral Storage" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:272(para) +msgid "Ephemeral storage is associated with a single unique instance. Its size is defined by the flavor of the instance." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:276(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/src/docbkx/openstack-compute-admin/aboutcompute.xml:284(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/src/docbkx/openstack-compute-admin/aboutcompute.xml:300(title) +msgid "Volume Storage" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:302(para) +msgid "Volume storage is independent or any particular instance and is persistent. Volumes are user created and within quota and availability limits may be of any arbitrary size." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:306(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/src/docbkx/openstack-compute-admin/aboutcompute.xml:314(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 sill 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 it shutdown. Details of this configuration are discussed in the Boot From Volume section of this manual." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutcompute.xml:325(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 out side of it, but are not features provided by the OpenStack software." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:519(None) +msgid "@@image: 'figures/FlatNetworkSingleInterfaceAllInOne.png'; md5=62c566cb0bec67a301b3e04a3558af5f" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:534(None) +msgid "@@image: 'figures/FlatNetworkSingleInterface.png'; md5=e300bdc787cffbcf94bbf2fbae581012" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:549(None) +msgid "@@image: 'figures/FlatNetworkMultInterface.png'; md5=3f2fb8bad994799a71f1edede28930a3" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:612(None) +msgid "@@image: 'figures/flatdchp-net.jpg'; md5=10aa6ae05353866d89f55e51fc10850f" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:665(None) +msgid "@@image: 'figures/XenApiFlatDHCPMultInterfaceHA.png'; md5=b8c79e4d44bf76665a9d4a849471461b" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:738(None) +msgid "@@image: 'figures/SingleInterfaceOutbound_1.png'; md5=44c4b7321b9bdd3e06ebd56d44df190c" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:751(None) +msgid "@@image: 'figures/SingleInterfaceOutbound_2.png'; md5=8885f24dd619a4561487a393d45ff91f" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:978(None) +msgid "@@image: 'figures/XenApiVLANMultInterfaceHA.png'; md5=af1029940de11b3b324ff4cfd8b95a66" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1622(None) +msgid "@@image: 'figures/cloudpipe/cloudpipe-viscosity-step1.jpg'; md5=33f7edf6286f3393997a196d5e2f461d" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1635(None) +msgid "@@image: 'figures/cloudpipe/cloudpipe-viscosity-step2.jpg'; md5=e5aac8ffe8ba9e7278a7b4e9fecd19d7" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1649(None) +msgid "@@image: 'figures/cloudpipe/cloudpipe-viscosity-step3.jpg'; md5=bfe96627756d58698fee412c1ce97817" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1663(None) +msgid "@@image: 'figures/cloudpipe/cloudpipe-viscosity-step4.jpg'; md5=0e57679d5c59fb6b106a1a58e13d0f8d" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1980(None) +msgid "@@image: '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/src/docbkx/openstack-compute-admin/computenetworking.xml:1988(None) +msgid "@@image: '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/src/docbkx/openstack-compute-admin/computenetworking.xml:1996(None) +msgid "@@image: 'figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-VLAN-manager.jpg'; md5=0acaf3e2041f941d8fee2d111f37e7ac" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2083(None) +msgid "@@image: 'figures/ha-net.jpg'; md5=e0e2593a14fea7f9b24f8d8b459f9db5" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:6(title) +msgid "Networking with nova-network" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:7(para) +msgid "By understanding the available networking configuration options you can design the best configuration for your OpenStack Compute instances." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:12(title) +msgid "Networking Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:13(para) +msgid "This section offers a brief overview of each concept in networking for Compute. With the Folsom release, you can chose either to install and configure nova-network for networking between VMs or use the Networking service (quantum) for networking. Refer to the Network Administration Guide to configure Compute networking options with Quantum." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:21(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 allows the virtual interfaces to connect to the outside network through the physical interface.)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:26(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/src/docbkx/openstack-compute-admin/computenetworking.xml:32(para) +msgid "Flat Network Manager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:35(para) +msgid "Flat DHCP Network Manager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:38(para) +msgid "VLAN Network Manager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:29(para) +msgid "Currently, Compute with nova-network supports three kinds of networks, implemented in three “Network Manager” types:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:40(para) +msgid "The three kinds of networks can co-exist in a cloud system. However, since 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/src/docbkx/openstack-compute-admin/computenetworking.xml:44(para) +msgid "All of the networking options require network connectivity to be already set up between OpenStack physical nodes. OpenStack will not configure any physical network interfaces. OpenStack will automatically create all network bridges (i.e., br100) and VM virtual interfaces." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:51(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/src/docbkx/openstack-compute-admin/computenetworking.xml:56(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 will have to receive packets whose target MAC address is of the guest VM, not of the host." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:63(para) +msgid "All the network managers configure the network using network drivers, e.g. the linux L3 driver (l3.py and linux_net.py) which makes use of iptables, route and other network management facilities, and also of 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 etc.) only when the first VM lands on this host node." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:71(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, there is just 1 instance of nova-network which is used as a default gateway for VMs and hosts a single DHCP server (dnsmasq), whereas in multi-host mode every compute node has its own nova-network. In any case, all traffic between VMs and the outer world flows through nova-network. There are pros and cons to both modes, read more in Existing High Availability Options." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:80(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/src/docbkx/openstack-compute-admin/computenetworking.xml:87(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/src/docbkx/openstack-compute-admin/computenetworking.xml:98(para) +msgid "The configuration injection currently only works on Linux-style systems that keep networking configuration in /etc/network/interfaces." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:103(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/src/docbkx/openstack-compute-admin/computenetworking.xml:107(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). It will 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). For every instance, nova will allocate a fixed IP address and configure dnsmasq with the MAC/IP pair for the VM, i.e. 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/src/docbkx/openstack-compute-admin/computenetworking.xml:119(para) +msgid "In any setup with flat networking, the host(-s) with nova-network on it is (are) responsible for forwarding traffic from the private network configured with the fixed_range configuration option in nova.conf. Such host(-s) needs 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 per project and instance to protect against IP/MAC address spoofing and ARP poisoning." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:129(para) +msgid "In single-host Flat DHCP mode you will be able to ping VMs via their fixed IP from the nova-network node, but you will not be able to ping them from the compute nodes. This is expected behavior." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:134(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 via a dedicated VPN connection from the Internet. In this mode, each project gets its own VLAN, Linux networking bridge, and subnet." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:144(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/src/docbkx/openstack-compute-admin/computenetworking.xml:153(para) +msgid "With the default Compute settings, once a virtual machine instance is destroyed, it can take some time for the IP address associated with the destroyed instance to become available for assignment to a new instance." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:156(para) +msgid "The force_dhcp_release=True configuration option, when set, causes the Compute service to send out a DHCP release packet when it destroys a virtual machine instance. The result is that the IP address assigned to the instance is immediately released." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:160(para) +msgid "This configuration option applies to both Flat DHCP mode and VLAN Manager mode." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:162(para) +msgid "Use of this option requires the program. Verify that this program is installed on all hosts running the nova-compute service before enabling this option. This can be checked with the command, and will return the complete path if the program is installed. As root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:172(title) +msgid "DHCP server: dnsmasq" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:173(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/src/docbkx/openstack-compute-admin/computenetworking.xml:180(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 high availability section 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/src/docbkx/openstack-compute-admin/computenetworking.xml:192(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/src/docbkx/openstack-compute-admin/computenetworking.xml:200(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/src/docbkx/openstack-compute-admin/computenetworking.xml:207(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, replacing the flat_network_dhcp_start configuration option that was available in Diablo. 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/src/docbkx/openstack-compute-admin/computenetworking.xml:218(title) +msgid "Metadata service" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:220(title) +msgid "Introduction" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:221(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/src/docbkx/openstack-compute-admin/computenetworking.xml:226(para) +msgid "To retrieve a list of supported versions for the OpenStack metadata API, make a GET request to For example:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:229(para) +msgid " To retrieve a list of supported versions for the EC2-compatible metadata API, make a GET request to " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:234(para) ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:300(para) ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:331(para) ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1858(para) +msgid "For example:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:248(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/src/docbkx/openstack-compute-admin/computenetworking.xml:253(title) +msgid "OpenStack metadata API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:254(para) +msgid "Metadata from the OpenStack API is distributed in JSON format. To retrieve the metadata, make a GET request to For example:Here is the same content after having run through a JSON pretty-printer:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:278(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/src/docbkx/openstack-compute-admin/computenetworking.xml:291(title) +msgid "EC2 metadata API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:292(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 will work properly with OpenStack." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:297(para) +msgid "The EC2 API exposes a separate URL for each metadata. A listing of these elements can be retrieved by making a GET query to:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:328(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/src/docbkx/openstack-compute-admin/computenetworking.xml:337(para) +msgid "Instances can retrieve user data by making a GET request to: For example:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:347(title) +msgid "Running the metadata service" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:348(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 section titled Existing High Availability Options for Networking 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/src/docbkx/openstack-compute-admin/computenetworking.xml:368(para) +msgid "The metadata_host configuration option must be an IP address, not a hostname." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:371(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 the following change in the /etc/nova/nova.conf file on the host running the nova-network service:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:377(para) +msgid "Set the metadata_host configuration option to the IP address of the host where the nova-api service is running." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:360(para) +msgid "To allow instances to reach the metadata service, the nova-network service will configure iptables to NAT port 80 of the 169.254.169.254 address to the IP address specified in metadata_host (default $my_ip, which is the IP address of the nova-network service) and port specified in metadata_port (default 8775) in /etc/nova/nova.conf. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:384(title) +msgid "Configuring Networking on the Compute Node" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:385(para) +msgid "To configure the Compute node's networking for the VM images, the overall steps are:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:390(para) +msgid "Set the network_manager option in nova.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:393(para) +msgid "Use the nova-manage network create label CIDR n n command to create the subnet that the VMs reside on." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:398(para) +msgid "Integrate the bridge with your network." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:401(para) +msgid "By default, Compute uses the VLAN Network Mode. You choose the networking mode for your virtual instances in the nova.conf file. Here are the three possible options:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:406(literal) +msgid "--network_manager=nova.network.manager.FlatManager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:407(para) +msgid "Simple, non-VLAN networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:410(literal) +msgid "--network_manager=nova.network.manager.FlatDHCPManager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:411(para) +msgid "Flat networking with DHCP, you must set a bridge using the flat_network_bridge option" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:415(literal) +msgid "--network_manager=nova.network.manager.VlanManager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:416(para) +msgid "VLAN networking with DHCP. This is the Default if no network manager is defined in nova.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:424(literal) +msgid "nova-manage network create private 192.168.0.0/24 1 256" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:421(para) +msgid "When you issue the nova-manage network create command, it uses the settings from the nova.conf configuration options file. Use the following command to create the subnet that your VMs will run on : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:426(para) +msgid "When using the XenAPI compute driver, the OpenStack services run in a virtual machine. This means networking is significantly different when compared to the networking with the libvirt compute driver. Before reading how to configure networking using the XenAPI compute driver, you may find it useful to read the Citrix article on Understanding XenServer Networking and the section of this document that describes XenAPI and OpenStack." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:439(title) +msgid "Configuring Flat Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:440(para) +msgid "FlatNetworking uses ethernet adapters configured as bridges to allow network traffic to transit between all the various nodes. This setup can be done with a single adapter on the physical host, or multiple. This option does not require a switch that does VLAN tagging as VLAN networking does, and is a common development installation or proof of concept setup. When you choose Flat networking, Nova does not manage networking at all. Instead, IP addresses are injected into the instance via the file system (or passed in via a guest agent). Metadata forwarding must be configured manually on the gateway if it is required within your network." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:453(para) +msgid "To configure flat networking, ensure that your nova.conf file contains the following line:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:461(para) +msgid "When configuring Flat Networking, failing to enable flat_injected can prevent guest VMs from receiving their IP information at boot time." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:468(title) +msgid "Libvirt Flat Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:469(para) +msgid "Compute defaults to a bridge device named ‘br100’ which is stored in the Nova database, so you can change the name of the bridge device by modifying the entry in the database. Consult the diagrams for additional configuration options." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:474(para) +msgid "In any set up with FlatNetworking (either Flat or FlatDHCP), the host with nova-network on it is responsible for forwarding traffic from the private network configured with the --fixed_range= directive in nova.conf and the --flat_network_bridge setting. This host needs to have br100 configured and talking to any other nodes that are hosting VMs. With either of the Flat Networking options, the default gateway for the virtual machines is set to the host which is running nova-network." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:486(para) +msgid "Set the compute node's external IP address to be on the bridge and add eth0 to that bridge. To do this, edit your network interfaces configuration to look like the following example:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:506(para) +msgid "Next, restart networking to apply the changes: sudo /etc/init.d/networking restart" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:509(para) +msgid "For an all-in-one development setup, this diagram represents the network setup." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:513(title) +msgid "Flat network, all-in-one server installation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:523(para) +msgid "For multiple compute nodes with a single network adapter, which you can use for smoke testing or a proof of concept, this diagram represents the network setup." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:528(title) +msgid "Flat network, single interface, multiple servers" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:538(para) +msgid "For multiple compute nodes with multiple network adapters, this diagram represents the network setup. You may want to use this setup for separate admin and data traffic." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:543(title) +msgid "Flat network, multiple interfaces, multiple servers" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:556(title) +msgid "XenAPI Flat Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:557(para) +msgid "When using the XenAPI driver, the virtual machines creates OpenStack are attached to the XenServer bridge configured in the flat_network_bridge setting. Otherwise, flat networking works in a very similar way with both the libvirt driver and the XenAPI driver." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:567(title) +msgid "Configuring Flat DHCP Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:568(para) +msgid "With Flat DHCP, the host(-s) running nova-network act as the gateway to the virtual nodes. If you're using single-host networking, you can optionally set network_host on the nova.conf stored on the nova-compute node to tell it which host the nova-network is running on so it can more efficiently communicate with nova-network. In any setup with flat networking, the hosts with nova-network on it are responsible for forwarding traffic from the private network configured with the fixed_range= directive in nova.conf and the flat_network_bridge flag which you must also set to the name of the bridge (as there is no default). The nova-network service will track leases and releases in the database, using dnsmasq's dhcp-script facility (the script bin/nova-dhcpbridge is supplied) so it knows if a VM instance has stopped properly configuring via DHCP (e.g. when a DHCP lease expires, the fixed IP is released from the nova database). Lastly, it sets up iptables rules to allow the VMs to communicate with the outside world and contact a special metadata server to retrieve information from the cloud." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:584(para) +msgid "Compute hosts in the FlatDHCP model are responsible for bringing up a matching bridge and bridging the VM tap devices into the same ethernet device that the network host is on. The compute hosts should not have an IP address on the VM network, because the bridging puts the VMs and the network host on the same logical network. When a VM boots, the VM sends out DHCP packets, and the DHCP server on the network host responds with their assigned IP address (remember, the address is actually assigned by nova and put into DHCP server's configuration file, the DHCP server merely tells the VM what it is)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:592(para) +msgid "You can read a detailed walk-through of what exactly happens in single-host Flat DHCP mode in this blogpost, parts of which are also relevant in other networking modes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:597(para) +msgid "FlatDHCP doesn't create VLANs, it creates a bridge. This bridge works just fine on a single host, but when there are multiple hosts, traffic needs a way to get out of the bridge onto a physical interface." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:603(title) +msgid "Libvirt Flat DHCP Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:604(para) +msgid "When using the libvirt driver, the setup will look like the figure below:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:607(title) +msgid "Flat DHCP network, multiple interfaces, multiple servers with libvirt driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:616(para) +msgid "Be careful when setting up --flat_interface. If you specify an interface that already has an IP it will break and if this is the interface you are connecting through with SSH, you cannot fix it unless you have ipmi/console access. In FlatDHCP mode, the setting for --network_size should be number of IPs in the entire fixed range. If you are doing a /12 in CIDR notation, then this number would be 2^20 or 1,048,576 IP addresses. That said, it will take a very long time for you to create your initial network, as an entry for each IP will be created in the database." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:629(para) +msgid "If you have an unused interface on your hosts (eg eth2) that has connectivity with no IP address, you can simply tell FlatDHCP to bridge into the interface by specifying flat_interface=<interface> in your configuration file. The network host will automatically add the gateway ip to this bridge. If this is the case for you, edit your nova.conf file to contain the following lines:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:637(para) +msgid " You can also add the unused interface to br100 manually and not set flat_interface." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:651(para) +msgid "Integrate your network interfaces to match this configuration." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:655(title) +msgid "XenAPI Flat DHCP Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:656(para) +msgid "The following figure shows a setup with Flat DHCP networking, network HA, and using multiple interfaces. For simplicity, the management network (on XenServer eth0 and eth2 of the VM running the OpenStack services) has been omitted from the figure below." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:662(title) +msgid "Flat DHCP network, multiple interfaces, multiple servers, network HA with XenAPI driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:668(para) ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:981(para) +msgid "Here is an extract from a nova.conf file in a system running the above setup:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:684(para) +msgid "You should notice that flat_interface and public_interface refer to the network interface on the VM running the OpenStack services, not the network interface on the Hypervisor." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:691(para) +msgid "Secondly flat_network_bridge refers to the name of XenAPI network that you wish to have your instance traffic on, i.e. the network on which the VMs will be attached. You can either specify the bridge name, such an xenbr2, or the name label, such as vmbr. Specifying the name-label is very useful in cases where your networks are not uniform across your XenServer hosts." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:701(para) +msgid "When you have a limited number of network cards on your server, it is possible to use networks isolated using VLANs for the public and network traffic. For example, if you have two XenServer networks xapi1 and xapi2 attached on VLAN 102 and 103 on eth0, respectively, you could use these for eth1 and eth3 on your VM, and pass the appropriate one to flat_network_bridge." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:711(para) +msgid "When using XenServer, it is best to use the firewall driver written specifically for XenServer. This pushes the firewall rules down to the hypervisor, rather than running them in the VM that is running nova-network." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:721(title) +msgid "Outbound Traffic Flow with Any Flat Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:723(para) +msgid "In any set up with FlatNetworking, the host with nova-network on it is responsible for forwarding traffic from the private network configured with the fixed_range=... directive in nova.conf. This host needs to have a bridge interface (e.g., br100) configured and talking to any other nodes that are hosting VMs. With either of the Flat Networking options, the default gateway for the virtual machines is set to the host which is running nova-network." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:729(para) +msgid "When a virtual machine sends traffic out to the public networks, it sends it first to its default gateway, which is where nova-network is configured." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:733(title) +msgid "Single adaptor hosts, first route" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:742(para) +msgid "Next, the host on which nova-network is configured acts as a router and forwards the traffic out to the Internet." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:746(title) +msgid "Single adaptor hosts, second route" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:756(para) +msgid "If you're using a single interface, then that interface (often eth0) needs to be set into promiscuous mode for the forwarding to happen correctly. This does not appear to be needed if you're running with physical hosts that have and use two interfaces." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:766(title) +msgid "Configuring VLAN Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:767(para) +msgid "Compute can be configured so that the virtual machine instances of different projects (tenants) are in different subnets, with each subnet having a different VLAN tag. This can be useful in networking environments where you have a large IP space which is cut up into smaller subnets. The smaller subnets are then trunked together at the switch level (dividing layer 3 by layer 2) so that all machines in the larger IP space can communicate. The purpose of this is generally to control the size of broadcast domains. It can also be useful to provide an additional layer of isolation in a multi-tenant environment." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:776(para) +msgid "The terms network and subnet are often used interchangeably in discussions of VLAN mode. In all cases, we are referring to a range of IP addresses specified by a subnet (e.g., 172.16.20.0/24) that are on the same VLAN (layer 2 network)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:785(para) +msgid "IP forwarding must be enabled" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:788(para) +msgid "The hosts running nova-network and nova-compute must have the 8021q kernel module loaded" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:792(para) +msgid "Your networking switches must support VLAN tagging" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:795(para) +msgid "Your networking switches must be configured to enable the specific VLAN tags you specify in your Compute setup" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:799(para) +msgid "You will need information about your networking setup from your network administrator to configure Compute properly (e.g., netmask, broadcast, gateway, ethernet device, VLAN IDs)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:783(para) +msgid "Running in VLAN mode is more complex than the other network modes. In particular:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:805(para) +msgid "The network_manager=nova.network.manager.VlanManager option specifies VLAN mode, which happens to be the default networking mode." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:807(para) +msgid "The bridges that are created by the network manager will be attached to the interface specified by vlan_interface, the example above uses the eth0 interface, which is the default." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:810(para) +msgid "The fixed_range option is a CIDR block which describes the IP address space for all of the instances: this space will be divided up into subnets. This range is typically a private network. The example above uses the private range 172.16.0.0/12." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:816(para) +msgid "The network_size option refers to the default number of IP addresses in each network, although this can be overriden at network creation time . The example above uses a network size of 256, whicih corresponds to a /24 network." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:820(para) +msgid "Networks are created with the command. Here is an example of how to create a network consistent with the above example configuration options, as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:824(para) +msgid "This creates a network called example-net associated with tenant a421ae28356b4cc3a25e1429a0b02e98. The subnet is 172.16.169.0/24 with a VLAN tag of 169 (the VLAN tag does not need to match the third byte of the address, though it is a useful convention to remember the association). This will create a bridge interface device called br169 on the host running the nova-network service. This device will appear in the output of an command." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:832(para) +msgid "Each network is associated with one tenant. As in the example above, you may (optionally) specify this association at network creation time by using the --project_id flag which corresponds to the tenant ID. Use the command to list the tenants and corresponding IDs that you have already created." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:837(para) +msgid "Instead of manually specifying a VLAN, bridge, and project id, you can create many networks at once and have the Compute service automatically associate these networks with tenants as needed, as well as automatically generating the VLAN IDs and bridge interface names. For example, the following command would create 100 networks, from 172.16.100.0/24 to 172.16.199.0/24. (This assumes the network_size=256 option has been set at nova.conf, though this can also be specified by passing --network_size=256 as a flag to the command)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:846(para) +msgid "The command supports many configuration options, which are displayed when called with the --help flag:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:885(literal) +msgid "--network_size" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:887(para) +msgid "Overrides the network_size configuration option" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:892(literal) +msgid "--bridge_interface" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:894(para) +msgid "Overrides the vlan_interface configuration option" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:882(para) +msgid "In particular, flags to the command can be used to override settings from nova.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:899(para) +msgid "To view a list of the networks that have been created, as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:901(para) +msgid "To modify an existing network, use the command, as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:916(para) +msgid "To delete a network, use , as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:925(para) +msgid "Note that a network must first be disassociated from a project using the command before it can be deleted." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:928(para) +msgid "Creating a network will automatically cause the Compute database to populate with a list of available fixed IP addresses. You can view the list of fixed IP addresses and their associations with active virtual machines by doing, as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:932(para) +msgid "If users need to access the instances in their project across a VPN, a special VPN instance (code named cloudpipe) needs to be created as described in the section titled Cloudpipe — Per Project VPNs." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:939(title) +msgid "Libvirt VLAN networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:940(para) +msgid "To configure your nodes to support VLAN tagging, install the vlan package and load the 8021q kernel module, as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:945(para) +msgid "To have this kernel module loaded on boot, add the following line to /etc/modules:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:947(para) +msgid "Here is an example of settings from /etc/nova/nova.conf for a host configured to run in VLAN mode" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:953(para) +msgid "In certain cases, the network manager may not properly tear down bridges and VLANs when it is stopped. If you attempt to restart the network manager and it does not start, check the logs for errors indicating that a bridge device already exists. If this is the case, you will likely need to tear down the bridge and VLAN devices manually. It is also advisable to kill any remaining dnsmasq processes. These commands would stop the service, manually tear down the bridge and VLAN from the previous example, kill any remaining dnsmasq processes, and start the service up again, as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:969(title) +msgid "XenAPI VLAN networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:970(para) +msgid "VLAN networking works quite differently with the XenAPI driver, compared to the libvit driver. The following figure shows how your setup might look:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:975(title) +msgid "VLAN network, multiple interfaces, multiple servers, network HA with XenAPI driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:994(para) +msgid "You should notice that vlan_interface refers to the network interface on the Hypervisor and the network interface on the VM running the OpenStack services. As with before public_interface refers to the network interfce on the VM running the OpenStack services." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1007(para) +msgid "First the XenServer network is attached to the appropriate physical interface (PIF) and VLAN unless the network already exsists." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1014(para) +msgid "When the VM is created, its VIF is attached to the above network." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1020(para) +msgid "The 'Openstack domU', i.e. where nova-network is running, acts as a gateway and DHCP for this instance. The DomU does this for multiple VLAN networks, so it has to be attached on a VLAN trunk. For this reason it must have an interface on the parent bridge of the VLAN bridge where VM instances are plugged." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1003(para) +msgid "With VLAN networking and the XenAPI driver, the following things happen when you start a VM: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1035(para) +msgid "A physical interface (PIF) identified either by (A) the vlan_interface flag or (B) the bridge_interface column in the networks db table will be used for creating a XenServer VLAN network. The VLAN tag is found in the vlan column, still in the networks table, and by default the first tag is 100." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1045(para) +msgid "VIF for VM instances within this network will be plugged in this VLAN network. You won't see the bridge until a VIF is plugged in it." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1052(para) +msgid "The 'Openstack domU', i.e. the VM running the nova network node, instead will not be plugged into this network; since it acts as a gateway for multiple VLAN networks, it has to be attached on a VLAN trunk. For this reason it must have an interface on the parent bridge of the VLAN bridge where VM instances are plugged. For example, if vlan_interface is eth0 it must be plugged in xenbr1, eth1 --> xenbr1, etc." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1064(para) +msgid "Within the Openstack domU, 'ip link' is then used to configure VLAN interfaces on the 'trunk' port. Each of this vlan interfaces is associated with a dnsmasq instance, which will distribute IP addresses to instances. The lease file for dnsmasq is constantly updated by nova-network, thus ensuring VMs get the IP address specified by the layer3 network driver (nova IPAM or Melange)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1031(para) +msgid "To help understand VLAN networking with the XenAPI further, here are some important things to note: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1077(para) +msgid "With this configuration, VM instances should be able to get the IP address assigned to them from the appropriate dnsmasq instance, and should be able to communicate without any problem with other VMs on the same network and with the their gateway." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1082(para) +msgid "The above point (3) probably needs some more explanations. With Open vSwitch, we don't really have distinct bridges for different VLANs; even if they appear as distinct bridges to linux and XenServer, they are actually the same OVS instance, which runs a distinct 'fake-bridge' for each VLAN. The 'real' bridge is the 'parent' of the fake one. You can easily navigate fake and real bridges with ovs-vsctl." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1090(para) +msgid "As you can see I am referring to Openvswitch only. This is for a specific reason: the fake-parent mechanism automatically imply that ports which are not on a fake bridge are trunk ports. This does not happen with linux bridge. A packet forwarded on a VLAN interfaces does not get back in the xenbrX bridge for ethX. For this reason, with XenAPI, you must use Open vSwitch when running VLAN networking with network HA (i.e. mult-host) enabled. On XenServer 6.0 and later, Open vSwitch is the default network stack. When using VLAN networking with XenAPI and linux bridge, the default networking stack on XenServer prior to version 6.0, you must run the network node on a VM on a XenServer that does not host any nova-compute controlled instances." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1107(title) +msgid "Known issue with failed DHCP leases in VLAN configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1108(para) +msgid "Text in this section was adapted from an email from Vish Ishaya on the OpenStack mailing list." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1111(para) +msgid "There is an issue with the way Compute uses dnsmasq in VLAN mode. Compute starts up a single copy of dnsmasq for each VLAN on the network host (or on every host in multi_host mode). The problem is in the way that dnsmasq binds to an IP address and port. Both copies can respond to broadcast packets, but unicast packets can only be answered by one of the copies." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1119(para) +msgid "As a consequence, guests from only one project will get responses to their unicast DHCP renew requests. Unicast projects from guests in other projects get ignored. What happens next is different depending on the guest OS. Linux generally will send a broadcast packet out after the unicast fails, and so the only effect is a small (tens of ms) hiccup while the interface is reconfigured. It can be much worse than that, however. There have been observed cases where Windows just gives up and ends up with a non-configured interface." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1126(para) +msgid "This bug was first noticed by some users of OpenStack who rolled their own fix. In short, on Linux, if you set the SO_BINDTODEVICE socket option, it will allow different daemons to share the port and respond to unicast packets, as long as they listen on different interfaces. Simon Kelley, the maintainer of dnsmasq, has integrated a fix for the issue in dnsmaq version 2.61." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1133(para) +msgid "If upgrading dnsmasq is out of the question, a possible workaround is to minimize lease renewals with something like the following combination of config options. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1145(title) +msgid "Cloudpipe — Per Project Vpns" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1147(para) +msgid "Cloudpipe is a method for connecting end users to their project instances in VLAN networking mode." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1149(para) +msgid "The support code for cloudpipe implements admin commands (via an extension) to automatically create a VM for a project that allows users to VPN into the private network of their project. Access to this VPN is provided through a public port on the network host for the project. This allows users to have free access to the virtual machines in their project without exposing those machines to the public internet." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1157(para) +msgid "The cloudpipe image is basically just a Linux instance with openvpn installed. It needs a simple script to grab user data from the metadata server, b64 decode it into a zip file, and run the autorun.sh script from inside the zip. The autorun script will configure and run openvpn to run using the data from nova." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1164(para) +msgid "It is also useful to have a cron script that will periodically redownload the metadata and copy the new Certificate Revocation List (CRL). This list is contained within the payload file and will keeps revoked users from connecting and will disconnect any users that are connected with revoked certificates when their connection is renegotiated (every hour). (More infos about revocation can be found in the following section : \"Certificates and Revocation\")." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1170(para) +msgid "In this how-to, we are going to create our cloud-pipe image from a running Ubuntu instance which will serve as a template. When all the components will be installed and configured, we will create an image from that instance that will be uploaded to the Glance repositories." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1176(title) +msgid "Creating a Cloudpipe Image Template" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1179(para) +msgid "Installing the required packages" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1180(para) +msgid "We start by installing the required packages on our instance : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1184(para) +msgid "Creating the server configuration template" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1185(para) +msgid "Create a configuration for Openvpn, and save it under /etc/openvpn/server.conf :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1226(para) +msgid "Create the network scripts" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1227(para) +msgid "The next step is to create both scripts that will be used when the network components will start up and shut down. The scripts will be respectively saved under /etc/openvpn.up.sh and /etc/openvpn/down.sh :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1232(filename) +msgid "/etc/openvpn/up/sh" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1241(filename) +msgid "/etc/openvpn/down.sh" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1250(para) +msgid "Make these two scripts executables by running the following command : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1254(para) +msgid "Edit the network interface configuration file" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1255(para) +msgid "Update the /etc/network/interfaces accordingly (We tear down the main interface and enable the bridged interface) :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1276(para) +msgid "Edit the rc.local file" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1277(para) +msgid "The next step consists in updating the /etc/rc.local file. We will ask our image to retrive the payload, decrypt it, and use both key and CRL for our Openvpn service : /etc/rc.local The called script (autorun.sh) is a script which mainly parses the network settings of the running instances in order to set up the initial routes. Your instance is now ready to be used as a cloudpipe image. In the next step, we will update that instance to Glance." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1329(title) +msgid "Upload your instance to Glance" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1330(para) +msgid "We will make use of the nova snapshot feature in order to create an image from our running instance. We start by retrieving the instance ID :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1343(para) +msgid "We create an image with, using the instance ID : Make sure the instance has been upload to the Glance repository : Make that image public (snapshot-based images are private by default): You can ensure the image is now public, running " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1360(title) +msgid "Update /etc/nova.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1361(para) +msgid "Some settings need to be added into /etc/nova.conffile in order to make nova able to use our image : /etc/nova.conf You can now restart all the services : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1373(title) +msgid "Power-up your instance" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1374(para) +msgid "Use the nova cloudpipe feature the following way : Retrive all the tenants : Let's create our cloudpipe project using the tenant\"s ID : We can check the service availability : The output basically shows our instance is started. Nova will create the necessary rules for our cloudpipe instance (icmp and OpenVPN port) : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1407(title) +msgid "VPN Access" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1408(para) +msgid "In VLAN networking mode, the second IP in each private network is reserved for the cloudpipe instance. This gives a consistent IP to the instance so that nova-network can create forwarding rules for access from the outside world. The network for each project is given a specific high-numbered port on the public IP of the network host. This port is automatically forwarded to 1194 on the VPN instance." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1424(replaceable) +msgid "[new_ip]" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1425(replaceable) +msgid "[new_port]" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1417(para) +msgid "If specific high numbered ports do not work for your users, you can always allocate and associate a public IP to the instance, and then change the vpn_public_ip and vpn_public_port in the database. Rather than using the database directly, you can also use " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1430(title) +msgid "Certificates and Revocation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1431(para) +msgid "For certificate management, it is also useful to have a cron script that will periodically download the metadata and copy the new Certificate Revocation List (CRL). This will keep revoked users from connecting and disconnects any users that are connected with revoked certificates when their connection is re-negotiated (every hour). You set the use_project_ca option in nova.conf for cloudpipes to work securely so that each project has its own Certificate Authority (CA)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1438(para) +msgid "If the use_project_ca config option is set (required to for cloudpipes to work securely), then each project has its own CA. This CA is used to sign the certificate for the vpn, and is also passed to the user for bundling images. When a certificate is revoked using nova-manage, a new Certificate Revocation List (crl) is generated. As long as cloudpipe has an updated crl, it will block revoked users from connecting to the vpn." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1444(para) +msgid "The userdata for cloudpipe isn't currently updated when certs are revoked, so it is necessary to restart the cloudpipe instance if a user's credentials are revoked." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1452(title) +msgid "Restarting and Logging into the Cloudpipe VPN" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1454(para) +msgid "You can reboot a cloudpipe vpn through the api if something goes wrong (using for example), but if you generate a new crl, you will have to terminate it and start it again using the cloudpipe extension. The cloudpipe instance always gets the first ip in the subnet and if force_dhcp_release is not set it takes some time for the ip to be recovered. If you try to start the new vpn instance too soon, the instance will fail to start because of a \"NoMoreAddresses\" error. It is therefore recommended to use force_dhcp_release." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1467(para) +msgid "The keypair that was used to launch the cloudpipe instance should be in the keys/<project_id> folder. You can use this key to log into the cloudpipe instance for debugging purposes. If you are running multiple copies of nova-api this key will be on whichever server used the original request. To make debugging easier, you may want to put a common administrative key into the cloudpipe image that you create." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1480(title) +msgid "Remote access to your cloudpipe instance from an OpenVPN client" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1481(para) +msgid "Now your cloudpipe instance is running, you can use your favorite OpenVPN client in order to access your instances within their private network cloudpipe is connected to. In these sections we will present both ways of using cloudpipe, the first using a configuration file for clients without interfaces, and for clients using an interface." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1486(emphasis) +msgid "Connect to your cloudpipe instance without an interface (CLI)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1490(para) +msgid "Generate your certificates" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1491(para) +msgid "Start by generating a private key and a certificate for your project: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1496(para) +msgid "Create the openvpn configuration file" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1497(para) +msgid "The following template, which can be found under nova/cloudpipe/client.ovpn.template contains the necessary instructions for establishing a connection :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1502(emphasis) +msgid "/path/to/the/cert/file" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1503(emphasis) +msgid "/path/to/the/key/file" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1511(emphasis) +msgid "$cloudpipe-public-ip $cloudpipe-port" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1527(para) +msgid "Update the file accordingly. In order to get the public IP and port of your cloudpipe instance, you can run the following command : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1539(para) +msgid "Start your OpenVPN client" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1542(para) +msgid "Depending on the client you are using, make sure to save the configuration file under the directory it should be, so the certificate file and the private key. Usually, the file is saved under /etc/openvpn/clientconf/client.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1550(para) +msgid "Download an OpenVPN client" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1554(para) +msgid "For Ubuntu :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1555(link) +msgid "OpenVPN" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1559(link) +msgid "network-manager-openvpn" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1561(para) +msgid "kvpnc (For Kubuntu)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1565(link) +msgid "gopenvpn" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1568(para) +msgid "For Mac OsX :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1570(link) ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1586(link) +msgid "OpenVPN (Official Client)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1576(link) +msgid "Viscosity" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1580(link) +msgid "Tunnelblick" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1584(para) +msgid "For Windows :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1551(para) +msgid "In order to connect to the project's network, you will need an OpenVPN client for your computer. Here are several clients " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1593(para) +msgid "Configure your client" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1594(para) +msgid "In this example we will use Viscosity, but the same settings apply to any client. Start by filling the public ip and the public port of the cloudpipe instance." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1597(para) +msgid "These informations can be found by running a " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1607(title) +msgid "Configuring Viscosity" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1610(para) +msgid "Connection Name : \"Openstack-cloudpipe\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1611(para) +msgid "Remote server : \"172.17.1.3\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1612(para) +msgid "Port : \"1000\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1613(para) +msgid "Protocol : \"udp\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1614(para) +msgid "Device Type : \"tap\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1627(para) +msgid "Certificate : The generated certificate" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1628(para) +msgid "Key : The private key" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1640(para) +msgid "Persistence options : \"Persistent TUN\" and \"Persistent key\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1642(para) +msgid "Other :\" No bind\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1654(para) +msgid "Advanced" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1655(para) +msgid "Extra settings : \"nobind\" and \"resolv-retry infinite\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1547(para) +msgid "Connect to your cloudpipe instance using an interfaceYou can now save the configuration and establish the connection!" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1671(title) +msgid "Cloudpipe Troubleshooting and Automation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1674(emphasis) +msgid "Troubleshoot your cloudpipe instance" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1676(para) +msgid "A periodic task disassociates the fixed ip address for the cloudpipe instance. Into /var/log/nova/nova-network.log, the following line should appear : Once the job has been run, should not return anything ; but if the cloudpipe instance is respawned too quickly; the following error could be encountered : In order to resolve that issue, log into the mysql server and update the ip address status : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1701(emphasis) +msgid "Cloudpipe-related configuration option reference" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1717(emphasis) +msgid "Cloudpipe-related files" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1718(para) +msgid "Nova stores cloudpipe keys into /var/lib/nova/keys." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1720(para) +msgid "Certificates are stored into /var/lib/nova/CA." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1721(para) +msgid "Credentials are stored into /var/lib/nova/CA/projects/" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1727(emphasis) +msgid "Automate the cloudpipe image installation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1729(para) +msgid "You can automate the image creation by download that script and running it from inside the instance : Get the script from Github" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1739(title) +msgid "Enabling Ping and SSH on VMs" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1740(para) +msgid "Be sure you enable access to your VMs by using the or command. Below, you will find the commands to allow and to your VMs:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1746(para) +msgid "These commands need to be run as root only if the credentials used to interact with nova-api have been put under /root/.bashrc. If the EC2 credentials have been put into another user's .bashrc file, then, it is necessary to run these commands as the user." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1753(para) +msgid "Using the nova command-line tool:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1758(para) +msgid "Using euca2ools:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1764(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 the following as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1777(title) +msgid "Configuring Public (Floating) IP Addresses" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1780(title) +msgid "Private and Public IP Addresses" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1781(para) +msgid "Every virtual instance is automatically assigned a private IP address. You may optionally assign public IP addresses to instances. OpenStack uses the term \"floating IP\" to refer to an IP address (typically public) that can be dynamically added to a running virtual instance. OpenStack Compute uses Network Address Translation (NAT) to assign floating IPs to virtual instances." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1789(para) +msgid "If you plan to use this feature, you must add the following to your nova.conf file to specify which interface the nova-network service will bind public IP addresses to:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1796(para) +msgid "Restart the nova-network service if you change nova.conf while the service is running." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1798(title) +msgid "Traffic between VMs using floating IPs" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1799(para) +msgid "Note that due to the way floating IPs are implemented using a source NAT (SNAT rule in iptables), inconsistent behaviour of security groups can be seen if VMs use their floating IP to communicate with other virtual machines - particularly on the same physical host. Traffic from VM to VM across the fixed network does not have this issue, and this is the recommended path. To ensure traffic doesn't get SNATed to the floating range, explicitly set dmz_cidr=x.x.x.x/y. x.x.x.x/y is the range of floating ips for each pool of floating ips you define. This configuration is also necessary to make source_groups work if the vms in the source group have floating ips." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1814(title) +msgid "Enabling IP forwarding" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1818(para) +msgid "The IP forwarding only needs to be enabled on the nodes running the service nova-network. If the multi_host mode is used, make sure to enable it on all the compute node, otherwise, enable it on the node running the nova-network service." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1815(para) +msgid "By default, the IP forwarding is disabled on most of Linux distributions. The \"floating IP\" feature requires the IP forwarding enabled in order to work. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1824(para) +msgid "you can check if the forwarding is enabled by running the following command: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1826(para) +msgid "Or using sysctl" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1829(para) +msgid "In this example, the IP forwarding is disabled. You can enable it on the fly by running the following command: or In order to make the changes permanent, edit the /etc/sysctl.conf and update the IP forwarding setting : Save the file and run the following command in order to apply the changes : It is also possible to update the setting by restarting the network service. Here's an example for Ubuntu: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1845(para) +msgid "Here's an example for RHEL/Fedora/CentOS:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1852(title) +msgid "Creating a List of Available Floating IP Addresses" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1854(para) +msgid "Nova maintains a list of floating IP addresses that are available for assigning to instances. Use the command to add entries to this list, as root." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1862(para) +msgid "The following nova-manage commands apply to floating IPs." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1866(para) +msgid ": List the floating IP addresses in the pool." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1871(para) +msgid ": Create specific floating IPs for either a single address or a subnet." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1877(para) +msgid ": Remove floating IP addresses using the same parameters as the create command." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1886(title) +msgid "Adding a Floating IP to an Instance" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1887(para) +msgid "Adding a floating IP to an instance is a two step process:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1891(para) +msgid ": Allocate a floating IP address from the list of available addresses." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1896(para) +msgid ": Add an allocated floating IP address to a running instance." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1902(para) +msgid "Here's an example of how to add a floating IP to a running instance with an ID of 12" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1916(para) +msgid "If the instance no longer needs a public address, remove the floating IP address from the instance and de-allocate the address:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1926(title) +msgid "Automatically adding floating IPs" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1927(para) +msgid "The nova-network service can be configured to automatically allocate and assign a floating IP address to virtual instances when they are launched. Add the following line to nova.conf and restart the nova-network service" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1936(para) +msgid "Note that if this option is enabled and all of the floating IP addresses have already been allocated, the command will fail with an error." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1943(title) +msgid "Removing a Network from a Project" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1944(para) +msgid "You will find that you cannot remove a network that has already been associated to a project by simply deleting it. You can disassociate the project from the network with a scrub command and the project name as the final parameter:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1954(title) +msgid "Using multiple interfaces for your instances (multinic)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1961(para) +msgid "SSL Configurations (VIPs)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1964(para) +msgid "Services failover/ HA" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1967(para) +msgid "Bandwidth Allocation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1970(para) +msgid "Administrative/ Public access to your instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1977(title) +msgid "multinic flat manager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1985(title) +msgid "multinic flatdhcp manager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1993(title) +msgid "multinic VLAN manager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:1957(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/src/docbkx/openstack-compute-admin/computenetworking.xml:2002(title) +msgid "Using the multinic feature" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2015(para) +msgid "Make sure to power up the second interface on the instance, otherwise that last won't be reacheable via 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/src/docbkx/openstack-compute-admin/computenetworking.xml:2019(filename) +msgid "/etc/network/interfaces" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2003(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/src/docbkx/openstack-compute-admin/computenetworking.xml:2031(para) +msgid "If the Virtual Network Service Quantum 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/src/docbkx/openstack-compute-admin/computenetworking.xml:2041(title) +msgid "Existing High Availability Options for Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2043(para) +msgid "Based off a blog post by Vish Ishaya" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2047(para) +msgid "As illustrated in the Flat DHCP diagram in Section Configuring Flat DHCP Networking titled Flat DHCP network, multiple interfaces, multiple servers, traffic from the VM to the public internet has to go through the host running nova network. DHCP is handled by nova-network as well, listening on the gateway address of the fixed_range network. The compute hosts can optionally have their own public IPs, or they can use the network host as their gateway. This mode is pretty simple and it works in the majority of situations, but it has one major drawback: the network host is a single point of failure! If the network host goes down for any reason, it is impossible to communicate with the VMs. Here are some options for avoiding the single point of failure." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2058(title) +msgid "HA Option 1: Multi-host" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2059(para) +msgid "To eliminate the network host as a single point of failure, Compute can be configured to allow each compute host to do all of the networking jobs for its own VMs. Each compute host does NAT, DHCP, and acts as a gateway for all of its own VMs. While there is still a single point of failure in this scenario, it is the same point of failure that applies to all virtualized systems." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2068(para) +msgid "This setup requires adding an IP on the VM network to each host in the system, and it implies a little more overhead on the compute hosts. It is also possible to combine this with option 4 (HW Gateway) to remove the need for your compute hosts to gateway. In that hybrid version they would no longer gateway for the VMs and their responsibilities would only be DHCP and NAT." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2076(para) +msgid "The resulting layout for the new HA networking option looks the following diagram:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2079(title) +msgid "High Availability Networking Option" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2087(para) +msgid "In contrast with the earlier diagram, all the hosts in the system are running the nova-compute, nova-network and nova-api services. Each host does DHCP and does NAT for public traffic for the VMs running on that particular host. In this model every compute host requires a connection to the public internet and each host is also assigned an address from the VM network where it listens for DHCP traffic. The nova-api service is needed so that it can act as a metadata server for the instances." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2106(para) +msgid " or " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2097(para) +msgid "To run in HA mode, each compute host must run the following services:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2110(para) +msgid "If the compute host is not an API endpoint, use the service. The nova.conf file should contain:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2117(para) +msgid "The send_arp_for_ha option facilitates sending of gratuitous arp messages to ensure the arp caches on compute hosts are up to date." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2121(para) +msgid "If a compute host is also an API endpoint, use the service. Your enabled_apis option will need to contain metadata, as well as additional options depending on the API services. For example, if it supports compute requests, volume requests, and EC2 compatibility, the nova.conf file should contain: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2134(para) +msgid "The multi_host option must be in place when you create the network and nova-network must be run on every compute host. These created multi hosts networks will send all network related commands to the host that the specific VM is on. You need to edit the configuration option enabled_apis such that it includes metadata in the list of enabled APIs. Other options become available when you configure multi_host nova networking please refer to Configuration: nova.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2142(para) +msgid "You must specify the multi_host option on the command line when creating fixed networks. For example: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2153(title) +msgid "HA Option 2: Failover" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2154(para) +msgid "The folks at NTT labs came up with a ha-linux configuration that allows for a 4 second failover to a hot backup of the network host. Details on their approach can be found in the following post to the openstack mailing list: https://lists.launchpad.net/openstack/msg02099.html" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2161(para) +msgid "This solution is definitely an option, although it requires a second host that essentially does nothing unless there is a failure. Also four seconds can be too long for some real-time applications." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2165(para) +msgid "To enable this HA option, your nova.conf file must contain the following option:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2167(para) +msgid "See https://bugs.launchpad.net/nova/+bug/782364 for details on why this option is required when configuring for failover." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2172(title) +msgid "HA Option 3: Multi-nic" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2173(para) +msgid "Recently, nova gained support for multi-nic. This allows us to bridge a given VM into multiple networks. This gives us some more options for high availability. It is possible to set up two networks on separate vlans (or even separate ethernet devices on the host) and give the VMs a NIC and an IP on each network. Each of these networks could have its own network host acting as the gateway." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2181(para) +msgid "In this case, the VM has two possible routes out. If one of them fails, it has the option of using the other one. The disadvantage of this approach is it offloads management of failure scenarios to the guest. The guest needs to be aware of multiple networks and have a strategy for switching between them. It also doesn't help with floating IPs. One would have to set up a floating IP associated with each of the IPs on private the private networks to achieve some type of redundancy." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2193(title) +msgid "HA Option 4: Hardware gateway" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2206(replaceable) +msgid "172.16.100.1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2201(para) +msgid "Create a dnsmasq configuration file (e.g., /etc/dnsmasq-nova.conf) that contains the IP address of the external gateway. If running in FlatDHCP mode, assuming the IP address of the hardware gateway was 172.16.100.1, the file would contain the line:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2207(para) +msgid "If running in VLAN mode, a separate router must be specified for each network. The networks are identified by the --label argument when calling to create the networks as documented in the Configuring VLAN Networking subsection. Assuming you have three VLANs, that are labeled red, green, and blue, with corresponding hardware routers at 172.16.100.1, 172.16.101.1 and 172.16.102.1, the dnsmasqconfiguration file (e.g., /etc/dnsmasq-nova.conf) would contain the following:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2224(para) +msgid "Edit /etc/nova/nova.conf to specify the location of the dnsmasq configuration file:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2229(para) +msgid "Configure the hardware gateway to forward metadata requests to a host that's running the nova-api service with the metadata API enabled." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2232(para) +msgid "The virtual machine instances access the metadata service at 169.254.169.254 port 80. The hardware gateway should forward these requests to a host running the nova-api service on the port specified as the metadata_host config option in /etc/nova/nova.conf, which defaults to 8775." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2239(para) +msgid "Make sure that the list in the enabled_apis configuration option /etc/nova/nova.conf contains metadata in addition to the other APIs. An example that contains the EC2 API, the OpenStack compute API, the OpenStack volume API, and the metadata service would look like: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2247(para) +msgid "Ensure you have set up routes properly so that the subnet that you use for virtual machines is routable." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2194(para) +msgid "The dnsmasq service can be configured to use an external gateway instead of acting as the gateway for the VMs. This offloads HA to standard switching hardware and it has some strong benefits. Unfortunately, the nova-network service is still responsible for floating IP natting and DHCP, so some failover strategy needs to be employed for those options. To configure for hardware gateway:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2255(title) +msgid "Troubleshooting Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2256(title) +msgid "Can't reach floating IPs" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2257(para) +msgid "If you aren't able to reach your instances via 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/src/docbkx/openstack-compute-admin/computenetworking.xml:2272(para) +msgid "Ensure the NAT rules have been added to iptables on the node that nova-network is running on, as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2288(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/src/docbkx/openstack-compute-admin/computenetworking.xml:2305(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/src/docbkx/openstack-compute-admin/computenetworking.xml:2314(replaceable) +msgid "eth2" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2308(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/src/docbkx/openstack-compute-admin/computenetworking.xml:2315(para) +msgid "If this solves your issue, add the following line to /etc/sysctl.conf so that the revesrse path filter will be disabled the next time the compute host reboots:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2321(title) +msgid "Disabling firewall" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2322(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/src/docbkx/openstack-compute-admin/computenetworking.xml:2325(para) +msgid "We strongly recommend you remove the above line to re-enable the firewall once your networking issues have been resolved." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2328(title) +msgid "Packet loss from instances to nova-network server (VLANManager mode)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2329(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 (e.g., ), then there may be packet loss occurring on the connection to the instance." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2333(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 (e.g., vlan100) and the associated bridge interface (e.g., br100) on the host running the nova-network service." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2337(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/src/docbkx/openstack-compute-admin/computenetworking.xml:2339(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/src/docbkx/openstack-compute-admin/computenetworking.xml:2343(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/src/docbkx/openstack-compute-admin/computenetworking.xml:2347(para) +msgid "In the third terminal, SSH inside of the instance and generate DNS requests by using the command:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2350(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 will hang for several seconds." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2354(para) +msgid "If the command somteimes 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/src/docbkx/openstack-compute-admin/computenetworking.xml:2360(para) +msgid "If this solves your issue, add the following line to /etc/sysctl.conf so that these changes will take effect the next time the host reboots:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2367(title) +msgid "KVM: Network connectivity works initially, then fails" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computenetworking.xml:2368(para) +msgid "Some administrators have observed an issue with the KVM hypervisor where instances running Ubuntu 12.04 will sometimes lose 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/src/docbkx/openstack-compute-admin/computenetworking.xml:2377(para) +msgid "Note that loading the module will have no effect on instances that are already running." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computehypervisors.xml:7(para) +msgid "This section assumes you have a working installation of OpenStack Compute and want to select a particular hypervisor or run with multiple hypervisors. Before you try to get a VM running within OpenStack Compute, be sure you have installed a hypervisor and used the hypervisor's documentation to run a test VM and get it working." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computehypervisors.xml:12(title) +msgid "Selecting a Hypervisor" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computehypervisors.xml:13(para) +msgid "OpenStack Compute supports many hypervisors, an array of which must provide a bit of difficulty in selecting a hypervisor unless you are already familiar with one. Most installations only use a single hypervisor, however as of the Folsom release, it is possible to use the ComputeFilter and ImagePropertiesFilter to allow scheduling to different hypervisors within the same installation. The following links provide additional information for choosing a hypervisor. Refer to http://wiki.openstack.org/HypervisorSupportMatrix for a detailed list of features and support across the hypervisors." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computehypervisors.xml:24(para) +msgid "Here is a list of the supported hypervisors with links to a relevant web site for configuration and use:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computehypervisors.xml:27(para) +msgid "KVM - Kernel-based Virtual Machine. The virtual disk formats that it supports it inherits 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/src/docbkx/openstack-compute-admin/computehypervisors.xml:31(para) +msgid "LXC - Linux Containers (through libvirt), use to run Linux-based virtual machines." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computehypervisors.xml:33(para) +msgid "QEMU - Quick EMUlator, generally only used for development purposes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computehypervisors.xml:35(para) +msgid "UML - User Mode Linux, generally only used for development purposes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computehypervisors.xml:37(para) +msgid "VMWare ESX/ESXi 4.1 update 1, runs VMWare-based Linux and Windows images through a connection with the ESX server." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computehypervisors.xml:40(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/src/docbkx/openstack-compute-admin/computehypervisors.xml:43(para) +msgid " PowerVM - Server virtualization with IBM PowerVM, use to run AIX, IBM i and Linux environments on IBM POWER technology." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computehypervisors.xml:46(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/src/docbkx/openstack-compute-admin/computehypervisors.xml:49(para) +msgid " Bare Metal - Not a hypervisor in the traditional sense, this driver provisions physical hardware via pluggable sub-drivers (eg. PXE for image deployment, and IPMI for power management)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computehypervisors.xml:57(title) +msgid "Hypervisor Configuration Basics" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computehypervisors.xml:58(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/src/docbkx/openstack-compute-admin/computehypervisors.xml:60(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/src/docbkx/openstack-compute-admin/computehypervisors.xml:62(para) +msgid "Here are the nova.conf options that are used to configure the compute 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/src/docbkx/openstack-compute-admin/computescheduler.xml:78(None) +msgid "@@image: 'figures/filteringWorkflow1.png '; md5=THIS FILE DOESN'T EXIST" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:482(None) +msgid "@@image: 'figures/filteringWorkflow2.png '; md5=THIS FILE DOESN'T EXIST" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:6(title) +msgid "Scheduling" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:7(para) +msgid "Compute uses the service to determine how to dispatch compute and volume requests. For example, the service determines which host a VM should launch on. The term \"host\" in the context of filters means a physical node that has a service running on it. The scheduler is configurable through a variety of options." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:14(para) +msgid "Compute is configured with the following default scheduler options:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:25(para) +msgid "Compute is configured by default to use the Multi Scheduler, which allows the admin to specify different scheduling behavior for compute requests versus volume requests." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:29(para) +msgid "The volume scheduler is configured by default as a Chance Scheduler, which picks a host at random that has the service running." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:32(para) +msgid "The compute scheduler is configured by default as a Filter Scheduler, described in detail in the next section. In the default configuration, this scheduler will only consider hosts that are in the requested availability zone (AvailabilityZoneFilter), that have sufficient RAM available (RamFilter), and that are actually capable of servicing the request (ComputeFilter)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:40(para) +msgid "From the resulting filtered list of eligible hosts, the scheduler will assign a cost to each host based on the amount of free RAM (nova.scheduler.least_cost.compute_fill_first_cost_fn), will multiply each cost value by -1 (compute_fill_first_cost_fn_weight), and will select the host with the minimum cost. This is equivalent to selecting the host with the maximum amount of RAM available." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:50(title) +msgid "Filter Scheduler" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:51(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. This Scheduler can only be used for scheduling compute requests, not volume requests, i.e. it can only be used with the compute_scheduler_driver configuration option." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:63(title) +msgid "Filters" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:73(title) +msgid "Filtering" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:64(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 costs and weight section. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:84(para) +msgid "The scheduler_available_filters configuration option in nova.conf provides the Compute service with the list of the filters that will be used by the scheduler. The default setting specifies all of the filter that are included with the Compute service: 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/src/docbkx/openstack-compute-admin/computescheduler.xml:104(para) +msgid "The scheduler_default_filters configuration option in nova.conf defines the list of filters that will be applied by the service. As mentioned above, the default filters are: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:113(para) +msgid "The available filters are described below." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:116(title) +msgid "AggregateInstanceExtraSpecsFilter" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:117(para) +msgid "Matches properties defined in an instance type's extra specs against admin-defined properties on a host aggregate. See the host aggregates section for documentation on how to use this filter." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:125(title) +msgid "AllHostsFilter" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:126(para) +msgid "This is a no-op filter, it does not eliminate any of the available hosts." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:131(title) +msgid "AvailabilityZoneFilter" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:132(para) +msgid "Filters hosts by availability zone. This filter must be enabled for the scheduler to respect availability zones in requests." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:138(title) +msgid "ComputeCapabilitiesFilter" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:139(para) +msgid "Matches properties defined in an instance type's extra specs against compute capabilities." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:141(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/src/docbkx/openstack-compute-admin/computescheduler.xml:149(title) +msgid "ComputeFilter" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:150(para) +msgid "Filters hosts by flavor (also known as instance type) and image properties. The scheduler will check to ensure that a compute host has sufficient capabilities to run a virtual machine instance that corresponds to the specified flavor. If the image has properties specified, this filter will also check that the host can support them. The image properties that the filter checks for are:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:160(para) +msgid "architecture: Architecture describes the machine architecture required by the image. Examples are i686, x86_64, arm, and ppc64." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:166(para) +msgid "hypervisor_type: Hypervisor type describes the hypervisor required by the image. Examples are xen, kvm, qemu, xenapi, and powervm." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:172(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/src/docbkx/openstack-compute-admin/computescheduler.xml:180(para) +msgid "In general, this filter should always be enabled." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:185(title) +msgid "CoreFilter" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:186(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 (i.e., the virtual cores running on an instance may exceed the physical cores)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:191(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: With this setting, if there are 8 vCPUs on a node, the scheduler will allow instances up to 128 vCPU to be run on that node." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:203(para) +msgid "To disallow vCPU overcommitment set:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:210(title) +msgid "DifferentHostFilter" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:211(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: With the API, use the os:scheduler_hints key. For example: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:241(title) +msgid "GroupAntiAffinityFilter" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:242(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. Using the command-line tool, use the --hint flag. For example: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:256(title) +msgid "ImagePropertiesFilter" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:257(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. E.g., 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 using " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:271(title) +msgid "IsolatedHostsFilter" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:272(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." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:277(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/src/docbkx/openstack-compute-admin/computescheduler.xml:290(title) +msgid "JsonFilter" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:295(para) +msgid "=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:298(para) +msgid "<" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:301(para) +msgid ">" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:304(para) +msgid "in" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:307(para) +msgid "<=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:310(para) +msgid ">=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:313(para) +msgid "not" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:316(para) +msgid "or" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:319(para) +msgid "and" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:323(para) +msgid "$free_ram_mb" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:326(para) +msgid "$free_disk_mb" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:329(para) +msgid "$total_usable_ram_mb" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:332(para) +msgid "$vcpus_total" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:335(para) +msgid "$vcpus_used" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:291(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: With the API, use the os:scheduler_hints key: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:359(title) +msgid "RamFilter" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:360(para) +msgid "Only schedule instances on hosts if there is sufficient RAM available. If this filter is not set, the scheduler may over provision a host based on RAM (i.e., the RAM allocated by virtual machine instances may exceed the physical RAM)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:365(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: With this setting, if there is 1GB of free RAM, the scheduler will allow instances up to size 1.5GB to be run on that instance." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:380(title) +msgid "RetryFilter" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:381(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 will prevent the scheduler from retrying that host for the service request." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:387(para) +msgid "This filter is only useful if the scheduler_max_attempts configuration option is set to a value greater than zero." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:394(title) +msgid "SameHostFilter" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:395(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: With the API, use the os:scheduler_hints key: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:425(title) +msgid "SimpleCIDRAffinityFilter" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:431(literal) +msgid "build_near_host_ip" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:433(para) +msgid "The first IP address in the subnet (e.g., 192.168.1.1)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:439(literal) +msgid "cidr" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:441(para) +msgid "The CIDR that corresponds to the subnet (e.g., /24)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:426(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: Using the command-line tool, use the --hint flag. For example, to specify the IP subnet 192.168.1.1/24" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:453(para) +msgid "With the API, use the os:scheduler_hints key:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:473(title) +msgid "Costs and Weights" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:477(title) +msgid "Computing weighted costs" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:487(para) +msgid "The Filter Scheduler takes the hosts that remain after the filters have been applied and applies one or more cost function to each host to get numerical scores for each host. Each cost score is multiplied by a weighting constant specified in the nova.conf config file. The weighting constant configuration option is the name of the cost function, with the _weight string appended. Here is an example of specifying a cost function and its corresponding weight:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:501(para) +msgid "Multiple cost functions can be specified in the least_cost_functions configuration option, separated by commas. For example:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:509(para) +msgid "If there are multiple cost functions, then the weighted cost scores are added together. The scheduler selects the host that has the minimum weighted cost." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:512(para) +msgid "The Compute service comes with three cost functions:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:514(title) +msgid "nova.scheduler.least_cost.compute_fill_first_cost_fn" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:515(para) +msgid "This cost function calculates the amount of free memory (RAM) available on the node. Because the scheduler minimizes cost, if this cost function is used as a weight of +1, by doing: then the scheduler will tend to \"fill up\" hosts, scheduling virtual machine instances to the same host until there is no longer sufficient RAM to service the request, and then moving to the next node" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:526(para) +msgid "If the user specifies a weight of -1 by doing: then the scheduler will favor hosts that have the most amount of available RAM, leading to a \"spread-first\" behavior." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:535(title) +msgid "nova.scheduler.least_cost.retry_host_cost_fn" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:536(para) +msgid "This cost function adds additional cost for retrying scheduling a host that was already used for a previous scheduling attempt." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:539(para) +msgid "The normal method of using this function is to set retry_host_cost_fn_weight to a positive value, so that hosts which consistently encounter build failures will be used less often." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:546(title) +msgid "nova.scheduler.least_cost.noop_cost_fn" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:547(para) +msgid "This cost function returns 1 for all hosts. It is a \"no-op\" cost function (i.e., it does not do anything to discriminate among hosts). In practice, this cost function is never used." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:555(title) +msgid "Other Schedulers" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:557(para) +msgid "While an administrator is likely to only need to work with the Filter Scheduler, Compute comes with other schedulers as well, described below." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:561(title) +msgid "Chance Scheduler" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:562(para) +msgid "The Chance Scheduler (nova.scheduler.chance.ChanceScheduler) randomly selects from the lists of filtered hosts. It is the default volume scheduler." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:568(title) +msgid "Multi Scheduler" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computescheduler.xml:569(para) +msgid "The Multi Scheduler nova.scheduler.multi.MultiScheduler holds multiple sub-schedulers, one for nova-compute requests and one for nova-volume requests. It is the default top-level scheduler as specified by the scheduler_driver configuration option." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:27(title) +msgid "System Administration" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:28(para) +msgid "By understanding how the different installed nodes interact with each other you can administer the OpenStack Compute installation. OpenStack 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 Nova services." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:32(para) +msgid "The OpenStack Compute cloud works via 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/src/docbkx/openstack-compute-admin/computeadmin.xml:38(para) +msgid "Currently, Services are nova-api, nova-objectstore (which can be replaced with Glance, the OpenStack Image Service), nova-compute, nova-volume, 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/src/docbkx/openstack-compute-admin/computeadmin.xml:44(para) +msgid "For example, other components that need to deal with volumes in some way, should do so by calling methods on the VolumeManager instead of directly changing fields in the database. This allows us to keep all of the code relating to volumes in the same place." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:49(para) +msgid "nova-api - The nova-api service 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/src/docbkx/openstack-compute-admin/computeadmin.xml:55(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/src/docbkx/openstack-compute-admin/computeadmin.xml:62(para) +msgid "nova-compute - The nova-compute service is responsible for managing virtual machines. It loads a Service object which exposes the public methods on ComputeManager via Remote Procedure Call (RPC)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:67(para) +msgid "nova-volume - The nova-volume service is responsible for managing attachable block storage devices. It loads a Service object which exposes the public methods on VolumeManager via RPC." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:72(para) +msgid "nova-network - The nova-network service is 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/src/docbkx/openstack-compute-admin/computeadmin.xml:84(title) +msgid "Understanding the Compute Service Architecture" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:85(para) +msgid "These basic categories describe the service architecture and what's going on within the cloud controller." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:86(title) +msgid "API Server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:88(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/src/docbkx/openstack-compute-admin/computeadmin.xml:90(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/src/docbkx/openstack-compute-admin/computeadmin.xml:92(title) +msgid "Message Queue" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:93(para) +msgid "A messaging queue brokers the interaction between compute nodes (processing), volumes (block storage), 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/src/docbkx/openstack-compute-admin/computeadmin.xml:96(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 hostname. 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/src/docbkx/openstack-compute-admin/computeadmin.xml:99(title) +msgid "Compute Worker" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:101(para) +msgid "Compute workers manage computing instances on host machines. Through the API, commands are dispatched to compute workers to:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:104(para) +msgid "Run instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:105(para) +msgid "Terminate instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:106(para) +msgid "Reboot instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:107(para) +msgid "Attach volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:108(para) +msgid "Detach volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:109(para) +msgid "Get console output" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:111(title) +msgid "Network Controller" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:113(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/src/docbkx/openstack-compute-admin/computeadmin.xml:115(para) +msgid "Allocate fixed IP addresses" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:116(para) +msgid "Configuring VLANs for projects" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:117(para) +msgid "Configuring networks for compute nodes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:119(title) +msgid "Volume Workers" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:121(para) +msgid "Volume Workers interact with iSCSI storage to manage LVM-based instance volumes. Specific functions include:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:124(para) +msgid "Create volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:125(para) +msgid "Delete volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:126(para) +msgid "Establish Compute volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:128(para) +msgid "Volumes may easily be transferred between instances, but may be attached to only a single instance at a time." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:130(title) +msgid "Managing Compute Users" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:131(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 will verify the signature and execute commands on behalf of the user." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:135(para) +msgid "In order to begin using nova, you will need to create a user with the Identity Service." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:140(title) +msgid "Managing the Cloud" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:140(para) +msgid "There are three main tools that a system administrator will find useful to manage their cloud; the nova client, the nova-manage command, and the Euca2ools commands." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:142(para) +msgid "The nova-manage command may only be run by cloud administrators. Both novaclient and euca2ools can be used by all users, though specific commands may be restricted by Role Based Access Control in the deprecated nova auth system or in the Identity Management service." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:145(title) +msgid "Using the nova command-line tool" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:146(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 username 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/src/docbkx/openstack-compute-admin/computeadmin.xml:150(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/src/docbkx/openstack-compute-admin/computeadmin.xml:158(para) +msgid "Now that you have installed the python-novaclient, confirm the installation by entering:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:170(para) +msgid "In return, you will get a listing of all the commands and parameters for the nova command line client. By setting up the required parameters as environment variables, you can fly through these commands on the command line. You can add --os-username on the nova command, or set them as environment variables:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:183(para) +msgid "Using the Identity Service, you are supplied with an authentication endpoint, which nova recognizes as the OS_AUTH_URL." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:193(title) +msgid "Using the nova-manage command" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:194(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/src/docbkx/openstack-compute-admin/computeadmin.xml:197(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/src/docbkx/openstack-compute-admin/computeadmin.xml:204(para) +msgid "For administrators, the standard pattern for executing a nova-manage command is:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:206(replaceable) +msgid "[args]" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:209(para) +msgid "For example, to obtain a list of all projects: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:212(para) +msgid "Run without arguments to see a list of available command categories: nova-manage" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:213(para) +msgid "You can also run with a category argument such as user to see a list of all commands in that category: nova-manage service" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:215(title) +msgid "Using the euca2ools commands" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:216(para) +msgid "For a command-line interface to EC2 API calls, use the euca2ools command line tool. It is documented at http://open.eucalyptus.com/wiki/Euca2oolsGuide_v1.3" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:227(title) +msgid "Managing logs" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:229(title) +msgid "Logging module" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:230(para) +msgid "Adding the following line to /etc/nova/nova.conf will allow you to specify a configuration file for changing the logging behavior, in particular for changing the logging level (e.g., DEBUG, INFO, WARNING, ERROR):" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:235(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/src/docbkx/openstack-compute-admin/computeadmin.xml:243(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/src/docbkx/openstack-compute-admin/computeadmin.xml:253(title) +msgid "Syslog" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:262(filename) +msgid "/etc/nova/nova.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:265(filename) +msgid "/etc/keystone/keystone.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:268(filename) +msgid "/etc/glance/glance-api.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:271(filename) +msgid "/etc/glance/glance-registry.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:274(filename) +msgid "/etc/cinder/cinder.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:282(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/src/docbkx/openstack-compute-admin/computeadmin.xml:255(para) +msgid "OpenStack Compute services can be configured to send logging information to syslog. This is particularly useful if you want to use rsyslog, which will forward 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 the following lines to: In addition to enabling syslog, these settings also turn off more verbose output and debugging output from the log." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:292(title) +msgid "Rsyslog" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:293(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/src/docbkx/openstack-compute-admin/computeadmin.xml:298(para) +msgid "This example shows a minimal configuration for /etc/rsyslog.conf on the log server host which will receive the log files:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:307(replaceable) +msgid "compute-01" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:304(para) +msgid "Add to /etc/rsyslog.conf a filter rule on which looks for a hostname. The example below use compute-01 as an example of a compute host name:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:308(para) +msgid "On the compute hosts, create a file named /etc/rsyslog.d/60-nova.conf, with the following content." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:314(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/src/docbkx/openstack-compute-admin/computeadmin.xml:322(title) +msgid "Using Migration" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:323(para) +msgid "Before starting migrations, review the Configuring Migrations section." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:325(para) +msgid "Migration provides a scheme to migrate running instances from one OpenStack Compute server to another OpenStack Compute server. This feature can be used as described below." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:330(para) +msgid "First, look at the running instances, to get the ID of the instance you wish to migrate." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:341(para) +msgid "Second, look at information associated with that instance - our example is vm1 from above." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:359(para) +msgid "In this example, vm1 is running on HostB." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:362(para) +msgid "Third, select the server to migrate instances to." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:371(para) +msgid "In this example, HostC can be picked up because nova-compute is running on it." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:374(para) +msgid "Third, ensure that HostC has enough resource for migration." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:387(para) +msgid "cpu:the nuber of cpu" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:390(para) +msgid "mem(mb):total amount of memory (MB)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:393(para) +msgid "hddtotal amount of NOVA-INST-DIR/instances(GB)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:396(para) +msgid "1st line shows total amount of resource physical server has." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:399(para) +msgid "2nd line shows current used resource." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:402(para) +msgid "3rd line shows maximum used resource." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:405(para) +msgid "4th line and under is used resource per project." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:410(para) +msgid "Finally, use the command to migrate the instances." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:419(para) +msgid "While the nova command is called , under the default Compute configuration options the instances are suspended before migration. See the Configuring Migrations section for more details." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:416(para) +msgid "Make sure instances are migrated successfully with . If instances are still running on HostB, check logfiles (src/dest nova-compute and nova-scheduler) to determine why. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:429(title) +msgid "Recovering from a failed compute node" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:430(para) +msgid "If you have deployed OpenStack Compute with a shared filesystem, you can quickly recover from a failed compute node." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:433(title) +msgid "Working with host information" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:434(para) +msgid "The first step is to 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/src/docbkx/openstack-compute-admin/computeadmin.xml:443(para) +msgid "First, you can review the status of the host 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/src/docbkx/openstack-compute-admin/computeadmin.xml:470(title) +msgid "Recover the VM" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:471(para) +msgid "Armed with the information of VMs on the failed host, determine which compute host the affected VMs should be moved to. In this case, the VM will move to np-rcc46, which is achieved using this database command:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:478(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 nova compute host that is the VMs new home, and update the VNC IP if it isn't already 0.0.0.0." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:485(para) +msgid "Next, reboot the VM: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:491(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 nova services or updating the vm_state and power_state in the nova database." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:500(title) +msgid "Recovering from a UID/GID mismatch" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:501(para) +msgid "When running OpenStack compute, using a shared filesystem 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/src/docbkx/openstack-compute-admin/computeadmin.xml:509(para) +msgid "First,make sure you don't use numbers that are already used for some other user/group." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:510(para) +msgid "Set the nova uid in /etc/passwd to the same number in all hosts (e.g. 112)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:511(para) +msgid "Set the libvirt-qemu uid in /etc/passwd to the same number in all hosts (e.g. 119)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:512(para) +msgid "Set the nova group in /etc/group file to the same number in all hosts (e.g. 120)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:513(para) +msgid "Set the libvirtd group in /etc/group file to the same number in all hosts (e.g. 119)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:514(para) +msgid "Stop the services on the compute node" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:515(para) +msgid "Change all the files owned by nova or group by nova, e.g. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:521(para) +msgid "Repeat the steps for the libvirt-qemu owned files if those were needed to change" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:522(para) +msgid "Restart the services" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:506(para) +msgid "The following is a basic procedure run on nova-compute hosts, based on the KVM hypervisor, that could help to restore the situation: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:525(para) +msgid "Following this, you can run the command to verify that all files using the correct identifiers." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:531(title) +msgid "Nova Disaster Recovery Process" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:532(para) +msgid "Sometimes, things just don't go right. An incident is never planned, by its definition." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:534(para) +msgid "In this section, we will review managing your cloud after a disaster, and how to easily backup the persistent storage volumes, which is another approach when you face a disaster. Even apart from the disaster scenario, backup ARE mandatory. While the Diablo release includes the snapshot functions, both the backup procedure and the utility do apply to the Cactus release." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:541(para) +msgid "For reference, you cand find a DRP definition here : http://en.wikipedia.org/wiki/Disaster_Recovery_Plan." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:545(title) +msgid "A- The disaster Recovery Process presentation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:551(para) +msgid "A cloud controller (nova-api, nova-objecstore, nova-volume, nova-network)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:556(para) +msgid "A compute node (nova-compute)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:559(para) +msgid "A Storage Area Network used by nova-volumes (aka SAN)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:568(para) +msgid "From the SAN to the cloud controller, we have an active iscsi session (used for the \"nova-volumes\" LVM's VG)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:573(para) +msgid "From the cloud controller to the compute node we also have active iscsi sessions (managed by nova-volume)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:578(para) +msgid "For every volume an iscsi session is made (so 14 ebs volumes equals 14 sessions)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:583(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/src/docbkx/openstack-compute-admin/computeadmin.xml:589(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 (mountpoint, volume id, volume status, etc..)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:546(para) +msgid "A disaster could happen to several components of your architecture : a disk crash, a network loss, a power cut, etc. In this example, we suppose the following setup : The example disaster will be 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 : Now, after the power loss occurs and all hardware components restart, the situation is as follows:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:602(para) +msgid "From the SAN to the cloud, the ISCSI session no longer exists." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:606(para) +msgid "From the cloud controller to the compute node, the ISCSI sessions no longer exist." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:611(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/src/docbkx/openstack-compute-admin/computeadmin.xml:617(para) +msgid "From the cloud controller, instances turn into a shutdown state (because they are no longer running)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:622(para) +msgid "Into the database, data was not updated at all, since nova could not have guessed the crash." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:599(para) +msgid "Before going further, and in order to prevent the admin to make fatal mistakes, the instances won't be lost, since no \"\" or \"\" command had been invoked, so the files for the instances remain on the compute node." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:634(para) +msgid "The plan is to perform the following tasks, in that exact order. Any extra step would be dangerous at this stage :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:641(para) +msgid "We need to get the current relation from a volume to its instance, since we will recreate the attachment." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:645(para) +msgid "We need to update the database in order to clean the stalled state. (After that, we won't be able to perform the first step)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:649(para) +msgid "We need to restart the instances (so go from a \"shutdown\" to a \"running\" state)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:653(para) +msgid "After the restart, we can reattach the volumes to their respective instances." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:657(para) +msgid "That step, which is not a mandatory one, exists in an SSH into the instances in order to reboot them." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:664(title) +msgid "B - The Disaster Recovery Process itself" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:668(emphasis) +msgid "Instance to Volume relation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:671(para) +msgid "We need to get the current relation from a volume to its instance, since we will recreate the attachment :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:674(para) +msgid "This relation could be figured by running " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:680(emphasis) +msgid "Database Update" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:683(para) +msgid "Second, we need to update the database in order to clean the stalled state. Now that we have saved the attachments we need to restore for every volume, the database can be cleaned with the following queries: Now, when running all volumes should be available." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:700(emphasis) +msgid "Instances Restart" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:706(replaceable) +msgid "$instance" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:703(para) +msgid "We need to restart the instances. This can be done via a simple " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:708(para) +msgid "At that stage, depending on your image, some instances will completely reboot and become reachable, while others will stop on the \"plymouth\" stage." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:712(para) +msgid "DO NOT reboot a second time the ones which are stopped at that stage (see below, the fourth step). In fact it depends on whether you added an /etc/fstab entry for that volume or not. Images built with the cloud-init package will remain on a pending state, while others will skip the missing volume and start. (More information is available on help.ubuntu.com) But remember that the idea of that stage is only to ask nova to reboot every instance, so the stored state is preserved." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:732(emphasis) +msgid "Volume Attachment" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:735(para) +msgid "After the restart, we can reattach the volumes to their respective instances. Now that nova has restored the right status, it is time to perform the attachments via a " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:741(para) +msgid "Here is a simple snippet that uses the file we created : At that stage, instances which were pending on the boot sequence (plymouth) will automatically continue their boot, and restart normally, while the ones which booted will see the volume." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:763(emphasis) +msgid "SSH into instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:766(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 via nova. So, we SSH into the instance and perform a reboot : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:665(para) +msgid "Voila! You successfully recovered your cloud after that." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:779(para) +msgid "Here are some suggestions :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:782(para) +msgid "Use the parameter errors=remount in the fstab file, which will prevent data corruption." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:786(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 nova-volume server (the one which performs the ISCSI connection to the SAN), but also into the instances' fstab file." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:796(para) +msgid "Do not add the entry for the SAN's disks to the nova-volume's fstab file." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:799(para) +msgid "Some systems will hang on that step, which means you could lose access to your cloud-controller. In order to re-run the session manually, you would run the following command before performing the mount: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:810(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/src/docbkx/openstack-compute-admin/computeadmin.xml:818(para) +msgid "This will allow you to connect to the instance, even without the volume attached, if you allow only connections via public keys." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:827(title) +msgid "C- Scripted DRP" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:828(para) +msgid "You can download from here a bash script which performs these five steps :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:832(para) +msgid "The \"test mode\" allows you to perform that whole sequence for only one instance." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:834(para) +msgid "To reproduce the power loss, connect to the compute node which runs that same instance and close the iscsi session. Do not dettach the volume via , but instead manually close the iscsi session." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeadmin.xml:840(para) +msgid "In the following example, the iscsi session is number 15 for that instance : Do not forget the flag -r; otherwise, you will close ALL sessions." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:6(title) +msgid "Cells" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:8(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/src/docbkx/openstack-compute-admin/computecells.xml:12(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 a cells as a normal Compute deployment in tht each cell has its own database server and message queue broker." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:20(para) +msgid "The nova-cells service handles communication between cells and selecting a cell for new instances. This service is required for every cell. Communication between cells is pluggable, with the only option currently implemented being communication via RPC." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:24(para) +msgid "Cells scheduling is separate from host scheduling. nova-cells first picks a cell (currently randomly, future releases will add filtering/weighing functionality and decisions can be based on broadcasts of capacity/capabilities). Once a cell has been selected and the new build request has reached its nova-cells service, it will be sent over to the host scheduler in that cell and the build proceeds as it does without cells." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:30(para) +msgid "Cell functionality is currently considered experimental." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:33(title) +msgid "Cell configuration options" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:38(literal) +msgid "enable" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:40(para) +msgid "Set this is True to turn on cell functionality, which is off by default." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:45(literal) +msgid "name" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:47(para) +msgid "Name of the current cell. This must be unique for each cell." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:51(literal) +msgid "capabilities" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:53(para) +msgid "List of arbitrary key=value pairs defining capabilities of the current cell. These are sent to parent cells, but aren't used in scheduling until later filter/weight support is added." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:61(literal) +msgid "call_timeout" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:63(para) +msgid "How long to wait for replies from calls between cells." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:34(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/src/docbkx/openstack-compute-admin/computecells.xml:69(title) +msgid "Configuring the API (top-level) cell" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:70(para) +msgid "The compute API class must be changed in the API cell so that requests can be proxied via nova-cells down to the correct cell properly. Add the following to nova.conf in the API cell:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:82(title) +msgid "Configuring the child cells" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:91(replaceable) +msgid "cell1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:83(para) +msgid "Add the following to nova.conf in the child cells, replacing cell1 with the name of each cell:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:94(title) +msgid "Configuring the database in each cell" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:95(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 need to know about their immediate arents. The information needed is the RabbitMQ server credentials for the particular cell." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:100(para) +msgid "Use the command to add this informtion to the database in each cell:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:119(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/src/docbkx/openstack-compute-admin/computecells.xml:127(para) +msgid "And in the child cell named cell1 we have the following RabbitMQ server info:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:134(para) +msgid "We would run this in the API cell, as root." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:136(para) +msgid "Repeat the above for all child cells." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computecells.xml:137(para) +msgid "In the child cell, we would run the following, as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:6(title) +msgid "Instance Management" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:8(para) +msgid "Instances are the running virtual machines within an OpenStack cloud. The Images and Instances section of the Introduction to OpenStack Compute Chapter provides a high level overview of instances and their life cycle" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:15(para) +msgid "This chapter deals with the details of how to manage that life cycle" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:20(title) +msgid "Interfaces to managing instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:22(para) +msgid "OpenStack provides command line, web based, and API based instance management. Additionally a number of third party management tools are available for use with OpenStack using either the native API or the provided EC2 compatibility API." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:29(title) +msgid "Nova CLI" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:31(para) +msgid "The nova command provided by the OpenStack python-novaclient package is the basic command line utility for users interacting with OpenStack. This is available as a native package for most modern Linux distributions or the latest version can be installed directly using pip python package installer: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:42(para) +msgid "Full details for nova and other CLI tools are provided in the OpenStack CLI Guide. What follows is the minimal introduction required to follow the CLI example in this chapter. In the case of a conflict the OpenStack CLI Guide should be considered authoritative (and a bug filed against this section)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:53(para) +msgid "In order to function the nova CLI needs to know four things:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:58(para) +msgid "Authentication URL. This can be passed as the --os_auth_url flag or using the OS_AUTH_URL environment variable." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:63(para) +msgid "Tenant(sometimes referred to as project) name. This can be passed as the --os_tenant_name flag or using the OS_TENANT_NAME environment variable." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:69(para) +msgid "User name. This can be passed as the --os_username flag or using the OS_USERNAME environment variable." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:74(para) +msgid "Password. This can be passed as the --os_password flag or using the OS_PASSWORD environment variable." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:80(para) +msgid "For example if you have your Keytone identity management service running on the default port (5000) on host keystone.example.com and want to use the nova cli as the user \"demouser\" with the password \"demopassword\" in the \"demoproject\" tenant you can export the following values in your shell environment or pass the equivalent command line args (presuming these identities already exist):" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:97(para) +msgid "If you are using the Horizon web dashboard, users can easily download credential files like this with the correct values for your particular implementation." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:105(title) +msgid "Horizon web dashboard" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:106(para) +msgid "Horizon is the highly customizable and extensible OpenStack web dashboard. The Horizon Project home page has detailed information on deploying horizon." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:114(title) +msgid "Compute API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:115(para) +msgid "OpenStack provides a RESTful API for all functionality. Complete API documentation is available at at http://docs.openstack.org/api. The OpenStack Compute API documentation refers to instances as \"servers\"." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:121(para) +msgid "The nova cli can be made to show the API calls it is making by passing it the --debug flag " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:148(title) +msgid "EC2 Compatibility API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:150(para) +msgid "In addition to the native compute API OpenStack provides an EC2 compatible API. This allows legacy workflows built for EC2 to work with OpenStack." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:154(para) +msgid "Configuring the EC2 API lists configuration options for customizing this compatibility API on your OpenStack cloud." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:161(title) +msgid "Third Party Tools" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:163(para) +msgid "There are numerous third party tools and language specific SDKs for interacting with OpenStack clouds both through native and compatibility APIs. These are not OpenStack projects so we can only provide links to some of the more popular projects and a brief description. For detailed installation and usage info please see the individual project pages" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:174(para) +msgid "euca2ools is a popular open source CLI for interacting with the EC2 API. This is convenient for multi cloud environments where EC2 is the common API, or for transitioning from EC2 API based clouds to OpenStack." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:184(para) +msgid "hybridfox is a Firefox browser add-on that provides a graphical interface to many popular public and private cloud technologies." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:192(para) +msgid "boto is a Python library for interacting with Amazon Web Services. It can be used to access OpenStack through the EC2 compatibility API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:200(para) +msgid "fog is the Ruby cloud services library and provides methods for interacting with a large number of cloud and virtualization platforms." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:208(para) +msgid "heat is a high level orchestration system that provides a programmable interface to orchestrate multiple cloud applications implementing well known standards such as CloudFormation and TOSCA. Unlike other projects mentioned in this section heat requires changes to your OpenStack deployment and is working toward official inclusion as an OpenStack project. At this point heat is a development project not a production resource, but it does show what the not too distant future of instance management may be like." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:234(title) +msgid "Instance building blocks" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:236(para) +msgid "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\" may actually be \"software\" but conceptually you still need an operating system and something to run it on." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:244(title) +msgid "Images" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:245(para) +msgid "In OpenStack the base operating system is usually copied from an \"image\" stored in the Glance image service. This is the most common case and results in an ephemeral instance which starts from a know templated state and lose all accumulated state on shutdown. It is also possible in special cases 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 state which is preserved across restarts. To get a list of available images on your system run: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:272(para) +msgid "ID: the automatically generate UUID of the image" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:276(para) +msgid "Name: a free form human readable name given to the image" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:280(para) +msgid "Status: shows the status of the image ACTIVE images are available for use." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:285(para) +msgid "Server: for images that are created as snapshots of running instance this is the UUID of the instance the snapshot derives from, for uploaded images it is blank" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:270(para) +msgid "The displayed image attributes are " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:296(title) +msgid "Flavors" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:297(para) +msgid "Virtual hardware templates are called \"flavors\" in OpenStack. The default install provides a range of five flavors. These are configurable by admin users (this too is configurable and may be delegated by redefining the access controls for \"compute_extension:flavormanage\" in /etc/nova/policy.json on the compute-api server) . To get a list of available flavors on your system run: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:321(para) +msgid "The command allows authorized users to create new flavors. Additional flavor manipulation commands can be shown with the command " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:329(para) +msgid "ID: a unique numeric id" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:332(para) +msgid "Name: a descriptive name. xx.size_name is conventional not required, though some third party tools may rely on it." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:338(para) +msgid "Memory_MB: virtual machine memory in megabytes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:342(para) +msgid "Disk: virtual root disk size in gigabytes. This is an ephemeral disk the base image is copied into. When booting rom 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/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:354(para) +msgid "Ephemeral: 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/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:360(para) +msgid "Swap: optional swap space allocation for the instance" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:364(para) +msgid "VCPUs: number of virtual CPUs presented to the instance" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:368(para) +msgid "RXTX_Factor: 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/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:377(para) +msgid "Is_Public: Boolean value, whether flavor is available to all users or private to the tenant it was created in. Defaults to True." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:383(para) +msgid "extra_specs: additional optional restrictions on which compute nodes the flavor can run on. This is implemented as key/value pairs that must match against the corresponding key/value pairs on compute nodes. Can be used to implement things like special resources (e.g., flavors that can only run on compute nodes with GPU hardware)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:327(para) +msgid "Flavors define a number of elements " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:400(title) +msgid "Creating instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:406(title) +msgid "Controlling where instances run" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:407(para) +msgid "The scheduler filters section 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/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:415(para) +msgid "Additionally admin users can specify and exact compute node to run on by specifying --availability-zone <availibility-zone>:<compute-host> on the command line, for example to force an instance to launch on the nova-1 compute node in the default nova availability zone: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:426(title) +msgid "Instance specific data" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:427(para) +msgid "For each instance, you can specify certain data including authorized_keys key injection, user-data, metadata service, and file injection." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:441(title) +msgid "Managing instance networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:451(title) +msgid "Accessing running instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml:452(para) +msgid "The most common access method for running instances is probably ssh, but this requires you have setup your instance with ssh keys and you have arranged for it to be running ssh with a public ip and opened the ssh port in your security group configuration. If you haven;t done this or you are trying to debug a problem image OpenStack can be configured to provide a VNC console, be aware that VNC is an unencrypted protocol so you should be cautious what you type across that link, see Getting Started With VNC Proxy section for details on how to configure and connect to this service." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:6(title) +msgid "OpenStack Compute Tutorials" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:7(para) +msgid "We want OpenStack to make sense, and sometimes the best way to make sense of the cloud is to try out some basic ideas with cloud computing. Flexible, elastic, and scalable are a few attributes of cloud computing, so these tutorials show various ways to use virtual computing or web-based storage with OpenStack components." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:9(title) +msgid "Running Your First Elastic Web Application on the Cloud" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:11(para) +msgid "In this OpenStack Compute tutorial, we’ll walk through the creation of an elastic, scalable cloud running a WordPress installation on a few virtual machines." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:14(para) +msgid "The tutorial assumes you have obtained a TryStack account at http://trystack.org. It has a working installation of OpenStack Compute, or you can install your own using the installation guides." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:18(para) +msgid "We'll go through this tutorial in parts:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:21(para) +msgid "Setting up a user on the TryStack cloud." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:23(para) +msgid "Getting images for your application servers." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:25(para) +msgid "On the instances you spin up, installing Wordpress and its dependencies, the Memcached plugin, and multiple memcache servers." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:29(title) +msgid "Part I: Setting Up as a TryStack User" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:30(para) +msgid "In this part, we'll get a TryStack account using our Facebook login. Onward, brave cloud pioneers!" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:32(para) +msgid "Go to the TryStack Facebook account at https://www.facebook.com/groups/269238013145112/ and request to join the group." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:36(para) +msgid "Once you've joined the group, go to the TryStack dashboard and click Login using Facebook." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:39(para) +msgid "Enter your Facebook login information to receive your username and password that you can use with the Compute API." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:42(para) +msgid "Next, install the python-novaclient and set up your environment variables so you can use the client with your username and password already entered. Here's what works well on Mac OS X. Next, create a file named openrc to contain your TryStack credentials, such as: Lastly, run this file to source your credentials. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:60(para) +msgid "You can always retrieve your username and password from https://trystack.org/dash/api_info/ after logging in with Facebook." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:65(para) +msgid "Okay, you've created the basic scaffolding for your cloud user so that you can get some images and run instances on TryStack with your starter set of StackDollars. You're rich, man! Now to Part II!" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:72(title) +msgid "Part II: Starting Virtual Machines" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:73(para) +msgid "Understanding what you can do with cloud computing means you should have a grasp on the concept of virtualization. With virtualization, you can run operating systems and applications on virtual machines instead of physical computers. To use a virtual machine, you must have an image that contains all the information about which operating system to run, the user login and password, files stored on the system, and so on. Fortunately, TryStack provides images for your use." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:83(para) +msgid "Basically, run:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:89(para) +msgid "and look for the images available in the text that returns. Look for the ID value." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:101(para) +msgid "Now get a list of the flavors you can launch:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:107(para) +msgid "Create a keypair to launch the image, in a directory where you run the nova boot command later. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:123(para) +msgid "Create security group that enables public IP access for the webserver that will run WordPress for you. You can also enable port 22 for SSH." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:130(para) +msgid "Next, with the ID value of the server you want to launch and the ID of the flavor you want to launch, use your credentials to start up the instance with the identifier you got by looking at the image list." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:136(para) +msgid "Now you can look at the state of the running instances by using nova list. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:169(para) +msgid "The instance goes from “launching” to “running” in a short time, and you should be able to connect via SSH. Look at the IP addresses so that you can connect to the instance once it starts running." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:175(title) +msgid "Diagnose your compute node" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:177(para) +msgid "You can obtain extra informations about the instance you just spawned : its CPU usage, the memory, the disk io or network io, per instance, by running the command: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:212(title) +msgid "Part III: Installing the Needed Software for the Web-Scale Scenario" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:213(para) +msgid "Basically launch a terminal window from any computer, and enter:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:217(para) +msgid "On this particular image, the 'ubuntu' user has been set up as part of the sudoers group, so you can escalate to 'root' via the following command:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:223(title) +msgid "On the first VM, install WordPress" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:224(para) +msgid "Now, you can install WordPress. Create and then switch to a blog directory:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:230(para) +msgid "Download WordPress directly to you by using wget:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:234(para) +msgid "Then unzip the package using:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:238(para) +msgid "The WordPress package will extract into a folder called wordpress in the same directory that you downloaded latest.tar.gz." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:240(para) +msgid "Next, enter \"exit\" and disconnect from this SSH session." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:243(title) +msgid "On a second VM, install MySQL" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:244(para) +msgid "Next, SSH into another virtual machine and install MySQL and use these instructions to install the WordPress database using the MySQL Client from a command line: Using the MySQL Client - Wordpress Codex." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:250(title) +msgid "On a third VM, install Memcache" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:250(para) +msgid "Memcache makes Wordpress database reads and writers more efficient, so your virtual servers can go to work for you in a scalable manner. SSH to a third virtual machine and install Memcache:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:257(title) +msgid "Configure the Wordpress Memcache plugin" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:257(para) +msgid "From a web browser, point to the IP address of your Wordpress server. Download and install the Memcache Plugin. Enter the IP address of your Memcache server." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:259(title) +msgid "Running a Blog in the Cloud" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computetutorials.xml:259(para) +msgid "That's it! You're now running your blog on a cloud server in OpenStack Compute, and you've scaled it horizontally using additional virtual images to run the database and Memcache. Now if your blog gets a big boost of comments, you'll be ready for the extra reads-and-writes to the database." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:26(title) +msgid "OpenStack Compute Automated Installations" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:27(para) +msgid "In a large-scale cloud deployment, automated installations are a requirement for successful, efficient, repeatable installations. Automation for installation also helps with continuous integration and testing. This chapter offers some tested methods for deploying OpenStack Compute with either Puppet (an infrastructure management platform) or Chef (an infrastructure management framework) paired with Vagrant (a tool for building and distributing virtualized development environments)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:35(title) +msgid "Deployment Tool for OpenStack using Puppet (dodai-deploy)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:37(para) +msgid "The dodai-deploy is a software management tool. It supports the following softwares." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:41(para) +msgid "OpenStack Folsom(Compute, Glance, Swift, Keystone). Compute includes Nova, Horizon, Cinder and Quantum." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:44(para) ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:95(para) +msgid "hadoop 0.22.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:47(para) ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:102(para) +msgid "sun grid engine 6.2u5" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:51(title) +msgid "Features" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:54(para) +msgid "Manage installation, uninstallation and testing of a software." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:57(para) +msgid "Support deployment on multiple machines." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:60(para) +msgid "Support target machines in different network segments." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:63(para) +msgid "Provide web UI to facilitate user operations." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:66(para) +msgid "Provide REST API to make it possible to integrate it with other tools." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:69(para) +msgid "Support parallel installation of software components." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:74(title) ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:76(caption) +msgid "OSes supported" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:80(para) +msgid "ubuntu 10.10" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:81(para) +msgid "ubuntu 11.04" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:82(para) +msgid "ubuntu 11.10" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:83(para) +msgid "ubuntu 12.04" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:88(para) +msgid "OpenStack Folsom (Compute, Glance, Swift, Keystone)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:92(para) ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:96(para) ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:97(para) ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:98(para) ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:103(para) ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:104(para) ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:105(para) +msgid ":)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:113(title) +msgid "Glossary" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:116(para) +msgid "dodai-deploy server - The server in which services of dodai-deploy is started." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:119(para) +msgid "Node - The machine that is the target of installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:122(para) +msgid "Nova, Glance, Swift etc." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:124(para) +msgid "Proposal - The set of the kinds of configurations which describe how to install a software. The configurations include \"Node config\", \"Config item\", \"Software config\", \"Component config\"." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:126(para) +msgid "Node config - A configuration that describes which component to be installed on a node." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:129(para) +msgid "Config item - A variable which can be used in the content of software config and component config." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:132(para) +msgid "Software config - A configuration that describes the content of a configuration file for all components." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:135(para) +msgid "Component config - A configuration that describes the content of a configuration file for only one component." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:139(title) +msgid "Installation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:140(para) +msgid "The $home in the following sections is the path of the home directory of the dodai-deploy." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:146(para) +msgid "Download dodai-deploy." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:147(para) +msgid "Execute the following commands on the dodai-deploy server and all the nodes. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:156(para) +msgid "Set up the dodai-deploy server." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:157(para) +msgid "Execute the following commands on dodai-deploy server to install necessary softwares and modify their settings." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:166(para) +msgid "Set up nodes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:167(para) +msgid "Execute the following commands on all the nodes to install necessary softwares and modify their settings." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:173(para) +msgid "The $server in the above command is the fully qualified domain name (fqdn) of the dodai-deploy server. You can confirm the fqdn with the following command." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:177(para) +msgid "After nodes were set up, the system time of nodes should be synchronized with dodai-deploy server." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:179(para) +msgid "Set up storage device for Swift." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:180(para) +msgid "You must set up a storage device before swift is installed. You should execute the commands for a physical device or for a loopback device on all nodes in which swift storage server is to be installed." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:188(para) ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:223(para) +msgid "For a physical device, use the following command." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:193(para) ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:204(para) ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:228(para) ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:239(para) +msgid "For example," +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:199(para) ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:234(para) +msgid "For a loopback device, use the following command." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:214(para) +msgid "Create volume group for nova-volume." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:215(para) +msgid "You must create a volume group before nova-volume is installed. You should execute the commands for a physical device or for a loopback device on the node in which nova-volume is to be installed." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:249(para) +msgid "Start servers." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:250(para) +msgid "Execute the following command on the dodai-deploy server to start the web server and job server." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:254(para) +msgid "You can stop the web server and job server with the following command." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:262(title) +msgid "Using web UI" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:263(para) +msgid "You can find step-by-step guidance at http://$dodai_deploy_server:3000/." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:265(title) +msgid "Using REST APIs" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:266(para) +msgid "An API simulator can be found at http://$dodai_deploy_server:3000/rest_apis/index.html. You can get the list of REST APIs with it. You can also execute APIs by simply filling in parameters and clicking the \"Execute\" button." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:272(title) +msgid "Notes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:275(para) +msgid "SSH login nova instance after test of nova" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:276(para) +msgid "An instance will be started during the test of nova. After the test, you can login the instance by executing the following commands." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:278(para) +msgid "For openstack nova folsom," +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:288(para) +msgid "Glance should be installed before using nova, because nova depends on glance in default settings." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:291(para) +msgid "In /etc/nova/nova.conf the value of setting image_service is nova.image.glance.GlanceImageService." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:297(para) +msgid "Change Linux's setting net.ipv4.ip_forward to 1 in the machine where nova-network will be installed before nova installation with the following command." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeautomation.xml:306(para) +msgid "You can recover the setting with the following command." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:63(None) +msgid "@@image: 'figures/NOVA_install_arch.png'; md5=0f72da9079e5e0516ac664d2e4a15910" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:80(None) +msgid "@@image: 'figures/NOVA_compute_nodes.png'; md5=bc6a5eb2b9358d000d96f274800752aa" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:96(None) +msgid "@@image: 'figures/NOVA_ARCH.png'; md5=d44c02f6f2e523d621993bdbf80b5bb1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:10(title) +msgid "Installing OpenStack Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:12(para) +msgid "The OpenStack system has several key projects that are separate installations but can work together depending on your cloud needs: OpenStack Compute, OpenStack Block Storage, OpenStack Object Storage, and the OpenStack Image Service. You can install any of these projects separately and then configure them either as standalone or connected entities." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:21(title) +msgid "Example Installation Architectures" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:23(para) +msgid "OpenStack Compute uses a shared-nothing, messaging-based architecture. While very flexible, the fact that you can install each nova- service on an independent server means there are many possible methods for installing OpenStack Compute. Here are the types of installation architectures:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:31(para) +msgid "Single node: Only one server runs all nova- services and also drives all the virtual instances. Use this configuration only for trying out OpenStack Compute, or for development purposes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:37(para) +msgid "Two nodes: A cloud controller node runs the nova- services except for , and a compute node runs . A client computer is likely needed to bundle images and interfacing to the servers, but a client is not required. Use this configuration for proof of concepts or development environments." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:46(para) +msgid "Multiple nodes: You can add more compute nodes to the two node installation by simply installing on an additional server and copying a nova.conf file to the added node. This would result in a multiple node installation. You can also add a volume controller and a network controller as additional nodes in a more complex multiple node installation. A minimum of 4 nodes is best for running multiple virtual instances that require a lot of processing power." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:57(para) +msgid "This is an illustration of one possible multiple server installation of OpenStack Compute; virtual server networking in the cluster may vary." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:67(para) +msgid "An alternative architecture would be to add more messaging servers if you notice a lot of back up in the messaging queue causing performance problems. In that case you would add an additional RabbitMQ server in addition to or instead of scaling up the database server. Your installation can run any nova- service on any server as long as the nova.conf is configured to point to the RabbitMQ server and the server can send messages to the server." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:75(para) +msgid "Multiple installation architectures are possible, here is another example illustration." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:88(title) +msgid "Service Architecture" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:90(para) +msgid "Because Compute has multiple services and many configurations are possible, here is a diagram showing the overall service architecture and communication systems between the services." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:102(title) +msgid "Installing OpenStack Compute on Debian" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:103(para) +msgid "Starting with Debian 7.0 \"Wheezy\", the OpenStack packages are provided as part of the distribution." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:109(literal) ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:125(literal) +msgid "nova-api" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:110(literal) +msgid "nova-scheduler" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:111(literal) +msgid "glance" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:112(literal) +msgid "keystone" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:113(literal) +msgid "mysql-server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:114(literal) +msgid "rabbitmq" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:115(literal) +msgid "memcached" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:116(literal) +msgid "openstack-dashboard" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:105(para) +msgid "For the management or controller node install the following packages: (via ) " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:123(literal) +msgid "nova-compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:124(literal) +msgid "nova-network" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:120(para) +msgid "For the compute node(s) install the following packages: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:129(para) +msgid "Because this manual takes active advantage of the \"sudo\" command, it would be easier for you to add to it your Debian system, by doing:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:135(para) +msgid "then re-login. Otherwise you will have to replace every \"\" call by executing from root account." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:143(title) +msgid "Installing on Fedora or Red Hat Enterprise Linux 6" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:145(para) +msgid "The Fedora project provides OpenStack packages in Fedora 16 and later. Fedora also provides packages for RHEL6 via the EPEL (Extra Packages for Enterprise Linux) 6 repository. If you would like to install OpenStack on RHEL6, see this page for more information on enabling the use of EPEL: http://fedoraproject.org/wiki/EPEL." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:152(para) +msgid "Detailed instructions for installing OpenStack Compute on Fedora or RHEL6 can be found in the OpenStack Install and Deploy Manual - Red Hat." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:156(para) +msgid "Here is a listing of known installation guides:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:160(term) +msgid "OpenStack Install and Deploy Manual - Red Hat (Grizzly)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:165(para) +msgid "This guide walks through an installation using packages available through Fedora 17 as well as on RHEL and derivatives through the EPEL repository. It offers explanations for the configuration choices as well as sample configuration files." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:173(term) +msgid "Getting Started with OpenStack on Fedora 18 (Folsom)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:179(para) +msgid "The Folsom release is in Fedora 18. This page discusses the installation of Folsom on Fedora 18. Once EPEL 6 has been updated to include Folsom, these instructions should be used if installing on RHEL 6. The main difference between the Fedora 18 instructions and what must be done on RHEL 6 is that RHEL 6 does not use systemd, so the commands will have to substituted with the RHEL 6 equivalent." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:193(title) +msgid "Installing on openSUSE or SUSE Linux Enterprise Server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:195(para) +msgid "B1 Systems GmbH provides packages for openSUSE 12.2 and SUSE Linux Enterprise Server 11 SP2 on the openSUSE Open Build Server." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:200(para) +msgid "For the Folsom release you can find the packages in the project isv:B1-Systems:OpenStack:release:Folsom." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:205(title) +msgid "SUSE Linux Enterprise Server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:206(para) ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:260(para) +msgid "First of all you have to import the signing key of the repository. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:212(para) ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:266(para) +msgid "Now you can declare the repository to libzypp with . " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:225(para) ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:279(para) +msgid "After declaring the repository you have to update the metadata with . " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:235(para) ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:289(para) +msgid "You can list all available packages for OpenStack with . You can install packages with ." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:240(para) +msgid "You have to apply the latest available updates for SLES11 SP2. Without doing that it's not possible to run OpenStack on SLES11 SP2. For evaluation purposes you can request a free 60 day evaluation for SLES11 SP2 to gain updates." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:247(para) +msgid "To verify that you use the correct Python interpreter simply check the version. You should use at least Python 2.6.8. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:259(title) +msgid "openSUSE" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:296(title) +msgid "Installing on Ubuntu" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:298(para) +msgid "How you go about installing OpenStack Compute depends on your goals for the installation. You can use an ISO image, you can use a scripted installation, and you can manually install with a step-by-step installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:304(title) +msgid "ISO Installation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:306(para) +msgid "See Installing Rackspace Private Cloud on Physical Hardware for download links and instructions for the Rackspace Private Cloud ISO. For documentation on the Rackspace, see http://www.rackspace.com/cloud/private." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:315(title) +msgid "Scripted Installation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:317(para) +msgid "You can download a script for a standalone install for proof-of-concept, learning, or for development purposes for Ubuntu 12.04 at https://devstack.org." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:324(para) +msgid "Install Ubuntu 12.04 or RHEL/CentOS/Fedora 16:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:326(para) +msgid "In order to correctly install all the dependencies, we assume a specific version of the OS to make it as easy as possible." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:331(para) +msgid "Download DevStack:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:335(para) +msgid "The devstack repo contains a script that installs OpenStack Compute, Object Storage, the Image Service, Volumes, the Dashboard and the Identity Service and offers templates for configuration files plus data scripts." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:341(para) +msgid "Start the install:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:345(para) +msgid "It takes a few minutes, we recommend reading the well-documented script while it is building to learn more about what is going on." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:354(title) +msgid "Manual Installation on Ubuntu" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:356(para) +msgid "The manual installation involves installing from packages shipped on Ubuntu 12.04 as a user with root (or sudo) permission. The OpenStack Install and Deploy Manuals provide instructions for installing using Ubuntu 12.04 packages. Refer to those manuals for detailed instructions by going to http://docs.openstack.org and clicking the links next to the manual title." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:370(title) +msgid "Installing on Citrix XenServer" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:372(para) +msgid "When using OpenStack Compute with Citrix XenServer or XCP hypervisor, OpenStack Compute should be installed in a virtual machine running on your hypervisor, rather than installed directly on the hypervisor, as you would do when using the Libvirt driver. For more information see: XenAPI Install." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:380(para) +msgid "Given how you should deploy OpenStack with XenServer, the first step when setting up the compute nodes in your OpenStack cloud is to install XenServer and install the required XenServer plugins. You can install XCP by installing Debian or Ubuntu, but generally rather than installing the operating system of your choice on your compute nodes, you should first install XenServer. For more information see: XenAPI Deployment Architecture." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinstall.xml:391(para) +msgid "Once you have installed XenServer and the XenAPI plugins on all your compute nodes, you next need to create a virtual machine on each of those compute nodes. This must be a Linux virtual machine running in para-virtualized mode. It is inside each of these VMs that you will run the OpenStack components. You can follow the previous distribution specific instructions to get the OpenStack code running in your Virtual Machine. Once installed, you will need to configure OpenStack Compute to talk to your XenServer or XCP installation. For more information see: Introduction to Xen." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:6(title) +msgid "Introdution to the OpenStack Image Service" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:7(para) +msgid "You can use OpenStack Image Services for discovering, registering, and retrieving virtual machine images. The service includes a RESTful API that allows users to query VM image metadata and retrieve the actual image with HTTP requests, or you can use a client class in your Python code to accomplish the same tasks." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:8(para) +msgid "VM images made available through OpenStack Image Service can be stored in a variety of locations from simple file systems to object-storage systems like the OpenStack Object Storage project, or even use S3 storage either on its own or through an OpenStack Object Storage S3 interface." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:12(title) +msgid "Overview of Architecture" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:13(para) +msgid "There are two main parts to the Image Service’s architecture:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:15(para) +msgid "API server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:16(para) +msgid "Registry server(s)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:20(para) +msgid "OpenStack Image Service is designed to be as adaptable as possible for various back-end storage and registry database solutions. There is a main API server (the ``glance-api`` program) that serves as the communications hub betweenvarious client programs, the registry of image metadata, and the storage systems that actually contain the virtual machine image data." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:24(title) +msgid "OpenStack Image Service API Server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:26(para) +msgid "The API server is the main interface for OpenStack Image Service. It routes requests from clients to registries of image metadata and to its backend stores, which are the mechanisms by which OpenStack Image Service actually saves incoming virtual machine images." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:28(para) +msgid "The backend stores that OpenStack Image Service can work with are as follows:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:29(para) +msgid "OpenStack Object Storage - OpenStack Object Storage is the highly-available object storage project in OpenStack." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:31(para) +msgid "Filesystem - The default backend that OpenStack Image Service uses to store virtual machine images is the filesystem backend. This simple backend writes image files to the local filesystem." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:33(para) +msgid "S3 - This backend allows OpenStack Image Service to store virtual machine images in Amazon’s S3 service." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:35(para) +msgid "HTTP - OpenStack Image Service can read virtual machine images that are available via HTTP somewhere on the Internet. This store is readonly." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:40(title) +msgid "OpenStack Image Service Registry Servers" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/aboutimages.xml:42(para) +msgid "OpenStack Image Service registry servers are servers that conform to the OpenStack Image Service Registry API. OpenStack Image Service ships with a reference implementation of a registry server that complies with this API (bin/OpenStack Image Service-registry)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computesecurity.xml:10(title) +msgid "Security Hardening" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computesecurity.xml:11(para) +msgid "OpenStack Compute can be integrated with variously third-party technologies to increase security." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:6(title) +msgid "Install nova-volume on the cloud controller" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:7(para) +msgid "While nova-volume does not directly use the network, you must have networking set up for Compute prior to configuring the volumes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:8(para) +msgid "On Ubuntu, install nova-volume and lvm2." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:12(para) +msgid "On RHEL and derivatives, the nova-volume service should already be installed." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:19(emphasis) +msgid "Configure Volumes for use with nova-volume" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:32(para) +msgid "Press to create a new disk partition," +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:37(para) +msgid "Press to create a primary disk partition," +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:42(para) +msgid "Press to denote it as 1st disk partition," +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:47(para) +msgid "Either press ENTER twice to accept the default of 1st and last cylinder – to convert the remainder of hard disk to a single disk partition -OR- press ENTER once to accept the default of the 1st, and then choose how big you want the partition to be by specifying +size[K,M,G] e.g. +5G or +6700M." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:59(para) +msgid "Press and select the new partition that you have created." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:64(para) +msgid "Press change your new partition to 8e, i.e. Linux LVM partition type." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:70(para) +msgid "Press to display the hard disk partition setup. Please take note that the first partition is denoted as /dev/sda1 in Linux." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:78(para) ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:181(para) +msgid "Press to write the partition table and exit fdisk upon completion." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:81(para) +msgid "Refresh your partition table to ensure your new partition shows up, and verify with . We then inform the OS about the table partition update :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:91(para) +msgid "You should see your new partition in this listing." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:93(para) +msgid "Here is how you can set up partitioning during the OS install to prepare for this nova-volume configuration:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:109(emphasis) +msgid "/dev/sda5 24328 32352 64452608 8e Linux LVM" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:110(emphasis) +msgid "/dev/sda6 32352 40497 65428480 8e Linux LVM" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:115(para) +msgid "Now that you have identified a partition has been labeled for LVM use, perform the following steps to configure LVM and prepare it as nova-volumes. You must name your volume group ‘nova-volumes’ or things will not work as expected:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/install-nova-volume.xml:21(para) +msgid "The openstack-nova-volume service requires an LVM Volume Group called nova-volumes to exist. If you do not already have LVM volumes on hand, but have free drive space, you will need to create a LVM volume before proceeding. Here is a short run down of how you would create a LVM from free drive space on your system. Start off by issuing an fdisk command to your drive with the free space: Once in fdisk, perform the following commands: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:7(title) +msgid "Configuring nova-volume on the compute nodes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:9(para) +msgid "Since you have created the volume group, you will be able to use the following tools for managing your volumes:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:12(simpara) +msgid "nova volume-create" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:13(simpara) +msgid "nova volume-attach" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:14(simpara) +msgid "nova volume-detach" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:15(simpara) +msgid "nova volume-delete" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:16(para) +msgid "If you are using KVM as your hypervisor, then the actual device name in the guest will be different than the one specified in the nova volume-attach command. You can specify a device name to the KVM hypervisor, but the actual means of attaching to the guest is over a virtual PCI bus. When the guest sees a new device on the PCI bus, it picks the next available name (which in most cases is /dev/vdc) and the disk shows up there on the guest." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:26(emphasis) +msgid "Installing and configuring the iSCSI initiator" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:28(para) +msgid "Remember that every node will act as the iSCSI initiator while the server running nova-volumes will act as the iSCSI target. So make sure, before going further that your nodes can communicate with you nova-volumes server. If you have a firewall running on it, make sure that the port 3260 (tcp) accepts incoming connections." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:33(para) +msgid "First install the open-iscsi package on the initiators, so on the compute-nodes only" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:38(para) +msgid "Then run on the nova-controller (iscsi target), start tgt, which is installed as a dependency of the volume package:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:44(para) +msgid "And on the compute-nodes (iscsi initiators) :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:51(emphasis) +msgid "Start nova-volume and create volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:52(para) +msgid "You are now ready to fire up nova-volume, and start creating volumes!" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:58(para) +msgid "Once the service is started, login to your controller and ensure you’ve properly sourced your ‘novarc’ file." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:60(para) +msgid "One of the first things you should do is make sure that nova-volume is checking in as expected. You can do so using nova-manage:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:67(para) +msgid "If you see a smiling ‘nova-volume’ in there, you are looking good. Now create a new volume:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:69(para) +msgid " --display_name sets a readable name for the volume, while the final argument refers to the size of the volume in GB." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:75(para) +msgid "You should get some output similar to this:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:85(para) +msgid "You can view that status of the volumes creation using . Once that status is ‘available,’ it is ready to be attached to an instance:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:88(para) +msgid " The first argument refers to the instance you will attach the volume to; the second is the volume ID; The third is the mountpoint on the compute-node that the volume will be attached to. Compute generates a non-conflicting device name if one is not passed to attach_volume and ensures that the volume name isn't already attached there." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:99(para) +msgid "By doing that, the compute-node which runs the instance basically performs an iSCSI connection and creates a session. You can ensure that the session has been created by running :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:105(para) +msgid "Which should output :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:110(para) +msgid "If you do not get any errors, you can login to the instance and see if the new space is there. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:113(emphasis) +msgid "KVM changes the device name, since it's not considered to be the same type of device as the instances uses as it's local one, you will find the nova-volume will be designated as \"/dev/vdX\" devices, while local are named \"/dev/sdX\"." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:117(para) +msgid "You can check the volume attachment by running :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:118(para) +msgid " You should from there see a new disk. Here is the output from :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:131(emphasis) +msgid "Disk /dev/vdb: 21.5 GB, 21474836480 bytes <—–Here is our new volume!" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:137(para) +msgid "Now with the space presented, let’s configure it for use:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:145(para) +msgid "Press to create a new disk partition." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:149(para) +msgid "Press to create a primary disk partition." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:153(para) +msgid "Press to designated it as the first disk partition." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:158(para) +msgid "Press ENTER twice to accept the default of first and last cylinder – to convert the remainder of hard disk to a single disk partition." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:164(para) +msgid "Press , then select the new partition you made." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:169(para) +msgid "Press change your new partition to 83, i.e. Linux partition type." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:174(para) +msgid "Press to display the hard disk partition setup. Please take note that the first partition is denoted as /dev/vda1 in your instance." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:186(para) +msgid "Lastly, make a file system on the partition and mount it. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/configure-nova-volume.xml:195(para) +msgid "Your new volume has now been successfully mounted, and is ready for use! The commands are pretty self-explanatory, so play around with them and create new volumes, tear them down, attach and reattach, and so on." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:10(title) +msgid "OpenStack Compute Administration Manual" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:18(orgname) +msgid "OpenStack" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:22(year) +msgid "2010" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:23(year) +msgid "2011" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:24(year) +msgid "2012" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:25(year) +msgid "2013" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:26(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:28(releaseinfo) +msgid "current" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:29(productname) +msgid "OpenStack Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:30(pubdate) +msgid "2012-12-18" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:33(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:38(remark) +msgid "Remaining licensing details are filled in by the template." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:42(para) +msgid "OpenStack™ Compute offers open source software for cloud administration and management for any organization. This manual provides guidance for installing, managing, and understanding the software that runs OpenStack Compute." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:48(date) +msgid "2013-02-19" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:52(para) +msgid "Adds SPICE HTML5 information for remote access to server instances." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:58(date) +msgid "2012-11-09" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:62(para) +msgid "Folsom release of this document." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:65(para) +msgid "Adds Cinder Volume service configuration and troubleshooting information." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:71(date) +msgid "2012-09-18" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:75(para) +msgid "Adds Hyper-V configuration information." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:81(date) +msgid "2012-09-17" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:85(para) +msgid "Adds updates to filter information, networking documentation, storage sections, nova-manage, configuration options and other various doc improvements." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:95(date) +msgid "2012-08-01" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:99(para) +msgid "Adds QEMU information, XenAPI information, EC2 API configuration, rootwrap configuration, updates to cloudpipe information, dnsmasq information, expands network troubleshooting, and other various doc improvements." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:111(date) +msgid "2012-05-03" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:115(para) +msgid "Begin trunk designation." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:121(date) +msgid "2012-05-02" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:125(para) +msgid "Essex release." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:131(date) +msgid "2012-05-01" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:135(para) +msgid "Fixed PDF link." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:141(date) +msgid "2012-04-25" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:145(para) +msgid "Adds listing of all 467 configuration options in a new chapter." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:153(date) +msgid "2012-03-20" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:157(para) +msgid "Large reorganization, moving identity and image service administration as chapters in this book." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:163(date) +msgid "2011-11-15" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:167(para) +msgid "Added RSS feed and PDF link to header." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:173(date) +msgid "2011-11-09" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:176(para) +msgid "Updates for auth section regarding EC2 creds and drafted info about IP address association." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml:178(para) +msgid "Compute conceptual info on projects and quotas and RBAC updated to describe deprecated auth vs identity service concepts." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-options-reference.xml:6(title) +msgid "Configuration: nova.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-options-reference.xml:12(title) +msgid "List of configuration options" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/compute-options-reference.xml:13(para) +msgid "For a complete list of all available configuration options for each OpenStack Compute service, run bin/nova-<servicename> --help." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinterfaces.xml:7(title) +msgid "OpenStack Interfaces" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeinterfaces.xml:8(para) +msgid "OpenStack has components that provide a view of the OpenStack installation such as a Django-built website that serves as a dashboard and the ability to connect to running instances using a VNC connection via a VNC Proxy." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/remote-console-access.xml:7(title) +msgid "Remote Console Access" +msgstr "" + +#. +#: ./doc/src/docbkx/openstack-compute-admin/remote-console-access.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 "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:439(None) +msgid "@@image: '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/src/docbkx/openstack-compute-admin/computeconfigure.xml:482(None) +msgid "@@image: 'figures/SCH_5005_V00_NUAC-Network_mode_XEN_Flat_OpenStack.png'; md5=3b151435a0fda3702d4fac5a964fac83" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1082(None) +msgid "@@image: 'figures/moosefs/SCH_5008_V00_NUAC-MooseFS_OpenStack.png'; md5=236a5259962709793569a77e6fa27017" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:10(title) +msgid "Configuring OpenStack Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:12(para) +msgid "The OpenStack system has several key projects that are separate installations but can work together depending on your cloud needs: OpenStack Compute, OpenStack Object Storage, and OpenStack Image Store. There are basic configuration decisions to make, and the OpenStack Install Guide covers a basic walkthrough." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:20(title) +msgid "Post-Installation Configuration for OpenStack Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:22(para) +msgid "Configuring your Compute installation involves many configuration files - the nova.conf file, the api-paste.ini file, and related Image and Identity management configuration files. This section contains the basics for a simple multi-node installation, but Compute can be configured many ways. You can find networking options and hypervisor options described in separate chapters." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:31(title) +msgid "Setting Configuration Options in the nova.conf File" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:34(para) +msgid "The configuration file nova.conf is installed in /etc/nova by default. A default set of options are already configured in nova.conf when you install manually." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:39(para) +msgid "Starting with the default file, you must define the following required items in /etc/nova/nova.conf. The options are described below. You can place comments in the nova.conf file by entering a new line with a # sign at the beginning of the line. To see a listing of all possible configuration options, refer to the Compute Options Reference." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:48(para) +msgid "Here is a simple example nova.conf file for a small private cloud, with all the 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 rabbit installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:64(para) +msgid "If your OpenStack deployment uses Qpid as the message queue instead of RabbitMQ (e.g., on Fedora, CentOS, RHEL), you would see qpid_hostname instead of rabbit_host in the nova.conf file." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:69(para) +msgid "Create a nova group, so you can set permissions on the configuration file:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:74(para) +msgid "The nova.config file should have its owner set to root:nova, and mode set to 0640, since the file could contain your MySQL server’s username and password. You also want to ensure that the nova user belongs to the nova group." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:82(option) +msgid "username" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:87(title) +msgid "Setting Up OpenStack Compute Environment on the Compute Node" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:90(para) +msgid "These are the commands you run to ensure the database schema is current:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:94(para) +msgid "You also need to populate the database with the network configuration information that Compute obtains from the nova.conf file." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:96(replaceable) +msgid "<network-label> <project-network> <number-of-networks-in-project> <addresses-in-each-network>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:99(para) +msgid "Here is an example of what this looks like with real values entered:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:105(para) +msgid "For this example, the number of IPs is /24 since that falls inside the /16 range that was set in fixed-range in nova.conf. Currently, there can only be one network, and this set up would use the max IPs available in a /24. You can choose values that let you use any valid amount that you would like." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:112(para) +msgid "The service assumes that the first IP address is your network (like 192.168.0.0), that the 2nd IP is your gateway (192.168.0.1), and that the broadcast is the very last IP in the range you defined (192.168.0.255). If this is not the case you will need to manually edit the sql db networks table." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:118(para) +msgid "When you run the command, entries are made in the networks and fixed_ips tables. However, one of the networks listed in the networks table needs to be marked as bridge in order for the code to know that a bridge exists. The network in the Nova networks table is marked as bridged automatically for Flat Manager." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:126(title) +msgid "Creating Credentials" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:127(para) +msgid "The credentials you will use to launch instances, bundle images, and all the other assorted API functions can be sourced in a single file, such as creating one called /creds/openrc." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:131(para) +msgid "Here's an example openrc file you can download from the Dashboard in Settings > Project Settings > Download RC File." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:149(para) +msgid "You also may want to enable EC2 access for the euca2ools. Here is an example ec2rc file for enabling EC2 access with the required credentials." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:167(para) +msgid "Lastly, here is an example openrc file that works with nova client and ec2 tools." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:184(para) +msgid "Next, add these credentials to your environment prior to running any nova client commands or nova commands." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:191(title) +msgid "Creating Certificates" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:192(para) +msgid "You can create certificates contained within pem files using these nova client commands, ensuring you have set up your environment variables for the nova client: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:201(title) +msgid "Enabling Access to VMs on the Compute Node" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:203(para) +msgid "One of the most commonly missed configuration areas is not allowing the proper access to VMs. Use nova client commands to enable access. Below, you will find the commands to allow and to your VMs :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:209(para) +msgid "These commands need to be run as root only if the credentials used to interact with have been put under /root/.bashrc. If the EC2 credentials have been put into another user's .bashrc file, then, it is necessary to run these commands as the user." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:219(para) +msgid "Another common issue is you cannot ping or SSH to your instances after issuing the commands. Something to look at is the amount of processes that are running. If you have a running instance, check to see that TWO processes are running. If not, perform the following:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:229(para) +msgid "If you get the instance not found message while performing the restart, that means the service was not previously running. You simply need to start it instead of restarting it:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:237(title) +msgid "Configuring Multiple Compute Nodes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:239(para) +msgid "If your goal is to split your VM load across more than one server, you can connect an additional node to a cloud controller node. This configuring can be reproduced on multiple compute servers to start building a true multi-node OpenStack Compute cluster." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:245(para) +msgid "To build out and scale the Compute platform, you spread out services amongst many servers. While there are additional ways to accomplish the build-out, this section describes adding compute nodes, and the service we are scaling out is called ." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:251(para) +msgid "For a multi-node install you only make changes to nova.conf and copy it to additional compute nodes. Ensure each nova.conf file points to the correct IP addresses for the respective services." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:257(para) +msgid "By default, Nova sets the bridge device based on the setting in flat_network_bridge. Now you can edit /etc/network/interfaces with the following template, updated with your IP information." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:274(replaceable) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:275(replaceable) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:276(replaceable) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:277(replaceable) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:278(replaceable) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:280(replaceable) +msgid "xxx.xxx.xxx.xxx" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:283(para) +msgid "Restart networking:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:287(para) +msgid "With nova.conf updated and networking set, configuration is nearly complete. First, bounce the relevant services to take the latest updates:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:294(para) +msgid "To avoid issues with KVM and permissions with Nova, run the following commands to ensure we have VM's that are running optimally:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:301(para) +msgid "If you want to use the 10.04 Ubuntu Enterprise Cloud images that are readily available at http://uec-images.ubuntu.com/releases/10.04/release/, you may run into delays with booting. Any server that does not have running on it needs this iptables entry so that UEC images can get metadata info. On compute nodes, configure the iptables with this next step:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:309(replaceable) +msgid "$NOVA_API_IP" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:311(para) +msgid "Lastly, confirm that your compute node is talking to your cloud controller. From the cloud controller, run this database query:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:314(replaceable) +msgid "$MYSQL_USER" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:314(replaceable) +msgid "$MYSQL_PASS" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:316(para) +msgid "In return, you should see something similar to this:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:329(para) +msgid "You can see that osdemo0{1,2,4,5} are all running . When you start spinning up instances, they will allocate on any node that is running from this list." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:336(title) +msgid "Determining the Version of Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:338(para) +msgid "You can find the version of the installation by using the command:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:345(title) +msgid "Diagnose your compute nodes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:347(para) +msgid "You can obtain extra informations about the running virtual machines: their CPU usage, the memory, the disk IO or network IO, per instance, by running the command with a server ID:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:352(para) +msgid "The output of this command will vary depending on the hypervisor. Example output when the hypervisor is Xen: While the command should work with any hypervisor that is controlled through libvirt (e.g., KVM, QEMU, LXC), it has only been tested with KVM. Example output when the hypervisor is KVM:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:393(title) +msgid "General Compute Configuration Overview" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:395(para) +msgid "Most configuration information is available in the nova.conf configuration option file. Here are some general purpose configuration options that you can use to learn more about the configuration option file and the node. The configuration file nova.conf is typically stored in /etc/nova/nova.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:402(para) +msgid "You can use a particular configuration option file by using the option (nova.conf) parameter when running one of the nova-* services. This inserts configuration option definitions from the given configuration file name, which may be useful for debugging or performance tuning. Here are some general purpose configuration options." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:410(para) +msgid "If you want to maintain the state of all the services, you can use the state_path configuration option to indicate a top-level directory for storing data related to the state of Compute including images if you are using the Compute object store." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:418(title) +msgid "Example nova.conf Configuration Files" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:419(para) +msgid "The following sections describe many of the configuration option settings that can go into the nova.conf files. Copies of each nova.conf file need to be copied to each compute node. Here are some sample nova.conf files that offer examples of specific configurations." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:426(title) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:434(title) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:477(title) +msgid "KVM, Flat, MySQL, and Glance, OpenStack or EC2 API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:428(para) +msgid "This example nova.conf file is from an internal Rackspace test system used for demonstrations." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:446(title) +msgid "XenServer, Flat networking, MySQL, and Glance, OpenStack API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:449(para) +msgid "This example nova.conf file is from an internal Rackspace test system." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:489(title) +msgid "Configuring Logging" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:490(para) +msgid "You can use nova.conf configuration options to indicate where Compute will log events, the level of logging, and customize log formats." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:493(para) +msgid "To customize log formats for OpenStack Compute, use these configuration option settings." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:500(title) +msgid "Configuring Hypervisors" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:502(para) +msgid "OpenStack Compute requires a hypervisor and supports several hypervisors and virtualization standards. Configuring and running OpenStack Compute to use a particular hypervisor takes several installation and configuration steps. The libvirt_type configuration option indicates which hypervisor will be used. Refer to Hypervisor Configuration Basics for more details. To customize hypervisor support in OpenStack Compute, refer to these configuration settings in nova.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:516(title) +msgid "Configuring Authentication and Authorization" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:518(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. Refer to Identity Management for additional information." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:522(para) +msgid "To customize authorization settings for Compute, see these configuration settings in nova.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:526(para) +msgid "To customize certificate authority settings for Compute, see these configuration settings in nova.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:528(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/src/docbkx/openstack-compute-admin/computeconfigure.xml:533(title) +msgid "Configuring Compute to use IPv6 Addresses" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:535(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 autoconfiguration 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/src/docbkx/openstack-compute-admin/computeconfigure.xml:544(para) +msgid "This configuration has been tested with VM images that have IPv6 stateless address autoconfiguration capability (must use EUI-64 address for stateless address autoconfiguration), 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/src/docbkx/openstack-compute-admin/computeconfigure.xml:551(para) +msgid "On all nova-nodes, install python-netaddr:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:555(para) +msgid "On all nova-network nodes install radvd and configure IPv6 networking:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:562(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/src/docbkx/openstack-compute-admin/computeconfigure.xml:566(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/src/docbkx/openstack-compute-admin/computeconfigure.xml:570(replaceable) +msgid "fixed_range" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:570(replaceable) +msgid "num_networks" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:570(replaceable) +msgid "network_size" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:570(replaceable) +msgid "vlan_start" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:570(replaceable) +msgid "vpn_start" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:570(replaceable) +msgid "fixed_range_v6" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:572(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/src/docbkx/openstack-compute-admin/computeconfigure.xml:580(para) +msgid "Here is a usage example for VlanManager:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:584(para) +msgid "Here is a usage example for FlatDHCPManager:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:588(para) +msgid "Note that vlan_start and vpn_start parameters are not used by FlatDHCPManager." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:595(title) +msgid "Configuring Image Service and Storage for Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:597(para) +msgid "Compute relies on an external image service to store virtual machine images and maintain a catalog of available images. Compute is configured by default to use the OpenStack Image service (Glance), which is the only currently supported image service." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:602(para) +msgid "If your installation requires the use of euca2ools for registering new images, you will need to run the nova-objectstore service. This service provides an Amazon S3 frontend for Glance, which is needed because euca2ools can only upload images to an S3-compatible image store." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:612(title) +msgid "Configuring Migrations" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:615(para) +msgid "This feature is for cloud administrators only." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:619(para) +msgid "Migration allows 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/src/docbkx/openstack-compute-admin/computeconfigure.xml:626(para) +msgid "Migration (or non-live migration): In this case the instance will be shut down (and the instance will know that it has been rebooted) for a period of time in order to be moved to another hypervisor." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:632(para) +msgid "Live migration (or true live migration): Almost no instance downtime, it is useful when the instances must be kept running during the migration." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:623(para) +msgid "There are two types of migration: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:642(para) +msgid "Shared storage based live migration: In this case both hypervisors have access to a shared storage." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:645(para) +msgid "Block live migration: for this type of migration, no shared storage is required." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:639(para) +msgid "There are two types of live migration: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:650(para) +msgid "The following sections describe how to configure your hosts and compute nodes for migrations using the KVM and XenServer hypervisors." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:655(title) +msgid "KVM-Libvirt" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:660(para) +msgid "Hypervisor: KVM with libvirt" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:663(para) +msgid "Shared storage:NOVA-INST-DIR/instances/ (eg /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/src/docbkx/openstack-compute-admin/computeconfigure.xml:670(para) +msgid "Instances: Instance can be migrated with iSCSI based volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:675(para) +msgid "Migrations done by the Compute service do not use libvirt's live migration functionality by default. Because of this, guests are suspended before migration and may therefore experience several minutes of downtime. See True Migration for KVM and Libvirt for more details." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:681(para) +msgid "This guide assumes the default value for instances_path in your nova.conf (NOVA-INST-DIR/instances). If you have changed the state_path or instances_path variables, please modify accordingly." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:687(para) +msgid "You must specify vncserver_listen=0.0.0.0 or live migration will not work correctly." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:692(emphasis) +msgid "Example Nova Installation Environment" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:694(para) +msgid "Prepare 3 servers at least; for example, HostA, HostB and HostC" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:699(para) +msgid "HostA is the \"Cloud Controller\", and should be running: nova-api, nova-scheduler, nova-network, nova-volume, nova-objectstore." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:705(para) +msgid "HostB and HostC are the \"compute nodes\", running nova-compute." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:709(para) +msgid "Ensure that, NOVA-INST-DIR (set with state_path in nova.conf) is same on all hosts." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:714(para) +msgid "In this example, HostA will be the NFSv4 server which exports NOVA-INST-DIR/instances, and HostB and HostC mount it." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:719(emphasis) +msgid "System configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:723(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/src/docbkx/openstack-compute-admin/computeconfigure.xml:733(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 will work correctly." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:738(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/src/docbkx/openstack-compute-admin/computeconfigure.xml:742(para) +msgid "Our 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/src/docbkx/openstack-compute-admin/computeconfigure.xml:749(replaceable) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:764(replaceable) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:770(replaceable) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:780(replaceable) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:790(replaceable) +msgid "NOVA-INST-DIR" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:746(para) +msgid "Using your knowledge from the Ubuntu documentation, configure the NFS server at HostA by adding a line to /etc/exports" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:751(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/src/docbkx/openstack-compute-admin/computeconfigure.xml:759(para) +msgid "Set the 'execute/search' bit on your shared directory" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:760(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, execute the following command:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:767(para) +msgid "Configure NFS at HostB and HostC by adding below to /etc/fstab." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:772(para) +msgid "Then ensure that the exported directory can be mounted." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:777(para) +msgid "Check that \"NOVA-INST-DIR/instances/\" directory can be seen at HostA" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:780(filename) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:790(filename) +msgid "/instances/" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:787(para) +msgid "Perform the same check at HostB and HostC - paying special attention to the permissions (nova should be able to write)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:811(para) +msgid "Update the libvirt configurations. Modify /etc/libvirt/libvirtd.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:824(para) +msgid "Modify /etc/init/libvirt-bin.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:831(para) +msgid "Modify /etc/default/libvirt-bin" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:838(para) +msgid "Restart libvirt. After executing the command, ensure that libvirt is successfully restarted." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:850(para) +msgid "Configure your firewall to allow libvirt to communicate between nodes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:851(para) +msgid "Information about ports used with libvirt can be found at 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/src/docbkx/openstack-compute-admin/computeconfigure.xml:858(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/src/docbkx/openstack-compute-admin/computeconfigure.xml:866(title) +msgid "Enabling true live migration" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:867(para) +msgid "By default, the Compute service does not use libvirt's live migration functionality. To enable this functionality, add the following line to nova.conf: The Compute service does not use libvirt's live miration by default because there is a risk that the migration process will never terminate. This can happen if the guest operating system dirties blocks on the disk faster than they can migrated." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:877(title) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:988(title) +msgid "XenServer" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:880(title) +msgid "Shared Storage" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:884(para) +msgid "Compatible XenServer hypervisors. For more information, please refer to the Requirements for Creating Resource Pools section of the XenServer Administrator's Guide." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:893(para) +msgid "Please check the NFS VHD section of the XenServer Administrator's Guide for the supported NFS versions." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:890(para) +msgid "Shared storage: an NFS export, visible to all XenServer hosts. " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:903(para) +msgid "In order to use shared storage live migration with XenServer hypervisors, the hosts must be joined to a XenServer pool. In order to create that pool, a host aggregate must be created with special metadata. This metadata will be used by the XAPI plugins to establish the pool." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:912(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 of the XenServer Administrator's Guide." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:919(para) +msgid "Configure all the compute nodes to use the default sr for pool operations, by including: in your nova.conf configuration files across your compute nodes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:927(para) +msgid "Create a host aggregate The command will display a table which contains the id of the newly created aggregate. Now add special metadata to the aggregate, to mark it as a hypervisor pool Make the first compute node part of that aggregate At this point, the host is part of a XenServer pool." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:945(para) +msgid "At this point the added compute node and the host will be shut down, in order to join the host to the XenServer pool. The operation will fail, if any server other than the compute node is running/suspended on your host." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:941(para) +msgid "Add additional hosts to the pool: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:956(title) +msgid "Block migration" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:960(para) +msgid "Compatible XenServer hypervisors. The hypervisors must support the Storage XenMotion feature. Please refer to the manual of your XenServer to make sure your edition has this feature." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:966(para) +msgid "Please note, that you need to use an extra option --block-migrate for the live migration command, in order to use block migration." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:970(para) +msgid "Please note, that block migration works only with EXT local storage SRs, and the server should not have any volumes attached." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:980(title) +msgid "Configuring Resize" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:981(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. In order for this feature to work properly, some underlying virt layers may need further configuration; this section describes the required configuration steps for each hypervisor layer provided by OpenStack." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:989(para) +msgid "To get resize to work with XenServer (and XCP) you need to:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:991(para) +msgid "Establish a root trust between all hypervisor nodes of your deployment:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:993(para) +msgid "You can simply do so, by generating an ssh key-pair (with ) and then ensuring 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/src/docbkx/openstack-compute-admin/computeconfigure.xml:998(para) +msgid "Provide a /images mountpoint to your hypervisor's dom0:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:999(para) +msgid "Dom0 space is a premium so creating a directory in dom0 is kind of dangerous, and almost surely bound to fail especially when resizing big servers. The least you can do is to symlink /images to your local storage SR. The instructions below 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/src/docbkx/openstack-compute-admin/computeconfigure.xml:1016(title) +msgid "Installing MooseFS as shared storage for the instances directory" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1017(para) +msgid "In the previous section we presented a convenient way to deploy a shared storage using NFS. For better transactions performance, you could deploy MooseFS instead." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1019(para) +msgid "MooseFS (Moose File System) is a shared file system ; it implements the same rough concepts of shared storage solutions - such as Ceph, Lustre or even GlusterFS." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1025(para) +msgid "A metadata server (MDS), also called master server, which manages the file repartition, their access and the namespace." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1029(para) +msgid "A metalogger server (MLS) which backs up the MDS logs, including, objects, chunks, sessions and object metadata" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1033(para) +msgid "A chunk server (CSS) which store the data as chunks and replicate them across the chunkservers" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1037(para) +msgid "A client, which talks with the MDS and interact with the CSS. MooseFS clients manage MooseFS filesystem using FUSE" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1021(para) +msgid "Main concepts For more informations, please see the Official project website" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1043(para) +msgid "Our setup will be made the following way :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1047(para) +msgid "Two compute nodes running both MooseFS chunkserver and client services." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1050(para) +msgid "One MooseFS master server, running the metadata service." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1053(para) +msgid "One MooseFS slave server, running the metalogger service." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1044(para) +msgid " For that particular walkthrough, we will use the following network schema :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1059(para) +msgid "10.0.10.15 for the MooseFS metadata server admin IP" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1062(para) +msgid "10.0.10.16 for the MooseFS metadata server main IP" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1065(para) +msgid "10.0.10.17 for the MooseFS metalogger server admin IP" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1068(para) +msgid "10.0.10.18 for the MooseFS metalogger server main IP" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1071(para) +msgid "10.0.10.19 for the MooseFS first chunkserver IP" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1074(para) +msgid "10.0.10.20 for the MooseFS second chunkserver IP" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1078(title) +msgid "MooseFS deployment for OpenStack" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1088(title) +msgid "Installing the MooseFS metadata and metalogger servers" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1089(para) +msgid "Both components could be run anywhere , as long as the MooseFS chunkservers can reach the MooseFS master server." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1091(para) +msgid "In our deployment, both MooseFS master and slave run their services inside a virtual machine ; you just need to make sure to allocate enough memory to the MooseFS metadata server, all the metadata being stored in RAM when the service runs." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1097(emphasis) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1198(para) +msgid "Hosts entry configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1098(para) +msgid "In the /etc/hosts add the following entry : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1104(emphasis) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1201(para) +msgid "Required packages" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1105(para) +msgid "Install the required packages by running the following commands : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1111(emphasis) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1204(para) +msgid "User and group creation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1112(para) +msgid "Create the adequate user and group : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1117(emphasis) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1207(para) +msgid "Download the sources" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1118(para) +msgid "Go the the MooseFS download page and fill the download form in order to obtain your URL for the package." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1124(emphasis) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1210(emphasis) +msgid "Extract and configure the sources" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1125(para) +msgid "Extract the package and compile it : For the MooseFS master server installation, we disable from the compilation the mfschunkserver and mfsmount components : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1133(emphasis) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1219(emphasis) +msgid "Create configuration files" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1134(para) +msgid "We will keep the default settings, for tuning performance, you can read the MooseFS official FAQ" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1137(para) +msgid " In /etc/moosefs/mfsexports.cfg edit the second line in order to restrict the access to our private network :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1146(para) +msgid "Create the metadata file : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1152(emphasis) +msgid "Power up the MooseFS mfsmaster service" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1153(para) +msgid "You can now start the mfsmaster and mfscgiserv deamons on the MooseFS metadataserver (The mfscgiserv is a webserver which allows you to see via a web interface the MooseFS status realtime) : Open the following url in your browser : http://10.0.10.16:9425 to see the MooseFS status page" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1162(emphasis) +msgid "Power up the MooseFS metalogger service" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1172(title) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1194(emphasis) +msgid "Installing the MooseFS chunk and client services" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1173(para) +msgid "In the first part, we will install the last version of FUSE, and proceed to the installation of the MooseFS chunk and client in the second part." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1176(emphasis) +msgid "Installing FUSE" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1180(emphasis) +msgid "Required package" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1186(emphasis) +msgid "Download the sources and configure them" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1187(para) +msgid "For that setup we will retrieve the last version of fuse to make sure every function will be available : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1211(para) +msgid "Extract the package and compile it : For the MooseFS chunk server installation, we only disable from the compilation the mfsmaster component : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1220(para) +msgid "The chunk servers configuration is relatively easy to setup. You only need to create on every server directories that will be used for storing the datas of your cluster." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1223(para) +msgid " Edit /etc/moosefs/mfhdd.cfg and add the directories you created to make them part of the cluster :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1241(emphasis) +msgid "Power up the MooseFS mfschunkserver service" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1195(para) +msgid "For installing both services, you can follow the same steps that were presented before (Steps 1 to 4) : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1250(title) +msgid "Access to your cluster storage" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1268(emphasis) +msgid "mfsmaster:9421 on /var/lib/nova/instances type fuse.mfs (rw,allow_other,default_permissions)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1251(para) +msgid "You can now access your cluster space from the compute node, (both acting as chunkservers) : You can interact with it the way you would interact with a classical mount, using build-in linux commands (cp, rm, etc...)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1273(para) +msgid "The MooseFS client has several tools for managing the objects within the cluster (set replication goals, etc..). You can see the list of the available tools by running You can read the manual for every command. You can also see the online help" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1282(emphasis) +msgid "Add an entry into the fstab file" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1283(para) +msgid "In order to make sure to have the storage mounted, you can add an entry into the /etc/fstab on both compute nodes : " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1292(title) +msgid "Configuring Database Connections" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1294(para) +msgid "You can configure OpenStack Compute to use any SQLAlchemy-compatible database. The database name is nova and entries to it are mostly written by the nova-scheduler service, although all the services need to be able to update entries in the database. Use these settings to configure the connection string for the nova database." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1303(title) +msgid "Configuring the Compute Messaging System" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1305(para) +msgid "OpenStack Compute uses an open standard for messaging middleware known as AMQP. This messaging middleware enables the OpenStack compute services which will exist across multiple servers to talk to each other. OpenStack Compute supports two implementations of AMQP: RabbitMQ and Qpid." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1313(title) +msgid "Configuration for RabbitMQ" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1315(para) +msgid "OpenStack Compute uses RabbitMQ by default. This section discusses the configuration options that are relevant when RabbitMQ is used. The rpc_backend option is not required as long as RabbitMQ is the default messaging system. However, if it is included the configuration, it must be set to nova.rpc.impl_kombu." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1328(para) +msgid "The following tables describe the rest of the options that can be used when RabbitMQ is used as the messaging system. You can configure the messaging communication for different installation scenarios as well as tune RabbitMQ's retries and the size of the RPC thread pool. If you want to monitor notifications through RabbitMQ, you must set the notification_driver option in nova.conf to nova.notifier.rabbit_notifier. The default for sending usage data is 60 seconds plus a randomized 0-60 seconds." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1341(filename) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1404(filename) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1504(filename) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1602(filename) +msgid "nova.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1341(caption) +msgid "Description of configuration options for Remote Procedure Calls and RabbitMQ Messaging" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1347(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1410(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1509(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1608(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1701(td) +msgid "Configuration option" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1357(literal) +msgid "rabbit_host" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1359(literal) +msgid "localhost" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1361(application) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1371(application) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1379(application) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1389(application) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1397(application) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1432(application) +msgid "RabbitMQ" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1361(td) +msgid "IP address; Location of installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1366(literal) +msgid "rabbit_password" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1368(literal) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1386(literal) +msgid "guest" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1370(td) +msgid "String value; Password for the server." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1375(literal) +msgid "rabbit_port" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1377(literal) +msgid "5672" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1379(td) +msgid "Integer value; Port where server is running/listening." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1384(literal) +msgid "rabbit_userid" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1388(td) +msgid "String value; User ID used for connections." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1393(literal) +msgid "rabbit_virtual_host" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1395(literal) +msgid "/" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1397(td) +msgid "Location of a virtual installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1404(caption) +msgid "Description of configuration options for Tuning RabbitMQ Messaging" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1420(literal) +msgid "-rabbit_max_retries" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1420(td) +msgid "-" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1422(literal) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1424(literal) +msgid "0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1424(td) +msgid "Integer value; maximum retries with trying to connect to RabbitMQ(the default of implies an infinite retry count)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1428(literal) +msgid "rabbit_retry_interval" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1430(literal) +msgid "1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1432(td) +msgid "Integer value: connection retry interval." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1437(literal) +msgid "rpc_thread_pool_size" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1439(literal) +msgid "1024" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1441(td) +msgid "Integer value: Size of Remote Procedure Call thread pool." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1448(title) +msgid "Configuration for Qpid" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1450(para) +msgid "This section discusses the configuration options that are relevant if Qpid is used as the messaging system for OpenStack Compute. Qpid is not the default messaging system, so it must be enabled by setting the rpc_backend option in nova.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1461(para) +msgid "This next critical option points the compute nodes to the Qpid broker (server). Set qpid_hostname in nova.conf to be the hostname where the broker is running." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1467(para) +msgid "The --qpid_hostname option accepts a value in the form of either a hostname or an IP address." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1475(para) +msgid "If the Qpid broker is listening on a port other than the AMQP default of 5672, you will need to set the qpid_port option:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1483(para) +msgid "If you configure the Qpid broker to require authentication, you will need to add a username and password to the configuration:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1492(para) +msgid "By default, TCP is used as the transport. If you would like to enable SSL, set the qpid_protocol option:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1499(para) +msgid "The following table lists the rest of the options used by the Qpid messaging driver for OpenStack Compute. It is not common that these options are used." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1504(caption) +msgid "Remaining configuration options for Qpid support" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1519(literal) +msgid "qpid_sasl_mechanisms" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1521(literal) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1530(literal) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1539(literal) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1548(literal) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1557(literal) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1566(literal) +msgid "(Qpid default)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1523(td) +msgid "String value: A space separated list of acceptable SASL mechanisms to use for authentication." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1528(literal) +msgid "qpid_reconnect_timeout" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1532(td) +msgid "Integer value: The number of seconds to wait before deciding that a reconnect attempt has failed." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1537(literal) +msgid "qpid_reconnect_limit" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1541(td) +msgid "Integer value: The limit for the number of times to reconnect before considering the connection to be failed." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1546(literal) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1569(literal) +msgid "qpid_reconnect_interval_min" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1550(td) +msgid "Integer value: Minimum number of seconds between connection attempts." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1555(literal) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1570(literal) +msgid "qpid_reconnect_interval_max" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1559(td) +msgid "Integer value: Maximum number of seconds between connection attempts." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1564(literal) +msgid "qpid_reconnect_interval" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1568(td) +msgid "Integer value: Equivalent to setting and to the same value." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1575(literal) +msgid "qpid_heartbeat" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1577(literal) +msgid "5" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1579(td) +msgid "Integer value: Seconds between heartbeat messages sent to ensure that the connection is still alive." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1584(literal) +msgid "qpid_tcp_nodelay" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1588(td) +msgid "Boolean value: Disable the Nagle algorithm." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1595(title) +msgid "Common Configuration for Messaging" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1597(para) +msgid "This section lists options that are common between both the RabbitMQ and Qpid messaging drivers." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1602(caption) +msgid "Description of configuration options for Customizing Exchange or Topic Names" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1618(literal) +msgid "control_exchange" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1620(literal) +msgid "nova" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1622(td) +msgid "String value; Name of the main AMQP exchange to connect to if using RabbitMQ or Qpid for RPC (not Zeromq)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1626(literal) +msgid "ajax_console_proxy_topic" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1628(literal) +msgid "ajax_proxy" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1630(td) +msgid "String value; Topic that the ajax proxy nodes listen on" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1634(literal) +msgid "console_topic" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1636(literal) +msgid "console" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1638(td) +msgid "String value; The topic console proxy nodes listen on" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1642(literal) +msgid "network_topic" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1644(literal) +msgid "network" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1646(td) +msgid "String value; The topic network nodes listen on." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1650(literal) +msgid "scheduler_topic" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1652(literal) +msgid "scheduler" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1654(td) +msgid "String value; The topic scheduler nodes listen on." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1658(literal) +msgid "volume_topic" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1660(literal) +msgid "volume" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1662(td) +msgid "String value; Name of the topic that volume nodes listen on" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1671(title) +msgid "Configuring the Compute API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1673(title) +msgid "Configuring Compute API password handling" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1675(para) +msgid "The OpenStack Compute API allows the user to specify an admin password when creating (or rebuilding) a server instance. If no password is specified, a randomly generated password is used. The password is returned in the API response." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1680(para) +msgid "In practice, the handling of the admin password depends on the hypervisor in use, and may require additional configuration of the instance, such as installing an agent to handle the password setting. If the hypervisor and instance configuration do not support the setting of a password at server create time, then the password returned by the create API call will be misleading, since it was ignored." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1689(para) +msgid "To prevent this confusion, the configuration configuration option enable_instance_password can be used to disable the return of the admin password for installations that don't support setting instance passwords." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1696(caption) +msgid "Description of nova.conf API related configuration options" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1711(literal) +msgid "enable_instance_password" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1713(literal) +msgid "true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1715(td) +msgid "When true, the create and rebuild compute API calls return the server admin password. When false, the server admin password is not included in API responses." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1725(title) +msgid "Configuring Compute API Rate Limiting" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1727(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/src/docbkx/openstack-compute-admin/computeconfigure.xml:1732(para) +msgid "When API rate limits are exceeded, HTTP requests will return a error with a status code of 413 \"Request entity too large\", and will also include a 'Retry-After' HTTP header. The response body will include the error details, and the delay before the request should be retried." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1737(para) +msgid "Rate limiting is not available for the EC2 API." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1740(title) +msgid "Specifying Limits" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1742(para) +msgid "Limits are specified using five values:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1746(para) +msgid "The HTTP method used in the API call, typically one of GET, PUT, POST, or DELETE." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1751(para) +msgid "A human readable URI that is used as a friendly description of where the limit is applied." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1756(para) +msgid "A regular expression. The limit will be applied to all URI's that match the regular expression and HTTP Method." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1762(para) +msgid "A limit value that specifies the maximum count of units before the limit takes effect." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1767(para) +msgid "An interval that specifies time frame the limit is applied to. The interval can be SECOND, MINUTE, HOUR, or DAY." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1773(para) +msgid "Rate limits are applied in order, relative to the HTTP method, going from least to most specific. For example, although the default threshold for POST to */servers is 50 per day, one cannot POST to */servers more than 10 times within a single minute because the rate limits for any POST is 10/min." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1781(title) +msgid "Default Limits" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1783(para) +msgid "OpenStack compute is normally installed with the following limits enabled:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1787(caption) +msgid "Default API Rate Limits" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1791(td) +msgid "HTTP method" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1793(td) +msgid "API URI" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1795(td) +msgid "API regular expression" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1797(td) +msgid "Limit" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1803(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1813(td) +msgid "POST" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1805(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1825(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1845(td) +msgid "any URI (*)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1807(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1827(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1847(td) +msgid ".*" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1809(td) ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1829(td) +msgid "10 per minute" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1815(td) +msgid "/servers" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1817(td) +msgid "^/servers" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1819(td) +msgid "50 per day" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1823(td) +msgid "PUT" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1833(td) +msgid "GET" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1835(td) +msgid "*changes-since*" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1837(td) +msgid ".*changes-since.*" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1839(td) +msgid "3 per minute" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1843(td) +msgid "DELETE" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1849(td) +msgid "100 per minute" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1856(title) +msgid "Configuring and Changing Limits" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1858(para) +msgid "The actual limits are specified in the file etc/nova/api-paste.ini, as part of the WSGI pipeline." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1862(para) +msgid "To enable limits, ensure the 'ratelimit' filter is included in the API pipeline specification. If the 'ratelimit' filter is removed from the pipeline, limiting will be disabled. There should also be a definition for the ratelimit filter. The lines will appear as follows:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1879(para) +msgid "To modify the limits, add a 'limits' specification to the [filter:ratelimit] section of the file. The limits are specified in the order HTTP method, friendly URI, regex, limit, and interval. The following example specifies the default rate limiting values:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1894(title) +msgid "Configuring the EC2 API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1896(para) +msgid "You can use nova.conf configuration options to control which network address and port the EC2 API will listen on, the formatting of some API responses, and authentication related options." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1901(para) +msgid "To customize these options for OpenStack EC2 API, use these configuration option settings." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1908(title) +msgid "Configuring Quotas" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1913(para) +msgid "Number of volumes which may be created (volumes=10)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1916(para) +msgid "Total size of all volumes within a project as measured in GB (gigabytes=1000)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1919(para) +msgid "Number of instances which may be launched (instances=10)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1922(para) +msgid "Number of processor cores which may be allocated (cores=20)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1925(para) +msgid "Publicly accessible IP addresses (floating_ips=10)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1928(para) +msgid "Amount of RAM that can be allocated in MB (ram=512000)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1931(para) +msgid "Number of files that can be injected (injected_files=5)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1934(para) +msgid "Maximal size of injected files in B (injected_file_content_bytes=10240)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1937(para) +msgid "Number of security groups that may be created (security_groups=10)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1940(para) +msgid "Number of rules per security group (security_group_rules=20)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1910(para) +msgid "For tenants, quota controls are available to limit the (flag and default shown in parenthesis):" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1943(para) +msgid "The defaults may be modified by setting the variable in nova.conf, then restarting the nova-api service." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/computeconfigure.xml:1946(para) +msgid "To modify a value for a specific project, the command should be used. For example: Alternately, quota settings are available through the OpenStack Dashboard in the \"Edit Project\" page." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:7(title) +msgid "Backup your nova-volume disks" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:8(para) +msgid "While Diablo provides the snapshot functionality (using LVM snapshot), you can also back up your volumes. The advantage of this method is that it reduces the size of the backup; only existing data will be backed up, instead of the entire volume. For this example, assume that a 100 GB nova-volume has been created for an instance, while only 4 gigabytes are used. This process will back up only those 4 giga-bytes, with the following tools:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:19(para) +msgid ", directly manipulates the volumes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:23(para) +msgid " discovers the partition table created inside the instance." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:27(para) +msgid " creates a minimum-sized backup" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:31(para) +msgid " calculates the backup checksum, to check its consistency" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:36(emphasis) +msgid "1- Create a snapshot of a used volume" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:39(para) +msgid "In order to backup our volume, we first need to 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 will not be manipulated during the process of creating the volume itself. Remember the volumes created through a exist in an LVM's logical volume." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:49(para) +msgid "Before creating the snapshot, ensure that you 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, there is a risk that the snapshot could become corrupted." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:57(para) +msgid "Use the following command to obtain a list of all volumes.In this example, we will refer to a volume called volume-00000001, which is a 10GB volume. This process can be applied to all volumes, not matter their size. At the end of the section, we will present a script that you could use to create scheduled backups. The script itself exploits what we discuss here." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:70(para) +msgid "First, create the snapshot; this can be achieved while the volume is attached to an instance :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:78(para) +msgid "We indicate to LVM we want a snapshot of an already existing volume with the --snapshot configuration option. 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 (In most cases, the path will be /dev/nova-volumes/$volume_name)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:87(para) +msgid "The size doesn't have to be the same as the volume of the snapshot. The size parameter designates the space that LVM will reserve for the snapshot volume. As a precaution, the size should be the same as that of the original volume, even if we know the whole space is not currently used by the snapshot." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:94(para) +msgid "We now have a full snapshot, and it only took few seconds !" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:95(para) +msgid "Run again to verify the snapshot. You should see now your snapshot :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:141(emphasis) +msgid "2- Partition table discovery" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:144(para) +msgid "If we want to exploit that snapshot with the program, we first need to mount our partition on the nova-volumes server." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:148(para) +msgid " is a small utility which performs table partition discoveries, and maps it. It can be used to view partitions created inside the instance. Without using the partitions created inside instances, we won' t be able to see its content and create efficient backups." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:160(para) +msgid "If no errors are displayed, it means the tools has been able to find it, and map the partition table. Note that on a Debian flavor distro, you could also use ." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:165(para) +msgid "You can easily check the partition table map by running the following command:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:167(para) +msgid "You should now see a partition called nova--volumes-volume--00000001--snapshot1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:173(para) +msgid "If you created more than one partition on that volumes, you should have accordingly several partitions; for example. nova--volumes-volume--00000001--snapshot2, nova--volumes-volume--00000001--snapshot3 and so forth." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:179(para) +msgid "We can now mount our partition :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:185(para) +msgid "If there are no errors, you have successfully mounted the partition." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:187(para) +msgid "You should now be able to directly access the data that were created inside the instance. If you receive a message asking you to specify a partition, or if you are unable to mount it (despite a well-specified filesystem) there could be two causes :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:195(para) +msgid "You didn't allocate enough space for the snapshot" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:199(para) +msgid " was unable to discover the partition table." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:193(para) +msgid "Allocate more space to the snapshot and try the process again." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:209(emphasis) +msgid "3- Use tar in order to create archives" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:212(para) +msgid "Now that the volume has been mounted, you can create a backup of it :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:219(para) +msgid "This command will create a tar.gz file containing the data, and data only. This ensures that you do not waste space by backing up empty sectors." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:228(emphasis) +msgid "4- Checksum calculation I" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:231(para) +msgid "You should always have the checksum for your backup files. The checksum is a unique identifier for a file." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:234(para) +msgid "When you transfer that same file over the network, you can run another checksum calculation. If the checksums are different, this indicates that the file is corrupted; thus, the checksum provides a method to ensure your file has not been corrupted during its transfer." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:241(para) +msgid "The following command runs a checksum for our file, and saves the result to a file :" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:244(para) +msgid "Be aware the should be used carefully, since the required time for the calculation is directly proportional to the file's size." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:252(para) +msgid "For files larger than ~4-6 gigabytes, and depending on your CPU, the process may take a long time." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:257(emphasis) +msgid "5- After work cleaning" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:264(para) +msgid "Unmount the volume: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:269(para) +msgid "Delete the partition table: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:274(para) +msgid "Remove the snapshot: " +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:260(para) +msgid "Now that we have an efficient and consistent backup, the following commands will clean up the file system." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:279(para) +msgid "And voila :) You can now repeat these steps for every volume you have." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:283(emphasis) +msgid "6- Automate your backups" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:285(para) +msgid "Because you can expect that more and more volumes will be allocated to your nova-volume service, you may want to automate your backups. This script here will assist you on this task. The script performs the operations from the previous example, but also provides a mail report and runs the backup based on the backups_retention_days setting. It is meant to be launched from the server which runs the nova-volumes component." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:296(para) +msgid "Here is an example of a mail report:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/backup-nova-volume-disks.xml:312(para) +msgid "The script also provides the ability to SSH to your instances and run a mysqldump into them. In order to make this to work, ensure the connection via the nova's project keys is enabled. If you don't want to run the mysqldumps, you can turn off this functionality by adding enable_mysql_dump=0 to the script." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for LDAP" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:16(td) +msgid "ldap_cloudadmin= \"cn=cloudadmins,ou=Groups,dc=example,dc=com\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:18(td) +msgid "(StrOpt) CN for Cloud Admins" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:21(td) +msgid "ldap_developer= \"cn=developers,ou=Groups,dc=example,dc=com\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:23(td) +msgid "(StrOpt) CN for Developers" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:26(td) +msgid "ldap_itsec= \"cn=itsec,ou=Groups,dc=example,dc=com\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:27(td) +msgid "(StrOpt) CN for ItSec" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:30(td) +msgid "ldap_netadmin= \"cn=netadmins,ou=Groups,dc=example,dc=com\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:32(td) +msgid "(StrOpt) CN for NetAdmins" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:35(td) +msgid "ldap_password= \"changeme\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:36(td) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:45(td) +msgid "(StrOpt) LDAP password" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:39(td) +msgid "ldap_suffix= \"cn=example,cn=com\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:40(td) +msgid "(StrOpt) LDAP suffix" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:43(td) +msgid "ldap_use_dumb_member=False" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:44(td) +msgid "(BoolOpt) Simulates an LDAP member" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:47(td) +msgid "ldap_project_subtree= \"ou=Groups,dc=example,dc=com\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:49(td) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:50(td) +msgid "(StrOpt) OU for Projects" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:52(td) +msgid "ldap_objectClass= inetOrgPerson" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:53(td) +msgid "(StrOpt) LDAP objectClass to use" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:56(td) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:53(td) +msgid "ldap_schema_version=2" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:57(td) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:54(td) +msgid "(IntOpt) Current version of the LDAP schema" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:60(td) +msgid "ldap_sysadmin= \"cn=sysadmins,ou=Groups,dc=example,dc=com\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:62(td) +msgid "(StrOpt) CN for Sysadmins" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:65(td) +msgid "ldap_url= \"ldap://localhost\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:66(td) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:63(td) +msgid "(StrOpt) Point this at your ldap server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:69(td) +msgid "ldap_user= \"dc=Manager,dc=example,dc=com\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:70(td) +msgid "(StrOpt) LDAP User" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:73(td) +msgid "ldap_user_tree_dn=\"ou=Users,dc=example,dc=com\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:74(td) ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:99(td) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:84(td) +msgid "(StrOpt) OU for Users" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:77(td) +msgid "ldap_user_dn= \"cn=Manager,dc=example,dc=com\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:78(td) ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:82(td) +msgid "(StrOpt) DN of Users" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:81(td) +msgid "ldap_user_objectClass= inetOrgPerson" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:85(td) +msgid "ldap_user_id_attribute= cn" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:86(td) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:71(td) +msgid "(StrOpt) Attribute to use as id" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:89(td) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:74(td) +msgid "ldap_user_modify_only=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:90(td) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:75(td) +msgid "(BoolOpt) Modify user attributes instead of creating/deleting" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:94(td) +msgid "ldap_user_name_attribute= cn" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:95(td) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:80(td) +msgid "(StrOpt) Attribute to use as name" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:98(td) +msgid "ldap_user_subtree= \"ou=Users,dc=example,dc=com\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:102(td) +msgid "ldap_user_unit= \"Users\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:103(td) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:88(td) +msgid "(StrOpt) OID for Users" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:106(td) +msgid "ldap_tenant_tree_dn=\"ou=Groups,dc=example,dc=com\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:107(td) +msgid "(StrOpt) OU for Tenants" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:110(td) +msgid "ldap_tenant_objectclass= groupOfNames" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:111(td) +msgid "(StrOpt) LDAP ObjectClass to use for Tenants" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:114(td) +msgid "ldap_tenant_id_attribute= cn" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:115(td) +msgid "(strOpt) Attribute to use as Tenant" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:118(td) +msgid "ldap_tenant_member_attribute= member" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:119(td) +msgid "(strOpt) Attribute to use as Member" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:122(td) +msgid "ldap_role_tree_dn= \"ou=Roles,dc=example,dc=com\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:123(td) +msgid "(strOpt) OU for Roles" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:126(td) +msgid "ldap_role_objectclass= organizationalRole" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:127(td) +msgid "(strOpt) LDAP ObjectClass to use for Roles" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:130(td) +msgid "ldap_role_project_subtree= \"ou=Groups,dc=example,dc=com\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:131(td) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:93(td) +msgid "(StrOpt) OU for Roles" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:134(td) +msgid "ldap_role_member_attribute= roleOccupant" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:135(td) +msgid "(StrOpt) Attribute to use as Role member" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:138(td) +msgid "ldap_role_id_attribute= cn" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ldap-nova-conf.xml:139(td) +msgid "(StrOpt) Attribute to use as Role" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for EC2 API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:16(para) +msgid "ec2_listen=0.0.0.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:17(para) +msgid "(StrOpt) IP address for EC2 API to listen" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:20(para) +msgid "ec2_listen_port=8773" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:21(para) +msgid "(IntOpt) port for ec2 api to listen" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:24(para) +msgid "ec2_private_dns_show_ip=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:25(para) +msgid "(BoolOpt) Return the IP address as private dns hostname in describe instances, else returns instance name" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:30(para) +msgid "keystone_ec2_url=http://localhost:5000/v2.0/ec2tokens" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:32(para) +msgid "(StrOpt) URL to get token from ec2 request" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:35(para) +msgid "lockout_attempts=5" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:36(para) +msgid "(IntOpt) Number of failed auths before lockout." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:40(para) +msgid "lockout_minutes=15" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:41(para) +msgid "(IntOpt) Number of minutes to lockout if triggered." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:45(para) +msgid "lockout_window=15" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-ec2-nova-conf.xml:46(para) +msgid "(IntOpt) Number of minutes for lockout window." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/live-migration-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for live migration" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/live-migration-nova-conf.xml:15(td) +msgid "live_migration_bandwidth=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/live-migration-nova-conf.xml:16(td) +msgid "(IntOpt) Maximum bandwidth to be used during migration transfer, in Mbps." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/live-migration-nova-conf.xml:20(td) +msgid "live_migration_flag= VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/live-migration-nova-conf.xml:21(td) +msgid "(StrOpt) Migration flags to be set for live migration, defines parameters for use during the migration." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/live-migration-nova-conf.xml:26(td) +msgid "live_migration_retry_count=30" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/live-migration-nova-conf.xml:27(td) +msgid "(IntOpt) Number of one-second retries needed in live_migration." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/live-migration-nova-conf.xml:31(td) +msgid "live_migration_uri=qemu+tcp://%s/system" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/live-migration-nova-conf.xml:32(td) +msgid "(StrOpt) Define Host URI used by live_migration feature. Any included \"%s\" is replaced with the migration target host name." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for credentials (crypto)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:17(td) +msgid "ca_file=cacert.pem" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:18(td) +msgid "(StrOpt) Filename of root CA (Certificate Authority)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:22(td) +msgid "ca_path=$state_path/CA" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:23(td) +msgid "(StrOpt) Where we keep our root CA" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:26(td) +msgid "crl_file=crl.pem" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:27(td) +msgid "(StrOpt) Filename of root Certificate Revocation List" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:31(td) +msgid "key_file=private/cakey.pem" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:32(td) +msgid "(StrOpt) Filename of private key" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:35(td) +msgid "keys_path=$state_path/keys" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:36(td) +msgid "(StrOpt) Where we keep our keys" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:39(td) +msgid "project_cert_subject=\"/C=US/ST=California/O=OpenStack/OU=NovaDev/CN=project-ca-%.16s-%s\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:41(td) +msgid "(StrOpt) Subject for certificate for projects, %s for project, timestamp" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:45(td) +msgid "use_project_ca=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:46(td) +msgid "(BoolOpt) Whether to use a CA for each project (tenant)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:50(td) +msgid "user_cert_subject=\"/C=US/ST=California/O=OpenStack/OU=NovaDev/CN=%.16s-%.16s-%s\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ca-nova-conf.xml:52(td) +msgid "(StrOpt) Subject for certificate for users, %s for project, user, timestamp" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for quotas" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:16(para) +msgid "max_age=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:17(para) +msgid "(IntOpt) number of seconds between subsequent usage refreshes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:20(para) +msgid "quota_cores=20" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:21(para) +msgid "(IntOpt) number of instance cores allowed per project (tenant)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:25(para) +msgid "quota_driver=nova.quota.DbQuotaDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:26(para) +msgid "(StrOpt) Default driver to use for quota checks" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:29(para) +msgid "quota_floating_ips=10" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:30(para) +msgid "(IntOpt) number of floating ips allowed per project (tenant)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:34(para) +msgid "quota_gigabytes=1000" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:35(para) +msgid "(IntOpt) number of volume gigabytes allowed per project (tenant)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:39(para) +msgid "quota_injected_file_content_bytes=10240" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:40(para) +msgid "(IntOpt) number of bytes allowed per injected file" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:44(para) +msgid "quota_injected_file_path_bytes=255" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:45(para) +msgid "(IntOpt) number of bytes allowed per injected file path" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:49(para) +msgid "quota_injected_files=5" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:50(para) +msgid "(IntOpt) number of injected files allowed" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:53(para) +msgid "quota_instances=10" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:54(para) +msgid "(IntOpt) number of instances allowed per project (tenant)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:58(para) +msgid "quota_key_pairs=100" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:59(para) +msgid "(IntOpt) number of key pairs allowed per user" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:62(para) +msgid "quota_metadata_items=128" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:63(para) +msgid "(IntOpt) number of metadata items allowed per instance" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:67(para) +msgid "quota_ram=51200" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:68(para) +msgid "(IntOpt) megabytes of instance ram allowed per project (tenant)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:72(para) +msgid "quota_security_group_rules=20" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:73(para) +msgid "(IntOpt) number of security rules per security group" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:77(para) +msgid "quota_security_groups=10" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:78(para) +msgid "(IntOpt) number of security groups per project (tenant)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:82(para) +msgid "quota_volumes=10" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:83(para) +msgid "(IntOpt) number of volumes allowed per project (tenant)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:87(para) +msgid "reservation_expire=86400" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:88(para) +msgid "(IntOpt) number of seconds until a reservation expires" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:92(para) +msgid "until_refresh=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-quotas-nova-conf.xml:93(para) +msgid "(IntOpt) count of reservations until usage is refreshed" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/config-drive-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for config drive features" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/config-drive-nova-conf.xml:16(para) +msgid "config_drive_format=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/config-drive-nova-conf.xml:17(para) +msgid "(StrOpt) File format for the config drive, options: iso9660, vfat" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/config-drive-nova-conf.xml:20(para) +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/src/docbkx/openstack-compute-admin/tables/config-drive-nova-conf.xml:22(para) +msgid "(StrOpt) Version numbers of the config drive releases to skip" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/config-drive-nova-conf.xml:25(para) +msgid "config_drive_tempdir=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/config-drive-nova-conf.xml:26(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:201(para) +msgid "(StrOpt)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/config-drive-nova-conf.xml:29(para) +msgid "force_config_drive=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/config-drive-nova-conf.xml:30(para) +msgid "(StrOpt) Forces use of config drive, such as using config drive based on image properties; reserved for future use" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/config-drive-nova-conf.xml:33(para) +msgid "using_config_drive=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/config-drive-nova-conf.xml:34(para) +msgid "(StrOpt) Enables use of config drive for images launched" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-policies-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for policies (policy.json)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-policies-nova-conf.xml:16(para) +msgid "policy_default_rule=default" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-policies-nova-conf.xml:17(para) +msgid "(StrOpt) Rule checked when requested rule is not found" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-policies-nova-conf.xml:21(para) +msgid "policy_file=policy.json" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-policies-nova-conf.xml:22(para) +msgid "(StrOpt) JSON file representing policy" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-policies-nova-conf.xml:25(para) +msgid "allow_instance_snapshots=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-policies-nova-conf.xml:26(para) +msgid "(BoolOpt) Permit instance snapshot operations." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-policies-nova-conf.xml:30(para) +msgid "osapi_max_request_body_size=114688" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-policies-nova-conf.xml:31(para) +msgid "(BoolOpt)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for roles and authentication" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:16(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:96(td) +msgid "allowed_roles=cloudadmin,itsec,sysadmin,netadmin,developer" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:18(para) +msgid "(ListOpt) Allowed roles for project (tenant)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:21(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:101(td) +msgid "auth_driver=nova.auth.dbdriver.DbDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:22(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:102(td) +msgid "(StrOpt) Driver that auth manager uses" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:25(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:105(td) +msgid "credential_cert_file=cert.pem" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:26(para) ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:42(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:106(td) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:122(td) +msgid "(StrOpt) Filename of certificate in credentials zip" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:30(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:110(td) +msgid "credential_key_file=pk.pem" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:31(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:111(td) +msgid "(StrOpt) Filename of private key in credentials zip" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:35(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:115(td) +msgid "credential_rc_file=%src" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:36(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:116(td) +msgid "(StrOpt) Filename of rc in credentials zip %s will be replaced by name of the region (nova by default)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:41(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:121(td) +msgid "credential_vpn_file=nova-vpn.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:46(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:126(td) +msgid "credentials_template=$pybasedir/nova/auth/novarc.template" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:48(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:128(td) +msgid "(StrOpt) Template for creating users rc file" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:52(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:132(td) +msgid "global_roles=cloudadmin,itsec" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:53(para) +msgid "(ListOpt) Roles that apply to all projects (tenants)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:57(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:136(td) +msgid "superuser_roles=cloudadmin" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:58(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:137(td) +msgid "(ListOpt) Roles that ignore authorization checking completely" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:62(para) ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:141(td) +msgid "vpn_client_template=$pybasedir/nova/cloudpipe/client.ovpn.template" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:64(para) +msgid "(StrOpt) Template for creating users vpn file" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:68(para) +msgid "use_forwarded_for=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/roles-auth-nova-conf.xml:69(para) +msgid "(BoolOpt) Treat X-Forwarded-For as the canonical remote address. Only enable this if you have a sanitizing proxy." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for nova- services" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:18(para) +msgid "enable_new_services=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:19(para) +msgid "(BoolOpt) Services to be added to the available pool on create" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:23(para) +msgid "instance_name_template=instance-%08x" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:24(para) ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:108(para) +msgid "(StrOpt) Template string to be used to generate instance names" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:28(para) +msgid "matchmaker_ringfile=/etc/nova/matchmaker_ring.json" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:31(para) +msgid "(StrOpt) When using rpc_backend set to ZeroMQ (nova.rpc.impl_zmq), enables use of a static hash table from a JSON file, cycles hosts per bare topic to create a directed topic." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:38(para) +msgid "metadata_listen=0.0.0.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:39(para) +msgid "(StrOpt) IP address for metadata api to listen" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:43(para) +msgid "metadata_listen_port=8775" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:44(para) +msgid "(IntOpt) port for metadata api to listen" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:47(para) +msgid "metadata_manager=nova.api.manager.MetadataManager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:49(para) +msgid "(StrOpt) OpenStack metadata service manager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:52(para) +msgid "osapi_compute_listen=0.0.0.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:53(para) +msgid "(StrOpt) IP address for OpenStack API to listen" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:57(para) +msgid "osapi_compute_listen_port=8774" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:58(para) +msgid "(IntOpt) list port for osapi compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:61(para) +msgid "osapi_compute_unique_server_name_scope=''" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:62(para) +msgid "(StrOpt) When set, the Compute API will consider duplicate hostnames (case insensitive) invalid within the specified scope. Valid scope settings are empty, \"project\" or \"global\"." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:68(para) +msgid "osapi_volume_listen=0.0.0.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:69(para) +msgid "(StrOpt) IP address for OpenStack Volume API to listen" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:73(para) +msgid "osapi_volume_listen_port=8776" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:74(para) +msgid "(IntOpt) port for os volume api to listen" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:77(para) +msgid "periodic_fuzzy_delay=60" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:78(para) +msgid "(IntOpt) range of seconds to randomly delay when starting the periodic task scheduler to reduce stampeding. (Disable by setting to 0)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:83(para) +msgid "periodic_interval=60" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:84(para) +msgid "(IntOpt) seconds between running periodic tasks" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:88(para) +msgid "report_interval=10" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:89(para) +msgid "(IntOpt) seconds between nodes reporting state to datastore" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:93(para) +msgid "rpc_backend=nova.rpc.impl_kombu" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:94(para) +msgid "(StrOpt) The messaging module to use, defaults to kombu." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:98(para) +msgid "servicegroup_driver=default_driver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:99(para) +msgid "(StrOpt) The driver for servicegroup service" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:102(para) +msgid "snapshot_name_template=snapshot-%08x" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:103(para) +msgid "(StrOpt) Template string to be used to generate snapshot names" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-services-nova-conf.xml:107(para) +msgid "volume_name_template=volume-%s" +msgstr "" + +#. xml:id="hypervisors-nova-conf" +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for hypervisors" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:16(td) +msgid "block_migration_flag=VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER,VIR_MIGRATE_NON_SHARED_INC" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:18(td) +msgid "(StrOpt) Define block migration behavior." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:21(td) +msgid "checksum_base_images=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:24(filename) +msgid "/var/lib/nova/instances/_base" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:22(td) +msgid "(BoolOpt) Used as an additional check to detect if cached images have become corrupted. If true, the compute service will write checksums for image files in the directory to disk, and do periodic checks to verify that this checksum is valid. If the checksum fails to validate, the failure is recorded to the log as an error, but no other action is taken: it is assumed that an operator will monitor the logs and take appropriate action. If false, image hashes are not verified." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:31(td) +msgid "hyperv_attaching_volume_retry_count=10" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:32(td) +msgid "(IntOpt) Number of times to retry attaching to a volume when using the Hyper-V hypervisor" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:35(td) +msgid "hyperv_wait_between_attach_retry=5" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:36(td) +msgid "(IntOpt) To be written: found in /nova/virt/hyperv/volumeops.py" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:39(td) +msgid "libvirt_cpu_mode=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:40(td) +msgid "(StrOpt) Configures the guest CPU model exposed to the hypervisor. Valid options are: custom, host-model, host-passthrough, none. If the hypervisor is KVM or QEMU, the default value is host-model, otherwise the default value is none." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:46(td) +msgid "libvirt_cpu_model=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:48(literal) +msgid "libvirt_cpu_mode" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:49(literal) +msgid "custom" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:50(filename) +msgid "/usr/share/libvirt/cpu_map.xml" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:47(td) +msgid "(StrOpt) Specify the guest CPU model exposed to the hypervisor. This configuration option is only applicable if is set to . Valid options: one of the named models specified in , e.g.: Westmere, Nehalem, Opteron_G3." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:54(td) +msgid "libvirt_disk_prefix=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:55(td) +msgid "(StrOpt) Override the default disk prefix for the devices attached to a server, which is dependent on libvirt_type. (valid options are: sd, xvd, uvd, vd)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:61(td) +msgid "libvirt_inject_key=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:62(td) +msgid "(BoolOpt) Inject the ssh public key at boot time" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:66(td) +msgid "libvirt_inject_partition=1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:67(td) +msgid "(IntOpt) The partition to inject to : -2 => disable, -1 => inspect (libguestfs only), 0 => not partitioned, >0 => partition number'" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:73(para) +msgid "libvirt_images_type=default" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:74(para) +msgid "(StrOpt) Instance ephemeral storage backend format. Acceptable values are: raw, qcow2, lvm, default. If default is specified, then use_cow_images flag is used instead of this one. Please note, that current snapshot mechanism in OpenStack Compute works only with instances backed with Qcow2 images." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:82(para) +msgid "libvirt_images_volume_group=None" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:83(para) +msgid "(StrOpt) LVM Volume Group that is used for instance ephemerals, when you specify libvirt_images_type=lvm." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:88(td) +msgid "libvirt_inject_password=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:89(td) +msgid "(BoolOpt) Inject the admin password at boot time, without an agent." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:93(td) +msgid "libvirt_lvm_snapshot_size=1000" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:94(td) +msgid "(IntOpt) The amount of storage (in megabytes) to allocate for LVM snapshot copy-on-write blocks." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:98(td) +msgid "libvirt_nonblocking=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:99(td) +msgid "(BoolOpt) Use a separated OS thread pool to realize non-blocking libvirt calls" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:103(td) +msgid "libvirt_snapshots_directory=$instances_path/snapshots" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:104(td) +msgid "(StrOpt) Location where libvirt driver will store snapshots before uploading them to image service" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:108(td) +msgid "libvirt_snapshot_compression=False" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:109(td) +msgid "(BoolOpt) Compresses snapshot images when possible. This currently applies exclusively to qcow2 images." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:113(para) +msgid "libvirt_sparse_logical_volumes=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:114(para) +msgid "(BoolOpt) Create sparse (not fully allocated) LVM volumes for instance ephemerals if you use LVM backend for them." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:118(td) +msgid "libvirt_type=kvm" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:119(td) +msgid "(StrOpt) Libvirt domain type (valid options are: kvm, lxc, qemu, uml, xen)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:123(td) +msgid "libvirt_uri=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:124(td) +msgid "(StrOpt) Override the default libvirt URI (which is dependent on libvirt_type)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:128(td) +msgid "libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtGenericVifDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:130(td) +msgid "(StrOpt) The libvirt VIF driver to configure the VIFs." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:135(para) +msgid "libvirt_volume_drivers=\"iscsi=nova.virt.libvirt.volume.LibvirtISCSIVolumeDriver," +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:135(para) +msgid "local=nova.virt.libvirt.volume.LibvirtVolumeDriver," +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:135(para) +msgid "fake=nova.virt.libvirt.volume.LibvirtFakeVolumeDriver," +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:135(para) +msgid "rbd=nova.virt.libvirt.volume.LibvirtNetVolumeDriver,sheepdog=nova.virt.libvirt.volume.LibvirtNetVolumeDriver\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:136(td) +msgid "(ListOpt) Libvirt handlers for remote volumes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:140(td) +msgid "libvirt_wait_soft_reboot_seconds=120" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:141(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/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:147(td) +msgid "limit_cpu_features=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:148(td) +msgid "(BoolOpt) Used by Hyper-V" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:152(td) +msgid "remove_unused_base_images=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:153(td) +msgid "(BoolOpt) Indicates whether unused base images should be removed" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:157(td) +msgid "remove_unused_kernels=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:158(td) +msgid "(BoolOpt) Indicates whether unused kernels should be removed. If using shared storage, this option is only safe to enable if all compute nodes have been updated to support this option." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:164(td) +msgid "remove_unused_original_minimum_age_seconds=86400" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:165(td) +msgid "(IntOpt) Unused unresized base images younger than this will not be removed" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:169(td) +msgid "remove_unused_resized_minimum_age_seconds=3600" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:170(td) +msgid "(IntOpt) Unused resized base images younger than this will not be removed" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:174(td) +msgid "rescue_image_id=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:175(td) +msgid "(StrOpt) Rescue ami image" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:178(td) +msgid "rescue_kernel_id=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:179(td) +msgid "(StrOpt) Rescue aki image" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:182(td) +msgid "rescue_ramdisk_id=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:183(td) +msgid "(StrOpt) Rescue ari image" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:186(td) +msgid "snapshot_image_format=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:187(td) +msgid "(StrOpt) Snapshot image format (valid options are : raw, qcow2, vmdk, vdi). Defaults to same as source image" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:192(td) +msgid "use_usb_tablet=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:193(td) +msgid "(BoolOpt) Sync virtual and real mouse cursors in Windows VMs" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:197(td) +msgid "libvirt integration" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:201(td) +msgid "libvirt_ovs_bridge=br-int" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:202(td) +msgid "(StrOpt) Name of Integration Bridge used by Open vSwitch" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:206(td) +msgid "libvirt_use_virtio_for_bridges=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:207(td) +msgid "(BoolOpt) Use virtio for bridge interfaces" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:210(td) +msgid "VMWare integration" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:214(td) +msgid "vmwareapi_wsdl_loc=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:215(td) +msgid "(StrOpt) VIM Service WSDL Location e.g http://<server>/vimService.wsdl, due to a bug in vSphere ESX 4.1 default wsdl." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:221(td) +msgid "vmware_vif_driver=nova.virt.vmwareapi.vif.VMWareVlanBridgeDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:223(td) +msgid "(StrOpt) The VMWare VIF driver to configure the VIFs." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:227(td) +msgid "vmwareapi_api_retry_count=10" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:228(td) +msgid "(FloatOpt) The number of times we retry on failures, e.g., socket error, etc. Used only if compute_driver is vmwareapi.VMWareESXDriver." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:233(td) +msgid "vmwareapi_host_ip=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:234(td) +msgid "(StrOpt) URL for connection to VMWare ESX host.Required if compute_driver is vmwareapi.VMWareESXDriver." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:239(td) +msgid "vmwareapi_host_password=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:240(td) +msgid "(StrOpt) Password for connection to VMWare ESX host. Used only if compute_driver is vmwareapi.VMWareESXDriver." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:245(td) +msgid "vmwareapi_host_username=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:246(td) +msgid "(StrOpt) Username for connection to VMWare ESX host. Used only if compute_driver is vmwareapi.VMWareESXDriver." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:251(td) +msgid "vmwareapi_task_poll_interval=5.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:252(td) +msgid "(FloatOpt) The interval used for polling of remote tasks. Used only if compute_driver is vmwareapi.VMWareESXDriver," +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:257(td) +msgid "vmwareapi_vlan_interface=vmnic0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:258(td) +msgid "(StrOpt) Physical ethernet adapter name for vlan networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:262(td) +msgid "powervm_mgr_type=ivm" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:263(td) +msgid "(StrOpt) PowerVM system manager type (ivm, hmc)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:266(td) +msgid "powervm_mgr=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:267(td) +msgid "(StrOpt) PowerVM manager host or ip" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:270(td) +msgid "powervm_vios=powervm_mgr" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:271(td) +msgid "(StrOpt) PowerVM VIOS host or ip if different from manager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:274(td) +msgid "powervm_mgr_user=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:275(td) +msgid "(StrOpt) PowerVM manager user name" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:278(td) +msgid "powervm_mgr_passwd=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:279(td) +msgid "(StrOpt) PowerVM manager user password" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:282(td) +msgid "powervm_img_remote_path=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:283(td) +msgid "(StrOpt) PowerVM image remote path. Used to copy and store images from Glance on the PowerVM VIOS LPAR." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:287(td) +msgid "powervm_img_local_path=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml:288(td) +msgid "(StrOpt) Local directory on the compute host to download glance images to." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for compute nodes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:16(para) +msgid "base_dir_name=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:17(para) +msgid "(StrOpt) Directory where cached images are stored under directory indicated with instances_path" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:20(para) +msgid "compute_driver=nova.virt.connection.get_connection" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:22(para) +msgid "(StrOpt) Driver to use for controlling virtualization" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:26(para) +msgid "console_host=MGG2WEDRJM" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:27(para) +msgid "(StrOpt) Console proxy host to use to connect to instances on this host." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:31(para) +msgid "default_notification_level=INFO" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:32(para) +msgid "(StrOpt) Default notification level for outgoing notifications" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:36(para) +msgid "default_publisher_id=$host" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:37(para) +msgid "(StrOpt) Default publisher_id for outgoing notifications" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:41(para) +msgid "heal_instance_info_cache_interval=60" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:42(para) +msgid "(IntOpt) Number of seconds between instance info_cache self healing updates" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:46(para) +msgid "host_state_interval=120" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:47(para) +msgid "(IntOpt) Interval in seconds for querying the host status" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:51(para) +msgid "image_cache_manager_interval=40" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:52(para) +msgid "(IntOpt) Number of periodic scheduler ticks to wait between runs of the image cache manager." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:57(para) +msgid "instances_path=$state_path/instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:58(para) +msgid "(StrOpt) where instances are stored on disk" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:62(para) +msgid "reboot_timeout=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:63(para) +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/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:68(para) +msgid "rescue_timeout=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:69(para) +msgid "(IntOpt) Automatically unrescue an instance after N seconds. Set to 0 to disable." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:73(para) +msgid "resize_confirm_window=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:74(para) +msgid "(IntOpt) Automatically confirm resizes after N seconds. Set to 0 to disable." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:78(para) +msgid "running_deleted_instance_action=log" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:79(para) +msgid "(StrOpt) Action to take if a running deleted instance is detected.Valid options are 'noop', 'log' and 'reap'. Set to 'noop' to disable." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:84(para) +msgid "running_deleted_instance_poll_interval=30" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:85(para) +msgid "(IntOpt) Number of periodic scheduler ticks to wait between runs of the cleanup task." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:89(para) +msgid "running_deleted_instance_timeout=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/compute-nodes-nova-conf.xml:90(para) +msgid "(IntOpt) Number of seconds after being deleted when a running instance should be considered eligible for cleanup." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:4(caption) +msgid "Description of nova.conf configuration options for authentication" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:16(td) +msgid "auth_strategy=noauth" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:17(td) +msgid "(StrOpt) The strategy to use for authentication. Supports noauth or keystone." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:21(td) +msgid "auth_token_ttl=3600" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:22(td) +msgid "(IntOpt) Seconds for auth tokens to linger" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:25(td) +msgid "ldap_cloudadmin=cn=cloudadmins,ou=Groups,dc=example,dc=com" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:27(td) +msgid "(StrOpt) cn for Cloud Admins" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:30(td) +msgid "ldap_developer=cn=developers,ou=Groups,dc=example,dc=com" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:32(td) +msgid "(StrOpt) cn for Developers" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:35(td) +msgid "ldap_itsec=cn=itsec,ou=Groups,dc=example,dc=com" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:36(td) +msgid "(StrOpt) cn for ItSec" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:39(td) +msgid "ldap_netadmin=cn=netadmins,ou=Groups,dc=example,dc=com" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:41(td) +msgid "(StrOpt) cn for NetAdmins" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:44(td) +msgid "ldap_password=changeme" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:48(td) +msgid "ldap_project_subtree=ou=Groups,dc=example,dc=com" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:57(td) +msgid "ldap_sysadmin=cn=sysadmins,ou=Groups,dc=example,dc=com" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:59(td) +msgid "(StrOpt) cn for Sysadmins" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:62(td) +msgid "ldap_url=ldap://localhost" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:66(td) +msgid "ldap_user_dn=cn=Manager,dc=example,dc=com" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:67(td) +msgid "(StrOpt) DN of admin user" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:70(td) +msgid "ldap_user_id_attribute=uid" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:79(td) +msgid "ldap_user_name_attribute=cn" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:83(td) +msgid "ldap_user_subtree=ou=Users,dc=example,dc=com" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:87(td) +msgid "ldap_user_unit=Users" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:91(td) +msgid "role_project_subtree=ou=Groups,dc=example,dc=com" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:98(td) +msgid "(ListOpt) Allowed roles for project" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:133(td) +msgid "(ListOpt) Roles that apply to all projects" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/auth-nova-conf.xml:143(td) +msgid "(StrOpt) Template for creating users VPN file" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for volumes attached to VMs" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:16(para) +msgid "cinder_cross_az_attach=True" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:17(para) +msgid "(BoolOpt) Allow attach between instance and volume in different availability zones." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:21(para) +msgid "iscsi_helper=ietadm" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:22(para) +msgid "(StrOpt) iscsi target user-land tool to use" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:25(para) +msgid "iscsi_ip_address=$my_ip" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:26(para) +msgid "(StrOpt) use this ip for iscsi" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:29(para) +msgid "iscsi_num_targets=100" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:30(para) +msgid "(IntOpt) Number of iscsi target ids per host" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:34(para) +msgid "iscsi_port=3260" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:35(para) +msgid "(IntOpt) The port that the iSCSI daemon is listening on" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:39(para) +msgid "iscsi_target_prefix=iqn.2010-10.org.openstack:" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:40(para) +msgid "(StrOpt) prefix for iscsi volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:43(para) +msgid "num_iscsi_scan_tries=3" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:44(para) +msgid "(StrOpt) number of times to rescan iSCSI target to find volume" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:48(para) +msgid "num_shell_tries=3" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:49(para) +msgid "(StrOpt) number of times to attempt to run flakey shell commands" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:53(para) +msgid "rbd_pool=rbd" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:54(para) +msgid "(StrOpt) the RADOS pool in which rbd volumes are stored" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:58(para) +msgid "rbd_secret_uuid=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:59(para) +msgid "(StrOpt) the libvirt uuid of the secret for the rbd_uservolumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:63(para) +msgid "rbd_user=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:64(para) +msgid "(StrOpt) the RADOS client name for accessing rbd volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:68(para) +msgid "volume_group=nova-volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:69(para) +msgid "(StrOpt) Name for the VG that will contain exported volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:73(para) +msgid "netapp_login=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:74(para) +msgid "(StrOpt) User name for the DFM server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:77(para) +msgid "netapp_password=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:78(para) +msgid "(StrOpt) Password for the DFM server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:81(para) +msgid "netapp_server_hostname=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:82(para) +msgid "(StrOpt) Hostname for the DFM server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:85(para) +msgid "netapp_server_port=8088" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:86(para) +msgid "(IntOpt) Port number for the DFM server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:89(para) +msgid "netapp_storage_service=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:90(para) +msgid "(StrOpt) Storage service to use for provisioning" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:94(para) +msgid "netapp_vfiler=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:95(para) +msgid "(StrOpt) Vfiler to use for provisioning" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:98(para) +msgid "netapp_wsdl_url=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:99(para) +msgid "(StrOpt) URL of the WSDL file for the DFM server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:103(para) +msgid "nexenta_blocksize=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:104(para) +msgid "(StrOpt) block size for volumes (blank=default,8KB)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:108(para) +msgid "nexenta_host=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:109(para) +msgid "(StrOpt) IP address of Nexenta SA" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:112(para) +msgid "nexenta_iscsi_target_portal_port=3260" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:113(para) +msgid "(IntOpt) Nexenta target portal port" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:116(para) +msgid "nexenta_password=nexenta" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:117(para) +msgid "(StrOpt) Password to connect to Nexenta SA" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:120(para) +msgid "nexenta_rest_port=2000" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:121(para) +msgid "(IntOpt) HTTP port to connect to Nexenta REST API server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:125(para) +msgid "nexenta_rest_protocol=auto" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:126(para) +msgid "(StrOpt) Use http or https for REST connection (default auto)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:130(para) +msgid "nexenta_sparse=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:131(para) +msgid "(BoolOpt) flag to create sparse volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:134(para) +msgid "nexenta_target_group_prefix=nova/" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:135(para) +msgid "(StrOpt) prefix for iSCSI target groups on SA" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:139(para) +msgid "nexenta_target_prefix=iqn.1986-03.com.sun:02:nova-" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:141(para) +msgid "(StrOpt) IQN prefix for iSCSI targets" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:144(para) +msgid "nexenta_user=admin" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:145(para) +msgid "(StrOpt) User name to connect to Nexenta SA" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:148(para) +msgid "nexenta_volume=nova" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:149(para) +msgid "(StrOpt) pool on SA that will hold all volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:153(para) +msgid "san_clustername=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:154(para) +msgid "(StrOpt) Cluster name to use for creating volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:158(para) +msgid "san_ip=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:159(para) +msgid "(StrOpt) IP address of SAN controller" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:162(para) +msgid "san_is_local=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:163(para) +msgid "(BoolOpt) Execute commands locally instead of over SSH; use if the volume service is running on the SAN device" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:168(para) +msgid "san_login=admin" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:169(para) +msgid "(StrOpt) Username for SAN controller" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:172(para) +msgid "san_password=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:173(para) +msgid "(StrOpt) Password for SAN controller" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:176(para) +msgid "san_private_key=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:177(para) +msgid "(StrOpt) Filename of private key to use for SSH authentication" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:181(para) +msgid "san_ssh_port=22" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:182(para) +msgid "(IntOpt) SSH port to use with SAN" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:185(para) +msgid "san_thin_provision=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:186(para) +msgid "(BoolOpt) Use thin provisioning for SAN volumes?" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:190(para) +msgid "san_zfs_volume_base=rpool/" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/volumes-nova-conf.xml:191(para) +msgid "(StrOpt) The ZFS path under which to create zvols for volumes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for VNC access to guest instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:16(para) +msgid "novncproxy_base_url=http://127.0.0.1:6080/vnc_auto.html" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:18(para) +msgid "(StrOpt) location of VNC console proxy, in the form \"http://127.0.0.1:6080/vnc_auto.html\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:22(para) +msgid "vnc_enabled=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:23(para) +msgid "(BoolOpt) enable VNC related features" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:26(para) +msgid "vnc_keymap=en-us" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:27(para) +msgid "(StrOpt) keymap for vnc" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:30(para) +msgid "vncserver_listen=127.0.0.1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:31(para) +msgid "(StrOpt) IP address on which instance VNC servers should listen" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:35(para) +msgid "vncserver_proxyclient_address=127.0.0.1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:36(para) +msgid "(StrOpt) the address to which proxy clients (like nova-xvpvncproxy) should connect" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:40(para) +msgid "xvpvncproxy_base_url=http://127.0.0.1:6081/console" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:42(para) +msgid "(StrOpt) location of nova XCP VNC console proxy, in the form \"http://127.0.0.1:6081/console\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:46(para) +msgid "xvpvncproxy_host=0.0.0.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:47(para) +msgid "(StrOpt) Address that the XCP VNC proxy should bind to" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:51(para) +msgid "xvpvncproxy_port=6081" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/vnc-guests-nova-conf.xml:52(para) +msgid "(IntOpt) Port that the XCP VNC proxy should bind to" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for testing purposes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:16(para) +msgid "allowed_rpc_exception_modules=['nova.exception']" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:17(para) +msgid "(IntOpt) Modules of exceptions that are permitted to be recreated upon receiving exception data from an rpc call" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:22(para) +msgid "consoleauth_topic=consoleauth" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:23(para) +msgid "(StrOpt) the topic console auth proxy nodes listen on" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:28(para) +msgid "fake_tests=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:29(para) +msgid "(BoolOpt) should we use everything for testing" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:33(para) +msgid "find_host_timeout=30" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:34(para) +msgid "(StrOpt) Timeout after NN seconds when looking for a host" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:38(para) +msgid "rpc_conn_pool_size=30" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:39(para) +msgid "(IntOpt) Size of RPC connection pool" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:42(para) +msgid "rpc_response_timeout=60" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:43(para) +msgid "(IntOpt) Seconds to wait for a response from call or multicall" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:47(para) +msgid "rpc_thread_pool_size=1024" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:48(para) +msgid "(IntOpt) Size of RPC thread pool" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:52(para) +msgid "storage_availability_zone=nova" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:53(para) +msgid "(StrOpt) availability zone of this service" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:56(para) +msgid "use_local_volumes=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:57(para) +msgid "(BoolOpt) if True, will not discover local volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:61(para) +msgid "volume_driver=nova.volume.driver.ISCSIDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:62(para) +msgid "(StrOpt) Driver to use for volume creation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:65(para) +msgid "volume_force_update_capabilities=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/nova-testing-nova-conf.xml:66(para) +msgid "(BoolOpt) if True will force update capabilities on each check" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:4(caption) +msgid "Description of nova.conf configuration options for databases" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:17(td) ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:21(para) +msgid "db_backend=sqlalchemy" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:18(td) ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:22(para) +msgid "(StrOpt) The backend to use for db" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:21(td) +msgid "db_driver=nova.db" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:22(td) +msgid "(StrOpt) driver to use for database access" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:25(td) +msgid "sql_connection=sqlite:///$state_path/$sqlite_db" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:26(td) ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:92(para) +msgid "(StrOpt) The SQLAlchemy connection string used to connect to the database" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:30(td) +msgid "sql_connection_debug=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:31(td) +msgid "(IntOpt) Verbosity of SQL debugging information. 0=None, 100=Everything" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:35(td) +msgid "sql_connection_trace=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:36(td) +msgid "(BoolOpt) Add python stack traces to SQL as comment strings" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:39(td) +msgid "sql_idle_timeout=3600" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:40(td) +msgid "(IntOpt) timeout before idle sql connections are reaped" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:44(td) +msgid "sql_max_retries=10" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:45(td) +msgid "(IntOpt) maximum db connection retries during startup. (setting -1 implies an infinite retry count)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:50(td) +msgid "sql_retry_interval=10" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:51(td) +msgid "(IntOpt) interval between retries of opening a sql connection" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:55(td) +msgid "sqlite_clean_db=clean.sqlite" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:56(td) +msgid "(StrOpt) File name of clean sqlite db" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:59(td) +msgid "sqlite_db=nova.sqlite" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:60(td) +msgid "(StrOpt) the filename to use with sqlite" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:63(td) +msgid "sqlite_synchronous=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:64(td) +msgid "(BoolOpt) If passed, use synchronous mode for sqlite" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:68(td) +msgid "sql_max_pool_size=5" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:71(literal) +msgid "pool_size" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:69(td) +msgid "(IntOpt) Maximum number of SQL connections to keep open in a pool. If set, this value is used for within sqlalchemy." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:75(td) +msgid "sql_min_pool_size=1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:76(td) +msgid "(IntOpt) Minimum number of SQL connections to keep open in a pool." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:81(td) +msgid "sql_max_overflow=None" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:83(literal) +msgid "max_overflow" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:82(td) +msgid "(IntOpt) If set, this value is used as within sqlalchemy." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:87(td) +msgid "sql_dbpool_enable=False" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:89(literal) +msgid "dbpool" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/database-nova-conf.xml:88(td) +msgid "(IntOpt) Enable the use of eventlet's for MySQL." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for networking options" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:16(para) +msgid "allow_same_net_traffic=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:17(para) +msgid "(BoolOpt) Whether to allow network traffic from same network" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:21(para) +msgid "defer_iptables_apply=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:22(para) +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/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:28(para) +msgid "dhcp_lease_time=120" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:29(para) +msgid "(IntOpt) Lifetime of a DHCP lease in seconds" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:33(para) +msgid "dhcpbridge=$bindir/nova-dhcpbridge" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:34(para) +msgid "(StrOpt) location of nova-dhcpbridge" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:37(para) +msgid "dhcpbridge_flagfile=/etc/nova/nova-dhcpbridge.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:39(para) +msgid "(StrOpt) location of flagfile for dhcpbridge" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:43(para) +msgid "dmz_cidr=10.128.0.0/24" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:44(para) +msgid "(StrOpt) dmz range that should be accepted" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:47(para) +msgid "dns_server=[]" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:48(para) +msgid "(MultiStrOpt) if set, uses specific dns server for dnsmasq. Can be specified multiple times." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:52(para) +msgid "use_network_dns_servers=False" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:53(para) +msgid "(BoolOpt) if set, uses the dns server from the node's network settings for the servers in dnsmasq." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:57(para) +msgid "dnsmasq_config_file=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:58(para) +msgid "(StrOpt) Override the default dnsmasq settings with this file" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:62(para) +msgid "linuxnet_interface_driver=nova.network.linux_net.LinuxBridgeInterfaceDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:64(para) +msgid "(StrOpt) Driver used to create ethernet devices." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:68(para) +msgid "linuxnet_ovs_integration_bridge=br-int" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:69(para) +msgid "(StrOpt) Name of Open vSwitch bridge used with linuxnet" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:74(para) +msgid "network_device_mtu=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:75(para) +msgid "(StrOpt) MTU setting for vlan" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:78(para) +msgid "networks_path=$state_path/networks" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:79(para) +msgid "(StrOpt) Location to keep network config files" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:83(para) +msgid "public_interface=eth0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:84(para) +msgid "(StrOpt) Interface for public IP addresses" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:87(para) +msgid "routing_source_ip=$my_ip" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:88(para) +msgid "(StrOpt) Public IP of network host" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:91(para) +msgid "send_arp_for_ha=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:92(para) +msgid "(BoolOpt) send gratuitous ARPs for HA setup" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:95(para) +msgid "use_single_default_gateway=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:96(para) +msgid "(BoolOpt) Use single default gateway. Only first nic of vm will get default gateway from dhcp server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:101(para) +msgid "auto_assign_floating_ip=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:102(para) +msgid "(BoolOpt) Autoassigning floating IP to VM" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:105(para) +msgid "cnt_vpn_clients=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:106(para) +msgid "(IntOpt) Number of addresses reserved for vpn clients" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:110(para) +msgid "create_unique_mac_address_attempts=5" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:111(para) +msgid "(IntOpt) Number of attempts to create unique mac address" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:115(para) +msgid "default_floating_pool=nova" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:116(para) +msgid "(StrOpt) Default pool for floating ips" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:119(para) +msgid "dhcp_domain=novalocal" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:120(para) +msgid "(StrOpt) domain to use for building the hostnames" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:124(para) +msgid "fake_call=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:125(para) +msgid "(BoolOpt) If True, skip using the queue and make local calls" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:129(para) +msgid "fixed_ip_disassociate_timeout=600" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:130(para) +msgid "(IntOpt) Seconds after which a deallocated IP is disassociated" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:134(para) +msgid "fixed_range=10.0.0.0/8" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:135(para) +msgid "(StrOpt) Fixed IP address block" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:139(para) +msgid "flat_injected=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:140(para) +msgid "(BoolOpt) Whether to attempt to inject network setup into guest" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:144(para) +msgid "flat_interface=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:145(para) +msgid "(StrOpt) FlatDhcp will bridge into this interface if set" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:149(para) +msgid "flat_network_bridge=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:150(para) +msgid "(StrOpt) Bridge for simple network instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:154(para) +msgid "flat_network_dns=8.8.4.4" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:155(para) +msgid "(StrOpt) Dns for simple network" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:158(para) +msgid "floating_range=4.4.4.0/24" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:159(para) +msgid "(StrOpt) Floating IP address block" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:162(para) +msgid "force_dhcp_release=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:163(para) +msgid "(BoolOpt) If True, send a dhcp release on instance termination" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:167(para) +msgid "gateway=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:168(para) +msgid "(StrOpt) Default IPv4 gateway" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:172(para) +msgid "l3_lib=nova.network.l3.LinuxNetL3" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:173(para) +msgid "(StrOpt) Indicates underlying L3 management library" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:177(para) +msgid "multi_host=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:178(para) +msgid "(BoolOpt) Default value for multi_host in networks. Enable when using nova networking (not quantum) on multiple compute nodes for creation and runtime efficiency. Also provides incremental fault tolerance." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:184(para) +msgid "share_dhcp_address=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:185(para) +msgid "(BoolOpt) If True and multi_host is also true all compute hosts will share the same dhcp address." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:190(para) +msgid "update_dns_entries=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:191(para) +msgid "(BoolOpt) True will message all network hosts to update their DNS entries when update occurs. Useful when multi_host is True." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:196(para) +msgid "network_host=MGG2WEDRJM" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:197(para) +msgid "(StrOpt) Network host to use for IP allocation in flat modes" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:201(para) +msgid "network_size=256" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:202(para) +msgid "(IntOpt) Number of addresses in each private subnet" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:206(para) +msgid "num_networks=1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:207(para) +msgid "(IntOpt) Number of networks to support" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:210(para) +msgid "vlan_interface=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:211(para) +msgid "(StrOpt) VLANs will bridge into this interface if set" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:215(para) +msgid "vlan_start=100" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:216(para) +msgid "(IntOpt) First VLAN for private networks" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:219(para) +msgid "vpn_ip=$my_ip" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:220(para) +msgid "(StrOpt) Public IP for the cloudpipe VPN servers" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:224(para) +msgid "vpn_start=1000" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:225(para) +msgid "(IntOpt) First VPN port for private networks" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:229(para) +msgid "CloudPipe specifics" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:233(para) +msgid "boot_script_template=$pybasedir/nova/cloudpipe/bootscript.template" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:235(para) +msgid "(StrOpt) Template for cloudpipe instance boot script" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:239(para) +msgid "dmz_mask=255.255.255.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:240(para) +msgid "(StrOpt) Netmask to push into openvpn config" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:244(para) +msgid "dmz_net=10.0.0.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:245(para) +msgid "(StrOpt) Network to push into openvpn config" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:249(para) +msgid "vpn_instance_type=m1.tiny" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:250(para) +msgid "(StrOpt) Instance type for vpn instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:253(para) +msgid "Quantum specifics" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:257(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:481(para) +msgid "network_api_class=nova.network.api.API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:258(para) +msgid "(StrOpt) Defaults to nova-network. Must be modified to nova.network.quantumv2.api.API indicate that Quantum should be used rather than the traditional nova-network networking model." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:264(para) +msgid "quantum_url=http://127.0.0.1:9696" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:265(para) +msgid "(IntOpt) URL for connecting to the Quantum networking service. Indicates the hostname/IP and port of the Quantum server for your deployment." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:271(para) +msgid "quantum_auth_strategy=keystone" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:272(para) +msgid "(StrOpt) Should be kept as default 'keystone' for all production deployments." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:277(para) +msgid "quantum_admin_tenant_name=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:279(para) +msgid "(StrOpt) Tenant name for connecting to Quantum network services in admin context through the OpenStack Identity service." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:285(para) +msgid "quantum_admin_username=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:287(para) +msgid "(StrOpt) Username for connecting to Quantum network services in admin context through the OpenStack Identity service." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:292(para) +msgid "quantum_admin_password=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:294(para) +msgid "(StrOpt) Password for connecting to Quantum network services in admin context through the OpenStack Identity service." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:299(para) +msgid "quantum_admin_auth_url=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:301(para) +msgid "(StrOpt) Points to the OpenStack 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/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:307(para) +msgid "quantum_region_name=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:309(para) +msgid "(StrOpt) Region name for connecting to quantum in admin context, through the OpenStack Identity service," +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:314(para) +msgid "quantum_extension_sync_interval=<600>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/network-nova-conf.xml:316(para) +msgid "(IntOpt) Some OpenStack Networking (quantum) extensions require Compute (nova) to pass in additional fields based on which extension the Networking (quantum) service is running. This is the number of seconds that nova will wait before requerying." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for console access to VMs on VMWare VMRC or XenAPI" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:17(para) +msgid "console_driver=nova.console.xvp.XVPConsoleProxy" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:20(para) +msgid "(StrOpt) Driver to use for the console proxy" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:24(para) +msgid "console_public_hostname=MGG2WEDRJM" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:26(para) +msgid "(StrOpt) Publicly visible name for this console host" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:30(para) +msgid "stub_compute=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:31(para) +msgid "(BoolOpt) Stub calls to compute worker for tests" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:35(para) +msgid "console_vmrc_error_retries=10" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:36(para) +msgid "(IntOpt) number of retries for retrieving VMRC information" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:40(para) +msgid "console_vmrc_port=443" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:41(para) +msgid "(IntOpt) port for VMware VMRC connections" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:45(para) +msgid "console_xvp_conf=/etc/xvp.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:46(para) +msgid "(StrOpt) generated XVP conf file" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:50(para) +msgid "console_xvp_conf_template=$pybasedir/nova/console/xvp.conf.template" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:53(para) +msgid "(StrOpt) XVP conf template" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:56(para) +msgid "console_xvp_log=/var/log/xvp.log" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:58(para) +msgid "(StrOpt) XVP log file" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:61(para) +msgid "console_xvp_multiplex_port=5900" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:63(para) +msgid "(IntOpt) port for XVP to multiplex VNC connections on" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:67(para) +msgid "console_xvp_pid=/var/run/xvp.pid" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:69(para) +msgid "(StrOpt) XVP master process pid file" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:73(para) +msgid "xenapi_agent_path=usr/sbin/xe-update-networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:76(para) +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/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:84(para) +msgid "xenapi_connection_concurrent=5" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:85(para) +msgid "(IntOpt) Maximum number of concurrent XenAPI connections. Used only if compute_driver=xenapi.XenAPIDriver." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:90(para) +msgid "xenapi_connection_url=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:92(para) +msgid "(StrOpt) URL for connection to XenServer/Xen Cloud Platform. Required if compute_driver=xenapi.XenAPIDriver." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:97(para) +msgid "xenapi_connection_username=root" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:99(para) +msgid "(StrOpt) Password for connection to XenServer/Xen Cloud Platform. Used only if compute_driver=xenapi.XenAPIDriver." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:104(para) +msgid "xenapi_connection_password=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:106(para) +msgid "(StrOpt) Username for connection to XenServer/Xen Cloud Platform. Used only if compute_driver=xenapi.XenAPIDriver." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:111(para) +msgid "xenapi_check_host=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:112(para) +msgid "(BoolOpt) Ensure compute service is running on host XenAPI connects to." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:116(para) +msgid "xenapi_login_timeout=10" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:117(para) +msgid "(BoolOpt) Timeout in seconds for XenAPI login." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:120(para) +msgid "xenapi_remap_vbd_dev=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:121(para) +msgid "(BoolOpt) Used to enable the remapping of VBD dev. (Works around an issue in Ubuntu Maverick)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:126(para) +msgid "xenapi_remap_vbd_dev_prefix=sd" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:127(para) +msgid "(StrOpt) Specify prefix to remap VBD dev to (ex. /dev/xvdb -> /dev/sdb). Used when xenapi_remap_vbd_dev=true." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:132(para) +msgid "xenapi_sr_base_path=/var/run/sr-mount" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:133(para) +msgid "(StrOpt) Base path to the storage repository." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:136(para) +msgid "xenapi_vhd_coalesce_poll_interval=5.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:137(para) +msgid "(FloatOpt) The interval used for polling of coalescing vhds. Used only if compute_driver=xenapi.XenAPIDriver." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:141(para) +msgid "xenapi_vhd_coalesce_max_attempts=5" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/console-xenapi-vmrc-nova-conf.xml:142(para) +msgid "(IntOpt) Max number of times to poll for VHD to coalesce. Used only if compute_driver=xenapi.XenAPIDriver." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/spice-guests-nova-conf.xml:4(caption) +msgid "Description of nova.conf [spice] section configuration options for SPICE HTML5 access to guest instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/spice-guests-nova-conf.xml:16(para) +msgid "html5proxy_base_url=http://127.0.0.1:6080/spice_auto.html" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/spice-guests-nova-conf.xml:18(para) +msgid "(StrOpt) location of spice html5 console proxy, in the form \"http://127.0.0.1:6080/spice_auto.html\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/spice-guests-nova-conf.xml:22(para) +msgid "enabled=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/spice-guests-nova-conf.xml:23(para) +msgid "(BoolOpt) enable spice related features" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/spice-guests-nova-conf.xml:26(para) +msgid "agent_enabled=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/spice-guests-nova-conf.xml:27(para) +msgid "(BoolOpt) enable spice guest agent support" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/spice-guests-nova-conf.xml:30(para) +msgid "keymap=en-us" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/spice-guests-nova-conf.xml:31(para) +msgid "(StrOpt) keymap for spice" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/spice-guests-nova-conf.xml:34(para) +msgid "server_listen=127.0.0.1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/spice-guests-nova-conf.xml:35(para) +msgid "(StrOpt) IP address on which instance spice servers should listen" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/spice-guests-nova-conf.xml:39(para) +msgid "server_proxyclient_address=127.0.0.1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/spice-guests-nova-conf.xml:40(para) +msgid "(StrOpt) the address to which proxy clients (like nova-html5proxy) should connect" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:4(caption) +msgid "Description of nova.conf log file configuration options" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:16(td) +msgid "default_log_levels=\"amqplib=WARN,sqlalchemy=WARN,boto=WARN,suds=INFO,eventlet.wsgi.server=WARN\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:18(td) +msgid "(ListOpt) list of logger=LEVEL pairs" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:21(td) +msgid "instance_format=[instance: %(uuid)s]" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:22(td) +msgid "(StrOpt) If an instance is passed with the log message, format it like this" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:26(td) +msgid "instance_uuid_format=[instance: %(uuid)s]" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:27(td) +msgid "(StrOpt) If an instance UUID is passed with the log message, format it like this" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:31(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:396(para) +msgid "log_config=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:32(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:397(para) +msgid "(StrOpt) If this option is specified, the logging configuration file specified is used and overrides any other logging options specified. Please see the Python logging module documentation for details on logging configuration files." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:39(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:405(para) +msgid "log_date_format=%Y-%m-%d %H:%M:%S" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:40(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:407(para) +msgid "(StrOpt) Format string for %(asctime)s in log records. Default: %default" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:44(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:411(para) +msgid "log_dir=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:45(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:412(para) +msgid "(StrOpt) (Optional) The directory to keep log files in (will be prepended to --logfile)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:49(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:417(para) +msgid "log_file=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:50(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:418(para) +msgid "(StrOpt) (Optional) Name of log file to output to. If not set, logging will go to stdout." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:54(para) +msgid "log_format=\"%(asctime)s %(levelname)8s [%(name)s] %(message)s\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:55(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:425(para) +msgid "(StrOpt) A logging.Formatter log message format string which may use any of the available logging.LogRecord attributes. Default: %default" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:61(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:431(para) +msgid "logdir=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:62(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:432(para) +msgid "(StrOpt) Log output to a per-service log file in named directory" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:66(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:436(para) +msgid "logfile=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:67(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:437(para) +msgid "(StrOpt) Log output to a named file" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:70(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:441(para) +msgid "logfile_mode=0644" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:71(para) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:442(para) +msgid "(StrOpt) Default file mode used when creating log files" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:75(td) +msgid "logging_context_format_string=\"%(asctime)s %(levelname)s %(name)s [%(request_id)s %(user_id)s %(project_id)s] %(instance)s%(message)s\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:78(td) +msgid "(StrOpt) format string to use for log messages with context" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:82(td) +msgid "logging_debug_format_suffix=\"from (pid=%(process)d) %(funcName)s %(pathname)s:%(lineno)d\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:85(td) +msgid "(StrOpt) data to append to log format when level is DEBUG" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:89(td) +msgid "logging_default_format_string=\"%(asctime)s %(levelname)s %(name)s [-] %(instance)s%(message)s\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:92(td) +msgid "(StrOpt) format string to use for log messages without context" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:96(td) +msgid "logging_exception_prefix=\"%(asctime)s TRACE %(name)s %(instance)s\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:98(td) +msgid "(StrOpt) prefix each line of exception output with this format" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:102(td) ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:106(td) +msgid "publish_errors=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:103(td) ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:107(td) +msgid "(BoolOpt) publish error events" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:110(td) +msgid "use_syslog=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:111(td) +msgid "(BoolOpt) Use syslog for logging" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:114(td) +msgid "syslog_log_facility=LOG_USER" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/log-file-nova-conf.xml:115(td) ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:743(para) +msgid "(StrOpt) syslog facility to receive log lines" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ipv6-nova-conf.xml:4(caption) +msgid "Description of nova.conf configuration options for IPv6" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ipv6-nova-conf.xml:17(td) +msgid "fixed_range_v6=fd00::/48" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ipv6-nova-conf.xml:18(td) +msgid "(StrOpt) Fixed IPv6 address block" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ipv6-nova-conf.xml:21(td) +msgid "gateway_v6=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ipv6-nova-conf.xml:22(td) +msgid "(StrOpt) Default IPv6 gateway" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ipv6-nova-conf.xml:26(td) +msgid "ipv6_backend=rfc2462" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ipv6-nova-conf.xml:27(td) +msgid "(StrOpt) Backend to use for IPv6 generation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ipv6-nova-conf.xml:30(td) +msgid "use_ipv6=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/ipv6-nova-conf.xml:31(td) +msgid "(BoolOpt) use IPv6" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/s3-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for S3 access to image storage" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/s3-nova-conf.xml:16(td) +msgid "image_decryption_dir=/tmp" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/s3-nova-conf.xml:17(td) +msgid "(StrOpt) parent dir for tempdir used for image decryption" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/s3-nova-conf.xml:21(td) +msgid "s3_access_key=notchecked" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/s3-nova-conf.xml:22(td) +msgid "(StrOpt) access key to use for s3 server for images" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/s3-nova-conf.xml:26(td) +msgid "s3_affix_tenant=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/s3-nova-conf.xml:27(td) +msgid "(BoolOpt) whether to affix the tenant id to the access key when downloading from s3" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/s3-nova-conf.xml:31(td) +msgid "s3_secret_key=notchecked" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/s3-nova-conf.xml:32(td) +msgid "(StrOpt) secret key to use for s3 server for images" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/s3-nova-conf.xml:36(td) +msgid "s3_use_ssl=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/s3-nova-conf.xml:37(td) +msgid "(BoolOpt) whether to use ssl when talking to s3" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for schedulers that use algorithms to assign VM launch on particular compute hosts" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:17(para) +msgid "scheduler_host_manager=nova.scheduler.host_manager.HostManager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:19(para) +msgid "(StrOpt) The scheduler host manager class to use." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:23(para) +msgid "scheduler_max_attempts=3" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:25(para) +msgid "(IntOpt) Maximum number of attempts to schedule an instance before giving up and setting the instance to error." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:30(para) +msgid "cpu_allocation_ratio=16.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:31(para) +msgid "(FloatOpt) Virtual CPU to Physical CPU allocation ratio." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:35(para) +msgid "ram_allocation_ratio=1.5" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:36(para) +msgid "(FloatOpt) virtual ram to physical ram allocation ratio." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:40(para) +msgid "reserved_host_disk_mb=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:41(para) +msgid "(IntOpt) Amount of disk in MB to reserve for host/dom0." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:45(para) +msgid "reserved_host_memory_mb=512" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:46(para) +msgid "(IntOpt) Amount of memory in MB to reserve for host/dom0." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:50(para) +msgid "scheduler_available_filters=nova.scheduler.filters.all_filters" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:52(para) +msgid "(MultiStrOpt) Filter classes available to the scheduler which may be specified more than once. An entry of \"nova.scheduler.filters.all_filters\" maps to all filters included with nova." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:59(para) +msgid "scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:61(para) +msgid "(ListOpt) Which filter class names to use for filtering hosts when not specified in the request." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:66(para) +msgid "compute_fill_first_cost_fn_weight=-1.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:67(para) +msgid "(FloatOpt) How much weight to give the fill-first cost function. A negative value will reverse behavior: e.g. spread-first." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:72(para) +msgid "retry_host_cost_fn_weight=1.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:73(para) +msgid "(FloatOpt) How much weight to give the retry host cost function. A negative value will reverse behavior: e.g. use multiple-times-retried hosts first." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:78(para) +msgid "least_cost_functions=nova.scheduler.least_cost.compute_fill_first_cost_fn" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:80(para) +msgid "(ListOpt) Which cost functions the LeastCostScheduler should use." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:84(para) +msgid "noop_cost_fn_weight=1.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:85(para) +msgid "(FloatOpt) How much weight to give the noop cost function." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:89(para) +msgid "scheduler_driver=nova.scheduler.multi.MultiScheduler" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:91(para) +msgid "(StrOpt) Default driver to use for the scheduler." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:95(para) +msgid "compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:97(para) +msgid "(StrOpt) Driver to use for scheduling Compute calls." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:101(para) +msgid "volume_scheduler_driver=nova.scheduler.chance.ChanceScheduler" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:103(para) +msgid "(StrOpt) Driver to use for scheduling volume calls." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:109(para) +msgid "scheduler_json_config_location=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:110(para) +msgid "(StrOpt) Absolute path to scheduler configuration JSON file." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:114(para) +msgid "max_cores=16" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:115(para) +msgid "(IntOpt) maximum number of instance cores to allow per host." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:119(para) +msgid "max_gigabytes=10000" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:120(para) +msgid "(IntOpt) maximum number of volume gigabytes to allow per host." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:124(para) +msgid "max_networks=1000" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:125(para) +msgid "(IntOpt) maximum number of networks to allow per host." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:129(para) +msgid "skip_isolated_core_check=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:130(para) +msgid "(BoolOpt) Allow overcommitting vcpus on isolated hosts." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:134(para) +msgid "scheduler_host_subset_size=1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/scheduler-nova-conf.xml:136(para) +msgid "(IntOpt) New instances will be scheduled on a host chosen randomly from a subset of the N best hosts, rather than just the host with the highest weight. 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/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:4(caption) +msgid "Description of common nova.conf configuration options for the Compute API, RabbitMQ, EC2 API, S3 API, instance types" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:17(para) +msgid "allow_resize_to_same_host=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:19(para) +msgid "(BoolOpt) Allow destination machine to match source for resize. Useful when testing in single-host environments. If you have separate configuration files for separate services, this flag is required on both nova-api and nova-compute." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:27(para) +msgid "api_paste_config=api-paste.ini" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:28(para) +msgid "(StrOpt) File name for the paste.deploy config for nova-api" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:32(para) +msgid "api_rate_limit=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:33(para) +msgid "(BoolOpt) whether to rate limit the Compute API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:37(para) +msgid "api_url=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:38(para) +msgid "(StrOpt) URL for the Zone's Auth API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:42(para) +msgid "auth_blob=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:43(para) +msgid "(StrOpt) To be written, found in /nova/scheduler/filters/trusted_filter.py, related to FLAGS.trusted_computing.auth_blob." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:49(para) +msgid "aws_access_key_id=admin" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:50(para) +msgid "(StrOpt) AWS Access ID" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:53(para) +msgid "aws_secret_access_key=admin" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:54(para) +msgid "(StrOpt) AWS Access Key" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:57(para) +msgid "backdoor_port=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:58(para) +msgid "(IntOpt) Port for eventlet backdoor to listen" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:62(para) +msgid "bandwidth_poll_interval=600" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:63(para) +msgid "(IntOpt) Interval to pull bandwidth usage info" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:67(para) +msgid "bindir=$pybasedir/bin" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:68(para) +msgid "(StrOpt) Directory where nova binaries are installed" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:72(para) +msgid "cache_images=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:73(para) +msgid "(BoolOpt) Cache glance images locally" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:77(para) +msgid "cert_manager=nova.cert.manager.CertManager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:79(para) +msgid "(StrOpt) full class name for the Manager for cert" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:83(para) +msgid "cert_topic=cert" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:84(para) +msgid "(StrOpt) the topic cert nodes listen on" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:88(para) +msgid "claim_timeout_seconds=600" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:89(para) +msgid "(IntOpt) Found in /nova/compute/resource_tracker.py" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:93(para) +msgid "compute_api_class=nova.compute.api.API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:95(para) +msgid "(StrOpt) The full class name of the Compute API class to use" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:99(para) +msgid "compute_manager=nova.compute.manager.ComputeManager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:102(para) +msgid "(StrOpt) full class name for the Manager for compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:106(para) +msgid "compute_topic=compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:107(para) +msgid "(StrOpt) the topic compute nodes listen on" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:111(para) +msgid "config_file=/etc/nova/nova.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:112(para) +msgid "(MultiStrOpt) Path to a config file to use. Multiple config files can be specified, with values in later files taking precedence. The default files used are: []" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:118(td) +msgid "compute_driver='nova.virt.connection.get_connection'" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:119(td) +msgid "String value; Driver to use for controlling virtualization. For convenience if the driver exists under the nove.virt namespace, nova.virt can be removed. There are 5 drivers in core openstack: fake.FakeDriver, libvirt.LibvirtDriver, baremetal.BareMetalDriver, xenapi.XenAPIDriver, vmwareapi.VMWareESXDriver. If nothing is specified the older connection_type mechanism will be used. Be aware that method will be removed after the Folsom release." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:131(td) +msgid "connection_type='libvirt' (Deprecated)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:132(td) +msgid "libvirt, xenapi, hyperv, or fake; Value that indicates the virtualization connection type. Deprecated as of Folsom, will be removed in G release." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:138(para) +msgid "console_manager=nova.console.manager.ConsoleProxyManager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:141(para) +msgid "(StrOpt) full class name for the Manager for console proxy" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:145(para) +msgid "console_topic=console" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:146(para) +msgid "(StrOpt) the topic console proxy nodes listen on" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:150(para) +msgid "control_exchange=nova" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:151(para) +msgid "(StrOpt) AMQP exchange to connect to if using RabbitMQ or Qpid for RPC (not Zeromq)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:154(para) +msgid "Currently you cannot set different exchange values for volumes and networks, for example." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:160(para) +msgid "debug=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:161(para) +msgid "(BoolOpt) Print debugging output" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:165(para) +msgid "default_access_ip_network_name=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:167(para) +msgid "(StrOpt) Name of network to use to set access ips for instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:171(para) +msgid "default_ephemeral_format=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:173(para) +msgid "(StrOpt) The default format an ephemeral_volume will be formatted with on creation." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:178(para) +msgid "default_image=ami-11111" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:179(para) +msgid "(StrOpt) default image to use, testing only" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:183(para) +msgid "default_instance_type=m1.small" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:184(para) +msgid "(StrOpt) default instance type to use, testing only" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:188(para) +msgid "default_project=openstack" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:189(para) +msgid "(StrOpt) the default project to use for OpenStack" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:193(para) +msgid "default_schedule_zone=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:195(para) +msgid "(StrOpt) availability zone to use when user doesn't specify one" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:199(para) +msgid "default_scheduler_driver=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:204(para) +msgid "disable_process_locking=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:205(para) +msgid "(BoolOpt) Whether to disable inter-process locks" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:209(para) +msgid "ec2_dmz_host=$my_ip" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:210(para) +msgid "(StrOpt) the internal IP address of the EC2 API server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:214(para) +msgid "ec2_host=$my_ip" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:215(para) +msgid "(StrOpt) the IP of the ec2 api server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:219(para) +msgid "ec2_path=/services/Cloud" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:220(para) +msgid "(StrOpt) the path prefix used to call the EC2 API server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:224(para) +msgid "ec2_port=8773" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:225(para) +msgid "(IntOpt) the port of the EC2 API server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:229(para) +msgid "ec2_scheme=http" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:230(para) +msgid "(StrOpt) the protocol to use when connecting to the EC2 API server (http, https)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:235(para) +msgid "ec2_strict_validation=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:236(para) +msgid "(BoolOpt) Enables strict validation for EC2 API server requests" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:240(para) +msgid "ec2_workers=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:241(para) +msgid "(StrOpt) To be written; Found in /nova/service.py" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:245(para) +msgid "enable_instance_password=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:246(para) +msgid "(BoolOpt) When true, Compute creates a random password for the instance at create time. Users can get the password from the return value of API call for the instance creation (or through their Dashboard if the Dashboard returns the password visibly). Note that the password isn't stored anywhere, it is returned only once." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:256(para) +msgid "enabled_apis=ec2,osapi_compute,osapi_volume,metadata" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:259(para) +msgid "(ListOpt) a list of APIs to enable by default" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:263(para) +msgid "fake_network=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:264(para) +msgid "(BoolOpt) If passed, use fake network devices and addresses" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:268(para) +msgid "fake_rabbit=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:269(para) +msgid "(BoolOpt) If passed, use a fake RabbitMQ provider" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:273(para) +msgid "fatal_deprecations=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:274(para) +msgid "(BoolOpt) To be written; Found in /nova/common/deprecated.py" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:278(para) +msgid "firewall_driver=nova.virt.firewall.libvirt.IptablesFirewallDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:280(para) +msgid "(StrOpt) Firewall driver (defaults to iptables)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:285(para) +msgid "floating_ip_dns_manager=nova.network.dns_driver.DNSDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:288(para) +msgid "(StrOpt) full class name for the DNS Manager for floating IPs" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:292(para) +msgid "glance_api_insecure=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:293(para) +msgid "(BoolOpt) Allow to perform insecure SSL (https) requests to glance" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:297(para) +msgid "glance_api_servers=$glance_host:$glance_port" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:300(para) +msgid "(ListOpt) A list of the glance API servers available to nova ([hostname|ip]:port)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:305(para) +msgid "glance_host=$my_ip" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:306(para) +msgid "(StrOpt) default glance hostname or IP" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:310(para) +msgid "glance_num_retries=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:311(para) +msgid "(IntOpt) Number retries when downloading an image from glance" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:315(para) +msgid "glance_port=9292" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:316(para) +msgid "(IntOpt) default glance port" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:319(para) +msgid "host=MGG2WEDRJM" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:320(para) +msgid "(StrOpt) Name of this node. This can be an opaque identifier. It is not necessarily a hostname, FQDN, or IP address." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:325(para) +msgid "image_info_filename_pattern=$instances_path/" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:328(para) +msgid "(StrOpt) Used for image caching; found in /nova/virt/libvirt/utils.py" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:332(para) +msgid "image_service=nova.image.glance.GlanceImageService" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:335(para) +msgid "(StrOpt) The service to use for retrieving and searching images." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:339(para) +msgid "instance_build_timeout=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:340(para) +msgid "(StrOpt) To be written; found in /nova/compute/manager.py" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:344(para) +msgid "instance_dns_domain=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:345(para) +msgid "(StrOpt) full class name for the DNS Zone for instance IPs" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:349(para) +msgid "instance_dns_manager=nova.network.dns_driver.DNSDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:352(para) +msgid "(StrOpt) full class name for the DNS Manager for instance IPs" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:356(para) +msgid "instance_usage_audit_period=month" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:358(para) +msgid "(StrOpt) time period to generate instance usages for. Time period must be hour, day, month or year" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:363(para) +msgid "instance_uuid_format= [instance: %(uuid)s]" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:365(para) +msgid "(StrOpt) To be written; found in /nova/openstack/common/log.py" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:369(para) +msgid "iptables_bottom_regex=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:370(para) +msgid "(StrOpt) Regular expressions to match iptables rules that should always be on the bottom." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:375(para) +msgid "iptables_top_regex=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:376(para) +msgid "(StrOpt) Regular expressions to match iptables rules that should always be on the top." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:381(para) +msgid "isolated_hosts=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:382(para) +msgid "(ListOpt) Host reserved for specific images" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:386(para) +msgid "isolated_images=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:387(para) +msgid "(ListOpt) Images to run on isolated host" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:391(para) +msgid "lock_path=$pybasedir" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:392(para) +msgid "(StrOpt) Directory to use for lock files" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:423(para) +msgid "log_format= \"%(asctime)s %(levelname)8s [%(name)s] %(message)s\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:446(para) +msgid "memcached_servers=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:447(para) +msgid "(ListOpt) Memcached servers or None for in process cache." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:451(para) +msgid "metadata_host=$my_ip" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:452(para) +msgid "(StrOpt) the IP address for the metadata API server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:456(para) +msgid "metadata_port=8775" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:457(para) +msgid "(IntOpt) the port for the metadata API port" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:461(para) +msgid "monkey_patch=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:462(para) +msgid "(BoolOpt) Whether to log monkey patching" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:466(para) +msgid "monkey_patch_modules=nova.api.ec2.cloud:nova.notifier.api.notify_decorator, nova.compute.api:nova.notifier.api.notify_decorator" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:470(para) +msgid "(ListOpt) List of modules/decorators to monkey patch" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:474(para) +msgid "my_ip=192.168.1.82" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:475(para) +msgid "(StrOpt) IP address of this host; change my_ip to match each host when copying nova.conf files to multiple hosts." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:483(para) +msgid "(StrOpt) The full class name of the network API class to use" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:487(para) +msgid "network_driver=nova.network.linux_net" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:489(para) +msgid "(StrOpt) Driver to use for network creation" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:493(para) +msgid "network_manager=nova.network.manager.VlanManager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:496(para) +msgid "(StrOpt) Full class name for the Manager for network" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:500(para) +msgid "network_topic=network" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:501(para) +msgid "(StrOpt) The topic network nodes listen on" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:505(para) +msgid "node_availability_zone=nova" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:506(para) +msgid "(StrOpt) Availability zone of this node" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:510(para) +msgid "non_inheritable_image_properties=['cache_in_nova', 'instance_uuid', 'user_id', 'image_type', 'backup_type', 'min_ram', 'min_disk']" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:515(para) +msgid "(ListOpt) These are image properties which a snapshot should not inherit from an instance" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:520(para) +msgid "notification_driver=nova.notifier.no_op_notifier" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:523(para) +msgid "(StrOpt) Default driver for sending notifications for RabbitMQ. By default, set to not send entries to the notifications.info queue. Set to nova.notifier.rabbit_notifier to send notifications." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:530(para) +msgid "null_kernel=nokernel" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:531(para) +msgid "(StrOpt) kernel image that indicates not to use a kernel, but to use a raw disk image instead" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:536(para) +msgid "osapi_compute_ext_list=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:537(para) +msgid "(ListOpt) Specify list of extensions to load when using osapi_compute_extension option with nova.api.openstack.compute.contrib.select_extensions" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:544(para) +msgid "osapi_compute_extension=nova.api.openstack.compute.contrib.standard_extensions" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:547(para) +msgid "(MultiStrOpt) Compute API extensions to load" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:551(para) +msgid "osapi_compute_link_prefix=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:553(para) +msgid "(StrOpt) Base URL that will be presented to users in links to the OpenStack Compute API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:558(para) +msgid "osapi_glance_link_prefix=<None>" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:560(para) +msgid "(StrOpt) Base URL that will be presented to users in links to glance resources" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:565(para) +msgid "osapi_max_limit=1000" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:566(para) +msgid "(IntOpt) the maximum number of items returned in a single response from a collection resource" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:571(para) +msgid "osapi_path=/v1.1/" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:572(para) +msgid "(StrOpt) the path prefix used to call the OpenStack Compute API server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:576(para) +msgid "osapi_scheme=http" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:577(para) +msgid "(StrOpt) the protocol to use when connecting to the OpenStack Compute API server (http, https)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:582(para) +msgid "osapi_volume_ext_list=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:583(para) +msgid "(ListOpt) Specify list of extensions to load when using osapi_volume_extension option with nova.api.openstack.volume.contrib.select_extensions" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:590(para) +msgid "osapi_volume_extension=nova.api.openstack.volume.contrib.standard_extensions" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:593(para) +msgid "(MultiStrOpt) osapi volume extension to load" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:597(para) +msgid "password_length=12" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:598(para) +msgid "(IntOpt) Length of generated instance admin passwords" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:602(para) +msgid "pybasedir=/usr/lib/python/site-packages" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:604(para) +msgid "(StrOpt) Directory where the nova python module is installed" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:608(para) +msgid "rabbit_durable_queues=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:609(para) +msgid "(BoolOpt) use durable queues in RabbitMQ" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:613(para) +msgid "rabbit_host=localhost" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:614(para) +msgid "(StrOpt) the RabbitMQ host" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:617(para) +msgid "rabbit_max_retries=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:618(para) +msgid "(IntOpt) maximum retries with trying to connect to RabbitMQ (the default of 0 implies an infinite retry count)" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:623(para) +msgid "rabbit_password=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:626(para) +msgid "(StrOpt) the RabbitMQ password" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:629(para) +msgid "rabbit_port=5672" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:630(para) +msgid "(IntOpt) the RabbitMQ port" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:633(para) +msgid "rabbit_retry_backoff=2" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:634(para) +msgid "(IntOpt) how long to backoff for between retries when connecting to RabbitMQ" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:639(para) +msgid "rabbit_retry_interval=1" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:640(para) +msgid "(IntOpt) how frequently to retry connecting with RabbitMQ" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:644(para) +msgid "rabbit_use_ssl=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:645(para) +msgid "(BoolOpt) connect over SSL for RabbitMQ" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:649(para) +msgid "rabbit_userid=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:651(para) +msgid "(StrOpt) the RabbitMQ userid" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:654(para) +msgid "rabbit_virtual_host=/" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:655(para) +msgid "(StrOpt) the RabbitMQ virtual host" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:659(para) +msgid "reclaim_instance_interval=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:660(para) +msgid "(IntOpt) Interval in seconds for reclaiming deleted instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:664(para) +msgid "region_list=" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:665(para) +msgid "(ListOpt) list of region=fqdn pairs separated by commas" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:669(para) +msgid "resume_guests_state_on_host_boot=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:671(para) +msgid "(BoolOpt) Whether to start guests that were running before the host rebooted. If enabled, this option causes guests assigned to the host to be restarted when nova-compute starts, if they had been active on the host while nova-compute last ran. If such a guest is already found to be running, it is left untouched." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:683(para) +msgid "rootwrap_config=sudo nova-rootwrap /etc/nova/rootwrap.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:685(para) +msgid "(StrOpt) Command prefix to use for running commands as root. Note that the configuration file (and executable) used here must match the one defined in the sudoers entry from packagers, otherwise the commands are rejected." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:693(para) +msgid "s3_dmz=$my_ip" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:694(para) +msgid "(StrOpt) hostname or IP for the instances to use when accessing the S3 API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:698(para) +msgid "s3_host=$my_ip" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:699(para) +msgid "(StrOpt) hostname or IP for OpenStack to use when accessing the S3 API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:703(para) +msgid "s3_port=3333" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:704(para) +msgid "(IntOpt) port used when accessing the S3 API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:708(para) +msgid "scheduler_manager=nova.scheduler.manager.SchedulerManager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:711(para) +msgid "(StrOpt) full class name for the Manager for scheduler" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:715(para) +msgid "scheduler_topic=scheduler" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:716(para) +msgid "(StrOpt) the topic scheduler nodes listen on" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:720(para) +msgid "security_group_handler=nova.network.quantum.sg.NullSecurityGroupHandler" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:723(para) +msgid "(StrOpt) The full class name of the security group handler class" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:727(para) +msgid "service_down_time=60" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:728(para) +msgid "(IntOpt) maximum time since last check-in for up service" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:732(para) +msgid "state_path=$pybasedir" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:733(para) +msgid "(StrOpt) Top-level directory for maintaining nova's state" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:737(para) +msgid "stub_network=False" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:738(para) +msgid "(StrOpt) Stub network related code" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:742(para) +msgid "syslog-log-facility=LOG_USER" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:747(para) +msgid "use_cow_images=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:748(para) +msgid "(BoolOpt) Whether to use cow images" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:753(para) +msgid "use_stderr=true" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:754(para) +msgid "(BoolOpt) Log output to standard error" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:758(para) +msgid "use-syslog=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:759(para) +msgid "(BoolOpt) Use syslog for logging." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:763(para) +msgid "verbose=false" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:764(para) +msgid "(BoolOpt) Print more verbose output" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:768(para) +msgid "volume_api_class=nova.volume.api.API" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:770(para) +msgid "(StrOpt) The full class name of the volume API class to use" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:774(para) +msgid "volume_manager=nova.volume.manager.VolumeManager" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:777(para) +msgid "(StrOpt) full class name for the Manager for volume" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:781(para) +msgid "volume_topic=volume" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:782(para) +msgid "(StrOpt) the topic volume nodes listen on" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:786(para) +msgid "vpn_image_id=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:787(para) +msgid "(StrOpt) image id used when starting up a cloudpipe VPN server" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:791(para) +msgid "vpn_key_suffix=-vpn" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:792(para) +msgid "(StrOpt) Suffix to add to project name for vpn key and secgroups" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:796(para) +msgid "zombie_instance_updated_at_window=172800" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/common-nova-conf.xml:798(para) +msgid "(IntOpt) Number of seconds zombie instances are cleaned up." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:4(caption) +msgid "Description of nova.conf file configuration options for bare metal deployment" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:17(para) +msgid "Options should be placed in the [baremetal] config group" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:25(para) +msgid "deply_kernel" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:26(para) +msgid "(StrOpt) Glance image UUID for the special deploy kernel. Can also be set on the flavor (instance type)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:31(para) +msgid "deploy_ramdisk" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:32(para) +msgid "(StrOpt) Glance image UUID for the special deploy ramdisk. Can also be set on the flavor (instance type)." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:37(para) +msgid "driver=nova.virt.baremetal.pxe.PXE" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:38(para) +msgid "(StrOpt) Nova class for the imaging sub-driver to use" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:42(para) +msgid "instance_type_extra_specs" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:43(para) +msgid "(StrOpt) Additional capabilities this baremetal compute host should advertise. Should include the \"cpu_arch\" of the baremetal nodes managed by this host, which must match hardware and flavor extra_specs. Example: cpu_arch:x86_64" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:50(para) +msgid "ipmi_power_retry=5" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:51(para) +msgid "(IntOpt) Number of times that an IPMI command should be retried before raising an error and aborting the action. Actions are retried at half second intervals." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:56(para) +msgid "net_config_template=$pybasedir/nova/virt/baremetal/net-dhcp.ubuntu.template" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:59(para) +msgid "(StrOpt) Template file for injected network. Use net-static.ubuntu.template if you are not using Quantum DHCP." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:64(para) +msgid "power_manager=nova.virt.baremetal.ipmi.IPMI" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:65(para) +msgid "(StrOpt) Nova class for the power sub-driver to use." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:69(para) +msgid "pxe_append_params" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:70(para) +msgid "(StrOpt) Any additional parameters that must be passed to the baremetal nodes during the PXE boot process." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:75(para) +msgid "pxe_config_template=$pybasedir/nova/virt/baremetal/pxe_config.template" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:78(para) +msgid "(StrOpt) Template file for PXE configuration." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:82(para) +msgid "pxe_deploy_timeout=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:83(para) +msgid "(IntOpt) Timeout in seconds to wait for PXE deployment to complete. Defaults to 0 (unlimited). This should be set to a value appropriate for each environment, but should not be more than instance_build_timeout." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:89(para) +msgid "sql_connection=sqlite:///$state_path/baremetal_$sqlite_db" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:96(para) +msgid "terminal=shellinaboxd" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:97(para) +msgid "(StrOpt) Path to remote terminal program that provides terminal access to baremetal nodes." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:101(para) +msgid "terminal_cert_dir" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:102(para) +msgid "(StrOpt) Path to directory which stores SSL/PEM certs for terminal access." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:106(para) +msgid "terminal_pid_dir" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:107(para) +msgid "(StrOpt) Path to directory which stores PID files for terminal access." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:111(para) +msgid "tftproot=/tftpboot" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:112(para) +msgid "(StrOpt) Path to directory where TFTP images should be placed. Required for PXE driver." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:116(para) +msgid "vif_driver=nova.virt.baremetal.vif_driver.BareMetalVIFDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:119(para) +msgid "(StrOpt) Nova class for the VIF sub-driver to use." +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:123(para) +msgid "volume_driver=nova.virt.baremetal.volume_driver.LibvirtVolumeDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:126(para) +msgid "(StrOpt) Nova class for the Volume sub-driver to use." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/src/docbkx/openstack-compute-admin/tables/bare-metal-nova-conf.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/src/docbkx/openstack-ha/locale/openstack-ha.pot b/doc/src/docbkx/openstack-ha/locale/openstack-ha.pot new file mode 100644 index 0000000000..9b335e4f28 --- /dev/null +++ b/doc/src/docbkx/openstack-ha/locale/openstack-ha.pot @@ -0,0 +1,32 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2013-03-12 15:09+0800\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/src/docbkx/openstack-ha/ha-guide-docinfo.xml:3(firstname) +msgid "Florian" +msgstr "" + +#: ./doc/src/docbkx/openstack-ha/ha-guide-docinfo.xml:4(surname) +msgid "Haas" +msgstr "" + +#: ./doc/src/docbkx/openstack-ha/ha-guide-docinfo.xml:6(email) +msgid "florian@hastexo.com" +msgstr "" + +#: ./doc/src/docbkx/openstack-ha/ha-guide-docinfo.xml:8(orgname) +msgid "hastexo" +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/src/docbkx/openstack-ha/ha-guide-docinfo.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/src/docbkx/openstack-install/locale/openstack-install.pot b/doc/src/docbkx/openstack-install/locale/openstack-install.pot new file mode 100644 index 0000000000..69af3e5b68 --- /dev/null +++ b/doc/src/docbkx/openstack-install/locale/openstack-install.pot @@ -0,0 +1,3721 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2013-03-12 15:09+0800\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/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:6(title) +msgid "Installing OpenStack Object Storage on Ubuntu" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:7(para) +msgid "Though you can install OpenStack Object Storage for development or testing purposes on a single server, a multiple-server installation enables the high availability and redundancy you want in a production distributed object storage system." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:8(para) +msgid "If you would like to perform a single node installation on Ubuntu for development purposes from source code, use the Swift All In One instructions or DevStack. See http://swift.openstack.org/development_saio.html for manual instructions or http://devstack.org for all-in-one including authentication and a dashboard." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:16(title) +msgid "Before You Begin" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:17(para) +msgid "Have a copy of the Ubuntu Server installation media on hand if you are installing on a new server." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:19(para) +msgid "This document demonstrates installing a cluster using the following types of nodes:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:23(para) +msgid "One Proxy node which runs the swift-proxy-server processes and may also run the optional swauth or tempauth services, this walkthrough uses the Identity service code-named Keystone. The proxy server serves proxy requests to the appropriate Storage nodes." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:31(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/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:39(para) ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:62(para) +msgid "Fewer Storage nodes can be used initially, but a minimum of 5 is recommended for a production cluster." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:44(title) +msgid "General Installation Steps" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:47(para) +msgid "Install the baseline operating system, such as Ubuntu Server (10.04 through 12.04) or RHEL, CentOS, or Fedora, on all nodes." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:51(para) +msgid "Install the swift service and openSSH." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:56(para) +msgid "Create and populate configuration directories on all nodes:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:64(para) +msgid "Create /etc/swift/swift.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:70(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/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:77(para) +msgid "Next, set up your storage nodes, proxy node, and an auth node, in this walkthrough we'll use the OpenStack Identity Service, Keystone, for the common auth piece." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:7(title) +msgid "OpenStack Folsom upgrade" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:8(para) +msgid "This chapter will lead you through the Essex to Folsom upgrade process. If you are running an earlier version, you should upgrade to Essex before continuing." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:12(para) +msgid "As a preliminary step, you should check the release notes:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:16(para) +msgid "Folsom release notes, 2012.2." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:20(para) +msgid "2012.2.1." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:24(para) +msgid "2012.2.2." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:27(para) +msgid "2012.2.3." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:31(para) +msgid "The upgrade process will be done in the following steps:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:34(para) +msgid "Upgrade the OpenStack Identity service (Keystone)." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:37(para) +msgid "Upgrade the OpenStack Image service (Glance)." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:40(para) +msgid "Upgrade all OpenStack Compute (Nova) services." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:43(para) +msgid "Optional: Upgrade nova-volume to OpenStack Block Storage (Cinder). Please note that nova-volume will be deprecated in the following release." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:47(para) +msgid "Optional: Upgrade nova-network to OpenStack Networking (Quantum). Please note that nova-network will be deprecated in the following release." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:53(title) +msgid "Identity service (Keystone) upgrade" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:56(para) ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:109(para) +msgid "Stop the services: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:64(para) ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:118(para) ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:208(para) +msgid "Create a backup of your configuration files and of your database contents: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:72(para) ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:126(para) +msgid "Upgrade the packages to the latest 2012.2 version, using your distribution package manager." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:78(para) ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:165(para) +msgid "Apply the database upgrade. " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:85(para) +msgid "Start the keystone service: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:92(para) ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:180(para) +msgid "Check that everything is running fine: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:106(title) +msgid "Image service (Glance) upgrade" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:132(para) +msgid "Change the configuration files according to the Release Notes." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:137(para) +msgid "You have to add the sql connection parameters to your API configuration file, or disable the new v2 API setting the enable_v2_api to false: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:145(para) +msgid "Also, the auth_token middleware configuration has been moved from the paste configuration to the server configuration. Unless you have made modifications to your paste config it is recommended to accept the distributed glance-api-paste.ini and glance-registry-paste.ini files and then add the auth_token configuration at the bottom of your glance-api.conf and glance-registry.conf, adapting it to your actual configuration: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:172(para) +msgid "Start the glance services: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:194(title) +msgid "Compute service (Nova) upgrade" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:195(para) +msgid "We will perform an upgrade of all the nova packages to the Folsom version. However, in this section we do not cover the upgrade to OpenStack Networking (Quantum) and OpenStack Block Storage (Cinder) of the respective and deprecated nova-network and nova-volume packages, as this will be covered in another section." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:202(para) +msgid "Stop all the nova services." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:216(para) +msgid "Upgrade the configuration files according to the Release Notes. You have to take into account the following:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:223(para) +msgid "IMPORTANT: If you are backing your instances with shared storage, make sure to disable image cache BEFORE upgrading to Folsom: There is a serious issue when using cache manager and shared storage, for more details please check this this bug report" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:233(para) +msgid "Change the nova.conf file to the new configuration format. In Essex the configuration was based on the old --option-name format, but in Folsom it has been changed to the INI config format, with options specified as key=value pairs. Because of this change, boolean options have to be explicitly set to true/false (such as verbose=true). The following code: Will transform into this. Check the compute options reference card to check if all your flags are recognized." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:255(para) +msgid "Check new the rootwrap configuration changes." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:263(para) +msgid "The connection_type flag has been deprecated in favor of the compute_driver flag, so connection_type=libvirt should be replaced with compute_driver=libvirt.LibvirtDriver and connection_type=xenapi should be replaced with compute_driver=xenapi.XenAPIDriver." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:272(para) +msgid "The libvirt.xml and cpuinfo.xml templates have been removed in favor of a new config API." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:260(para) +msgid "If you are using Libvirt: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:284(para) +msgid "Upgrade all the packages to the latest 2012.2 version, using your distribution package manager. Note that we are not migrating nova-network and nova-volume to OpenStack Networking (Quantum) and OpenStack Block Storage (Cinder) in this step, but just upgrade those packages to Folsom." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:291(para) +msgid "Upgrade the nova api paste. It is recommended to accept the new nova/api-paste.ini file from the package, and then check it against a backed file for any local modifications." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:297(para) +msgid "Upgrade the nova/policy.json file. Unless you have made local changes you should accept the new file provided with the package." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:303(para) +msgid "Apply the DB upgrade. " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:311(para) +msgid "Restart all the services." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:316(para) +msgid "Check that everything is working fine: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:333(title) +msgid "Upgrade nova-volume to OpenStack Block Storage (Cinder)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:337(para) +msgid "Install Folsom version of OpenStack Block Storage (Cinder)." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:343(para) +msgid "Create a cinder user in Keystone as an admin in service tenant." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:348(para) +msgid "Edit /etc/cinder/api-paste.ini to reflect the admin_user, admin_tenant_name, and admin_password that you created in the previous step." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:355(para) +msgid "Create Cinder database and database user." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:360(para) +msgid "Check the SQL connection in /etc/cinder/cinder.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:365(para) +msgid "Create initial Cinder database: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:371(para) +msgid "Copy volume tables using the following command: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:375(para) +msgid "Do not include the database names in --src or --dest; assumes your source database is named \"nova\" and that your destination database is named \"cinder\", and appends these to the strings you supply." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:385(para) +msgid "Copy iSCSI target configuration " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:391(para) +msgid "Set the correct volume api class in your nova.conf configuration file. " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:397(para) +msgid "Remove the osapi_volume from the enabled_apis in your /etc/nova/nova.conf. If you do not have such a configuration option, set it explicitly to the following (as it is included by default): " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:404(para) +msgid "Disable and stop the service. " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:411(para) +msgid "Restart the nova-api service " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:417(para) +msgid "Start cinder service: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:423(para) +msgid "Ensure that /etc/tgt/conf.d/cinder.conf exists and has an include line that matches volumes_dir option in cinder.conf. In the default case this is include /var/lib/cinder/volumes/*, if you edit this file restart the tgtd service." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:334(para) +msgid "We assume that all the services (including nova-volume) are migrated to Folsom. " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:434(title) +msgid "Upgrade nova-network to OpenStack Networking (Quantum)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:435(para) +msgid "This process has not yet been documented." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-troubleshooting.xml:6(title) +msgid "Troubleshooting the Identity Service (Keystone)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-troubleshooting.xml:7(para) +msgid "To begin troubleshooting, look at the logs in the /var/log/keystone.log file (the location of log files is configured in the /etc/keystone/logging.conf file). It shows all the components that have come in to the WSGI request, and will ideally have an error in that log that explains why an authorization request failed. If you're not seeing the request at all in those logs, then run keystone with \"--debug\" where --debug is passed in directly after the CLI command prior to parameters." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:6(title) +msgid "OpenStack Terminology" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:9(title) +msgid "Version Names" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:12(para) +msgid "Each OpenStack release has a name, in increasing alphabetical order (e.g., Grizzly follows Folsom). There are also version numbers corresponding to these releases, but the numbering schemes are different for OpenStack Compute and OpenStack Object Storage, as shown in the table below:
OpenStack version names
Release nameRelease dateOpenStack Compute version numberOpenStack Object Storage version number
GrizzlyApril 20132013.11.7.6
FolsomOctober 20122012.21.7.2
EssexApril 20122012.11.4.8
DiabloOctober 20112011.31.4.3
CactusApril 20112011.21.3.0
BexarMarch 20112011.11.2.0
AustinOctober 20100.9.01.0.0
Beginning with the Cactus release, OpenStack adopted a six month release schedule. The Havana release is scheduled for October 2013." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:84(title) +msgid "Code Names" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:100(para) +msgid "Identity" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:103(para) +msgid "Keystone" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:108(para) +msgid "Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:111(para) +msgid "Nova" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:116(para) +msgid "Image" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:119(para) +msgid "Glance" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:124(para) +msgid "Dashboard" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:127(para) +msgid "Horizon" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:132(para) +msgid "Object Storage" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:135(para) +msgid "Swift" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:140(para) +msgid "Volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:143(para) ./doc/src/docbkx/openstack-install/ch_externals.xml:107(title) +msgid "Cinder" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:148(para) +msgid "Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:151(para) +msgid "Quantum" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:85(para) +msgid "Each OpenStack service has a code name. For example, the Image Service is code-named Glance. The full list is shown in the table below:
Code names
Service nameCode name
" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:157(para) +msgid "These code names are reflected in the names of configuration files and command-line utility programs. For example, the Identity service has a configuration file called keystone.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:164(title) +msgid "OpenStack Services and Linux Services" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:165(para) +msgid "In the Linux world, a service (also known as a daemon) refers to a single program that runs in the background and typically listens on a port to respond to service requests. An OpenStack service, on the other hand, refers to a collection of Linux services working in concert." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:170(para) +msgid "OpenStack services are implemented by multiple Linux services. For example, and are two of the Linux services that implement the Compute service. OpenStack also depends on several third-party services, such as a database (typically MySQL) and a message broker (typically RabbitMQ or Qpid)." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:177(para) +msgid "In this document, we generally use the term \"service\" to refer both to lower-level Linux services and higher-level OpenStack services. It should be clear from the context whether we are referring to a high-level OpenStack service (e.g., Image), or a low-level Linux service (e.g., )." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:185(title) +msgid "Storage: objects, blocks, and files" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:186(para) +msgid "Many cloud computing use cases require persistent remote storage. Storage solutions are often divided into three categories: object storage, block storage, and file storage." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:189(para) +msgid "Note that some storage solutions support multiple categories. For example, NexentaStor supports both block storage and file storage (with announcements for future support for object storage), GlusterFS supports file storage and object storage, and Ceph Storage supports object storage, block storage, and file storage." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:196(title) +msgid "Object storage" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:197(para) +msgid "In OpenStack: Object Storage service (Swift)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:198(para) +msgid "Related concepts: Amazon S3, Rackspace Cloud Files, Ceph Storage" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:199(para) +msgid "With object storage, files are exposed through an HTTP interface, typically with a REST API. All client data access is done at the user level: the operating system is unaware of the presence of the remote storage system. In OpenStack, the Object Storage service provides this type of functionality. Users access and modify files by making HTTP requests. Because the data access interface provided by an object storage system is at a low level of abstraction, people often build on top of object storage to build file-based applications that provide a higher level of abstraction. For example, the OpenStack Image service can be configured to use the Object Storage service as a backend. Another use for object storage solutions is as a content delivery network (CDN) for hosting static web content (e.g., images, and media files), since object storage already provides an HTTP interface." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:220(title) +msgid "Block storage (SAN)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:221(para) +msgid "In OpenStack: Volumes (nova-volume service) in OpenStack Compute or cinder as a separate Volume service" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:224(para) +msgid "Related concepts: Amazon Elastic Block Store (EBS), Ceph RADOS Block Device (RBD), iSCSI" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:226(para) +msgid "With block storage, files are exposed through a low-level computer bus interface such as SCSI or ATA, that is accessible over the network. Block storage is synonymous with SAN (storage area network). Clients access data through the operating system at the device level: users access the data by mounting the remote device in a similar manner to how they would mount a local, physical disk (e.g., using the \"mount\" command in Linux). In OpenStack, the nova-volume service that forms part of the Compute service provides this type of functionality, and uses iSCSI to expose remote data as a SCSI disk that is attached to the network." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:235(para) +msgid "Because the data is exposed as a physical device, the end-user is responsible for creating partitions and formatting the exposed disk device. In addition, in OpenStack Compute a device can only be attached to one server at a time, so block storage cannot be used to share data across virtual machine instances concurrently." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:242(title) +msgid "File storage (NAS)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:243(para) +msgid "In OpenStack: none" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:244(para) +msgid "Related concepts: NFS, Samba/CIFS, GlusterFS, Dropbox, Google Drive" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:245(para) +msgid "With file storage, files are exposed through a distributed file system protocol. Filesystem storage is synonymous with NAS (network attached storage). Clients access data through the operating system at the file system level: users access the data by mounting a remote file system. Examples of file storage include NFS and GlusterFS. The operating system needs to have the appropriate client software installed to be able to access the remote file system." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:251(para) +msgid "Currently, OpenStack Compute does not have any native support for this type of file storage inside of an instance. However, there is a Gluster storage connector for OpenStack that enables the use of the GlusterFS file system as a back-end for the Image service." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/image-troubleshooting.xml:6(title) +msgid "Troubleshooting the Image Service (Glance)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/image-troubleshooting.xml:7(para) +msgid "To begin troubleshooting, look at the logs in the /var/log/glance/registry.log or /var/log/glance/api.log." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installobjectstorage.xml:6(title) +msgid "Installing OpenStack Object Storage" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installobjectstorage.xml:7(para) +msgid "The OpenStack Object Storage services work together to provide object storage and retrieval through a REST API." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:6(title) +msgid "Configuring OpenStack Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:7(para) +msgid "This section describes the relevant nova.conf settings for getting a minimal install running. Refer to the OpenStack Compute Administration Manual for guidance on more configuration options." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:13(literal) ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:36(literal) +msgid "my_ip" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:16(literal) ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:39(literal) +msgid "vncserver_listen" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:19(literal) ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:42(literal) +msgid "vncserver_proxyclient_address" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:10(para) +msgid "In general, you can use the same nova.conf file across the controller and compute nodes. However, the following configuration options need to be changed on each compute host: For the above configuration options, you must use the IP address of the specific compute host, not the cloud controller." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:24(para) +msgid "The packages automatically do these steps for a user named nova, but if you are installing as another user you should ensure that the nova.conf file should have its owner set to root:nova, and mode set to 0640, since the file contains your MySQL server’s username and password." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:30(para) +msgid "If you are installing as another user, you should set permissions correctly. This packaged install ensures that the nova user belongs to the nova group and that the .conf file permissions are set, but here are the manual commands, which should be run as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:41(para) +msgid "The hypervisor is set by editing /etc/nova/nova.conf. The hypervisor defaults to kvm, but if you are working within a VM already, switch to qemu on the libvirt_type= line. To use Xen, refer to the overview in this book for where to install nova components." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:45(para) +msgid "You can also configure the nova-compute service (and, for example configure a hypervisor-per-compute-node) with a separate nova-compute.conf file and then referring to nova-compute.conf in the nova.conf file." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:51(para) +msgid "Ensure the database connection defines your backend data store by adding a sql_connection line to nova.conf: sql_connection=mysql://[user]:[pass]@[primary IP]/[db name], such as sql_connection=mysql://nova:yourpassword@192.168.206.130/nova." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:56(para) +msgid "Add these settings to /etc/nova/nova.conf for the network configuration assumptions made for this installation scenario. You can place comments in the nova.conf file by entering a new line with a # sign at the beginning of the line. To see a listing of all possible configuration option settings, see the reference in the OpenStack Compute Administration Manual." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:73(para) +msgid "Here is an example nova.conf with commented sections:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:79(para) +msgid "The my_ip configuration option will be different for each host, edit it accordingly." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:83(para) +msgid "Stop the nova- services prior to running db sync, by running stop commands as root. Otherwise your logs show errors because the database has not yet been populated:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-mysql.xml:6(title) +msgid "Installing MySQL" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-mysql.xml:7(para) +msgid "Install MySQL as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-mysql.xml:12(para) +msgid "During the install, you'll be prompted for the mysql root password. Enter a password of your choice and verify it." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-mysql.xml:14(para) +msgid "Use to edit /etc/mysql/my.cnf to change bind-address from localhost (127.0.0.1) to any (0.0.0.0) and restart the mysql service, as root." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-mysql.xml:22(para) +msgid "Set MySQL to start the daemon every time you start and then start the server. " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-configure.xml:6(title) +msgid "Configuring the Dashboard" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-configure.xml:7(para) +msgid "A full example local_settings.py file is included in the Appendix of the OpenStack Install and Deploy manual. Here are some common options:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-configure.xml:11(para) +msgid "SWIFT_ENABLED: If an Object Storage (Swift) endpoint is available and configured in the Identity service catalog, set SWIFT_ENABLED = True." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-configure.xml:16(para) +msgid "QUANTUM_ENABLED: If a Network Connection (Quantum) service is available and configured in the Identity service catalog, set QUANTUM_ENABLED = True. Else keep it FALSE if you are not using Quantum." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installidentity.xml:6(title) +msgid "Installing OpenStack Identity Service" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installidentity.xml:7(para) +msgid "The OpenStack Identity service manages users, tenants (accounts or projects) and offers a common identity system for all the OpenStack components." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:3(title) +msgid "Instructions for a Multiple Server Swift Installation (Ubuntu)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:6(title) ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:14(title) +msgid "Prerequisites" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:10(para) +msgid "Ubuntu Server 10.04 LTS installation media" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:15(para) +msgid "Swift can run with other distros, but for this document we will focus on installing on Ubuntu Server, ypmv (your packaging may vary)." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:18(para) +msgid "Basic architecture and terms" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:28(para) +msgid "This document shows a cluster using the following types of nodes:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:33(para) +msgid "one Proxy node" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:38(para) +msgid "Runs the swift-proxy-server processes which proxy requests to the appropriate Storage nodes. The proxy server will also contain the TempAuth service as WSGI middleware." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:47(para) +msgid "five Storage nodes" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:52(para) +msgid "Runs 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/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:63(para) +msgid "This document describes each Storage node as a separate zone in the ring. It is recommended to have a minimum of 5 zones. 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. For more information about the ring and zones, see: The Ring." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:71(para) +msgid "To increase reliability, you may want to add additional Proxy servers for performance which is described in Adding a Proxy Server." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:77(title) +msgid "Network Setup Notes" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:79(para) +msgid "This document refers to two networks. An external network for connecting to the Proxy server, and a storage network that is not accessible from outside the cluster, to which all of the nodes are connected. All of the Swift services, as well as the rsync daemon on the Storage nodes are configured to listen on their STORAGE_LOCAL_NET IP addresses." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:87(para) +msgid "Run all commands as the root user" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:89(title) +msgid "General OS configuration and partitioning for each node" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:94(para) +msgid "Install the baseline Ubuntu Server 10.04 LTS on all nodes." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:99(para) +msgid "Install common Swift software prereqs:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:110(para) +msgid "Create and populate configuration directories:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:119(para) +msgid "On the first node only, create /etc/swift/swift.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:131(para) +msgid "On the second and subsequent nodes: Copy that file over. It must be the same on every node in the cluster!:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:140(para) +msgid "Publish the local network IP address for use by scripts found later in this documentation:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:150(para) +msgid "The random string of text in /etc/swift/swift.conf is used as a salt when hashing to determine mappings in the ring." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:152(title) +msgid "Configure the Proxy node" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:154(para) +msgid "It is assumed that all commands are run as the root user" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:157(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:17(para) +msgid "Install swift-proxy service:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:165(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:22(para) +msgid "Create self-signed cert for SSL:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:174(para) +msgid "If you don't create the cert files, Swift silently uses http internally rather than https. This document assumes that you have created these certs, so if you're following along step-by-step, create them." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:177(para) +msgid "Modify memcached to listen on the default interfaces. Preferably this should be on a local, non-public network. Edit the IP address in /etc/memcached.conf, for example:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:187(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:40(para) +msgid "Restart the memcached server:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:195(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:52(para) +msgid "Create /etc/swift/proxy-server.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:229(title) ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:234(title) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:127(title) ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:61(title) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:42(title) ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:67(title) ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:8(title) ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:71(title) +msgid "Note" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:229(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 like: `10.1.2.3:11211,10.1.2.4:11211`. Only the proxy server uses memcache." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:234(para) +msgid "The memcache_servers variable can also be set in a separate file: /etc/swift/memcache.conf. If it is set in both places, the value in proxy-server.conf will override the one in memcache.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:241(para) +msgid "Create the account, container and object rings. The builder command is basically creating a builder file with a few parameters. The parameter with the value of 18 represents 2 ^ 18th, the value that the partition will be sized to. Set this \"partition power\" value based on the total amount of storage you expect your entire ring to use. The value of 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/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:262(para) +msgid "For every storage device in /srv/node on each node add entries to each ring:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:277(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:102(para) +msgid "Assuming there are 5 zones with 1 node per zone, ZONE should start at 1 and increment by one for each additional node." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:280(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:108(para) +msgid "Verify the ring contents for each ring:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:290(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:118(para) +msgid "Rebalance the rings:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:300(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:128(para) +msgid "Rebalancing rings can take some time." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:303(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:132(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/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:310(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:137(para) +msgid "Make sure all the config files are owned by the swift user:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:318(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:142(para) +msgid "Start Proxy services:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:327(title) +msgid "Configure the Storage nodes" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:329(para) +msgid "Swift should work on any modern filesystem that supports Extended Attributes (XATTRS). We currently recommend XFS as it demonstrated the best overall performance for the swift use case after considerable testing and benchmarking at Rackspace. It is also the only filesystem that has been thoroughly tested. These instructions assume that you are going to devote /dev/sdb1 to an XFS filesystem." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:332(para) ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:17(para) +msgid "Install Storage node packages:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:340(para) +msgid "For every device on the node, setup the XFS volume (/dev/sdb is used as an example):" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:354(para) +msgid "Create /etc/rsyncd.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:386(para) +msgid "Edit the RSYNC_ENABLE= line in /etc/default/rsync:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:394(para) ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:69(para) +msgid "Start rsync daemon:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:402(para) ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:72(para) +msgid "The rsync daemon requires no authentication, so it should be run on a local, private network." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:405(para) +msgid "Create /etc/swift/account-server.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:429(para) +msgid "Create /etc/swift/container-server.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:453(para) +msgid "Create /etc/swift/object-server.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:477(para) +msgid "Start the storage services. If you use this command, it will try to start every service for which a configuration file exists, and throw a warning for any configuration files which don't exist:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:486(para) +msgid "Or, if you want to start them one at a time, run them as below. Note that if the server program in question generates any output on its stdout or stderr, swift-init has already redirected the command's output to /dev/null. If you encounter any difficulty, stop the server and run it by hand from the command line. Any server may be started using \"swift-$SERVER-$SERVICE /etc/swift/$SERVER-config\", where $SERVER might be object, continer, or account, and $SERVICE might be server, replicator, updater, or auditor." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:513(title) +msgid "Create Swift admin account and test" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:515(para) +msgid "You run these commands from the Proxy node." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:520(para) ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:31(para) +msgid "Get an X-Storage-Url and X-Auth-Token:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:528(para) ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:37(para) +msgid "Check that you can HEAD the account:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:536(para) +msgid "Check that swift works (at this point, expect zero containers, zero objects, and zero bytes):" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:545(para) +msgid "Use swift to upload a few files named 'bigfile[1-2].tgz' to a container named 'myfiles':" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:555(para) +msgid "Use swift to download all files from the 'myfiles' container:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:564(para) +msgid "Use swift to save a backup of your builder files to a container named 'builders'. Very important not to lose your builders!:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:574(para) +msgid "Use swift to list your containers:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:582(para) +msgid "Use swift to list the contents of your 'builders' container:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:591(para) +msgid "Use swift to download all files from the 'builders' container:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:601(title) +msgid "Adding a Proxy Server" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:603(para) +msgid "For reliability's sake you may want to have more than one proxy server. You can set up the additional proxy node in the same manner that you set up the first proxy node but with additional configuration steps." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:609(para) +msgid "Once you have more than two proxies, you also want to load balance between the two, which means your storage endpoint also changes. You can select from different strategies for load balancing. For example, you could use round robin dns, or an actual load balancer (like pound) in front of the two proxies, and point your storage url to the load balancer." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:617(para) +msgid "See config-proxy for the initial setup, and then follow these additional steps." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:623(para) +msgid "Update the list of memcache servers in /etc/swift/proxy-server.conf for all the added proxy servers. If you run multiple memcache servers, use this pattern for the multiple IP:port listings: `10.1.2.3:11211,10.1.2.4:11211` in each proxy server's conf file.:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:637(para) +msgid "Change the storage url for any users to point to the load balanced url, rather than the first proxy server you created in /etc/swift/proxy-server.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:649(para) ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:53(para) +msgid "Next, copy all the ring information to all the nodes, including your new proxy nodes, and ensure the ring info gets to all the storage nodes as well." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:656(para) +msgid "After you sync all the nodes, make sure the admin has the keys in /etc/swift and the ownership for the ring file is correct." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:663(title) +msgid "Troubleshooting Notes" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:665(para) +msgid "If you see problems, look in var/log/syslog (or messages on some distros)." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:669(para) +msgid "Also, at Rackspace we have seen hints at drive failures by looking at error messages in /var/log/kern.log." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:673(para) +msgid "There are more debugging hints and tips in the Troubleshooting section." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:6(title) +msgid "Verifying the Identity Service Installation" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:7(para) +msgid "Verify that authentication is behaving as expected by using your established username and password to generate an authentication token:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:23(para) +msgid "You should receive a token in response, paired with your user ID." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:26(para) +msgid "This verifies that keystone is running on the expected endpoint, and that your user account is established with the expected credentials." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:30(para) +msgid "Next, verify that authorization is behaving as expected by requesting authorization on a tenant:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:47(para) +msgid "You should receive a new token in response, this time including the ID of the tenant you specified." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:51(para) +msgid "This verifies that your user account has an explicitly defined role on the specified tenant, and that the tenant exists as expected." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:55(para) +msgid "You can also set your --os-* variables in your environment to simplify CLI usage. First, set up a keystonerc file with the admin credentials and admin endpoint:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:67(para) +msgid "Save and source the file." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:71(para) +msgid "Verify that your keystonerc is configured correctly by performing the same command as above, but without any --os-* arguments." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:89(para) +msgid "You should receive a new token in response, reflecting the same tenant and user ID values as above." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:93(para) +msgid "This verifies that you have configured your environment variables correctly." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:97(para) +msgid "Finally, verify that your admin account has authorization to perform administrative commands." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:102(title) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:76(title) +msgid "Reminder" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:103(para) +msgid "Unlike basic authentication/authorization, which can be performed against either port 5000 or 35357, administrative commands MUST be performed against the admin API port: 35357). This means that you MUST use port 35357 in your OS_AUTH_URL or --os-auth-url setting." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:127(para) +msgid "This verifies that your user account has the admin role, as defined in keystone's policy.json file." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-cloud-controller.xml:6(title) +msgid "Installing the Cloud Controller" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-cloud-controller.xml:7(para) +msgid "Install the required nova- packages, and dependencies are automatically installed." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-cloud-controller.xml:10(para) +msgid "If you see the error: ensure that you have installed the Ubuntu Cloud Archive packages by adding the following to /etc/apt/sources.list.d/folsom.list: Prior to running apt-get update and apt-get upgrade, install the keyring: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-rabbitmq.xml:6(title) +msgid "Installing RabbitMQ" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-rabbitmq.xml:7(para) +msgid "Install the messaging queue server, RabbitMQ." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-rabbitmq.xml:8(para) +msgid "You have the option of installing Apache Qpid, refer to the Compute Administration Manual for configuration instructions, including adding rpc_backend=nova.rpc.impl_qpid to your nova.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/src/docbkx/openstack-install/ch_externals.xml:23(None) +msgid "@@image: 'figures/nova-external-1.svg'; md5=f9c2bec7596726c484472ddef91a0da7" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:26(None) +msgid "@@image: 'figures/nova-external-1.png'; md5=fbdd2189f1ea2caf0c7f1c0d0c89c867" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:33(None) +msgid "@@image: 'figures/nova-external-2.svg'; md5=3d002addd52a75b22ff44c2e353ec54c" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:36(None) +msgid "@@image: 'figures/nova-external-2.png'; md5=dd9285024dc9167294d3bec75929643a" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:6(title) +msgid "Underlying Technologies" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:7(para) +msgid "You can think of OpenStack Compute as a toolkit for building a cloud computing environment by stitching together existing Linux technologies." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:10(para) +msgid "The figures below shows two examples of how these underlying technologies can be assembled to construct an OpenStack Compute cloud. The circles are Linux services that are part of OpenStack Compute, and the rectangles are external (not maintained by the OpenStack project) components. Solid lines show interactions between OpenStack components and external components, and dashed lines show interactions between external components. All services that are part of OpenStack Compute interact with a queueing backend (e.g., RabbitMQ, Qpid) and a database backend (e.g., MySQL, PostgreSQL); these connections are not shown. Also not shown are services that do not explicitly rely on external technologies. For example, the nova-api service, the Identity service, and the Image service are not shown." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:20(title) +msgid "Underlying technologies (Scenario 1)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:30(title) +msgid "Underlying technologies (Scenario 2)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:41(para) +msgid "Many of the external technologies can be substituted with other components, as shown in the table below.
Technologies and supported implementations
TechnologySupported implementations
Message queueRabbitMQ, Qpid, ZeroMQ
Virtualizationxapi+XCP, xapi+XenServer, libvirt+KVM, libvirt+QEMU, libvirt+LXC, libvirt+VMWare
iSCSI back-endLVM+IET, LVM+tgt, Xen Storage Manager, SAN (Solaris, HP, SolidFire), NexentaStor, NetApp, Ceph, Sheepdog
DatabaseMySQL, PostgreSQL, sqlite
Web serverApache, Nginx
Session cachememcache, any Django-supported database backend (e.g., MySQL, PostgreSQL, sqlite)
" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:82(title) ./doc/src/docbkx/openstack-install/ch_instances-running.xml:84(systemitem) +msgid "nova-compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:82(para) +msgid "The nova-compute service depends on a virtualization driver to manage virtual machines. By default, this driver is libvirt, which is used to drive KVM. However, the libvirt driver can also drive other hypervisor technologies, and there is a separate Xen virtualization driver for driving Xen-based virtual machines if configured to use Xen Cloud Platform (XCP) or XenServer. Open-iscsi is used to mount remote block devices, also known as volumes. Open-iscsi exposes these remote devices as local device files which can be attached to instances." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:91(title) ./doc/src/docbkx/openstack-install/ch_instances-running.xml:92(systemitem) +msgid "nova-network" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:92(para) +msgid "The nova-network service depends on a number of Linux networking technologies. It uses Linux bridging to create network bridges to connect virtual machines to the physical networks. These bridges may be associated with VLANs using Linux networking VLAN support, if running in the VLAN networking mode. Iptables is used to implement security rules and implement NAT functionality, which is used for providing instances with access to the metadata service and for supporting floating IP addresses. Dnsmasq is used as a DHCP server to hand out IP addresses to virtual machine instances, as well as a DNS server." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:102(para) +msgid "In a future OpenStack release, functionality that is currently implemented by nova-network will be available through a separate OpenStack project, codenamed Quantum." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:108(para) +msgid "By default, Cinder service uses LVM to create and manage local volumes, and exports them via iSCSI using IET or tgt. It can also be configured to use other iSCSI-based storage technologies." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:112(para) +msgid "In the Folsom OpenStack release, functionality available through nova-volume is also available through a separate OpenStack Volumes project, code-named Cinder." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:118(title) +msgid "openstack-dashboard" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_externals.xml:119(para) +msgid "The openstack-dashboard is a Django-based application that runs behind an Apache web server by default. It uses memcache for the session cache by default. A web-based VNC client called novnc is used to provide access to the VNC consoles associated with the running KVM instances." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:6(title) +msgid "Compute and Image System Requirements" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:7(para) +msgid "Hardware: OpenStack components are intended to run on standard hardware. Recommended hardware configurations for a minimum production deployment are as follows for the cloud controller nodes and compute nodes for Compute and the Image Service, and object, account, container, and proxy servers for Object Storage." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:15(caption) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:10(caption) +msgid "Hardware Recommendations" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:22(td) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:17(td) +msgid "Server" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:23(td) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:18(td) +msgid "Recommended Hardware" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:24(td) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:19(td) +msgid "Notes" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:29(td) +msgid "Cloud Controller node (runs network, volume, API, scheduler and image services)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:32(para) ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:47(para) +msgid "Processor: 64-bit x86" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:33(para) +msgid "Memory: 12 GB RAM" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:34(para) +msgid "Disk space: 30 GB (SATA, SAS or SSD)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:35(para) +msgid "Volume storage: two disks with 2 TB (SATA) for volumes attached to the compute nodes" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:37(para) +msgid "Network: one 1 Gbps Network Interface Card (NIC)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:40(para) +msgid "Two NICS are recommended but not required. A quad core server with 12 GB RAM would be more than sufficient for a cloud controller node." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:45(td) +msgid "Compute nodes (runs virtual instances)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:48(para) +msgid "Memory: 32 GB RAM" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:49(para) +msgid "Disk space: 30 GB (SATA)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:50(para) +msgid "Network: two 1 Gbps NICs" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:53(para) +msgid "With 2 GB RAM you can run one m1.small instance on a node or three m1.tiny instances without memory swapping, so 2 GB RAM would be a minimum for a test-environment compute node. As an example, Rackspace Cloud Builders use 96 GB RAM for compute nodes in OpenStack deployments." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:58(para) +msgid "Specifically for virtualization on certain hypervisors on the node or nodes running nova-compute, you need a x86 machine with an AMD processor with SVM extensions (also called AMD-V) or an Intel processor with VT (virtualization technology) extensions." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:62(para) +msgid "For XenServer and XCP refer to the XenServer installation guide and the XenServer harware compatibility list." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:67(para) +msgid "For LXC, the VT extensions are not required." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:74(para) +msgid "While certain parts of OpenStack are known to work on various operating systems, currently the only feature-complete, production-supported host environment is 64-bit Linux." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:85(para) +msgid "The Folsom release of OpenStack Compute requires Ubuntu 12.04 or later, as the version of libvirt that ships with Ubuntu 11.10 does not function properly with OpenStack due to bug #1011863." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:91(para) +msgid "The Folsom release of OpenStack Compute requires Fedora 16 or later, as the version of libvirt that ships with Fedora 15 does not function properly with OpenStack due to bug #1011863." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:78(para) +msgid "Operating System: OpenStack currently has packages for the following distributions: CentOS, Debian, Fedora, RHEL, and Ubuntu. These packages are maintained by community members, refer to http://wiki.openstack.org/Packaging for additional links. " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:98(para) +msgid "Database: For OpenStack Compute, you need access to either a PostgreSQL or MySQL database, or you can install it as part of the OpenStack Compute installation process." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:102(para) +msgid "Permissions: You can install OpenStack services either as root or as a user with sudo permissions if you configure the sudoers file to enable all the permissions." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:106(para) +msgid "Network Time Protocol: You must install a time synchronization program such as NTP. For Compute, time synchronization avoids problems when scheduling VM launches on compute nodes. For Object Storage, time synchronization ensure the object replications are accurately updating objects when needed so that the freshest content is served." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-db-sync.xml:5(title) +msgid "Configuring the Database for Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-db-sync.xml:6(para) +msgid "Create the tables in your backend data store by running the following command:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-db-sync.xml:9(para) +msgid "If you see any response, you can look in /var/log/nova/nova-manage.log to see the problem. No response means the command completed correctly and your nova database is now populated." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-db-sync.xml:13(title) +msgid "Deprecation warnings" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-db-sync.xml:14(para) +msgid "Note that if while running this command you see warnings such as SADeprecationWarning: The 'listeners' argument to Pool (and create_engine()) is deprecated. Use event.listen()., these will be fixed in future version of the libraries and can be safely ignored." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-db-sync.xml:16(para) +msgid "Restart all services in total, just to cover the entire spectrum:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-db-sync.xml:31(para) +msgid "All nova services are now installed and started. If the \"start\" command doesn't work, your services may not be running correctly (or not at all). Review the logs in /var/log/nova to look for clues." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-install/dashboard-verify.xml:18(None) ./doc/src/docbkx/openstack-install/dashboard-verify.xml:22(None) ./doc/src/docbkx/openstack-install/vnc-console.xml:18(None) ./doc/src/docbkx/openstack-install/vnc-console.xml:22(None) +msgid "@@image: 'figures/dashboard-overview.png'; md5=e8da604fd0de70c96f6becbef3cba0fa" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-verify.xml:6(title) ./doc/src/docbkx/openstack-install/vnc-console.xml:6(title) +msgid "Validating the Dashboard Install" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-verify.xml:7(para) +msgid "To validate the Dashboard installation, point your browser at http://192.168.206.130/horizon. Note that you cannot use VNC Console from a Chrome browser. You need both Flash installed and a Firefox browser. Once you connect to the Dashboard with the URL, you should see a login window. Enter the credentials for users you created with the Identity Service, Keystone. For example, enter \"admin\" for the username and \"secrete\" as the password." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:6(title) +msgid "Appendix: Configuration File Examples" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:8(para) +msgid "Included for your reference are all configuration files." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:9(title) +msgid "keystone.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:9(para) +msgid "The Identity service's configuration file is found in /etc/keystone/keystone.conf. This file needs to be modified after installing to use SQL for endpoint data and to replace the ADMIN key with the one created during the installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:15(title) +msgid "glance-registry.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:15(para) +msgid "The Image service's registry, which stores the metadata about images, is found in /etc/glance/glance-registry.conf. This file needs to be modified after installing." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:21(title) +msgid "glance-registry-paste.ini" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:22(para) +msgid "The Image service's API middleware pipeline is found in /etc/glance/glance-registry-paste.ini. This file needs to be modified after installing." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:28(title) +msgid "glance-api.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:28(para) +msgid "The configuration file for the Image API is found in /etc/glance/glance-api.conf. You need to change this file to look like this example after installing from packages." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:34(title) +msgid "glance-api-paste.ini" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:35(para) +msgid "The Image service's API middleware pipeline is found in /etc/glance/glance-api-paste.ini. You should not need to modify this file." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:41(title) +msgid "glance-scrubber.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:41(para) +msgid "An additional configuration file for the Image service is found in /etc/glance/glance-scrubber.conf. The scrubber is a utility that cleans up images that have been deleted." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:46(title) +msgid "nova.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:46(para) +msgid "The configuration file for Compute (nova) settings is stored in /etc/nova/nova.conf. To see a list of all possible configuration options for this file, see the List of Tables at the beginning of the OpenStack Compute Admin guide ." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:55(literal) +msgid "service_host" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:58(literal) +msgid "auth_host" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:61(literal) +msgid "auth_uri" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:51(para) +msgid "This guide assumes that the IP address of the machine that runs the Identity service is 192.168.206.130. If the IP address of the machine on your setup is different, change the following configuration options:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:66(title) +msgid "api-paste.ini" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:66(para) +msgid "The /etc/nova/api-paste.ini file is a middleware configuration file used by the EC2 API and OpenStack Compute API. You should not need to edit it." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:69(title) +msgid "Credentials (openrc)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:69(para) +msgid "This file contains the credentials used by Compute, Image, and Identity services, you can optionally store in /home/openrc. The important concept to avoid errors is to ensure that it is sourced in the environment from which you issue commands. Run \"env | grep OS_\" or \"env | grep NOVA_\" to view what is being used in your environment." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:78(title) +msgid "Dashboard configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:78(para) +msgid "This file contains the database and configuration settings for the OpenStack Dashboard." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:81(title) +msgid "etc/swift/swift.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:82(para) +msgid "This file contains the settings to randomize the hash for the ring for Object Storage, code-named swift." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:86(title) +msgid "etc/network/interfaces.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:87(para) +msgid "These instructions are for using the FlatDHCP networking mode with a single network interface." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:90(title) +msgid "etc/swift/proxy-server.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:91(para) +msgid "This file contains the settings for the Object Storage proxy server, which contains the Identity service settings." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:94(title) +msgid "etc/swift/account-server.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:98(title) +msgid "etc/swift/account-server/1.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:102(title) +msgid "etc/swift/container-server.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:106(title) +msgid "etc/swift/container-server/1.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:110(title) +msgid "etc/swift/object-server.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:114(title) +msgid "etc/swift/object-server/1.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:6(title) +msgid "System Requirements for the Dashboard" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:7(para) +msgid "Because Apache does not serve content from a root user, you must use another user with sudo privileges and run as that user." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:8(para) +msgid "You should have a running OpenStack Compute installation with the Identity Service, Keystone, enabled for identity management." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:10(para) +msgid "The dashboard needs to be installed on the node that can contact the Identity Service." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:11(para) +msgid "You should know the URL of your Identity endpoint and the Compute endpoint." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:12(para) +msgid "You must know the credentials of a valid Identity service user." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:13(para) +msgid "You must have git installed. It's straightforward to install it with sudo apt-get install git-core." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:15(para) +msgid "Python 2.6 is required, and these instructions have been tested with Ubuntu 10.10. It should run on any system with Python 2.6 or 2.7 that is capable of running Django including Mac OS X (installing prerequisites may differ depending on platform)." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:18(para) +msgid "Optional components:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:21(para) +msgid "An Image Store (Glance) endpoint." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:22(para) +msgid "An Object Store (Swift) endpoint." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:23(para) +msgid "A Quantum (networking) endpoint." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:6(title) +msgid "Pre-configuring the network" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:7(para) +msgid "These instructions are for using the FlatDHCP networking mode with a single network interface. More complex configurations are described in the networking section, but this configuration is known to work. These configuration options should be set on all compute nodes." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:11(para) +msgid "Set your network interface in promiscuous mode so that it can receive packets that are intended for virtual machines. As root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:14(para) +msgid "Set up your /etc/network/interfaces file with these settings:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:15(para) +msgid "eth0: public IP, gateway" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:16(para) +msgid "br100: no ports, stp off, fd 0, first address from fixed_range set in nova.conf files." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:17(para) +msgid "Here's an Ubuntu/Debian example:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:33(para) +msgid "Here's an example network setup for RHEL, Fedora, or CentOS. Create /etc/sysconfig/network-scripts/ifcfg-br100:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:45(para) +msgid "Also install bridge-utils:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:48(para) +msgid "Ensure that you set up the bridge, although if you use flat_network_bridge=br100 in your nova.conf file, nova will set up the bridge for you when you run the nova-manage network command." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:53(para) +msgid "Lastly, restart networking to have these changes take effect. (This method is deprecated but \"restart networking\" doesn't always work.)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:58(title) +msgid "Configuration requirements with RHEL" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:60(para) +msgid "Ensure auth=no is set in /etc/qpidd.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:62(para) +msgid "Set selinux in permissive mode:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:64(para) +msgid "Otherwise you will get issues like https://bugzilla.redhat.com/show_bug.cgi?id=734346 /usr/bin/nova-dhcpbridge: No such file or directory." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:68(para) +msgid "If RHEL 6.2 based, use the openstack-config package to turn off force DHCP releases." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:71(para) +msgid "If RHEL 6.3 based, install dnsmasq utilities." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:73(para) +msgid "If you intend to use guest images that don't have a single partition, then allow libguestfs to inspect the image so that files can be injected, by setting:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:6(title) +msgid "Installing and Configuring the Proxy Node" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/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/src/docbkx/openstack-install/install-config-proxy-node.xml:13(para) +msgid "It is assumed that all commands are run as the root user." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:29(para) +msgid "Modify memcached to listen on the default interfaces. Preferably this should be on a local, non-public network. Edit the following line in /etc/memcached.conf, changing:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:45(para) +msgid "RHEL/CentOS/Fedora Only: To set up Object Storage to authenticate tokens we need to set the keystone Admin token in the swift proxy file with the openstack-config command. " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:57(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 like: Only the proxy server uses memcache." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:65(para) +msgid "Create the account, container and object rings. The builder command is basically creating a builder file with a few parameters. The parameter with the value of 18 represents 2 ^ 18th, the value that the partition will be sized to. Set this “partition power” value based on the total amount of storage you expect your entire ring to use. The value of 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/src/docbkx/openstack-install/install-config-proxy-node.xml:84(para) +msgid "For every storage device on each node add entries to each ring:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:92(para) +msgid "For example, if you were setting up a storage node with a partition in Zone 1 on IP 10.0.0.1. 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 would look like: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-verifying-install.xml:6(title) +msgid "Verifying the Compute Installation" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-verifying-install.xml:7(para) +msgid "You can ensure all the Compute services are running by using the command, as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-verifying-install.xml:10(para) +msgid "In return you should see \"smiley faces\" rather than three X symbols. Here's an example." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-verifying-install.xml:19(para) +msgid "If you see three X symbols and are running services on separate hosts, ensure that ntp is synchronizing time correctly and that all servers match their time. Out-of-sync time stamps are the most common cause of the XXX state." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-verifying-install.xml:18(para) +msgid "You can find the version of the installation by using the command, as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-verifying-install.xml:28(para) +msgid "The version number 2012.2 corresponds with the Folsom release of Compute." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:6(title) +msgid "Configuring the SQL Database (MySQL) on the Cloud Controller" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:8(para) +msgid "Start the mysql command line client by running:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:11(para) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:35(para) +msgid "Enter the mysql root user's password when prompted." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:12(para) +msgid "To configure the MySQL database, create the nova database." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:15(para) +msgid "Create a MySQL user and password for the newly-created nova database that has full control of the database." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:17(replaceable) ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:18(replaceable) ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:16(replaceable) ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:28(replaceable) +msgid "[YOUR_NOVADB_PASSWORD]" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:20(para) +msgid "In the above commands, even though the 'nova'@'%' also matches 'nova'@'localhost', you must explicitly specify the 'nova'@'localhost' entry." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:23(para) +msgid "By default, MySQL will create entries in the user table with User='' and Host='localhost'. The User='' acts as a wildcard, matching all users. If you do not have the 'nova'@'localhost' account, and you try to log in as the nova user, the precedence rules of MySQL will match against the User='' Host='localhost' account before it matches against the User='nova' Host='%' account. This will result in an error message that looks like:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:34(para) +msgid "Thus, we create a separate User='nova' Host='localhost' entry that will match with higher precedence." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:36(para) ./doc/src/docbkx/openstack-install/install-config-glance.xml:47(para) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:67(para) +msgid "See the MySQL documentation on connection verification for more details on how MySQL determines which row in the user table it uses when authenticating connections." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:41(para) +msgid "Enter quit at the mysql> prompt to exit MySQL." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:46(para) +msgid "The command to populate the database is described later in the documentation, in the Section entitled Configuring the Database for Compute." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:50(title) +msgid "Securing MySQL" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:51(para) +msgid "Additional steps are required to configure MySQL for production mode. In particular, anonymous accounts should be removed. On several distributions, these accounts can be removed by running the following script after installing mysql: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-hypervisor-selection.xml:5(title) +msgid "Configuring the Hypervisor" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-hypervisor-selection.xml:6(para) +msgid "For production environments the most tested hypervisors are KVM and Xen-based hypervisors. KVM runs through libvirt, Xen runs best through XenAPI calls. KVM is selected by default and requires the least additional configuration. This guide offers information on both but the specific walkthrough configuration options set up KVM." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:6(title) +msgid "Configuring the SQL Database (PostgreSQL) on the Cloud Controller" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:7(para) +msgid "Optionally, if you choose not to use MySQL, you can install and configure PostgreSQL for all your databases. Here's a walkthrough for the Nova database:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:10(para) +msgid "Start the PostgreSQL command line client by running:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:12(para) +msgid "Enter the postgresql root user's password if prompted." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:13(para) +msgid "To configure the database, create the nova database." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:21(para) +msgid "The database is created and we have a privileged user that controls the database. Now we have to install the packages that will help Nova access the database." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:26(para) +msgid "Configure the /etc/nova/nova.conf file, to ensure it knows to use the PostgreSQL database:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:29(para) +msgid "The command to populate the database is described later in the documentation, in the section entitled Configuring the Database for 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/src/docbkx/openstack-install/example-compute-install-arch.xml:57(None) +msgid "@@image: 'figures/NOVA_install_arch.png'; md5=0f72da9079e5e0516ac664d2e4a15910" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:70(None) +msgid "@@image: 'figures/NOVA_compute_nodes.png'; md5=bc6a5eb2b9358d000d96f274800752aa" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:6(title) +msgid "Example Compute Installation Architectures" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:7(para) +msgid "OpenStack architecture consists of these major components: Compute, Object Storage, Identity, and Images. A common Identity component provides authentication for users to have access to these components. The Image service stores and serves images to run virtual machines. Compute uses a shared-nothing, messaging-based architecture. While very flexible, the fact that you can install each nova- service on an independent server means there are many possible methods for installing OpenStack Compute. The only co-dependency between possible multi-node installations is that the Dashboard must be installed on a server running the nova-api service. Here are the types of installation architectures for OpenStack Compute with the Image and Identity Services:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:25(para) +msgid "Single node, Compute-only: Only one server runs all nova- services and also drives all the virtual instances. Use this configuration only for trying out OpenStack Compute, or for development purposes." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:30(para) +msgid "Two nodes, Compute-only: A cloud controller node runs the nova- services except for nova-compute, and a compute node runs nova-compute. A client computer is likely needed to bundle images and interfacing to the servers, but a client is not required. Use this configuration for proof of concepts or development environments." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:38(para) +msgid "Multiple nodes, Compute-only: You can add more compute nodes to the two node installation by simply installing nova-compute on an additional server and copying a nova.conf file to the added node. This would result in a multiple node installation. You can also add a volume controller and a network controller as additional nodes in a more complex multiple node installation. A minimum of 4 nodes is best for running multiple virtual instances that require a lot of processing power." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:52(para) +msgid "This is an illustration of one possible multiple server installation of OpenStack Compute; virtual server networking in the cluster may vary." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:60(para) +msgid "An alternative architecture would be to add more messaging servers if you notice a lot of back up in the messaging queue causing performance problems. In that case you would add an additional RabbitMQ server in addition to or instead of scaling up the database server. Your installation can run any nova- service on any server as long as the nova.conf is configured to point to the RabbitMQ server and the server can send messages to the server." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:66(para) +msgid "Multiple installation architectures are possible, here is another example illustration." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-configure-volumes.xml:5(title) +msgid "Installing and Configuring Volumes for Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-configure-volumes.xml:6(para) +msgid "For additional information about managing volumes including troubleshooting, refer to the OpenStack Compute Administration Guide." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:6(title) +msgid "Installing OpenStack Walk-through" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:7(para) +msgid "The OpenStack Compute and Image services work together to provide access to virtual servers and images through REST APIs. The Identity Service provides a common authorization layer for all OpenStack services. You must use the Identity Service to install the OpenStack Dashboard, which offers a web-based user interface for OpenStack components. The OpenStack Object Storage service provides not only a storage method for virtual images but also a cloud-based object storage system with a REST API to store and retrieve objects such as images or videos. This walk-through starts with Identity, then goes through Image and Compute and also provides deployment information about an Object Storage installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:20(para) +msgid "Here are the overall steps:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:22(para) +msgid "Review the most supported platforms. Red Hat Enterprise Linux, Scientific Linux, CentOS, Fedora, Debian, and Ubuntu are the most tested platforms currently." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:26(para) +msgid "Install the Identity Service (Keystone)." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:29(para) +msgid "Configure the Identity Service." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:32(para) +msgid "Install the Image Service (Glance)." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:35(para) +msgid "Configure the Image Service." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:38(para) +msgid "Install Compute (Nova)." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:41(para) +msgid "Review the assumptions made in this installation for Compute." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:45(para) +msgid "Configure Compute with FlatDHCP networking using 192.168.100.0/24 as the fixed range for our guest VMs on a bridge named br100." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:50(para) +msgid "Create and initialize the Compute database with MySQL. PostgreSQL is also documented but all examples follow MySQL as an assumed default." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:55(para) +msgid "Add images." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:58(para) +msgid "(optional) Install OpenStack Object Storage (Swift)." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:62(para) +msgid "Install the OpenStack Dashboard." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:65(para) +msgid "Launch the Dashboard." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:68(para) +msgid "Add a keypair through the Dashboard." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:71(para) +msgid "Launch an image through the Dashboard to verify the entire installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/determining-version-of-compute.xml:6(title) +msgid "Determining the Version of Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/determining-version-of-compute.xml:7(para) +msgid "You can find the version of the installation by using the nova-manage command:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:9(title) +msgid "Installing and Configuring the Image Service" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:11(para) +msgid "Install the Image service, as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:14(para) +msgid "10/10/12: When using the Ubuntu Cloud Archive, you need to re-install the python-keystoneclient after installing the glance packages listed above, otherwise you see an error." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:18(para) +msgid "If you are using Ubuntu, delete the glance.sqlite file created in the /var/lib/glance/ directory:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:22(title) +msgid "Configuring the Image Service database backend" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:23(para) +msgid "Configure the backend data store. For MySQL, create a glance MySQL database and a glance MySQL user. Grant the \"glance\" user full access to the glance MySQL database." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:24(para) +msgid "Start the MySQL command line client by running:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:25(para) +msgid "Enter the MySQL root user's password when prompted." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:26(para) +msgid "To configure the MySQL database, create the glance database." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:27(para) +msgid "Create a MySQL user for the newly-created glance database that has full control of the database." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:28(replaceable) ./doc/src/docbkx/openstack-install/install-config-glance.xml:29(replaceable) ./doc/src/docbkx/openstack-install/install-config-glance.xml:135(replaceable) ./doc/src/docbkx/openstack-install/install-config-glance.xml:170(replaceable) +msgid "[YOUR_GLANCEDB_PASSWORD]" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:31(para) +msgid "In the above commands, even though the 'glance'@'%' also matches 'glance'@'localhost', you must explicitly specify the 'glance'@'localhost' entry." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:34(para) +msgid "By default, MySQL will create entries in the user table with User='' and Host='localhost'. The User='' acts as a wildcard, matching all users. If you do not have the 'glance'@'localhost' account, and you try to log in as the glance user, the precedence rules of MySQL will match against the User='' Host='localhost' account before it matches against the User='glance' Host='%' account. This will result in an error message that looks like:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:45(para) +msgid "Thus, we create a separate User='glance' Host='localhost' entry that will match with higher precedence." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:52(para) +msgid "Enter quit at the mysql> prompt to exit MySQL." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:59(title) +msgid "Edit the Glance configuration files and paste ini middleware files" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:61(para) +msgid "The Image service has a number of options that you can use to configure the Glance API server, optionally the Glance Registry server, and the various storage backends that Glance can use to store images. By default, the storage backend is in file, specified in the glance-api.conf config file in the section [DEFAULT]." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:68(para) +msgid "The glance-api service implements versions 1 and 2 of the OpenStack Images API. By default, both are enabled by setting these configuration options to True in the glance-api.conf file." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:76(para) +msgid "Disable either version of the Images API by setting the option to False in the glance-api.conf file." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:80(para) +msgid "In order to use the v2 API, you must copy the necessary SQL configuration from your glance-registry service to your glance-api configuration file. The following instructions assume that you want to use the v2 Image API for your installation. The v1 API is implemented on top of the glance-registry service while the v2 API is not." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:88(para) +msgid "Most configuration is done via configuration files, with the Glance API server (and possibly the Glance Registry server) using separate configuration files. When installing through an operating system package management system, sample configuration files are installed in /etc/glance. You configure the PasteDeploy configuration, which controls the deployment of the WSGI application for each component, in files named component-paste.ini, such as glance-api-paste.ini." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:98(para) +msgid "This walkthrough installs the image service using a file backend and the Identity service (Keystone) for authentication." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:101(para) +msgid "Update /etc/glance/glance-api-paste.ini and configure the admin_* values under [filter:authtoken]." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:110(para) +msgid "Add the admin and service identifiers and flavor=keystone to the end of /etc/glance/glance-api.conf as shown below." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:132(para) +msgid "Ensure that /etc/glance/glance-api.conf points to the MySQL database rather than sqlite." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:136(para) +msgid "Restart glance-api to pick up these changed settings." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:139(para) +msgid "Update the last sections of /etc/glance/glance-registry.conf to reflect the values you set earlier for admin user and the service tenant, plus enable the Identity service with flavor=keystone." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:161(para) +msgid "Update /etc/glance/glance-registry-paste.ini by enabling the Identity service, keystone:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:167(para) +msgid "Ensure that /etc/glance/glance-registry.conf points to the MySQL database rather than sqlite." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:171(para) +msgid "Restart glance-registry to pick up these changed settings." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:175(para) +msgid "Any time you change the .conf files, restart the corresponding service." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:178(para) +msgid "On Ubuntu 12.04, the database tables are under version control and you must do these steps on a new install to prevent the Image service from breaking possible upgrades, as root: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:183(para) +msgid "Now you can populate or migrate the database. " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:185(para) +msgid "Restart glance-registry and glance-api services, as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:190(para) +msgid "This guide does not configure image caching, refer to http://docs.openstack.org/developer/glance/ for more information." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:6(title) +msgid "Verifying the Image Service Installation" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:7(para) +msgid "To validate the Image service client is installed, enter at the command line." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:10(para) +msgid "Obtain a test image." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:15(para) +msgid "Upload the kernel." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:16(para) +msgid "This example shows inputting --os-username, --os-password, --os-tenant-name, --os-auth-url on the command line for reference. You could also use the OS_* environment variables by setting them in an openrc file:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:21(para) +msgid "Then you would source these environment variables by running ." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:48(para) +msgid "Upload the initrd." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:75(para) +msgid "Upload the image." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:108(para) +msgid "Now a glance image-list should show three images." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/vnc-console.xml:7(para) +msgid "To validate the Dashboard installation, point your browser at http://192.168.206.130. Note that you cannot use VNC Console from a Chrome browser. You need both Flash installed and a Firefox browser. Once you connect to the Dashboard with the URL, you should see a login window. Enter the credentials for users you created with the Identity Service, Keystone. For example, enter \"admin\" for the username and \"secrete\" as the password." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:10(title) +msgid "OpenStack Install and Deploy Manual - Red HatUbuntu" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:20(orgname) ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:30(productname) +msgid "OpenStack" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:24(year) +msgid "2012" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:25(year) +msgid "2013" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:26(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:28(releaseinfo) +msgid "Grizzly, Compute 2013.1, Network 2013.1, Object Storage 1.7.6" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:31(pubdate) ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:57(date) +msgid "2013-02-12" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:34(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:38(para) +msgid "The OpenStack™ system has several key projects that are separate installations but can work together depending on your cloud needs: OpenStack Compute, OpenStack Object Storage, OpenStack Identity Service, and OpenStack Image Service. You can install any of these projects separately and then configure them either as standalone or connected entities. This guide walks through an installation using packages available through Ubuntu 12.04.This guide walks through an installation using packages available through Fedora 17 as well as on RHEL and derivatives through the EPEL repository. It offers explanations for the configuration choices as well as sample configuration files." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:61(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/src/docbkx/openstack-install/bk_openstackinstallguide.xml:71(date) +msgid "2013-01-16" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:75(para) +msgid "Fix file copy issue for figures in the /common/ directory." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:81(date) +msgid "2012-11-09" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:85(para) +msgid "Folsom release of this document." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:91(date) +msgid "2012-10-10" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:95(para) +msgid "Doc bug fixes: 10544591064745" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:105(date) +msgid "2012-09-26" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:109(para) +msgid "Adds an all-in-one install section." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:115(date) +msgid "2012-07-23" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:119(para) +msgid "Adds additional detail about installing and configuring nova-volumes." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:124(para) +msgid "Doc bug fixes: 9785101027230" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:135(date) +msgid "2012-07-17" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:139(para) +msgid "Update build process so two uniquely-named PDF files are output." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:145(date) +msgid "2012-07-13" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:149(para) +msgid "Doc bug fixes: 10258401025847" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:162(date) +msgid "2012-06-19" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:166(para) +msgid "Fix PDF links." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:169(para) +msgid "Doc bug fixes: 967778984959, 1002294, 1010163." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:187(date) +msgid "2012-05-31" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:191(para) +msgid "Revise install guide to encompass more Linux distros." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:195(para) +msgid "Doc bug fixes: 996988, 998116, 999005." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:207(date) +msgid "2012-05-03" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:211(para) +msgid "Fixes problems with glance-api-paste.ini and glance-registry-paste.ini samples and instructions." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:218(para) +msgid "Removes \"DRAFT\" designation." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:224(date) +msgid "2012-05-02" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:228(para) +msgid "Essex release." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:234(date) +msgid "2012-05-01" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:238(para) +msgid "Updates the Object Storage and Identity (Keystone) configuration." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:244(date) +msgid "2012-04-25" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:248(para) +msgid "Changes service_id copy/paste error for the EC2 service-create command." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:249(para) +msgid "Adds verification steps for Object Storage installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:250(para) +msgid "Fixes proxy-server.conf file so it points to keystone not tempauth." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:256(date) +msgid "2012-04-23" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:260(para) +msgid "Adds installation and configuration for mulit-node Object Storage service." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:266(date) +msgid "2012-04-17" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:270(para) +msgid "Doc bug fixes: 983417, 984106, 984034" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:282(date) +msgid "2012-04-13" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:286(para) +msgid "Doc bug fixes: 977905, 980882, 977823, adds additional Glance database preparation steps" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:300(date) +msgid "2012-04-10" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:304(para) +msgid "Doc bug fixes: 977831" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:310(date) +msgid "2012-03-23" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:314(para) +msgid "Updates for Xen hypervisor." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:320(date) +msgid "2012-03-09" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:324(para) +msgid "Updates for Essex release, includes new Glance config files, new Keystone configuration." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:332(date) +msgid "2012-01-24" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:336(para) +msgid "Initial draft for Essex." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:338(para) +msgid "Assumes use of Ubuntu 12.04 repository." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:345(date) +msgid "2011-01-24" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:349(para) +msgid "Initial draft for Diablo." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:6(title) +msgid "Configuring Multiple Compute Nodes" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:7(para) +msgid "If your goal is to split your VM load across more than one server, you can connect an additional nova-compute node to a cloud controller node. This configuring can be reproduced on multiple compute servers to start building a true multi-node OpenStack Compute cluster." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:12(para) +msgid "To build out and scale the Compute platform, you spread out services amongst many servers. While there are additional ways to accomplish the build-out, this section describes adding compute nodes, and the service we are scaling out is called 'nova-compute.'" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:17(para) +msgid "For a multi-node install you only make changes to nova.conf and copy it to additional compute nodes. Ensure each nova.conf file points to the correct IP addresses for the respective services. Customize the nova.conf example below to match your environment. The CC_ADDR is the Cloud Controller IP Address." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:40(para) +msgid "By default, Nova sets the bridge device based on the setting in --flat_network_bridge. Now you can edit /etc/network/interfaces with the following template, updated with your IP information." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:65(para) +msgid "Restart networking:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:67(para) +msgid "With nova.conf updated and networking set, configuration is nearly complete. First, bounce the relevant services to take the latest updates:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:71(para) +msgid "To avoid issues with KVM and permissions with Nova, run the following commands to ensure we have VM's that are running optimally:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:78(para) +msgid "If you want to use the 12.04 Ubuntu Enterprise Cloud images that are readily available at http://uec-images.ubuntu.com/releases/12.04/release/, you may run into delays with booting. Any server that does not have nova-api running on it needs this iptables entry so that UEC images can get metadata info. On compute nodes, configure the iptables with this next step:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:86(para) +msgid "Lastly, confirm that your compute node is talking to your cloud controller. From the cloud controller, run this database query:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:90(para) +msgid "In return, you should see something similar to this:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:104(para) +msgid "You can see that osdemo0{1,2,4,5} are all running nova-compute. When you start spinning up instances, they will allocate on any node that is running nova-compute from this list." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:6(title) +msgid "Defining Roles and Users in the Identity Service (Keystone)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:7(para) +msgid "Before you begin, ensure that the OpenStack Compute and Image services are installed and connect all databases prior to configuring the Identity Service endpoints." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:10(para) +msgid "Create tenants first. Here is an example set." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:15(para) +msgid "Next, create users." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:22(para) +msgid "Here are some roles to create." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:28(para) +msgid "Add Roles to Users in Tenants" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:36(para) +msgid "Also, the Member role is used by Horizon and Swift so we need to continue creating it:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:42(title) +msgid "Define Services and Endpoints" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:43(para) +msgid "Now that all your starter tenants, users, and roles have been created, let's move on to endpoints." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:45(para) +msgid "First add all the services you want to have the Identity service connected with. Here's an example using all the available services in this example." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:78(para) +msgid "The Identity Service, Keystone, is now configured and ready to accept requests." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:7(title) +msgid "Verify the Installation" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:8(para) +msgid "You can run these commands from the proxy server or any server with access to the Identity Service." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:11(para) +msgid "First, export the swift admin password (setup previously) in a variable so it can be re-used." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:15(para) +msgid "If you do not wish to have the swift admin password stored in your shell's history, you may perform the following:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:22(para) +msgid "Run the swift CLI, swift, with the correct Identity service URL. Export the information for ADMINPASS using $ export ADMINPASS=secrete." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:43(para) +msgid "Use swift to upload a few files named ‘bigfile[1-2].tgz’ to a container named ‘myfiles’:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:53(para) +msgid "Use swift to download all files from the ‘myfiles’ container:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:62(para) +msgid "If you are using swauth in preference to the OpenStack Identity service, you should use the default_swift_cluster variable to connect to your swift cluster. Please follow the swauth documentation to verify your installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:6(title) +msgid "Installing and Configuring the Identity Service" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:7(para) +msgid "Install the Identity service on any server that is accessible to the other servers you intend to use for OpenStack services, as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:12(para) +msgid "After installing, you need to delete the sqlite database it creates, then change the configuration to point to a MySQL database. This configuration enables easier scaling scenarios since you can bring up multiple Keystone front ends when needed, and configure them all to point back to the same database. Plus a database backend has built-in data replication features and documentation surrounding high availability and data redundancy configurations." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:20(para) +msgid "Delete the keystone.db file created in the /var/lib/keystone directory." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:23(para) +msgid "Configure the production-ready backend data store rather than using the catalog supplied by default for the ability to backup the service and endpoint data. This example shows MySQL." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:26(para) +msgid "The following sequence of commands will create a MySQL database named \"keystone\" and a MySQL user named \"keystone\" with full access to the \"keystone\" MySQL database." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:29(para) +msgid "On Fedora, RHEL, and CentOS, you can configure the Keystone database with the command." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:32(para) +msgid "To manually create the database, start the command line client by running:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:36(para) +msgid "To configure the MySQL database, create the keystone database." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:39(para) +msgid "Create a MySQL user for the newly-created keystone database that has full control of the keystone database." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:43(para) +msgid "Choose a secure password for the keystone user and replace all references to [YOUR_KEYSTONEDB_PASSWORD] with this password." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:48(replaceable) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:49(replaceable) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:87(replaceable) +msgid "[YOUR_KEYSTONEDB_PASSWORD]" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:52(para) +msgid "In the above commands, even though the 'keystone'@'%' also matches 'keystone'@'localhost', you must explicitly specify the 'keystone'@'localhost' entry." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:55(para) +msgid "By default, MySQL will create entries in the user table with User='' and Host='localhost'. The User='' acts as a wildcard, matching all users. If you do not have the 'keystone'@'localhost' account, and you try to log in as the keystone user, the precedence rules of MySQL will match against the User='' Host='localhost account before it matches against the User='keystone' Host='%' account. This will result in an error message that looks like:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:65(para) +msgid "Thus, we create a separate User='keystone' Host='localhost' entry that will match with higher precedence." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:72(para) +msgid "Enter quit at the mysql> prompt to exit MySQL." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:77(para) +msgid "Recall that this document assumes the Cloud Controller node has an IP address of 192.168.206.130." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:80(para) +msgid "Once Keystone is installed, it is configured via a primary configuration file (/etc/keystone/keystone.conf), and by initializing data into keystone using the command line client. By default, Keystone's data store is sqlite. To change the data store to mysql, change the line defining connection in /etc/keystone/keystone.conf like so:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:88(para) +msgid "Also, ensure that the proper service token is used in the keystone.conf file. An example is provided in the Appendix or you can generate a random string. The sample token is:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:93(para) +msgid "Next, restart the keystone service so that it picks up the new database configuration." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:97(para) +msgid "Lastly, initialize the new keystone database, as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:100(title) +msgid "Configuring Services to work with Keystone" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:101(para) +msgid "Once Keystone is installed and running, you set up users and tenants and services to be configured to work with it. You can either follow the manual steps or use a script." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:108(para) +msgid "The parameters --token and --endpoint are valid for the keystoneclient available after October 2012. Use --token and --endpoint with the keystoneclient released with the Folsom packaging. This install guide documents installing the client from packages, but you can use the client from another computer with the CLI Guide instructions for ." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:120(title) +msgid "Setting up tenants, users, and roles - manually" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:121(para) +msgid "You need to minimally define a tenant, user, and role to link the tenant and user as the most basic set of details to get other services authenticating and authorizing with the Identity service." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:126(title) +msgid "Scripted method available" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:127(para) +msgid "These are the manual, unscripted steps using the keystone client. A scripted method is available at Setting up tenants, users, and roles - scripted." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:132(para) +msgid "First, create a default tenant, we'll name it demo in this example." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:143(para) +msgid "Create a default user named admin." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:154(para) +msgid "Create an administrative role based on keystone's default policy.json file, admin." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:164(para) +msgid "Grant the admin role to the admin user in the demo tenant with \"user-role-add\"." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:169(para) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:198(para) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:214(para) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:230(para) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:247(para) +msgid "There is no output to this command." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:170(para) +msgid "Create a Service Tenant. This tenant contains all the services that we make known to the service catalog." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:181(para) +msgid "Create a Glance Service User in the Service Tenant. You'll do this for any service you add to be in the Keystone service catalog." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:194(para) +msgid "Grant the admin role to the glance user in the service tenant." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:199(para) +msgid "Create a Nova Service User in the Service Tenant." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:210(para) +msgid "Grant the admin role to the nova user in the service tenant." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:215(para) +msgid "Create an EC2 Service User in the Service Tenant." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:226(para) +msgid "Grant the admin role to the ec2 user in the service tenant." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:231(para) +msgid "Create an Object Storage Service User in the Service Tenant." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:243(para) +msgid "Grant the admin role to the swift user in the service tenant." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:248(para) +msgid "Next you create definitions for the services." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:253(title) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:7(title) +msgid "Defining Services" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:254(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:8(para) +msgid "Keystone also acts as a service catalog to let other OpenStack systems know where relevant API endpoints exist for OpenStack Services. The OpenStack Dashboard, in particular, uses the service catalog heavily - and this must be configured for the OpenStack Dashboard to properly function." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:263(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:17(para) +msgid "Using a template file" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:266(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:20(para) +msgid "Using a database backend" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:260(para) +msgid "There are two alternative ways of defining services with keystone: While using a template file is simpler, it is not recommended except for development environments such as DevStack. The template file does not enable CRUD operations on the service catalog through keystone commands, but you can use the service-list command when using the template catalog. A database backend can provide better reliability, availability, and data redundancy. This section describes how to populate the Keystone service catalog using the database backend. Your /etc/keystone/keystone.conf file should contain the following lines if it is properly configured to use the database backend." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:285(title) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:45(title) +msgid "Elements of a Keystone service catalog entry" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:293(literal) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:55(literal) +msgid "--name" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:295(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:56(para) +msgid "Name of the service (e.g., nova, ec2, glance, keystone)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:303(literal) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:59(literal) +msgid "--type" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:305(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:60(para) +msgid "Type of service (e.g., compute, ec2, image, identity)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:313(literal) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:63(literal) +msgid "--description" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:315(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:64(para) +msgid "A description of the service, (e.g., \"Nova Compute Service\")" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:289(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:50(para) +msgid "Use the command to create a database entry for the service, with the following attributes: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:324(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:70(para) +msgid "Use the command to create a database entry that describes how different types of clients can connect to the service, with the following attributes:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:330(literal) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:75(literal) +msgid "--region" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:332(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:76(para) +msgid "the region name you've given to the OpenStack cloud you are deploying (e.g., RegionOne)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:337(literal) +msgid "--service-id" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:339(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:81(para) +msgid "The ID field returned by the (e.g., 935fd37b6fa74b2f9fba6d907fa95825)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:345(literal) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:85(literal) +msgid "--publicurl" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:347(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:86(para) +msgid "The URL of the public-facing endpoint for the service (e.g., http://192.168.206.130:9292 or http://192.168.206.130:8774/v2/%(tenant_id)s)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:356(literal) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:89(literal) +msgid "--internalurl" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:358(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:90(para) +msgid "The URL of an internal-facing endpoint for the service." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:360(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:91(para) +msgid "This typically has the same value as publicurl." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:365(literal) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:94(literal) +msgid "--adminurl" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:367(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:95(para) +msgid "The URL for the admin endpoint for the service. The Keystone and EC2 services use different endpoints for adminurl and publicurl, but for other services these endpoints will be the same." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:286(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:46(para) +msgid "For each service in the catalog, you must perform two keystone operations: " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:379(para) +msgid "Keystone allows some URLs to contain special variables, which are automatically substituted with the correct value at runtime. Some examples in this document employ the tenant_id variable, which we use when specifying the Volume and Compute service endpoints. Variables can be specified using either %(varname)s or $(varname)s notation. In this document, we always use the %(varname)s notation (e.g., %(tenant_id)s) since $ is interpreted as a special character by Unix shells." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:394(title) +msgid "Creating keystone services and service endpoints" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:395(para) +msgid "Here we define the services and their endpoints." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:396(para) +msgid "Define the Identity service:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:436(para) +msgid "The %(tenant_id)s and single quotes around the publicurl, internalurl, and adminurl must be typed exactly as shown for both the Compute endpoint and the Volume endpoint." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:433(para) +msgid "Define the Compute service, which requires a separate endpoint for each tenant. Here we use the service tenant from the previous section. " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:479(para) +msgid "Define the Volume service, which also requires a separate endpoint for each tenant." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:521(para) +msgid "Define the Image service:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:562(para) +msgid "Define the EC2 compatibility service:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:601(para) +msgid "Define the Object Storage service:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:642(title) +msgid "Setting up Tenants, Users, Roles, and Services - Scripted" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:644(para) +msgid "The Keystone project offers a bash script for populating tenants, users, roles and services at https://github.com/openstack/keystone/blob/master/tools/sample_data.sh with sample data. This script uses 127.0.0.1 for all endpoint IP addresses. This script also defines services for you." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:7(title) +msgid "System Requirements" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:7(para) +msgid "Hardware: OpenStack Object Storage specifically is designed to run on commodity hardware." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:22(para) +msgid "Object Storage object servers" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:24(para) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:49(para) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:56(para) +msgid "Processor: dual quad core" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:24(para) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:50(para) +msgid "Memory: 8 or 12 GB RAM" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:25(para) +msgid "Disk space: optimized for cost per GB" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:27(para) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:51(para) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:56(para) +msgid "Network: one 1 GB Network Interface Card (NIC)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:29(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/src/docbkx/openstack-install/object-storage-sys-requirements.xml:41(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/src/docbkx/openstack-install/object-storage-sys-requirements.xml:48(para) +msgid "Object Storage container/account servers" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:53(para) +msgid "Optimized for IOPS due to tracking with SQLite databases." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:54(para) +msgid "Object Storage proxy server" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:57(para) +msgid "Higher network throughput offers better performance for supporting many API requests." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:59(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 10g networking to the proxy, or are terminating SSL traffic at the proxy, greater CPU power will be required." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:65(para) +msgid "Operating System: OpenStack Object Storage currently runs on Ubuntu, RHEL, CentOS, or Fedora and the large scale deployment at Rackspace runs on Ubuntu 10.04 LTS." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:69(para) +msgid "Networking: 1000 Mbps are suggested. 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/src/docbkx/openstack-install/object-storage-sys-requirements.xml:73(para) +msgid "Database: For OpenStack Object Storage, a SQLite database is part of the OpenStack Object Storage container and account management process." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:76(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 "" + +#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:6(title) +msgid "OpenStack Object Storage Post Installation" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:7(para) +msgid "Now that the proxy server and storage servers are configured, you want to restart the services." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:12(title) +msgid "Adding an Additional Proxy Server" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:13(para) +msgid "For reliability’s sake you may want to have more than one proxy server. You can set up the additional proxy node in the same manner that you set up the first proxy node but with additional configuration steps." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:19(para) +msgid "Once you have more than two proxies, you also want to load balance between the two, which means 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/src/docbkx/openstack-install/object-storage-post-install.xml:29(para) +msgid "Configure an initial proxy node for the initial setup, and then follow these additional steps for more proxy servers." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:34(para) +msgid "Update the list of memcache servers in /etc/swift/proxy-server.conf for all the added proxy servers. If you run multiple memcache servers, use this pattern for the multiple IP:port listings: in each proxy server’s conf file.:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:60(para) +msgid "After you sync all the nodes, make sure the admin has the keys in /etc/swift and the ownership for the ring file is correct." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:68(para) +msgid "If you are using swauth in preference to the OpenStack Identity service, there are additional steps to follow for the addition of a second proxy server. Please follow the swauth documentation Installation section, paying close attention to the default_swift_cluster variable." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installdashboard.xml:7(title) ./doc/src/docbkx/openstack-install/dashboard-install.xml:3(title) +msgid "Installing the OpenStack Dashboard" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installdashboard.xml:8(para) +msgid "OpenStack has components that provide a view of the OpenStack installation such as a Django-built website that serves as a dashboard." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installdashboard.xml:12(title) ./doc/src/docbkx/openstack-install/about-dashboard.xml:8(title) +msgid "About the Dashboard" +msgstr "" + +#. +#: ./doc/src/docbkx/openstack-install/ch_installdashboard.xml:13(para) ./doc/src/docbkx/openstack-install/about-dashboard.xml:10(para) +msgid "You can use a dashboard interface with an OpenStack Compute installation with a web-based console provided by the Openstack-Dashboard project. It provides web-based interactions with the OpenStack Compute cloud controller through the OpenStack APIs. For more information about the Openstack-Dashboard project, please visit: https://github.com/openstack/horizon/. These instructions are for an example deployment configured with an Apache web server." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:4(para) +msgid "Here are the overall steps for creating the OpenStack dashboard." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:7(para) +msgid "Install the OpenStack Dashboard framework including Apache and related modules." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:11(para) +msgid "Configure the Dashboard." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:14(para) +msgid "Restart and run the Apache server." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:17(para) +msgid "Install the OpenStack Dashboard, as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:20(para) +msgid "Next, modify the variable CACHE_BACKEND in /etc/openstack-dashboard/local_settings.py to match the ones set in /etc/memcached.conf/etc/sysconfig/memcached.conf. Open /etc/openstack-dashboard/local_settings.py and look for this line:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:26(para) +msgid "The address and port in the new value need to be equal to the ones set in /etc/memcached.conf/etc/sysconfig/memcached.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:28(para) +msgid "If you change the memcached settings, restart the Apache web server for the changes to take effect." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:30(para) +msgid "This guide has selected memcache as a session store for OpenStack Dashboard. There are other options available, each with benefits and drawbacks. Refer to the OpenStack Dashboard Session Storage section for more information." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:35(para) +msgid "In order to change the timezone you can use either dashboard or inside /etc/openstack-dashboard/local_settings.py you can change below mentioned parameter." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-network-planning.xml:5(title) +msgid "Compute Network Planning" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-network-planning.xml:6(para) +msgid "For both conserving network resources and ensuring that network administrators understand the needs for networks and public IP addresses for accessing the APIs and VMs as necessary, this section offers recommendations and required minimum sizes. Throughput of at least 1000 Mbps is suggested. This walkthrough shows network configurations for a single server." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-network-planning.xml:13(para) +msgid "For OpenStack Compute, networking is configured on multi-node installations between the physical machines on a single subnet. For networking between virtual machine instances, three network options are available: flat, DHCP, and VLAN. Two NICs (Network Interface Cards) are recommended on the server running nova-network." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-network-planning.xml:19(para) +msgid "Management Network (RFC1918 IP Range, not publicly routable): This network is utilized for all inter-server communications within the cloud infrastructure. Recommended size: 255 IPs (CIDR /24)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-network-planning.xml:23(para) +msgid "Public Network (Publicly routable IP range): This network is utilized for providing Public IP accessibility to the API endpoints within the cloud infrastructure. Minimum size: 8 IPs (CIDR /29)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-network-planning.xml:27(para) +msgid "VM Network (RFC1918 IP Range, not publicly routable): This network is utilized for providing primary IP addresses to the cloud instances. Recommended size: 1024 IPs (CIDR /22)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-network-planning.xml:30(para) +msgid "Floating IP network (Publicly routable IP Range): This network is utilized for providing Public IP accessibility to selected cloud instances. Minimum size: 16 IPs (CIDR /28)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:6(title) +msgid "Installation Assumptions" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:7(para) +msgid "OpenStack Compute has a large number of configuration options. To simplify this installation guide, we make a number of assumptions about the target installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:12(para) +msgid "You have a collection of compute nodes, each installed with Fedora 17, RHEL 6.2, Scientific Linux 6.1 or CentOS 6 + CR distributions (continuous release ( CR ) repository)." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:18(para) +msgid "You have a collection of compute nodes, each installed with Ubuntu Server 12.04." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:20(para) +msgid "There is also an OpenStack Install and Deploy Manual for UbuntuThere is also an OpenStack Install and Deploy Manual for RHEL, CentOS and Fedora Debian, openSUSE, and SLES also have OpenStack support, but are not documented here." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:23(para) +msgid "You have designated one of the nodes as the Cloud Controller, which will run all of the services (RabbitMQ or Qpid, MySQL, Identity, Image, nova-api, nova-network, nova-scheduler, nova-volume) except for nova-compute." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:28(para) +msgid "The disk partitions on your cloud controller are being managed by the Logical Volume Manager (LVM)." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:33(para) +msgid "Your Cloud Controller has an LVM volume group named \"nova-volumes\" to provide persistent storage to guest VMs. Either create this during the installation or leave some free space to create it prior to installing nova services." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:41(para) +msgid "Ensure that the server can resolve its own hostname, otherwise you may have problems if you are using RabbitMQ as the messaging backend. RabbitMQ is the default messaging back-end on UbuntuQpid is the default messaging back-end on Fedora" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:50(para) +msgid "192.168.206.130 is the primary IP for our host on eth0." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:54(para) +msgid "192.168.100.0/24 as the fixed range for our guest VMs, connected to the host via br100." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:58(para) +msgid "FlatDHCP with a single network interface." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:61(para) +msgid "KVM or Xen (XenServer or XCP) as the hypervisor." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:65(para) +msgid "On Ubuntu, enable the Cloud Archive repository by adding the following to /etc/apt/sources.list.d/folsom.list:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:69(para) +msgid "Prior to running apt-get update and apt-get upgrade, install the keyring :" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:73(para) +msgid "Ensure the operating system is up-to-date by running prior to the installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:76(para) +msgid "Ensure the operating system is up-to-date by running and prior to the installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:81(para) +msgid "On RHEL (and derivatives) enable the EPEL repository by running:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:84(para) +msgid "This installation process walks through installing a cloud controller node and a compute node using a set of packages that are known to work with each other. The cloud controller node contains all the nova- services including the API server and the database server. The compute node needs to run only the nova-compute service. You only need one nova-network service running in a multi-node install, though if high availability for networks is required, there are additional options." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installcomputeimage.xml:6(title) +msgid "Installing OpenStack Compute and Image Service" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_installcomputeimage.xml:7(para) +msgid "The OpenStack Compute and Image services work together to provide access to virtual servers and images through REST APIs." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-create-network.xml:6(title) +msgid "Creating the Network for Compute VMs" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-create-network.xml:7(para) +msgid "You must run the command that creates the network and the bridge using the br100 specified in the nova.conf file to create the network that the virtual machines use. This example shows the network range using 192.168.100.0/24 as the fixed range for our guest VMs, but you can substitute the range for the network you have available. We're labeling it with private in this case." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:6(title) +msgid "Running Virtual Machine Instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:8(title) +msgid "Security groups: Enabling SSH and ICMP (ping)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:9(para) +msgid "The Compute service uses the concept of security groups to control what network protocols (TCP, UDP, ICMP), ports, and IP addresses are permitted to access instances. Each tenant manages its own list of security groups and starts off with a security group called default. If no security group is specified upon boot, the virtual machine will be associated with the default security group." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:14(para) +msgid "Security groups can be listed by the command." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:21(para) +msgid "In this example, we will use the nova command to enable access to TCP port 22 (so we can SSH to instances) Allow access to port 22 from all IP addresses (specified in CIDR notation as 0.0.0.0/0) with the following command:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:25(para) +msgid "When specifying rules for TCP and UDP protocols, you may specify a range of port consecutive addresses in a single rule (e.g., from port 5901 to port 5999). In this case, only a single port is being enabled, so we specify the start port as 22 and the end port as 22." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:30(para) +msgid "To be able to ping virtual machine instances, you must specify a rule to allow ICMP traffic. When specifying ICMP rules, instead of specifying a begin and end port, you specify a pemitted ICMP code and ICMP type. You can also specify -1 for the code to enable all codes and -1 for the type to enable all ICMP types. Allow access to all codes and types of ICMP traffic from all IP addresses with the following command:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:41(title) +msgid "Adding a keypair" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:42(para) +msgid "The Compute service can inject an SSH public key into an account on the instance, assuming the virtual machine image being used supports this. To add a keypair to the Compute service, use the command. This command can be used to either generate a new keypair, or to upload an existing public key. The following example uploads an existing public key, located at ~/.ssh/id_rsa.pub, and gives the keypair the name mykey." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:49(para) +msgid "List the keypairs by doing:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:55(para) +msgid "Confirm that the uploaded keypair matches your local key by checking your key's fingerprint with the command:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:61(title) +msgid "Confirm all services running" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:65(systemitem) +msgid "nova-api" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:67(para) +msgid "The nova-api service must be running to respond to the request to boot an instance, as well as to serve as the metadata server so that the instance can retrieve the public key uploaded i a previous section. If the commands in the previous section succeeded, then the service is running." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:76(systemitem) +msgid "nova-scheduler" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:78(para) +msgid "The nova-scheduler service must be running in order to dispatch requests for a new virtual machine instance to a host running the nova-compute service that has sufficient resources." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:86(para) +msgid "The nova-compute service must be running in order to interact with the hypervisor to bring up a virtual machine instance." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:94(para) +msgid "The nova-network service must be running in order to perform networking tasks such as assigning an IP address to the virtual machine instance and implementing the security group rules." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:62(para) +msgid "Before trying to start an instance, confirm that all of the necessary services are running, in particular:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:103(para) +msgid "The command does not indicate whether the nova-api service is running." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:101(para) +msgid "The command can be used to confirm that these services are running properly." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:107(para) +msgid "As root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:113(para) +msgid "If any of the services are missing in your configuration, or the State column does not show a smiley face, then your Compute service will not be able to launch an instance." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:118(title) +msgid "Starting an instance" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:119(para) +msgid "To start an instance, we need to specify a flavor, also known as an instance type, which indicates the size of an instance. Use the command to view the list of available flavors:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:133(para) +msgid "We also need to specify the image. Use the to retrieve the ID of the CirrOS image." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:148(replaceable) +msgid "f4addd24-4e8a-46bb-b15d-fae2591f1a35" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:141(para) +msgid "Use the nova boot command to launch a new virtual machine instance. We'll use an m1.small instance in this example, using the CirrOS image, and the mykey keypair we added. We also need to give this virtual machine instance a name, we'll call it cirros. We will explicitly specify the default security group in this example, although this isn't strictly necessary since the default group will be used if no security group is specified." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:177(para) +msgid "Check the progress of the instance with the command. When the instance has booted, the command output will look something like:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:185(para) +msgid "You can view the boot messages of the instances using the command:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:214(para) +msgid "You should be able to ping your instance:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:228(para) +msgid "You should be able to ssh to your instance as the cirros user, using either the ssh keypair you uploaded or using the password cubswin:)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:239(title) +msgid "Bringing down an instance" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:240(para) +msgid "Bring down your instance using the command:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:6(title) +msgid "Installing and Configuring the Storage Nodes" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:9(para) +msgid "OpenStack Object Storage should work on any modern filesystem that supports Extended Attributes (XATTRS). We currently recommend XFS as it demonstrated the best overall performance for the swift use case after considerable testing and benchmarking at Rackspace. It is also the only filesystem that has been thoroughly tested." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:23(para) +msgid "For every device on the node you wish to use for storage, setup 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/src/docbkx/openstack-install/install-config-storage-nodes.xml:37(para) +msgid "Create /etc/rsyncd.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:65(para) +msgid "Edit the following line in /etc/default/rsync:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:76(para) +msgid "Create /etc/swift/account-server.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:96(para) +msgid "Create /etc/swift/container-server.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:116(para) +msgid "Create /etc/swift/object-server.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:138(para) +msgid "Start the storage services:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:152(title) +msgid "Don't Panic" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:152(para) +msgid "If you are following these instructions in a linear manner, at this point the ring files may not be present on the storage nodes. This may cause some of the services such as the *-replicator to fail to start. After you have created the ring files and distributed them to the storage nodes, a service restart should allow these to start." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-ntp.xml:6(title) +msgid "Installing Network Time Protocol (NTP)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-ntp.xml:7(para) +msgid "To keep all the services in sync across multiple machines, you need to install NTP, and if you do a multi-node configuration you will configure one server to be the reference server." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-ntp.xml:13(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. As root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-ntp.xml:20(para) +msgid "Set up the NTP client on your compute node so that the time between controller node and compute node is synchronized. Install the NTP package on the compute nodes in addition to the API nodes, to allow more gradual time updates." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:8(title) +msgid "OpenStack Grizzly deployment guide for Ubuntu Precise, Single node installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:10(para) +msgid "ASSUMPTION: Currently guide uses Nova-Network will be updated for Quantum soon, although we have created database and endpoint for the Quantum service." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:15(para) +msgid "One server with two NICs" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:17(para) +msgid "IF1 : Public traffic" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:18(para) +msgid "IF2 : Private traffic" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:49(para) +msgid "Download and install the Ubuntu Precise 12.04 LTS x86_64." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:51(para) +msgid "Add the following Ubuntu repository read about it on the Canonical blog. (as root):" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:60(para) +msgid "Install the required packages." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:64(para) +msgid "Enable the ip_forwarding." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:71(para) +msgid "Update the configuration." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:74(para) +msgid "Edit /etc/ntp.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:147(para) +msgid "Edit /etc/mysql/my.cnf and uncomment this line:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:149(para) +msgid "Restart mysql server." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:151(para) +msgid "Creating and adding the databases for all the services.Add mysql permissions for the created databases." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:172(title) +msgid "Installing and Configuring Identity service" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:173(para) +msgid "Install the packages.Edit /etc/keystone/keystone.conf and modify Admin token, SQLAlchemy, Catalog accordingly." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:177(para) +msgid "Restart Keystone." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:179(para) +msgid "Populate the database.Update the /home/$user/.bashrc by adding then credentials below.Source the environment setting.Add keystone users.Create roles." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:201(para) +msgid "Create tenants." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:204(para) +msgid "Create services.Create endpoints." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:241(para) +msgid "Retrieve all the ids." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:282(para) +msgid "Adding roles." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:305(para) +msgid "NOTE: All These ID will differ in your configuration - use the appropriate command and retrieve all the IDs." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:310(title) +msgid "Installing and configuring Image Service" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:311(para) +msgid "Install the packages." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:313(para) +msgid "Edit /etc/glance/glance-api-paste.ini (filter authoken).Edit /etc/glance/glance-registry-paste.ini (filter authtoken). Edit /etc/glance/glance-api.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:332(para) ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:338(para) +msgid "SQLAlchemy part of config." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:334(para) ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:340(para) +msgid "Append the following lines." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:337(para) +msgid "Edit /etc/glance/glance-registry.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:343(para) ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:532(para) +msgid "Populate the database." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:345(para) +msgid "Restart all services.Testing Glance configuration.If nothing is returned, then it is working." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:354(title) +msgid "Installing and configuring Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:356(para) +msgid "Install the packages.Update /etc/nova/nova.conf.Update the file ownership rights.Edit /etc/nova/api-paste.ini (filter authtoken).Populate the database.Create the private network. Restart everything." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:429(para) +msgid "The use of --vlan=100 in the above command is to work around a bug in OpenStack Folsom." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:434(para) +msgid "Check the smiling services." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:445(title) +msgid "Installing and configuring Dashboard" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:446(para) +msgid "Install the packages.Disable the quantum endpoint, as of now in our setup we are not using Quantum to do so Edit /etc/openstack-dashboard/local_settings.py - under TEMPLATE_DEBUG." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:453(para) +msgid "In order to change the timezone you can use either dashboard or inside /etc/openstack-dashboard/local_settings.py you can change the parameter below." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:461(para) +msgid "Also be aware that the local_settings.py config file has comments that instruct you to configure Apache to redirect according to the location where the Horizon login screen is installed, otherwise you just see the \"It works!\" text on the root landing page for the web server. Here is the meaningful section in local_settings.py:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:474(para) +msgid "Restart the services." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:476(para) +msgid "Logging into the dashboard with browser" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:480(title) +msgid "Installing and configuring Cinder" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:481(para) +msgid "Install the packages." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:484(para) +msgid "Edit /etc/cinder/api-paste.init (filter authtoken)." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:496(para) +msgid "Edit /etc/cinder/cinder.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:508(para) +msgid "Configuring Rabbit /etc/cinder/cinder.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:516(para) +msgid "Verify entries in nova.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:521(para) +msgid "Add a filter entry to the devices section /etc/lvm/lvm.conf to keep LVM from scanning devices used by virtual machines. NOTE: You must add every physical volume that is needed for LVM on the Cinder host. You can get a list by running pvdisplay. Each item in the filter array starts with either an \"a\" for accept, or an \"r\" for reject. Physical volumes that are needed on the Cinder host begin with \"a\". The array must end with \"r/.*/\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:527(para) +msgid "Setup the tgts file NOTE: $state_path=/var/lib/cinder/ and $volumes_dir = $state_path/volumes by default and path MUST exist!." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:530(para) +msgid "Restart the tgt service." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:534(para) +msgid "Create a 2GB test loopfile." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:536(para) +msgid "Mount it." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:538(para) +msgid "Initialise it as an lvm 'physical volume', then create the lvm 'volume group' " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:541(para) +msgid "Lets check if our volume is created. " +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:545(para) +msgid "Restart the services.Create a 1 GB test volume." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:560(title) +msgid "Installing and configuring Swift" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:561(para) +msgid "Install the packages.Create a loopback device. Create a mountpoint.Add an fstab entry inside /etc/fstab. ($user, replace it with your logged in Linux username)Mount it.Create the backend." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:580(para) +msgid "Configure rsync, by modifying /etc/default/rsync." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:582(para) +msgid "Create, /etc/rsyncd.conf and populate it with contents below.Restart the service.Create /etc/rsyslog.d/10-swift.conf.Append/add to /etc/rsyslog.conf.Configure the file permissions." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:698(para) +msgid "Configure the components." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:699(para) +msgid "Edit /etc/swift/swift.conf.Edit /etc/swift/proxy-server.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:759(para) +msgid "Create the account file /etc/swift/account-server/1.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:784(para) +msgid "Duplicate it." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:791(para) +msgid "Configure the container file (/etc/swift/container-server/1.conf).Duplicate it.Create the object server file (/etc/swift/object-server/1.conf).Duplicate it.Configure the rings.Create the zones and balance them. Restart the services. It will take sometime. Check the status" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:883(para) +msgid "Create a container name \"test\" and with the list option we can see it 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/src/docbkx/openstack-install/example-object-storage-install-arch.xml:40(None) +msgid "@@image: 'figures/swift_install_arch.png'; md5=c6519fb969c1184afa22e024de9bd2a6" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:6(title) +msgid "Example Object Storage Installation Architecture" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:9(para) +msgid "node - a host machine running one or more OpenStack Object Storage services" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:13(para) +msgid "Proxy node - node that runs Proxy services" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:16(para) +msgid "Auth node - an optionally separate node that runs the Auth service separately from the Proxy services" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:20(para) +msgid "Storage node - node that runs Account, Container, and Object services" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:24(para) +msgid "Ring - a set of mappings of OpenStack Object Storage data to physical devices" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:28(para) +msgid "To increase reliability, you may want to add additional Proxy servers for performance." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:30(para) +msgid "This document describes each Storage node as a separate zone in the ring. It is recommended to have a minimum of 5 zones. 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/src/docbkx/openstack-install/ch_images-uploading.xml:5(title) +msgid "Registering Virtual Machine Images" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:16(para) +msgid "Username: cirros" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:19(para) +msgid "Password: cubswin:)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:6(para) +msgid "To test your deployment, download some virtual machine images that are known to work with OpenStack. CirrOS is a small test image that is often used for testing OpenStack deployments. You can find the most recent CirrOS image on the CirrOS Launchpad home page under \"Downloads\". As of this writing the most recent image is version 0.3.0. A 64-bit version in QCOW2 format (compatible with KVM or QEMU hypervisors) can be downloaded at https://launchpad.net/cirros/trunk/0.3.0/+download/cirros-0.3.0-x86_64-disk.img. Once you launch the image, log in with the following credentials:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:22(para) +msgid "The 64-bit CirrOS QCOW2 image is the image we'll use for this walkthrough. More detailed information about how to obtain and create images can be found in the OpenStack Compute Administration Guide in the \"Image Management\" chapter." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:26(para) +msgid "Create a directory called stackimages to house your image files:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:31(para) +msgid "Download the CirrOS image into your stackimages directory." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:35(para) +msgid "Verify that your client can access the Image service by requesting a list of installed images:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:41(para) +msgid "If you get the following error, make sure that the environment variables set in ~/openrc" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:50(para) +msgid "Add the CirrOS image to the Image service using the command, passing the image file through standard input:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:58(para) +msgid "The returned image ID is generated dynamically, and therefore will be different on your deployment than in this example." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:64(literal) +msgid "name=cirros-0.3.0-x86_64" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:66(para) +msgid "The name field is an arbitrary label. In this example the name encodes the distribution, version, and architecture: cirros-0.3.0-x864_64." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:72(literal) +msgid "disk-format=qcow2" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:74(para) +msgid "The disk-format field specifies the format of the image file. In this case, the image file format is QCOW2, which can be verified using the command:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:79(para) +msgid "Other valid formats are raw, vhd, vmdk, vdi, iso, aki, ari and ami." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:86(literal) +msgid "container-format=bare" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:88(para) +msgid "The container-format field is required by the command but isn't actually used by any of the OpenStack services, so the value specified here has no effect on system behavior. We specify bare to indicate that the image file is not in a file format that contains metadata about the virtual machine." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:94(para) +msgid "Because the value is not used anywhere, it safe to always specify bare as the container format, although the command will accept other formats: ovf, aki, ari, ami." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:62(para) +msgid "The rationale for the arguments is:Confirm it was uploaded by listing the images in the Image service:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:105(para) +msgid "The command will also list the images in the Image service:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_dependencies.xml:6(title) +msgid "Appendix: Dependencies" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_dependencies.xml:8(para) +msgid "Included for your reference is a list of dependencies." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/ap_dependencies.xml:9(title) +msgid "Ubuntu 12.04 dependencies" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:6(title) +msgid "Installing Additional Compute Nodes" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:7(para) +msgid "There are many different ways to perform a multinode install of Compute in order to scale out your deployment and run more compute nodes, enabling more virtual machines to run simultaneously." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:11(para) +msgid "Ensure that the networking on each node is configured as documented in the Pre-configuring the network section." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:14(para) +msgid "In this case, you can install all the nova- packages and dependencies as you did for the Cloud Controller node, or just install nova-compute. Your installation can run any nova- services anywhere, so long as the service can access nova.conf so it knows where the Rabbitmq or Qpid messaging server is installed." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:20(para) +msgid "When running in a high-availability mode for networking, the compute node is where you configure the compute network, the networking between your instances. Learn more about high-availability for networking in the Compute Administration manual." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:25(para) +msgid "Because you may need to query the database from the compute node and learn more information about instances, the nova client and MySQL client or PostgresSQL client packages should be installed on any additional compute nodes." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:29(para) +msgid "Copy the nova.conf from your controller node to all additional compute nodes. As mentioned in the section entitled Configuring OpenStack Compute, modify the following configuration options so that they match the IP address of the compute host:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:6(title) +msgid "Compute Scripted Installations" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:7(para) +msgid "You can download a script for a standalone install for proof-of-concept, learning, or for development purposes for Ubuntu 11.04 at https://devstack.org. This is not a permanent installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:15(para) +msgid "Install Ubuntu 11.04 (Natty):" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:15(para) +msgid "In order to correctly install all the dependencies, we assume a specific version of Ubuntu to make it as easy as possible. OpenStack works on other flavors of Linux (and some folks even run it on Windows!) We recommend using a minimal install of Ubuntu server in a VM if this is your first time." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:22(para) +msgid "Download DevStack:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:24(para) +msgid "The devstack repo contains a script that installs OpenStack Compute with the Image Service and the Identity Service and OpenStack Object Storage. It offers templates for configuration files plus data scripts." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:32(para) +msgid "Start the install:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:32(para) +msgid "It takes a few minutes, we recommend reading the well-documented script while it is building to learn more about what is going on." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:38(para) +msgid "You can also install a more permanent deployment using an upstart script after running the devstack script." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:39(para) +msgid "Once you have tested stack.sh and tailored it to your system, you can convert the installation into upstart services. The additions with this script are the ability to run services like daemons instead of in screens, to store logs in files and offer an automatic start up after a reboot." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:46(para) +msgid "It works with glance- services, nova- services, novnc, and keystone, but not with quantum or swift as of November 22 2011. Here are the basic steps." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:50(para) +msgid "Ensure you've run ./stack.sh with all the configuration you need for your systems." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:52(para) +msgid "Download the upstart scripts:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:54(para) +msgid "The devstack repo contains a script that installs OpenStack Compute, the Image Service and the Identity Service and offers templates for configuration files plus data scripts." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:57(para) +msgid "Run the upstart install script." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:60(para) +msgid "Now the services are installed. To use them, either reboot to get rid of the services started by stack.sh, and automatically start those services, or do killall screen, then:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-network-planning.xml:5(title) +msgid "Object Storage Network Planning" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-network-planning.xml:6(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/src/docbkx/openstack-install/object-storage-network-planning.xml:12(para) +msgid "This document refers to two networks. One is a Public Network for connecting to the Proxy server, and the second is a Storage Network that is not accessible from outside the cluster, to which all of the nodes are connected. 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/src/docbkx/openstack-install/object-storage-network-planning.xml:18(para) +msgid "Public Network (Publicly routable IP range): This network is utilized for providing Public IP accessibility to the API endpoints within the cloud infrastructure." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-network-planning.xml:20(para) +msgid "Minimum size: 8 IPs (CIDR /29)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-network-planning.xml:21(para) +msgid "Storage Network (RFC1918 IP Range, not publicly routable): This network is utilized for all inter-server communications within the Object Storage infrastructure." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/object-storage-network-planning.xml:24(para) +msgid "Recommended size: 255 IPs (CIDR /24)" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-defining-services.xml:14(para) +msgid "There are two alternative ways of defining services with keystone: While using a template file is simpler, it is not recommended except for development environments such as DevStack. The template file does not enable Create, Read, Update, or Delete (CRUD) operations on the service catalog through keystone commands, but you can use the service-list command when using the template catalog. When keystone uses a template file backend, then changes made to the endpoints are kept in memory and don't persist if you restart the service or reboot the machine. Use the SQL backend when deploying a system for production." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-defining-services.xml:33(para) +msgid "A database backend can provide better reliability, availability, and data redundancy. This section describes how to populate the Keystone service catalog using the database backend. Your /etc/keystone/keystone.conf file should contain the following lines if it is properly configured to use the database backend." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-defining-services.xml:80(literal) +msgid "--service_id" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/identity-defining-services.xml:104(para) +msgid "Keystone allows some URLs to contain special variables, which are automatically substituted with the correct value at runtime. Some examples in this document employ the tenant_id variable, which we use when specifying the Volume and Compute service endpoints. Variables can be specified using either %(varname)s or $(varname)s notation. In this document, we always use the %(varname)s notation (e.g., %(tenant_id)s) since $ is interpeted as a special character by Unix shells." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configure-creds.xml:6(title) +msgid "Defining Compute and Image Service Credentials" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configure-creds.xml:7(para) +msgid "The commands in this section can be run on any machine that can access the cloud controller node over the network. You can run commands directly on the cloud controller, if you like, but it isn't required." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configure-creds.xml:10(para) +msgid "Create an openrc file that can contain these variables that are used by the (Compute) and (Image) command-line interface clients. These commands can be run by any user, and the openrc file can be stored anywhere. In this document, we store the openrc file in the ~/creds directory:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configure-creds.xml:20(para) +msgid "In this example, we are going to create an openrc file with credentials associated with a user who is not an administrator. Because the user is not an administrator, the credential file will use the URL associated with the keystone service API, which runs on port 5000. If we wanted to use the command-line tool to perform administrative commands, we would use the URL associated with the keystone admin API, which runs on port 35357." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configure-creds.xml:28(para) +msgid "In the openrc file you create, paste these values:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configure-creds.xml:30(para) +msgid "Next, ensure these are used in your environment. If you see 401 Not Authorized errors on commands using tokens, ensure that you have properly sourced your credentials and that all the pipelines are accurate in the configuration files." +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configure-creds.xml:39(para) +msgid "Verify your credentials are working by using the client to list the available images:" +msgstr "" + +#: ./doc/src/docbkx/openstack-install/configure-creds.xml:53(para) +msgid "Note that the ID values on your installation will be different." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/src/docbkx/openstack-install/configure-creds.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/src/docbkx/openstack-network-connectivity-admin/locale/openstack-network-connectivity-admin.pot b/doc/src/docbkx/openstack-network-connectivity-admin/locale/openstack-network-connectivity-admin.pot new file mode 100644 index 0000000000..7bdf3d0c4c --- /dev/null +++ b/doc/src/docbkx/openstack-network-connectivity-admin/locale/openstack-network-connectivity-admin.pot @@ -0,0 +1,4336 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2013-03-12 15:09+0800\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/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:17(None) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:273(None) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:276(None) +msgid "@@image: 'figures/Quantum-PhysNet-Diagram.png'; md5=f94377ebc99eb0f16d417f64730c5d46" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:4(title) +msgid "Provider Router with Private Networks" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:5(para) +msgid "This section describes how to install the OpenStack Networking service and its components for the \"Use Case: Provider Router with Private Networks\"." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:8(para) +msgid "We will follow the Basic Install document except for the Quantum, Open-vSwitch and Virtual Networking sections on each of the nodes." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:12(para) +msgid "The Basic Install document uses gre tunnels. This document will describe how to use vlans for separation instead." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:20(para) +msgid "There will be three nodes in the setup.
Nodes for Demo
NodeDescription
Controller NodeRuns the OpenStack Networking service, OpenStack Identity and all of the OpenStack Compute services that are required to deploy a VM. The service must have at least two network interfaces The first should be connected to the \"Management Network\". This will be used to communicate with the compute and network nodes. The second interface will be connected to the API/public network
Compute NodeRuns OpenStack Compute and the OpenStack Networking L2 agent. This node will not have access the public network. The node must have at least two network interfaces. The first is used to communicate with the controller node, via the management network. The VM will be able to receive its IP address from the DHCP agent on this network.
Network NodeRuns OpenStack Networking L2 agent, the DHCP agent and the L3 agent. This node will have access to the public network. The DHCP agent will allocate IP addresses to the VMs on the network. The L3 agent will perform NAT and enable the VMs to access the public network. The node must have at least three network interfaces. The first is used to communicate with the controller node, this is via the management network. The second interface will be used for the VM traffic, this is on the data network. The third interface will be used to connect to the external gateway on the network.
" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:60(title) +msgid "Installations" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:62(title) +msgid "Controller" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:68(para) +msgid "Install the packages :" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:72(para) +msgid "Configure Quantum services :" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:75(para) +msgid "Edit /etc/quantum/quantum.conf file and modify :" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:84(para) +msgid "Edit /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini file and modify :" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:94(para) +msgid "Edit /etc/quantum/api-paste.ini file and modify :" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:103(para) +msgid "Start the services :" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:108(title) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:62(td) +msgid "Network Node" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:115(para) +msgid "Install the packages:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:120(para) +msgid "Start Open vSwitch:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:124(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:200(para) +msgid "Add the integration bridge to the Open vSwitch:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:128(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:207(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:204(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:243(para) +msgid "Update the OpenStack Networking configuration file, /etc/quantum/quantum.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:135(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:153(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:214(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:163(para) +msgid "Update the plugin configuration file, /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:146(para) +msgid "Create the network bridge br-eth1 (All VM communication between the nodes will be done via eth1):" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:153(para) +msgid "Create the external network bridge to the Open vSwitch:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:158(para) +msgid "Edit , /etc/quantum/l3_agent.ini file and modify:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:169(para) +msgid "Edit , /etc/quantum/api-paste.ini file and modify:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:178(para) +msgid "Edit , /etc/quantum/dhcp_agent.ini file and modify:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:183(para) +msgid "Restart networking services" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:191(title) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:48(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:111(emphasis) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:122(emphasis) +msgid "Compute Node" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:195(para) +msgid "Install the packages." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:199(para) +msgid "Start open vSwitch Service" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:203(para) +msgid "Configure Virtual Bridging" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:213(para) +msgid "Update /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:223(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:259(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:294(para) +msgid "Start the DHCP agent" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:233(title) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:267(title) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:343(title) +msgid "Logical Network Configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:234(para) +msgid "All of the commands below can be done on the Network node." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:235(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:269(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:345(para) +msgid "Note please ensure that the following environment variables are set. These are used by the various clients to access OpenStack Identity." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:240(para) +msgid "Create novarc file :" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:252(para) +msgid "Export the variables :" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:261(emphasis) +msgid "Internal Networking Configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:263(para) +msgid "Get the tenant ID (Used as $TENANT_ID later)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:276(para) +msgid "Create a internal network named net1 on the demo tenant ($TENANT_ID will be e40fa60181524f9f9ee7aa1038748f08):" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:298(para) +msgid "Create a subnet on the network net1 (ID field below is used as $SUBNET_ID later):" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:321(emphasis) +msgid "External Networking Configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:323(para) +msgid "Create a router named router1 (ID is used as $ROUTER_ID later):" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:338(para) +msgid "Add an interface to router1 and attach the net1 subnet:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:345(para) +msgid "Create the external network named ext_net. Environment variables will attach this to the admin tenant (Used as $EXTERNAL_NETWORK_ID). Note this is a different $TENANT_ID than used previously:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:369(para) +msgid "Create the subnet for floating IPs. Note the DHCP service is disabled for this subnet:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:392(para) +msgid "Set the router gateway towards the external network:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:399(emphasis) +msgid "Floating IP Allocation" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:401(para) +msgid "After a VM is deployed a floating IP address can be associated to the VM. A VM that is created will be allocated an OpenStack Networking port ($PORT_ID). The port ID for the VM can be retrieved as follows (VIA the Controller or Compute Node) :" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:423(para) +msgid "Allocate a floating IP (Used as $FLOATING_ID):" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:439(para) +msgid "Associate a floating IP to a VM (in the case of the example it is 9aa47099-b87b-488c-8c1d-32f993626a30):" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:445(para) +msgid "Show the floating IP:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:459(para) +msgid "Test the floating IP:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:6(title) +msgid "Preface" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:7(para) +msgid "OpenStack Networking was created to provide a rich and tenant-facing API for defining network connectivity and addressing in the cloud. The project, code-named \"quantum,\" gives operators the ability to leverage different networking technologies to power their cloud networking.  " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:13(title) +msgid "Intended Audience" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:14(para) +msgid "This guide assists OpenStack administrators in leveraging different networking technologies to power their cloud networking. This document covers how to install, configure, and run OpenStack Networking." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:18(para) +msgid "The user should also have access to a plugin providing the implementation of the OpenStack Networking service. Several plugins are included in the OpenStack Networking distribution:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:24(para) +msgid "Openvswitch. Implements OpenStack Networking with Open vSwitch for the KVM and XenServer compute platforms." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:30(para) +msgid "Cisco. Implements OpenStack Networking for deployments by using Cisco UCS blades and Nexus switches for KVM compute platforms." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:36(para) +msgid "Linux Bridge Implements OpenStack Networking with the Linux Bridge for the KVM compute platforms." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:41(para) +msgid "Nicira NVP. Implements OpenStack Networking by using the Nicira Network Virtualization Platform (NVP) for KVM and XenServer compute platforms." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:47(para) +msgid "Ryu. Implements OpenStack Networking by using the Ryu OpenFlow Controller for KVM compute platforms." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:52(para) +msgid "NEC OpenFlow. Implements OpenStack Networking by using Trema Sliceable Switch OpenFlow Controller or NEC ProgrammableFlow Controller for KVM compute platforms." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:59(para) +msgid "Big Switch, Floodlight REST Proxy . Implements the OpenStack Networking plugin API and realizes the network abstractions by leveraging the Big Network Controller (BNC) or Floodlight OpenFlow Controller for KVM hypervisor based compute platforms." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:67(para) +msgid "Plugins can also be distributed separately from OpenStack Networking." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:69(para) +msgid "You should also be familiar with running the OpenStack Compute service as described in the operator's documentation." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:74(title) +msgid "Document Change History" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:75(para) +msgid "The most recent changes are described in the table below:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:80(title) +msgid "Resources" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:81(para) +msgid "For more information on OpenStack Networking and the other network-related projects, see the project page on the OpenStack wiki (wiki.openstack.org/Quantum)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:86(para) +msgid "For information about programming against the OpenStack Networking API, see the OpenStack Networking API Guide (v2.0)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:91(para) +msgid "We welcome feedback, comments, and bug reports at bugs.launchpad.net/Quantum." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:8(title) +msgid "OpenStack Networking Installation" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:9(para) +msgid "This chapter describes how to install the OpenStack Networking service and get it up and running." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:11(para) +msgid "If you are building a host from scratch to use for OpenStack Networking, we strongly recommend using Ubuntu 12.04/12.10 or Fedora 17/18 as these platforms have OpenStack Networking packages and receive significant testing." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:15(para) +msgid "OpenStack Networking requires at least dnsmasq 2.59, to support all the options it requires." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:18(title) +msgid "Install Packages (Ubuntu)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:20(para) +msgid "We are using Ubuntu cloud archive you can read more about it Explanation of each possible sources.list entry can be found here: http://bit.ly/Q8OJ9M " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:26(para) +msgid "Point to Folsom PPAs:                                                                        " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:33(para) +msgid "Please use \"sudo\" in order to install and configure packages with superuser privileges." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:37(title) +msgid "Install quantum-server" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:38(para) +msgid "Install quantum-server and CLI for accessing the API:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:41(para) +msgid "You will also want to install the plugin you choose to use, for example:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:44(para) +msgid "Most plugins require a database to be installed and configured in a plugin configuration file.  For example:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:48(para) +msgid "A database that you are already using for other OpenStack services will work fine for this.  Simply create a ‘quantum’ database:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:52(para) +msgid "And then configure the plugin’s configuration file to use this database.  Find the plugin configuration file in /etc/quantum/plugins (For example, /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini) and set:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:60(title) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:261(title) +msgid "RPC Setup" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:61(para) +msgid "OpenStack Networking uses RPC to allow DHCP agents and any plugin agents to communicate with the main quantum-server process.  Commonly, this can use the same RPC mechanism used by other OpenStack components like Nova. " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:66(para) +msgid "To use RabbitMQ as the message bus for RPC, make sure that rabbit is installed on a host reachable via the management network (if this is already the case because of deploying another service like Nova, this existing RabbitMQ setup is sufficient): " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:74(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:275(para) +msgid "Then update /etc/quantum/quantum.conf with these values:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:81(para) +msgid "This /etc/quantum/quantum.conf file should be copied to and used on all hosts running quantum-server, quantum-dhcp-agent, quantum-openvswitch-agent, or quantum-linuxbridge-agent (see below)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:89(title) +msgid "Configuring Open vSwitch Plugin" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:90(para) +msgid "Using the Open vSwitch (OVS) plugin in a deployment with multiple hosts requires the using of either tunneling or vlans in order to isolate traffic from multiple networks.  Tunneling is easier to deploy, as it does not require configuring VLANs on network switches, so that is what we describe here. More advanced deployment options are described in the " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:99(para) +msgid "Edit /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini to specify the following values:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:107(para) +msgid "After performing that change on the node running quantum-server, restart quantum-server to pick up the new settings." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:113(title) +msgid "Configuring Nicira NVP Plugin" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:114(para) +msgid "To configure OpenStack Networking to use the NVP plugin first edit /etc/quantum/quantum.conf and set:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:119(para) +msgid "Edit /etc/quantum/plugins/nicira/nvp.ini in order to configure the plugin. The quantum database created previously will be used by setting:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:125(para) +msgid "In order to tell OpenStack Networking about a controller cluster, create a [CLUSTER:<name>] section underneath the [NVP] section. Under this new cluster specify the Transport Zone by setting:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:131(para) +msgid "Specify the controllers in this cluster by setting:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:134(para) +msgid "one for each controller." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:135(para) +msgid "Lastly, restart quantum-server to pick up the new settings." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:141(title) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:311(title) +msgid "Install quantum-plugin-*-agent" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:142(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:312(para) +msgid "Some plugins utilize an agent that runs on each node that handles data packets. This includes any node running nova-compute, as well as nodes running dedicated OpenStack Networking agents like quantum-dhcp-agent and quantum-l3-agent (see below). If your plugin uses an agent, this section describes how to run the agent for this plugin, as well as the basic configuration options." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:151(title) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:321(title) +msgid "Open vSwitch Agent" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:152(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:322(para) +msgid "Install the OVS agent:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:154(para) +msgid "The ovs_quantum_plugin.ini created in the above step must be replicated on all nodes quantum-plugin-openvswitch-agent. When using tunneling, each node running quantum-plugin-openvswitch agent should have an IP address configured on the Data Network, and that IP address should be specified using the local_ip value in the ovs_quantum_plugin.ini file." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:162(para) +msgid "Then restart the agent" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:164(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:326(para) +msgid "All hosts running quantum-plugin-openvswitch-agent also requires that an OVS bridge named \"br-int\" exists. To create it, run:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:172(title) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:337(title) +msgid "Install quantum-dhcp-agent" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:173(para) +msgid "The host running quantum-server requires a network interface with an IP address on the “management network” and another interface on the “data network”." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:177(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:183(para) +msgid "Install the agent specific to the plugin (see plugin specific agent section above)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:181(title) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:348(title) +msgid "Install quantum-l3-agent" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:185(para) +msgid "Create a bridge \"br-ex\" that will be used to uplink this node running quantum-l3-agent to the external network, then attach the NIC attached to the external network to this bridge." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:190(para) +msgid "OpenStack does not manage this routing for you, so you need to make sure that your host running the metadata service always has a route to reach each private network's subnet via the external network IP of that subnet's OpenStack Networking router. To do this, you can run OpenStack Networking without namespaces, and run the quantum-l3-agent on the same host as nova-api. Alternatively, you can identify an IP prefix that includes all private network subnet's (e.g., 10.0.0.0/8) and then make sure that your metadata server has a route for that prefix with the OpenStack Networking router's external IP address as the next hop. For more validation information, refer to Advanced configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:206(para) +msgid "For example, with Open vSwitch and NIC eth1 connect to the external network, run:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:210(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:359(para) +msgid "The node running quantum-l3-agent should not have an IP address manually configured on the NIC connected to the external network. 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/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:218(para) +msgid "The quantum-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, quantum-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 \"ip addr list\" or \"ifconfig\" on the node. Similarly, you will not be able to directly ping fixed IPs. 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>. The following commands are examples of running commands in the namespace of a router with UUID 47af3868-0fa8-4447-85f6-1304de32153b:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:239(title) +msgid "Install OpenStack Networking CLI Client" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:240(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:376(para) +msgid "Install the OpenStack Networking CLI client:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:244(title) +msgid "Init, Config, and Log File Locations" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:245(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:381(para) +msgid "Services can be started and stopped using the 'service' command. For example:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:251(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:387(para) +msgid "Log files are found in /var/log/quantum." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:252(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:388(para) +msgid "Configuration files are in /etc/quantum." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:257(title) +msgid "Installing Packages (Fedora)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:258(para) +msgid "The OpenStack packages for Fedora can be retrieved from: https://apps.fedoraproject.org/packages/s/openstack." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:262(para) +msgid "OpenStack Networking uses RPC to allow DHCP agents and any plugin agents to communicate with the main quantum-server process.  Commonly, this can use the same RPC mechanism used by other OpenStack components like Nova." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:267(para) +msgid "To use QPID AMQP as the message bus for RPC, make sure that QPID is installed on a host reachable via the management network (if this is already the case because of deploying another service like Nova, this existing QPID setup is sufficient): " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:280(para) +msgid "The Fedora packaging has a number of utility scripts that configure all of the necessary configuration files. The scripts can also be used to understand what needs to be configured for the specific OpenStack Networking services. The scripts will be described below. Please note that the scripts make use of the package openstack-utils. Please install:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:294(title) +msgid "Install quantum-server and plugin" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:295(para) +msgid "Install quantum-server and plugin. Note the client is installed as a dependency for the OpenStack Networking service." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:301(para) +msgid "Most plugins require a database to be installed and configured in a plugin configuration file.  The Fedora packaging for OpenStack Networking a server setup utility scripts that will take care of this. For example:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:306(para) +msgid "Enable and start the service:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:324(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:341(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:368(para) +msgid "Run the agent setup script:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:331(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:343(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:370(para) +msgid "Enable and start the agent:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:338(para) +msgid "The DHCP agent is part of the openstack-quantum package." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:349(para) +msgid "The L3 agent is part of the openstack-quantum package." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:351(para) +msgid "Create a bridge \"br-ex\" that will be used to uplink this node running quantum-l3-agent to the external network, then attach the NIC attached to the external network to this bridge. For example, with Open vSwitch and NIC eth1 connect to the external network, run:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:375(title) +msgid "Install OpenStack Networking CLI client" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:380(title) +msgid "Init, Config, and Log File Locations" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo.xml:4(title) +msgid "Demos Setup" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo.xml:5(para) +msgid "This section describes how to configure the OpenStack Networking service and its components for some typical use cases." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:6(title) +msgid "Authentication and Authorization" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:26(para) +msgid "Operation-based: policies specify access criteria for specific operations, possibly with fine-grained control over specific attributes;" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:33(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/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:7(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/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:43(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/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:63(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/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:78(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/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:83(para) +msgid "The OpenStack Networking policy engine currently defines the following kinds of terminal rules:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:87(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/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:93(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/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:100(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/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:85(para) +msgid " The following is an extract from the default policy.json file:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:108(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:149(code) +msgid "{" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:109(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:150(code) +msgid "\"admin_or_owner\": [[\"role:admin\"], [\"tenant_id:%(tenant_id)s\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:110(emphasis) +msgid "[1]" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:111(code) +msgid "\"admin_or_network_owner\": [[\"role:admin\"], [\"tenant_id:%(network_tenant_id)s\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:113(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:151(code) +msgid "\"admin_only\": [[\"role:admin\"]], \"regular_user\": []," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:114(code) +msgid "\"shared\": [[\"field:networks:shared=True\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:115(code) +msgid "\"default\": [[\"rule:admin_or_owner\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:115(emphasis) +msgid "[2]" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:116(code) +msgid "\"create_subnet\": [[\"rule:admin_or_network_owner\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:117(code) +msgid "\"get_subnet\": [[\"rule:admin_or_owner\"], [\"rule:shared\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:118(code) +msgid "\"update_subnet\": [[\"rule:admin_or_network_owner\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:119(code) +msgid "\"delete_subnet\": [[\"rule:admin_or_network_owner\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:120(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:157(code) +msgid "\"create_network\": []," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:121(code) +msgid "\"get_network\": [[\"rule:admin_or_owner\"], [\"rule:shared\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:121(emphasis) +msgid "[3]" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:122(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:159(code) +msgid "\"create_network:shared\": [[\"rule:admin_only\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:122(emphasis) +msgid "[4]" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:124(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:160(code) +msgid "\"update_network\": [[\"rule:admin_or_owner\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:125(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:161(code) +msgid "\"delete_network\": [[\"rule:admin_or_owner\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:126(code) +msgid "\"create_port\": []," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:127(code) +msgid "\"create_port:mac_address\": [[\"rule:admin_or_network_owner\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:127(emphasis) +msgid "[5]" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:128(code) +msgid "\"create_port:fixed_ips\": [[\"rule:admin_or_network_owner\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:129(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:163(code) +msgid "\"get_port\": [[\"rule:admin_or_owner\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:130(code) +msgid "\"update_port\": [[\"rule:admin_or_owner\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:131(code) +msgid "\"delete_port\": [[\"rule:admin_or_owner\"]]" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:132(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:166(code) +msgid "}" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:133(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/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:135(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/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:137(para) +msgid "[3] This policy will evaluate successfully if either admin_or_owner, or shared evalutes successfully." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:140(para) +msgid "[4] This policy will restrict the ability of manipulating the shared attribute for a network to administrators only." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:142(para) +msgid "[5] This policy will restrict the ability of manipilating the mac_address attribute for a port only to administrators and the owner of the network where the port is attached." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:145(para) +msgid "In some cases, some operations should be restricted to administrators only; therefore, as a further example, let us consider how this sample policy file should be modified in a scenario where tenants are allowed only to define networks and see their resources, and all the other operations can be performed only in an administrative context:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:152(code) +msgid "\"default\": [[\"rule:admin_only\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:153(code) +msgid "\"create_subnet\": [[\"rule:admin_only\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:154(code) +msgid "\"get_subnet\": [[\"rule:admin_or_owner\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:155(code) +msgid "\"update_subnet\": [[\"rule:admin_only\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:156(code) +msgid "\"delete_subnet\": [[\"rule:admin_only\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:158(code) +msgid "\"get_network\": [[\"rule:admin_or_owner\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:162(code) +msgid "\"create_port\": [[\"rule:admin_only\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:164(code) +msgid "\"update_port\": [[\"rule:admin_only\"]]," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:165(code) +msgid "\"delete_port\": [[\"rule:admin_only\"]]" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:6(title) +msgid "Plugin pagination and sorting support" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:8(caption) +msgid "The plugins are supporting native pagination and sorting" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:12(th) +msgid "Plugin" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:13(th) +msgid "Support Native Pagination" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:14(th) +msgid "Support Native Sorting" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:20(td) +msgid "Open vSwitch" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:21(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:22(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:26(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:27(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:87(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:208(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:311(td) +msgid "True" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:25(td) +msgid "LinuxBridge" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:6(title) +msgid "Using OpenStack Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:8(para) +msgid "There are two main approaches to using OpenStack Networking.  The first is to expose the OpenStack Networking API to cloud tenants, allowing them to build rich network topologies.  The second is to have the cloud administrator, or another tool run the the cloud admin, create network connectivity on behalf of tenants.  In this document, we commonly describe operations as being performed by a tenant, but they might also be performed by the cloud admin on behalf of the tenant. " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:17(title) +msgid "Core OpenStack Networking API Features" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:18(para) +msgid "Once OpenStack Networking is installed and running, both tenants and admins primarily interact with the service via create-read-update-delete (CRUD) API operations performed either directly against the API, or more commonly via the 'quantum' CLI tool.  Like other OpenStack CLI tools, the 'quantum' tool is just a basic wrapper around the OpenStack Networking API, so any operation that can be performed via the CLI has an equivalent API call that can be performed programmatically. " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:27(para) +msgid "The CLI supports many options for filtering results, limiting fields show, etc.  For details, refer to the OpenStack Networking CLI documentation.  " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:30(title) +msgid "API Abstractions" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:31(para) +msgid "The OpenStack 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, providing capabilities similar to nova-network." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:35(para) +msgid "In the OpenStack Networking API, an isolated L2 network segment (similar to a VLAN) is called a 'Network' and forms the basis for describing the L2 network topology available in a given OpenStack Networking deployment." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:38(para) +msgid "The OpenStack Networking API uses the notion of a 'Subnet', which associates a block of IP addresses and other network configuration (e.g., default gateway, dns-servers) with an OpenStack Networking network. Each subnet represents an IPv4 or IPv6 address block and each OpenStack Networking network can have multiple subnets, if desired. " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:44(para) +msgid "A 'Port' represents an attachment port to a L2 OpenStack Networking network. When a port is created on the network, by default it will be 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, the allocated addresses return to the pool of available IPs on the subnet(s). Users of the OpenStack Networking API can either choose a specific IP address from the block, or let OpenStack Networking choose the first available IP address." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:51(para) +msgid "The table below summarizes the attributes available for each of these abstractions. For more operations about API abstraction and operations, please refer to the OpenStack Networking v2.0 API Developer Guide." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:57(caption) +msgid "Network" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:64(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:146(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:288(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:348(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:530(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:576(th) +msgid "Attribute name" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:65(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:132(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:231(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:147(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:289(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:349(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:531(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:577(th) +msgid "Type" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:66(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:133(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:232(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:148(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:290(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:350(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:532(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:578(th) +msgid "Default Value" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:67(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:134(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:233(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:31(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:149(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:291(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:351(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:533(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:579(th) +msgid "Description" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:72(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:139(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:238(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:296(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:356(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:538(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:584(td) +msgid "id" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:73(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:115(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:140(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:146(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:214(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:239(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:245(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:303(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:297(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:325(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:357(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:370(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:378(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:387(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:404(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:539(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:560(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:585(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:641(td) +msgid "uuid-str" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:74(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:141(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:240(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:276(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:298(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:358(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:540(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:586(td) +msgid "generated" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:75(td) +msgid "UUID for the network." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:78(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:151(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:251(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:302(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:544(td) +msgid "name" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:79(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:94(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:152(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:252(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:155(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:171(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:303(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:318(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:545(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:553(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:597(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:604(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:622(td) +msgid "String" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:80(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:153(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:253(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:291(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:298(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:304(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:546(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:554(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:605(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:611(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:617(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:623(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:629(td) +msgid "None" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:81(td) +msgid "Human-readable name for the network. Might not be unique." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:85(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:258(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:309(td) +msgid "admin_state_up" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:86(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:108(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:207(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:310(td) +msgid "Bool" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:88(td) +msgid "The administrative state of network. If false (down), the network does not forward packets." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:93(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:266(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:317(td) +msgid "status" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:95(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:116(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:147(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:166(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:215(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:246(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:268(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:304(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:156(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:184(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:319(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:326(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:371(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:379(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:405(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:561(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:598(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:642(td) +msgid "N/A" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:96(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:269(para) +msgid "Indicates whether network is currently operational." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:100(td) +msgid "subnets" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:101(td) +msgid "list(uuid-str)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:102(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:182(td) +msgid "Empty list" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:103(td) +msgid "Subnets associated with this network." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:107(td) +msgid "shared" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:109(td) +msgid "False" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:110(td) +msgid "Specifies whether the network resource can be accessed by any tenant or not." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:114(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:213(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:302(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:324(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:403(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:559(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:640(td) +msgid "tenant_id" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:117(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:216(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:305(td) +msgid "Owner of network. Only admin users can specify a tenant_id other than its own." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:124(caption) +msgid "Subnet" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:131(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:230(th) +msgid "Attribute" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:142(td) +msgid "UUID representing the subnet" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:145(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:244(td) +msgid "network_id" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:148(td) +msgid "network this subnet is associated with." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:154(td) +msgid "Human-readable name for the subnet. Might not be unique." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:158(td) +msgid "ip_version" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:159(td) +msgid "int" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:160(td) +msgid "4" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:161(td) +msgid "IP version" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:164(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:174(emphasis) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:190(emphasis) +msgid "cidr" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:165(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:172(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:267(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:275(td) +msgid "string" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:167(td) +msgid "cidr representing IP range for this subnet, based on IP version" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:171(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:191(emphasis) +msgid "gateway_ip" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:173(td) +msgid "first address in " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:176(td) +msgid "default gateway used by devices in this subnet" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:180(td) +msgid "dns_nameservers" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:181(td) +msgid "list(str)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:183(td) +msgid "DNS name servers used by hosts in this subnet." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:187(td) +msgid "allocation_pools" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:188(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:199(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:281(td) +msgid "list(dict)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:189(td) +msgid "Every address in , excluding if configured" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:193(td) +msgid "Sub-ranges of cidr available for dynamic allocation to ports [ { \"start\": \"10.0.0.2\", \"end\": \"10.0.0.254\"} ]" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:198(td) +msgid "host_routes" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:200(td) +msgid "Empty List" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:201(td) +msgid "Routes that should be used by devices with IPs from this subnet (not including local subnet route)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:206(td) +msgid "enable_dhcp" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:209(td) +msgid "Specifies whether DHCP is enabled for this subnet or not." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:223(caption) +msgid "Port" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:241(td) +msgid "UUID for the port." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:247(td) +msgid "Network that this port is associated with." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:254(td) +msgid "Human-readable name for the port. Might not be unique." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:259(td) +msgid "bool" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:260(td) +msgid "true" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:261(td) +msgid "Administrative state of port. If false (down), port does not forward packets." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:274(td) +msgid "mac_address" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:277(td) +msgid "Mac address to use on this port." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:280(td) +msgid "fixed_ips" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:282(td) +msgid "automatically allocated from pool" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:283(td) +msgid "Specifies IP addresses for the port thus associating the port itself with the subnets where the IP addresses are picked from" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:289(td) +msgid "device_id" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:290(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:297(td) +msgid "str" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:292(td) +msgid "identifies the device (e.g., virtual server) using this port." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:296(td) +msgid "device_owner" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:299(td) +msgid "Identifies the entity (e.g.: dhcp agent) using this port." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:313(title) +msgid "OpenStack Networking CLI Guide" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:314(para) +msgid "Before going further, we STRONGLY suggest that you quickly read the few pages in the OpenStack CLI Guide that are specific to OpenStack Networking. OpenStack Networking's CLI has some advanced capabilities that are described only in that guide." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:319(title) +msgid "Basic Operations" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:320(para) +msgid "Create a network" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:322(para) +msgid "Create a subnet associated with net1" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:324(para) +msgid "List ports on a tenant" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:326(para) +msgid "device_owner field describes who owns the port. A port whose device_owner begins with \"network:\" is created by OpenStack Networking and a port whose device_owner begins with \"compute:\" is created by OpenStack Compute (compute service)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:330(para) +msgid " shows a detail of a specified port." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:334(title) +msgid "Admin API configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:335(para) +msgid "These same calls can be performed by the cloud admin on half of the tenants by specifying a tenant_id in the request, for example:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:339(para) +msgid "This tenant_id should be the tenant ID from OpenStack Identity. To view all OpenStack Identity tenant IDs, run the following command as an OpenStack Identity (keystone) admin user:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:345(title) +msgid "Advanced API Operations Examples" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:347(title) +msgid "Network, Subnet & Port Creation" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:350(para) +msgid "Create a \"shared\" network (i.e., a network that can be used by all tenants)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:354(para) +msgid "Create a subnet that has a specific gateway IP address." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:358(para) +msgid "Create a subnet that has no gateway IP address." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:362(para) +msgid "Create a subnet for which DHCP is disabled." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:366(para) +msgid "Create subnet with a specific set of host routes:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:370(para) +msgid "Create subnet with a specific set of dns nameserver:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:376(title) +msgid "Searches" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:379(para) +msgid "Find all Ports/IPs allocated on a network." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:387(title) +msgid "Using OpenStack Compute with OpenStack Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:389(title) +msgid "Basic Workflow" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:390(para) +msgid "Check available networks:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:392(para) +msgid "Boot the VM with a single NIC on the selected network (net1):" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:394(para) +msgid "Congrats, you have booted a VM on an OpenStack Networking network. You may need to configure security group rules to allow accesses to the VM." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:398(para) +msgid "There is now an OpenStack Networking port on 'net1' that corresponds to the VM Nic.  You can view it with the following command, which searches for all ports with a \"device_id\" corresponding to the OpenStack Compute instance UUID:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:404(para) +msgid "To view only a few fields of the port, you can limit output using -c.  For example to see only the mac_address of the port, use:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:408(para) +msgid "You could temporarily disable the port from sending traffic by updating it to have admin_state_up=False:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:412(para) +msgid "When we delete the OpenStack Compute VM, the underlying OpenStack Networking port is automatically deleted:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:417(title) +msgid "Advanced VM creation" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:421(para) +msgid "Booting a VM with multiple NICs" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:426(para) +msgid "Booting a VM with a specific IP address. To do this, we need to create an OpenStack Networking port with a specific IP address first, and then boot a VM specifying a port-id rather than a net-id." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:431(para) +msgid " parameter of option in command is not supported with OpenStack Networking at the moment." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:435(para) +msgid "booting a VM with no --nic option specified. In this case the launched VM connects to all networks that are accessible to the tenant who submits the request." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:444(title) +msgid "Security Groups (Enabling Ping and SSH on VMs)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:445(para) +msgid "In Folsom release, the security groups feature is provided by OpenStack Compute not by OpenStack Networking. You can configure security group rules by using or command to enable accesses to your VMs. The example below allows or to your VMs." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:451(para) +msgid "For more detail about OpenStack Compute security groups, please see \"Networking with nova-network\" in OpenStack Compute Administration Manual." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:21(title) +msgid "OpenStack Networking Administration Guide" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:30(year) +msgid "2011" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:31(year) +msgid "2012" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:32(year) +msgid "2013" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:33(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:35(releaseinfo) +msgid "trunk" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:36(productname) +msgid "OpenStack Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:37(pubdate) ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:51(date) +msgid "2013-02-04" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:40(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:44(para) +msgid "This document is intended for administrators interested in running the OpenStack Networking Virtual Network Service." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:55(para) +msgid "Use OpenStack naming conventions through out document." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:61(date) +msgid "2012-12-20" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:65(para) +msgid "Trunk designation of this document." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:71(date) +msgid "2012-11-09" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:75(para) +msgid "Folsom release of this document." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:82(date) +msgid "2012-09-18" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:86(para) +msgid "First edition of this document." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:3(title) +msgid "High Availability" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:4(para) +msgid "Several aspects of an OpenStack Networking deployment benefit from high-availabilty to withstand individual node failures. In general, quantum-server and quantum-dhcp-agent can be run in an active-active fashion. The quantum-l3-agent service can be run only as active/passive, to avoid IP conflicts with respect to gateway IP addresses." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:11(title) +msgid "OpenStack Networking High Availability with Pacemaker" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:13(para) +msgid "You can run some OpenStack Networking services into a cluster (Active / Passive or Active / Active for OpenStack Networking Server only) with Pacemaker." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:18(para) +msgid "quantum-server: https://github.com/madkiss/openstack-resource-agents/blob/master/ocf/quantum-server" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:23(para) +msgid "quantum-dhcp-agent : https://github.com/madkiss/openstack-resource-agents/blob/master/ocf/quantum-agent-dhcp  " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:27(para) +msgid "quantum-l3-agent : https://github.com/madkiss/openstack-resource-agents/blob/master/ocf/quantum-agent-l3  " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:16(para) +msgid "Here you can download the latest Resources Agents :" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:31(para) +msgid "If you need more informations about \"How to build a cluster\", please refer to Pacemaker 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/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:18(None) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:21(None) +msgid "@@image: 'figures/demo_flat_install.png'; md5=27b45d5871859ff4951c92df7c8763d8" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:4(title) +msgid "Single Flat Network" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:5(para) +msgid "This section describes how to install the OpenStack Networking service and its components for the \"Use Case: Single Flat Network \"." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:9(para) +msgid "The diagram below shows the setup. For simplicity all of the 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/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:14(para) +msgid "Note the setup can be tweaked to make use of another supported plugin and its agent." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:24(para) +msgid "Here are some nodes in the setup." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:30(th) +msgid "Node" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:36(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:79(emphasis) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:91(emphasis) +msgid "Controller Node" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:43(emphasis) +msgid "Note" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:37(td) +msgid "Runs the OpenStack Networking service, OpenStack Identity and all of the OpenStack 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 hostname is 'controlnode', which every other node resolve to the controller node's IP. The nova-network service should not be running. This is replaced by OpenStack Networking." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:49(td) +msgid "Runs the OpenStack Networking L2 agent and the OpenStack Compute services that run VMs (nova-compute specifically, and optionally other nova-* services depending on configuration). The node must have at least two network interfaces. The first is used to communicate with the controller node via the management network. The second interface is used for the VM traffic on the Data network. The VM will be able to receive its IP address from the DHCP agent on this network." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:63(td) +msgid "Runs OpenStack Networking L2 agent and the DHCP agent. The DHCP agent will allocate IP addresses to the VMs on the network. The node must have at least two network interfaces. The first is used to communicate with the controller node via the management network. The second interface will be used for the VM traffic on the data network." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:72(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:281(caption) +msgid "Router" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:73(td) +msgid "Router has IP 30.0.0.1, which is the default gateway for all VMs. The router should have ability to access public networks." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:78(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:90(para) +msgid "The demo assumes the following:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:82(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:94(para) +msgid "Relevant OpenStack Compute services are installed, configured and running." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:86(para) +msgid "Glance is installed, configured and running. In addition to this there should be an image." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:90(para) +msgid "OpenStack Identity is installed, configured and running. An OpenStack Networking user quantum should be created on tenant servicetenant with password servicepassword." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:100(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:111(para) +msgid "RabbitMQ is running with default guest and its password" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:103(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:114(para) +msgid "MySQL server (user is root and password is root)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:98(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:109(para) +msgid "Additional services " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:114(para) +msgid "OpenStack Compute compute is installed and configured" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:118(title) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:129(title) +msgid "Installation" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:122(emphasis) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:133(emphasis) +msgid "Controller Node - OpenStack Networking Server" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:124(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:135(para) +msgid "Install the OpenStack Networking server." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:127(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:138(para) +msgid "Create database ovs_quantum. See the section on the Core Plugins for the exact details." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:135(para) +msgid "Update the OpenStack Networking configuration file, /etc/quantum/quantum.conf setting plugin choice and Identity Service user as necessary:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:164(para) +msgid "Start the OpenStack Networking service" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:169(emphasis) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:186(emphasis) +msgid "Compute Node - OpenStack Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:171(para) +msgid "Install the nova-compute service." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:174(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:191(para) +msgid "Update the OpenStack Compute configuration file, /etc/nova/nova.conf. Make sure the following is at the end of this file:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:190(para) +msgid "Restart the OpenStack Compute service" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:195(emphasis) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:212(emphasis) +msgid "Compute and Network Node - L2 Agent" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:197(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:214(para) +msgid "Install the L2 agent." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:224(para) +msgid "Create the network bridge br-eth0 (All VM communication between the nodes will be done via eth0):" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:233(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:259(para) +msgid "Start the OpenStack Networking L2 agent" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:238(emphasis) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:270(emphasis) +msgid "Network Node - DHCP Agent" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:240(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:272(para) +msgid "Install the DHCP agent." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:253(para) +msgid "Update the DHCP configuration file /etc/quantum/dhcp_agent.ini:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:268(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:344(para) +msgid "All of the commands below can be executed on the network node." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:281(para) +msgid "Get the tenant ID (Used as $TENANT_ID later):" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:297(para) +msgid "Get the User information:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:312(para) +msgid "Create a internal shared network on the demo tenant ($TENANT_ID will be b7445f221cda4f4a8ac7db6b218b1339):" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:335(para) +msgid "Create a subnet on the network:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:356(para) +msgid "Create a server for tenant A:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:367(para) +msgid "Ping the server of tenant A:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:375(para) +msgid "Ping the public network within the server of tenant A:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:386(para) +msgid "Note: The 192.168.1.1 is an IP on public network that the router is connecting." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:388(para) +msgid "Create servers for other tenants" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:389(para) +msgid "We can create servers for other tenants with similar commands. Since all these VMs share the same subnet, they will be able to access each other." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:6(title) +msgid "Advanced Operational Features" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:8(title) +msgid "Logging Settings" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:9(para) +msgid "OpenStack Networking components use Python logging module to do logging. Logging configuration can be provided in quantum.conf or as command line options. Command options will override ones in quantum.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:13(para) +msgid "Two ways to specify the logging configuration for OpenStack Networking components:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:17(para) +msgid "Provide logging settings in a logging configuration file." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:18(para) +msgid "Please see Python Logging HOWTO for logging configuration file." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:21(para) +msgid "Provide logging setting in quantum.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:48(title) +msgid "Notifications" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:50(title) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:431(caption) +msgid "Notification Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:51(para) +msgid "Notifications can be sent when OpenStack Networking resources such as network, subnet and port are created, updated or deleted. To support DHCP agent, rpc_notifier driver must be set. To set up the notification, edit notification options in quantum.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:87(title) +msgid "Setting Cases" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:89(title) +msgid "Logging and RPC" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:90(para) +msgid "The options below will make OpenStack Networking server send notifications via logging and RPC. The logging options are described in Logging Settings. RPC notifications will go to 'notifications.info' queue binded to a topic exchange defined by 'control_exchange' in quantum.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:127(title) +msgid "Multiple RPC Topics" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:128(para) +msgid "The options below will make OpenStack Networking server send notifications to multiple RPC topics. RPC notifications will go to 'notifications_one.info' and 'notifications_two.info' queues binded to a topic exchange defined by 'control_exchange' in quantum.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:166(title) +msgid "Quotas" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:167(para) +msgid "Quota is a function to limit number of resources. You can enforce default quota for all tenants. You will get error when you try to create more resources than the limit." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:171(para) +msgid "Per-tenant quota configuration is also supported by quota extension API. See Per-tenant quota configuration for details." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:177(title) +msgid "Basic quota configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:178(para) +msgid "In OpenStack Networking default quota mechanism, all tenants have a same quota value, i.e., a number of resources that a tenant can create. This is enabled by default." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:181(para) +msgid "The value of quota is defined in the OpenStack Networking configuration file (quantum.conf). If you want to disable quotas for a specific resource (e.g., network, subnet, port), remove a corresponding item from quota_items. Each of the quota values in the example below is the default value." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:200(para) +msgid "OpenStack Networking also supports quotas for L3 resources: router and floating IP. You can configure them by adding the following lines to QUOTAS section in quantum.conf. (Note that quota_items does not affect these quotas.)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:209(para) +msgid "OpenStack Networking also supports quotas for security group resources: number of security groups and the number of rules per security group. You can configure them by adding the following lines to QUOTAS section in quantum.conf. (Note that quota_items does not affect these quotas.)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:221(title) +msgid "Per-tenant quota configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:222(para) +msgid "OpenStack Networking also supports per-tenant quota limit by quota extension API. To enable per-tenant quota, you need to set quota_driver in quantum.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:225(para) +msgid "When per-tenant quota is enabled, the output of the following command contains quotas." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:254(para) +msgid "In Folsom release, per-tenant quota is supported by Open vSwitch plugin, Linux Bridge plugin, and Nicira NVP plugin and cannot be used with other plugins." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:258(para) +msgid "There are four CLI commands to manage per-tenant quota." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:265(para) +msgid "Only users with 'admin' role can change a quota value. Note that the default set of quotas are enforced for all tenants by default, so there is no quota-create command." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:270(para) +msgid "quota-list displays a list of tenants for which per-tenant quota is enabled. The tenants who have the default set of quota limits are not listed. This command is permitted to only 'admin' users." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:282(para) +msgid "quota-show reports the current set of quota limits for the specified tenant. Regular (non-admin) users can call this command (without --tenant_id parameter). If per-tenant quota limits are not defined for the tenant, the default set of quotas are displayed." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:298(para) +msgid "The below is an example called by a non-admin user." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:311(para) +msgid "You can update a quota of the given tenant by quota-update command." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:312(para) +msgid "Update the limit of network quota." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:323(para) +msgid "You can update quotas of multiple resources in one command." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:334(para) +msgid "To update the limits of L3 resource (router, floating IP), we need to specify new values of the quotas after '--'. The example below updates the limit of the number of floating IPs for the given tenant." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:349(para) +msgid "You can update the limits of multiple resources including L2 resources and L3 resource in one command." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:362(para) +msgid "To clear per-tenant quota limits, use quota-delete. After quota-delete, quota limits enforced to the tenant are reset to the default set of quotas." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:4(title) +msgid "Configuring other OpenStack Components" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:6(title) +msgid "OpenStack Identity Configuration for OpenStack Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:9(title) +msgid "To Configure OpenStack Compute for OpenStack Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:12(title) +msgid "To Create an OpenStack Networking Service Entry" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:14(para) +msgid "OpenStack Networking needs to be available in the  OpenStack Compute service catalog.  The steps for this depend on whether you are using the SQL catalog driver or the template catalog driver." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:19(para) +msgid "With the SQL driver, for a given region ($REGION), IP address of the OpenStack Networking server ($IP), and service ID ($ID) returned by the OpenStack Compute service catalog, run:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:25(para) +msgid "Make a note of the ID returned by the command and put it in the $ID location." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:28(para) +msgid "Here's an example with real values:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:40(para) +msgid "With the template driver, for a given region ($REGION) and IP address of the OpenStack Networking server ($IP), add the following content to your OpenStack Compute catalog template file (default_catalog.templates)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:49(para) +msgid "Here is an example with real values:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:57(title) +msgid "Create OpenStack Networking Service User" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:59(para) +msgid "For OpenStack Compute to speak to the OpenStack Networking API, and for some internal components of OpenStack Networking to communicate with the OpenStack Networking API, you need to provide them with admin user credentials that they can use when accessing the OpenStack Networking API.  The suggested approach is to create a special 'service' tenant, create a ‘quantum’ user within this tenant, and to assign this user an 'admin' role. Kindly check the ID for user, role and tenant." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:70(para) +msgid "For example:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:79(para) +msgid "See the OpenStack Installation Guides for more details about creating service entries and service users." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:83(title) +msgid "Running OpenStack Compute with OpenStack Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:85(para) +msgid "Unlike traditional OpenStack Compute deployments, when OpenStack Networking is in use, OpenStack Compute should not run a nova-network. Instead, OpenStack Compute delegates almost all of the network-related decisions to OpenStack Networking. This means many of the network-related CLI command and configuration options you are familiar with from using OpenStack Compute do not work with OpenStack Networking." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:93(para) +msgid "Therefore, it is very important that you refer to this guide when configuring networking, rather than relying on OpenStack Compute networking documentation or past experience with OpenStack Compute. If a Nova CLI command or configuration option related to networking is not mentioned in this guide, it is likely not supported for use with OpenStack Networking. In particular, using CLI tools like 'nova-manage' and 'nova' to manage networks or IP addressing, including both fixed and floating IPs, is not supported with OpenStack Networking." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:104(para) +msgid "It is strongly recommended that you uninstall nova-network and reboot any physical nodes that had been running nova-network before using them to run OpenStack Networking. Inadvertently running the nova-network process while using OpenStack Networking can cause problems, as can stale iptables rules pushed down by previously running nova-network." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:113(title) +msgid "Configuring OpenStack Compute to reach the OpenStack Networking API" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:115(para) +msgid "Each time a VM is provisioned or deprovisioned in OpenStack Compute, nova-* services communicate with OpenStack Networking via the standard API. To do so, it requires the following items in the nova.conf used by each nova-compute and nova-api instance: " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:122(para) +msgid "network_api_class: must be modified from default to nova.network.quantumv2.api.API indicate that OpenStack Networking should be used rather than the traditional nova-network networking model." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:129(para) +msgid "quantum_url: must include the hostname/IP and port of the Quantum server for this deployment." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:133(para) +msgid "quantum_auth_strategy: should be kept as default 'keystone' for all production deployments." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:137(para) +msgid "quantum_admin_tenant_name: must be modified to be the name of the service tenant created in the above section on OpenStack Compute configuration." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:143(para) +msgid "quantum_admin_username: must be modified to be the name of the user created in the above section on OpenStack Compute configuration." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:149(para) +msgid "quantum_admin_password: must be modified to be the password of the user created in the above section on OpenStack Compute configuration." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:155(para) +msgid "quantum_admin_auth_url: must be modified to point to the OpenStack Compute 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/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:164(title) +msgid "Configuring Vif-plugging in OpenStack Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:166(para) +msgid "When nova-compute creates a VM, it must \"plug\" each of the VM's vNICs into an OpenStack Networking controlled virtual switch, and inform the virtual switch about the OpenStack Networking port-id associated with each vNIC. This is done by specifying a field in the nova.conf of the nova-compute instance indicating what type of ''vif-plugging'' should be used. The exact field(s) you need to set depend on your plugin. For plugins not listed below, see the plugin's own documentation." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:177(title) +msgid "Vif-plugging with Open vSwitch Plugin" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:178(para) +msgid "The choice of vif-plugging for the Open vSwitch plugin depends on what version of libvirt you are using, as well as whether you are using OpenStack Compute security filtering (i.e., security groups, provider firewall, VM spoofing prevention)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:185(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:245(para) +msgid "When using libvirt (any version) with OpenStack Compute security filtering: libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:190(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:250(para) +msgid "When using libvirt (version < 0.9.11) without OpenStack Compute security filtering: libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtOpenVswitchDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:196(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:256(para) +msgid "When using libvirt (version >= 0.9.11) without OpenStack Compute security groups: libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtOpenVswitchVirtualPortDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:202(title) +msgid "Checking your libvirt version" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:203(para) +msgid "To check your libvirt version, use ." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:209(title) +msgid "Vif-plugging with Linux Bridge Plugin" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:212(para) +msgid "When using libvirt (any version): libvirt_vif_driver=nova.virt.libvirt.vif.QuantumLinuxBridgeVIFDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:218(title) +msgid "Vif-plugging with Nicira NVP Plugin" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:219(para) +msgid "The choice of vif-plugging for the NVP Plugin depends on what version of libvirt you are using (this assumes you are using NVP for security groups and VM spoof prevention)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:223(para) +msgid "When using libvirt (version < 0.9.11): libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtOpenVswitchDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:227(para) +msgid "When using libvirt (version >= 0.9.11): libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtOpenVswitchVirtualPortDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:231(para) +msgid "When using XenServer: xenapi_vif_driver=nova.virt.xenapi.vif.XenAPIOpenVswitchDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:237(title) +msgid "Vif-plugging with NEC OpenFlow Plugin" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:238(para) +msgid "The choice of vif-plugging for the NEC plugin depends on what version of libvirt you are using, as well as whether you are using OpenStack Compute security filtering (i.e., security groups, provider firewall, VM spoofing prevention)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:264(title) +msgid "Vif-plugging with Big Switch, Floodlight REST Proxy Plugin" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:267(para) +msgid "When using libvirt (any version) and Nova security filtering: libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:274(title) +msgid "Example nova.conf (for nova-compute and nova-api)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:275(para) +msgid "Example values for the above settings, assuming a cloud controller node running OpenStack Compute and OpenStack Networking with an IP address of 192.168.1.2 and vif-plugging using the LibvirtOpenVswitchDriver with virtio enabled." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:12(None) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:15(None) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:449(None) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:452(None) +msgid "@@image: 'figures/UseCase-MultiRouter.png'; md5=cdfb679dac788eaa8207635456d4e712" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:26(None) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:29(None) +msgid "@@image: 'figures/demo_routers_with_private_networks.png'; md5=985b8cacfd7161ce50ee13106b27f854" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:4(title) +msgid "Per-tenant Routers with Private Networks" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:5(para) +msgid "This section describes how to install the OpenStack Networking service and its components for the \"Use Case: Per-tenant Routers with Private Networks \"." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:19(para) +msgid "The diagram below shows the setup. All of the nodes should have one interface for management traffic. The example uses the Open vSwitch plugin. The agents are configured to use GRE for data transport. There is an external network where we will have floating IPs and router gateway ports. A physical router is connecting these floating IPs and router gateway ports to outside world." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:32(para) +msgid "Below are nodes in the setup: NodeDescriptionController NodeRuns the OpenStack Networking service, OpenStack Identity and all of the OpenStack 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 hostname is 'controlnode', which every other node resolve to the controller node's IP. Note The nova-network service should not be running. This is replaced by OpenStack Networking.Compute NodeRuns the OpenStack Networking L2 agent and the OpenStack Compute services that run VMs (nova-compute specifically, and optionally other nova-* services depending on configuration). The node must have at least two network interfaces. The first is used to communicate with the controller node via the management network. The second interface is used for the VM traffic on the Data network. The VM will be able to receive its IP address from the DHCP agent on this network.Network NodeRuns OpenStack Networking L2 agent, DHCP agent and L3 agent. This node will have access to the external network. The DHCP agent will allocate IP addresses to the VMs on data network (Technically, the addresses are allocated by the OpenStack Networking server, and distributed by the dhcp agent). The node must have at least two network interfaces. The first is used to communicate with the controller node via the management network. The second interface will be used as external network. GRE tunnels will be set up as data network.RouterRouter has IP 30.0.0.1, which is the default gateway for all VMs. The router should have ability to access public networks." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:98(para) +msgid "Glance is installed, configured and running. In addition to this there should be an image named tty." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:102(para) +msgid "OpenStack Identity is installed, configured and running. A OpenStack Networking user named quantum should be created on tenant servicetenant with password servicepassword." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:125(para) +msgid "OpenStack Compute is installed and configured" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:146(para) +msgid "Update the OpenStack Networking configuration file, /etc/quantum/quantum.conf, with plugin choice and Identity Service user as necessary:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:175(para) +msgid "Start the OpenStack Networking server" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:176(para) +msgid "The OpenStack Networking server can be a service of the operating system. The command may be different to start the service on different operating systems. One example of the command to run the OpenStack Networking server directly is:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:188(para) +msgid "Install OpenStack Compute services." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:207(para) +msgid "Restart relevant OpenStack Compute services" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:217(para) +msgid "Add the integration bridge to the Open vSwitch" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:221(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:275(para) +msgid "Update the OpenStack Networking configuration file, /etc/quantum/quantum.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:231(para) +msgid "Update the plugin configuration file, /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:234(para) +msgid "Compute Node:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:242(para) +msgid "Network Node:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:252(para) +msgid "Create the integration bridge br-int:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:260(para) +msgid "The OpenStack Networking Open vSwitch L2 agent can be a service of operating system. The command may be different to start the service on different operating systems. However the command to run it directly is kind of like:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:284(literal) +msgid "allow_overlapping_ips" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:284(emphasis) +msgid "We set because we have overlapping subnets for TenantA and TenantC." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:288(para) +msgid "Update the DHCP configuration file /etc/quantum/dhcp_agent.ini" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:295(para) +msgid "The OpenStack Networking DHCP agent can be a service of operating system. The command may be different to start the service on different operating systems. However the command to run it directly is kind of like:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:305(emphasis) +msgid "Network Node - L3 Agent" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:307(para) +msgid "Install the L3 agent." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:310(para) +msgid "Add the external network bridge" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:314(para) +msgid "Add the physical interface, for example eth0, that is connected to the outside network to this bridge" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:319(para) +msgid "Update the L3 configuration file /etc/quantum/l3_agent.ini:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:325(literal) +msgid "use_namespaces" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:325(emphasis) +msgid "We set (It is True by default.) because we have overlapping subnets for TenantA and TenantC and we are going to host the routers with one l3 agent network node." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:329(para) +msgid "Start the L3 agent" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:330(para) +msgid "The OpenStack Networking L3 agent can be a service of operating system. The command may be different to start the service on different operating systems. However the command to run it directly is kind of like:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:357(para) +msgid "Get the tenant ID (Used as $TENANT_ID later)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:373(para) +msgid "Get the user information" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:388(para) +msgid "Create the external network and its subnet by admin user:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:427(literal) +msgid "provider:network_type local" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:430(literal) +msgid "router:external true" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:426(emphasis) +msgid " means we don't need OpenStack Networking to realize this network through provider network. means we are creating an external network, on which we can create floating ip and router gateway port." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:437(para) +msgid "Add an IP on external network to br-ex" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:438(para) +msgid "Since we are using br-ex as our external network bridge, we will add an IP 30.0.0.100/24 to br-ex and then ping our VM's floating IP from our network node." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:445(para) +msgid "Serve TenantA" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:446(para) +msgid "For TenantA, we will create a private network, a subnet, a server, a router and a floating IP." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:449(para) +msgid "Create a network for TenantA" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:465(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:627(para) +msgid "After that we can use admin user to query the network's provider network information:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:483(para) +msgid "We can see that it has GRE tunnel ID (I.E. provider:segmentation_id) 1." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:486(para) +msgid "Create a subnet on the network TenantA-Net" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:508(para) +msgid "Create a server for TenantA" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:519(para) +msgid "Create and configure a router for TenantA:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:541(emphasis) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:704(emphasis) +msgid "We are using admin user to run last command since our external network is owned by admin tenant." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:544(para) +msgid "Associate a floating IP for TenantA_VM1" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:546(para) +msgid "1. Create a floating IP" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:560(para) +msgid "2. Get the port ID of the VM with ID 7c5e6499-7ef7-4e36-8216-62c2941d21ff" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:568(para) +msgid "3. Associate the floating IP with the VM port" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:580(para) +msgid "Ping the public network from the server of TenantA" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:581(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, we can ping the public network within the server of tenant A:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:596(para) +msgid "Ping floating IP of the TenantA's server" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:610(para) +msgid "Create other servers for TenantA" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:611(para) +msgid "We can create more servers for TenantA and add floating IPs for them." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:615(para) +msgid "Serve TenantC" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:616(para) +msgid "For TenantC, we will 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/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:620(para) +msgid "Create networks and subnets for TenantC" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:662(para) +msgid "We can see that we have GRE tunnel IDs (I.E. provider:segmentation_id) 2 and 3. And also note down the network IDs and subnet IDs because we will use them to create VMs and router." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:666(para) +msgid "Create a server TenantC-VM1 for TenantC on TenantC-Net1" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:670(para) +msgid "Create a server TenantC-VM3 for TenantC on TenantC-Net2" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:674(para) +msgid "List servers of TenantC" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:682(para) +msgid "Note down the server IDs since we will use them later." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:685(para) +msgid "Make sure servers get their IPs" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:686(para) +msgid "We can use VNC to log on the VMs to check if they get IPs. If not, we have to make sure the OpenStack Networking components are running right and the GRE tunnels work." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:693(para) +msgid "Create and configure a router for TenantC:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:707(para) +msgid "Checkpoint: ping from within TenantC's servers" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:708(para) +msgid "Since we have a router connecting to two subnets, the VMs on these subnets are able to ping each other. And since we have set the router's gateway interface, TenantC's servers are able to ping external network IPs, such as 192.168.1.1, 30.0.0.1 etc." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:712(para) +msgid "Associate floating IPs for TenantC's servers" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:714(para) +msgid "We can use the similar commands as we used in TenantA's section to finish this task." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:6(title) +msgid "Limitations" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:10(para) +msgid "OpenStack Networking overlapping IPs do not work with Nova security groups or Nova metadata server: Nova was designed assuming that a particular IP address will only ever be used by a single VM at any time. OpenStack Networking supports overlapping IPs if the allow_overlapping_ips config value is set to 'True'. We default this value to false to prevent unintentionally running Nova security groups or metadata server with overlapping IPs. If you enable this flag, you must disable both Nova security groups and the Nova metadata service." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:25(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 does not have an equivalent configuration, but is likely to add a similar capability in the future. However, since the nova-network multi_host design has some significant limitations in terms of deployment scale (limited to a single physical L2) and L3 forwarding behavior (does not map to a single L3 router for traffic between instances on separate networks), the OpenStack Networking feature may not be an exact match, or may be limited to a subnet of all OpenStack Networking deployment scenarios." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:43(para) +msgid "Linux network namespace required on nodes running quantum-l3-agent or quantum-dhcp-agent: . 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/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:54(para) +msgid "Linux kernel 2.6.24 or newer (with CONFIG_NET_NS=y in kernel configuration) and" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:58(para) +msgid "iproute2 utilities ('ip' command) version 3.1.0 (aka 20111117) or newer" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:62(para) +msgid "To check whether your host supports namespaces try running the following as root:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:66(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/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:71(para) +msgid "If you need to disable namespaces, make sure the quantum.conf used by quantum-server has the following setting:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:75(para) +msgid "and that the dhcp_agent.ini and l3_agent.ini have the following setting:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:78(para) +msgid "If the host does not support namespaces then the quantum-l3-agent and quantum-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/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:84(para) +msgid "If you run both L3 + DHCP services on the same node, you should enable namespaces to avoid conflicts with routes :" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:90(para) +msgid "No IPv6 support for L3 agent: The quantum-l3-agent supports only IPv4 forwarding. Currently, There are no errors provided if you configure IPv6 addresses via the API." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:94(para) +msgid "L3 Agent supports limited scale for OpenStack Networking Routers: The L3 agent polls the OpenStack Networking API to learn about changes to L3 configuration. If there are a large number of routers or router ports, this can lead to heavy load on the database used by an OpenStack Networking plugin. The suggested work-around is to increase the polling_interval value in l3_agent.ini . This will increase the possible time between when a L3 configuration change happens via the API and when it affects data forwarding." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:107(para) +msgid "ZeroMQ support is experimental: Some agents, including quantum-dhcp-agent, quantum-openvswitch-agent, and quantum-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, there are believed to be issues with ZeroMQ and the dhcp agent." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:113(para) +msgid "MetaPlugin is experimental: This release includes a \"MetaPlugin\" that is intended to support multiple plugins at the same time for different API requests, based on the content of those API requests. This functionality has not been widely reviewed or tested by the core team, and should be considered experimental until further validation is performed." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:119(para) +msgid "Horizon does not support Routers/Floating IPs with OpenStack Networking: Horizon support is limited to operations on OpenStack Networking Networks, Subnets, and Ports. Routers and Floating IPs must be configured via CLI." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:126(para) +msgid "L3 Router Extension does not support IPv6." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:4(title) +msgid "Advanced Configuration Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:5(para) +msgid "This section describes advanced configurations options for various system components (i.e. config options where the default is usually ok, but that the user may want to tweak). After installing from packages, $QUANTUM_CONF_DIR is /etc/quantum." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:9(title) +msgid "OpenStack Networking Server with Plugin" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:10(para) +msgid "This is the web server that runs the OpenStack Networking API Web Server. It is responsible for loading a plugin and passing the API calls to the plugin for processing. The quantum-server should receive one of more configuration files as it its input, for example:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:17(para) +msgid "The quantum config contains the common quantum configuration parameters. The plugin config contains the plugin specific flags. The plugin that is run on the service is loaded via the configuration parameter ‘core_plugin’. In some cases a plugin may have an agent that performs the actual networking. Specific configuration details can be seen in the Appendix - Configuration File Options." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:22(para) +msgid "Most plugins require a SQL database. After installing and starting the database server, set a password for the root account and delete the anonymous accounts:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:27(para) +msgid "Create a database and user account specifically for plugin:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:32(para) +msgid "Once the above is done you can update the settings in the relevant plugin configuration files. The plugin specific configuration files can be found at $QUANTUM_CONF_DIR/plugins." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:35(para) +msgid "Some plugins 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/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:40(para) +msgid "Two things need to be done prior to working with the plugin:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:43(para) +msgid "Ensure that the core plugin is updated." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:46(para) +msgid "Ensure that the database connection is correctly set." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:49(para) +msgid "The table below contains examples for these settings. Some Linux packages may provide installation utilities that configure these.
Settings
ParameterValue
Open vSwitch
core_plugin ($QUANTUM_CONF_DIR/quantum.conf)quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
sql_connection (in the plugin configuration file)mysql://<username>:<password>@localhost/ovs_quantum?charset=utf8
Plugin Configuration File$QUANTUM_CONF_DIR/plugins/openvswitch/ovs_quantum_plugin.ini
Agent quantum-openvswitch-agent
Linux Bridge
core_plugin ($QUANTUM_CONF_DIR/quantum.conf)quantum.plugins.linuxbridge.lb_quantum_plugin.LinuxBridgePluginV2
sql_connection (in the plugin configuration file)mysql://<username>:<password>@localhost/quantum_linux_bridge?charset=utf8
Plugin Configuration File$QUANTUM_CONF_DIR/plugins/linuxbridge/linuxbridge_conf.ini
Agent quantum-linuxbridge-agent
" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:103(para) +msgid "All of the plugin configuration files options can be found in the Appendix - Configuration File Options." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:107(title) +msgid "DHCP Agent" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:108(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/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:111(para) +msgid "The node that runs the DHCP agent should run:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:114(para) +msgid "Currently the DHCP agent uses dnsmasq to perform that static address assignment." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:116(para) +msgid "A driver needs to be configured that matches the plugin running on the service.
Basic settings
Parameter Value
Open vSwitch
interface_driver ($QUANTUM_CONF_DIR/dhcp_agent.ini)quantum.agent.linux.interface.OVSInterfaceDriver
Linux Bridge
interface_driver ($QUANTUM_CONF_DIR/dhcp_agent.ini)quantum.agent.linux.interface.BridgeInterfaceDriver
" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:146(para) +msgid "All of the DHCP agent configuration options can be found in the Appendix - Configuration File Options." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:149(title) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:225(title) +msgid "Namespace" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:150(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 Limitation section." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:153(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/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:161(title) +msgid "L3 Agent" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:162(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/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:166(para) +msgid "A driver needs to be configured that matches the plugin running on the service. The driver is used to create the routing interface.
Basic settings
Parameter Value
Open vSwitch
interface_driver ($QUANTUM_CONF_DIR/l3_agent.ini) quantum.agent.linux.interface.OVSInterfaceDriver
external_network_bridge ($QUANTUM_CONF_DIR/l3_agent.ini) br-ex
Linux Bridge
interface_driver ($QUANTUM_CONF_DIR/l3_agent.ini) quantum.agent.linux.interface.BridgeInterfaceDriver
external_network_bridge ($QUANTUM_CONF_DIR/l3_agent.ini) This field must be empty (or the bridge name for the external network).
" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:209(para) +msgid "OpenStack Identity authentication:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:211(para) +msgid "For example," +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:215(para) +msgid "Admin user details:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:206(para) +msgid "The L3 agent communicates with the OpenStack Networking server via the OpenStack Networking API, so the following configuration is required: " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:222(para) +msgid "All of the L3 agent configuration options can be found in the Appendix - Configuration File Options." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:226(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/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:229(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/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:234(para) +msgid "When use_namespaces is set as False, only one router ID can be supported per node. This must be configured via the configuration variable router_id." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:240(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/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:258(title) +msgid "Multiple Floating IP Pools" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:259(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/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:271(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/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:276(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/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:278(para) +msgid "For the first agent, invoke it with the following l3_agent.ini where handle_internal_only_routers is True." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:286(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/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:293(title) +msgid "OpenStack Compute Metadata Server Support" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:294(para) +msgid "To use OpenStack Compute metadata service, metadata_ip and metadata_port in the L3 agent configuration file need to be configured. Accessing from VMs to OpenStack Compute metadata service is forwarded to an external network through OpenStack Networking L3 router. OpenStack Compute metadata service must be reachable from the external network. As the Limitations section says, note that OpenStack Networking overlapping IPs support and OpenStack Compute metadata service cannot be used together." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:300(para) +msgid "Allowing VMs to reach the metadata service is a big point of confusion with OpenStack Networking. We need to make sure instructions for how to set this up are displayed more prominently than they already are, and that there are instructions for how to validate and troubleshoot in this scenario." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:304(para) +msgid "Example validation includes:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:305(emphasis) +msgid "VALIDATION STEP #1" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:306(para) +msgid "- on network node(l3_agent running) ping to metadata_ip that specified by l3_agent.py" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:308(para) +msgid "if you are not using namespace, just run:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:311(para) +msgid "for example, if the metadata server IP is 172.16.10.5, run:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:314(para) +msgid "if you using namespaces, identify the UUID of the router and run:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:317(para) +msgid "for example, if the router uuid is d7e9ec57-77c2-4046-aebf-d978ed4a4f83 and the metadata server IP is 172.16.10.5, run:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:321(emphasis) +msgid "VALIDATION STEP #2" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:322(para) +msgid "- on metadata server(nova_api server) check connection to vm's subnets using an un-NATed IP address of the VM, such as 10.0.0.2:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:324(emphasis) +msgid "NOTE" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:325(para) +msgid "OpenStack does not manage this routing for you, so you need to make sure that your host running the metadata service always has a route to reach each private network's subnet via the external network IP of that subnet's OpenStack Networking router. To do this, you can either run OpenStack Networking without namespaces, and run the quantum-l3-agent on the same host as nova-api. Otherwise, you can identify an IP prefix that includes all private network subnet's (e.g., 10.0.0.0/8) and then make sure that your metadata server has a route for that prefix with the OpenStack Networking router's external IP address as the next hop." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:6(title) +msgid "Advanced Features through API Extensions" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:7(para) +msgid "This section discusses two API extensions implemented by several plugins.  We include them in this guide as they are provide capabilities similar to what was available in nova-network and are thus likely to be relevant to a large portion of the OpenStack community. " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:13(title) +msgid "Provider Networks" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:14(para) +msgid "Provider networks allow cloud administrators to create OpenStack Networking networks that map directly to 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 may also be used to integrate with VLANs in the network that already have a defined meaning (e.g., allow 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/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:24(para) +msgid "The provider extension allows administrators to explicitly manage the relationship between OpenStack Networking virtual networks and underlying physical mechanisms such as VLANs and tunnels. When this extension is supported, OpenStack 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/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:33(para) +msgid "As of the Folsom release, the provider extension is supported by the openvswitch and linuxbridge plugins. Configuration of these plugins requires familiarity with this extension." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:38(title) +msgid "Terminology" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:43(para) +msgid "virtual network - An OpenStack Networking L2 network (identified by a UUID and optional name) whose ports can be attached as vNICs to OpenStack Compute instances and to various OpenStack Networking agents. The openvswitch and linuxbridge plugins each support several different mechanisms to realize virtual networks." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:55(para) +msgid "physical network - A network connecting virtualization hosts (i.e. OpenStack Compute nodes) with each other and with other network resources. Each physical network may support multiple virtual networks. The provider extension and the plugin configurations identify physical networks using simple string names." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:67(para) +msgid "tenant network - A \"normal\" virtual network created by/for a tenant. The tenant is not aware of how that network is physically realized." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:74(para) +msgid "provider network - 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/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:84(para) +msgid "VLAN network - A virtual network realized 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/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:99(para) +msgid "flat network - A virtual network realized 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/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:107(para) +msgid "local network - 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 may have other uses." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:116(para) +msgid "GRE network - A virtual network realized as network packets encapsulated using GRE. GRE networks are also referred to as \"tunnels\". GRE tunnel packets are routed by the host's IP routing table, so GRE networks are not associated by OpenStack Networking with specific physical networks." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:39(para) +msgid "A number of terms are used in the provider extension and in the configuration of plugins supporting the provider extension:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:127(para) +msgid "Both the openvswitch and linuxbridge plugins support VLAN networks, flat networks, and local networks. Only the openvswitch plugin currently supports GRE networks, provided that the host's Linux kernel supports the required Open vSwitch features." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:134(title) +msgid "Provider Attributes" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:135(para) +msgid "The provider extension extends the OpenStack Networking network resource with the following three additional attributes:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:139(caption) +msgid "Provider Network Attributes" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:154(td) +msgid "provider:network_type" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:157(td) +msgid "The physical mechanism by which the virtual network is realized. Possible values are \"flat\", \"vlan\", \"local\", and \"gre\", 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 realized as \"vlan\", \"gre\", or \"local\" network types depending on plugin configuration." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:170(td) +msgid "provider:physical_network" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:172(td) +msgid "If a physical network named \"default\" has been configured, and if provider:network_type is \"flat\" or \"vlan\", then \"default\" is used." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:176(td) +msgid "The name of the physical network over which the virtual network is realized for flat and VLAN networks. Not applicable to the \"local\" or \"gre\" network types." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:182(td) +msgid "provider:segmentation_id" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:183(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:610(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:616(td) +msgid "Integer" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:185(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 \"flat\" or \"local\" network types." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:195(para) +msgid "The provider attributes are returned by OpenStack Networking API operations when the client is authorized for the extension:provider_network:view action via the OpenStack Networking policy configuration. The provider attributes are only accepted for network API operations if the client is authorized for the extension:provider_network:set action. The default OpenStack Networking API policy configuration authorizes both actions for users with the admin role. See for details on policy configuration." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:210(title) +msgid "Provider API Workflow" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:211(para) +msgid "Show all attributes of a network, including provider attributes when invoked with the admin role:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:216(para) +msgid "Create a local provider network (admin-only):" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:220(para) +msgid "Create a flat provider network (admin-only):" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:224(para) +msgid "Create a VLAN provider network (admin-only):" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:228(para) +msgid "Create a GRE provider network (admin-only):" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:232(para) +msgid "When creating flat networks or VLAN networks, <phys-net-name> must be known to the plugin. See and for details on configuring network_vlan_ranges to identify all physical networks. When creating VLAN networks, <VID> can fall either within or outside any configured ranges of VLAN IDs from which tenant networks are allocated. Similarly, when creating GRE networks, <tunnel-id> can fall either within or outside any tunnel ID ranges from which tenant networks are allocated." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:244(para) +msgid "Once provider networks have been created, subnets can be allocated and they can be used similarly to other virtual networks, subject to authorization policy based on the specified <tenant_id>." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:252(title) +msgid "L3 Routing and NAT" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:253(para) +msgid "Just like the core OpenStack Networking API provides abstract L2 network segments that are decopuled from the technology used to implement the L2 network, OpenStack Networking includes an API extension that provides abstract L3 routers that API users can dynamically provision and configure. These OpenStack Networking routers can connect multiple L2 OpenStack Networking networks, and can also provide a \"gateway\" that connects one or more private L2 networks to a shared \"external\" network (e.g., a public network for access to the Internet). See and for details on common models of deploying OpenStack Networking L3 routers." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:267(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). Floating IPs can be allocated and then mapped from one OpenStack Networking port to another, as needed." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:279(title) +msgid "L3 API Abstractions" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:299(td) +msgid "UUID for the router." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:305(td) +msgid "Human-readable name for the router. Might not be unique." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:312(td) +msgid "The administrative state of router. If false (down), the router does not forward packets." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:320(para) +msgid "Indicates whether router is currently operational." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:327(td) +msgid "Owner of the router. Only admin users can specify a tenant_id other than its own." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:332(td) +msgid "external_gateway_info" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:333(td) +msgid "dict contain 'network_id' key-value pair" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:334(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:388(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:396(td) +msgid "Null" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:335(td) +msgid "External network that this router connects to for gateway services (e.g., NAT)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:341(caption) +msgid "Floating IP" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:359(td) +msgid "UUID for the floating IP." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:362(td) +msgid "floating_ip_address" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:363(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:395(td) +msgid "string (IP address)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:364(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:592(td) +msgid "allocated by OpenStack Networking" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:365(td) +msgid "The external network IP address available to be mapped to an internal IP address." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:369(td) +msgid "floating_network_id" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:372(para) +msgid "The network indicating the set of subnets from which the floating IP should be allocated" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:377(td) +msgid "router_id" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:380(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/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:386(td) +msgid "port_id" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:389(td) +msgid "Indicates the internal OpenStack Networking port associated with the external floating IP." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:394(td) +msgid "fixed_ip_address" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:397(td) +msgid "Indicates the IP address on the internal port that is mapped to by the floating IP (since an OpenStack Networking port might have more than one IP address)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:406(td) +msgid "Owner of the Floating IP. Only admin users can specify a tenant_id other than its own." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:415(title) +msgid "Common L3 Workflow" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:416(para) +msgid "Create external networks (admin-only)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:419(para) +msgid "Viewing external networks:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:421(para) +msgid "Creating routers" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:422(para) +msgid "Internal-only router to connect multiple L2 networks privately. " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:431(para) +msgid "The router will get an interface with the gateway_ip address of the subnet, and this interface will be attached to a port on the L2 OpenStack Networking network associated with the subnet. The router will also get an gateway interface to the specified external network.  This will provide SNAT connectivity to the external network as well as support for floating IPs allocated on that external networks (see below).  Commonly an external network maps to a network in the provider" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:441(para) +msgid "A router can also be connected to an “external network”, allowing that router to act as a NAT gateway for external connectivity. " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:445(para) +msgid "Viewing routers:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:446(para) +msgid "List all routers: " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:448(para) +msgid "Show a specific router: " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:450(para) +msgid "Show all internal interfaces for a router: " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:452(para) +msgid "Associating / Disassociating Floating IPs:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:453(para) +msgid "First, identify the port-id representing the VM NIC that the floating IP should map to:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:456(para) +msgid "This port must be on an OpenStack Networking subnet that is attached to a router uplinked to the external network that will be 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/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:465(para) +msgid "Create floating IP unassociated, then associate" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:469(para) +msgid "create floating IP and associate in a single step" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:472(para) +msgid "Viewing Floating IP State:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:474(para) +msgid "Find floating IP for a particular VM port:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:476(para) +msgid "Disassociate a Floating IP:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:478(para) +msgid "L3 Tear Down" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:479(para) +msgid "Delete the Floating IP:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:481(para) +msgid "Then clear the any gateway:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:483(para) +msgid "Then remove the interfaces from the router (deleting the network and subnet will do this as well):" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:486(para) +msgid "Finally, delete the router:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:491(title) +msgid "Security Groups" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:492(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/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:496(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/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:502(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=quantum 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 sametime." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:512(para) +msgid "In order to use the OpenStack Compute security group API with OpenStack Networking the OpenStack Networking plugin must implement the security group api. The following plugins currently implement this: Nicira NVP, Open vSwitch, Linux Bridge, NEC, and Ryu." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:516(para) +msgid "When using the security group API through OpenStack Compute, security groups are applied to all ports on an instance. The reason for this is that OpenStack Compute security group APIs are instances based and not port based as OpenStack Networking." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:521(title) +msgid "Security Group API Abstractions" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:523(caption) +msgid "Security Group Attributes" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:541(td) +msgid "UUID for the security group." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:547(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/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:552(td) +msgid "description" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:555(td) +msgid "Human-readable description of a security group." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:562(td) +msgid "Owner of the security group. Only admin users can specify a tenant_id other than their own." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:569(caption) +msgid "Security Group Rules" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:587(td) +msgid "UUID for the security group rule." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:590(td) +msgid "security_group_id" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:591(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:634(td) +msgid "uuid-str or Integer" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:593(td) +msgid "The security group to associate rule with." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:596(td) +msgid "direction" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:599(td) +msgid "The direction the traffic is allow (ingress/egress) from a VM." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:603(td) +msgid "protocol" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:606(td) +msgid "IP Protocol (icmp, tcp, udp, etc)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:609(td) +msgid "port_range_min" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:612(td) +msgid "Port at start of range" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:615(td) +msgid "port_range_max" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:618(td) +msgid "Port at end of range" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:621(td) +msgid "ethertype" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:624(td) +msgid "ethertype in L2 packet (IPv4, IPv6, etc)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:627(td) +msgid "source_ip_prefix" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:628(td) +msgid "string (IP cidr)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:630(td) +msgid "CIDR for address range" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:633(td) +msgid "source_group_id" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:635(td) +msgid "allocated by OpenStack Networking or OpenStack Compute" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:637(td) +msgid "Source security group to apply to rule." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:643(td) +msgid "Owner of the security group rule. Only admin users can specify a tenant_id other than its own." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:652(title) +msgid "Common Security Group Commands" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:653(para) +msgid "Create a security group for our web servers:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:656(para) +msgid "Viewing security groups:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:658(para) +msgid "Creating security group rule to allow port 80 ingress:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:662(para) +msgid "List security group rules:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:664(para) +msgid "Delete a security group rule:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:666(para) +msgid "Delete security group:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:668(para) +msgid "Create a port associated with security group:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:670(para) +msgid "Remove security groups from a port:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:6(title) +msgid "Core Configuration File Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:8(title) +msgid "quantum.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:9(para) +msgid "The configuration settings for the OpenStack Networking services are found in /etc/quantum/quantum.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:11(caption) +msgid "Debugging Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:14(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:35(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:90(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:148(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:235(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:287(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:355(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:434(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:475(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:529(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:576(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:684(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:746(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:919(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:959(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1021(th) +msgid "Configuration option=Default value" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:15(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:36(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:91(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:149(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:236(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:288(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:356(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:435(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:476(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:530(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:577(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:685(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:747(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:920(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:960(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1022(th) +msgid "(Type) Description" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:21(td) +msgid "debug=False" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:22(td) +msgid "(BoolOpt) Print debugging output" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:25(td) +msgid "verbose=False" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:26(td) +msgid "(BoolOpt) Print more verbose output" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:32(caption) +msgid "Logging Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:41(td) +msgid "log_config=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:42(td) +msgid "(StrOpt) If this option is specified, the logging configuration file specified is used and overrides any other logging options specified. Please see the Python logging module documentation for details on logging configuration files. Print debugging output" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:51(td) +msgid "log_format=%(asctime)s %(levelname)8s [%(name)s] %(message)s" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:53(td) +msgid "(StrOpt) A logging.Formatter log message format string which may use any of the available logging.LogRecord attributes." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:59(td) +msgid "log_date_format=%Y-%m-%d %H:%M:%S" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:60(td) +msgid "(StrOpt) Format string for %(asctime)s in log records." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:64(td) +msgid "log_file=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:65(td) +msgid "(StrOpt) (Optional) Name of log file to output to.  If not set, logging will go to stdout." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:70(td) +msgid "log_dir=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:71(td) +msgid "(StrOpt) (Optional) The directory to keep log files in (will be prepended to --logfile)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:76(td) +msgid "use_syslog=False" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:77(td) +msgid "(BoolOpt) Use syslog for logging." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:80(td) +msgid "syslog_log_facility=LOG_USER" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:81(td) +msgid "(StrOpt) syslog facility to receive log lines" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:87(caption) +msgid "Service Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:96(td) +msgid "bind_host=0.0.0.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:97(td) +msgid "(StrOpt) Server listening IP." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:100(td) +msgid "bind_port=9696" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:101(td) +msgid "(IntOpt) Server listening port." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:104(td) +msgid "api_paste_config=api-paste.ini" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:105(td) +msgid "(StrOpt) The paste configuration file. This is used to configure the WSGI application." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:110(td) +msgid "api_extensions_path=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:111(td) +msgid "(StrOpt) Enables custom addition to be made to the above configuration." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:115(td) +msgid "policy_file=policy.json" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:116(td) +msgid "(StrOpt) JSON file representing policies to access and view data. The usage and format is discussed in more detail in the Authentication and Authorization section." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:123(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1046(td) +msgid "auth_strategy=keystone" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:124(td) +msgid "(StrOpt) The strategy used for authentication. The supported values are ‘keystone’ and ‘noauth’." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:129(td) +msgid "core_plugin=quantum.plugins.sample.SamplePlugin.FakePlugin" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:131(td) +msgid "(StrOpt) The plugin to be loaded by the service." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:135(td) +msgid "pagination_max_limit=-1" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:137(td) +msgid "(StrOpt) The maximum number of items returned in a single response. A value of 'infinite', or a negative integer means no limit." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:145(caption) +msgid "Base Plugin Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:154(td) +msgid "base_mac=fa:16:3e:00:00:00" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:155(td) +msgid "(StrOpt) MAC addresses for a port are generated. The first 3 octets will remain unchanged. If the 4h octet is not 00, it will also used. The others will be randomly generated." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:162(td) +msgid "mac_generation_retries=16" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:163(td) +msgid "(IntOpt) The number of times the plugin attempts to generate a unique MAC address." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:168(td) +msgid "allow_bulk=True" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:169(td) +msgid "(BoolOpt) Enable or disable bulk create/update/delete operations." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:173(td) +msgid "allow_pagination=False" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:174(para) +msgid "(BoolOpt) Enable or disable pagination. If plugin doesn't support native pagination, it will enable emulated pagination. Please note native pagination depends on native sorting. If native pagination is enabled, native emulated sorting will be enabled automatically." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:181(para) +msgid "If the plugin supports native pagination, the plugin will returns the maximum limit of items as request. If the plugin didn't support that, quantum API can emulate the pagination behavior. The performance of native pagination is better than emulated pagiantion." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:192(td) +msgid "allow_sorting=False" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:193(para) +msgid "(BoolOpt) Enable or disable sorting. If plugin doesn't support native sorting, it will enable emulated sorting." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:197(para) +msgid "If the plugin supports native sorting, the plugin will returns ordered items as request. If the plugin didn't support that, quantum API can emulate the sorting behavior. The performance of native sorting is better than emulated sorting." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:207(td) +msgid "max_dns_nameservers=5" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:208(td) +msgid "(IntOpt) The maximum amount of DNS nameservers that can be configured per subnet." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:213(td) +msgid "max_subnet_host_routes=20" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:214(td) +msgid "(IntOpt) The maximum amount of host routes that can be configured per subnet." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:218(td) +msgid "state_path=." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:219(td) +msgid "(StrOpt) Top level directory for configuration files." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:223(td) +msgid "dhcp_lease_duration=120" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:224(td) +msgid "(IntOpt) The default expiration time for a DHCP address. This is in seconds." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:232(caption) +msgid "Common RPC Message Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:241(td) +msgid "control_exchange=quantum" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:242(td) +msgid "(StrOpt) AMQP exchange to connect to if using RabbitMQ or QPID" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:246(td) +msgid "rpc_back_end=quantum.openstack.common.rpc.impl_kombu" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:248(td) +msgid "(StrOpt) The messaging module to use, defaults to kombu. For qpid, make use of quantum.openstack.common.rpc.impl_qpid" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:254(td) +msgid "rpc_thread_pool_size=64" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:255(td) +msgid "(IntOpt) Size of RPC thread pool." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:258(td) +msgid "rpc_conn_pool_size=30" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:259(td) +msgid "(IntOpt) Size of RPC connection pool." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:263(td) +msgid "rpc_response_timeout=60" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:264(td) +msgid "(IntOpt) Seconds to wait for a response from call or multicall" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:268(td) +msgid "allowed_rpc_exception_modules='quantum.openstack.common.exception', 'nova.exception'" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:271(td) +msgid "(ListOpt) Modules of exceptions that are permitted to be recreated upon receiving exception data from an rpc call." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:276(td) +msgid "fake_rabbit=False" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:277(td) +msgid "(BoolOpt) If passed, use a fake RabbitMQ provider" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:284(caption) +msgid "Rabbit RPC Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:293(td) +msgid "kombu_ssl_version=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:294(td) +msgid "(StrOpt) SSL version to use (valid only if SSL enabled)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:298(td) +msgid "kombu_ssl_keyfile=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:299(td) +msgid "(StrOpt) SSL key file (valid only if SSL enabled)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:303(td) +msgid "kombu_ssl_certfile=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:304(td) +msgid "(StrOpt) SSL cert file (valid only if SSL enabled)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:308(td) +msgid "kombu_ssl_ca_certs=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:309(td) +msgid "(StrOpt) SSL certification authority file (valid only if SSL enabled)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:313(td) +msgid "rabbit_host=localhost" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:314(td) +msgid "(StrOpt) IP address of the RabbitMQ installation" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:318(td) +msgid "rabbit_password=guest" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:319(td) +msgid "            Password of the RabbitMQ server" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:323(td) +msgid "rabbit_port=5672" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:324(td) +msgid "(IntOpt) Port where RabbitMQ server is running/listening" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:328(td) +msgid "rabbit_userid=guest" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:329(td) +msgid "(StrOpt) User ID used for RabbitMQ connections" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:333(td) +msgid "rabbit_virtual_host=/" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:334(td) +msgid "(StrOpt) Location of a virtual RabbitMQ installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:338(td) +msgid "rabbit_max_retries=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:339(td) +msgid "(IntOpt) Maximum retries with trying to connect to RabbitMQ. The default of 0 implies an infinite retry count" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:344(td) +msgid "rabbit_retry_interval=1" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:345(td) +msgid "(IntOpt) RabbitMQ connection retry interval" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:352(caption) +msgid "QPID RPC Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:361(td) +msgid "qpid_hostname=localhost" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:362(td) +msgid "(StrOpt) Qpid broker hostname" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:365(td) +msgid "qpid_port=5672" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:366(td) +msgid "(IntOpt) Qpid broker port" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:369(td) +msgid "qpid_username=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:370(td) +msgid "(StrOpt) Username for qpid connection" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:374(td) +msgid "qpid_password=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:375(td) +msgid "(StrOpt) Password for qpid connection" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:379(td) +msgid "qpid_sasl_mechanisms=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:380(td) +msgid "(StrOpt) Space separated list of SASL mechanisms to use for auth" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:384(td) +msgid "qpid_reconnect=True" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:385(td) +msgid "(BoolOpt) Automatically reconnect" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:388(td) +msgid "qpid_reconnect_timeout=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:389(td) +msgid "(IntOpt) The number of seconds to wait before deciding that a reconnect attempt has failed" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:394(td) +msgid "qpid_reconnect_limit=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:395(td) +msgid "(IntOpt) The limit for the number of times to reconnect before considering the connection to be failed." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:400(td) +msgid "qpid_reconnect_interval_min=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:401(td) +msgid "(IntOpt) Minimum seconds between reconnection attempts" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:405(td) +msgid "qpid_reconnect_interval_max=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:406(td) +msgid "(IntOpt) Maximum seconds between reconnection attempts" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:410(td) +msgid "qpid_reconnect_interval=0" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:411(td) +msgid "(IntOpt) Equivalent to setting max and min to the same value" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:415(td) +msgid "qpid_heartbeat=60" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:416(td) +msgid "(IntOpt) Seconds between connection keepalive heartbeats" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:420(td) +msgid "qpid_protocol=tcp" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:421(td) +msgid "(StrOpt) Transport to use, either 'tcp' or 'ssl'" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:425(td) +msgid "qpid_tcp_nodelay=True" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:426(td) +msgid "(BoolOpt) Disable Nagle algorithm" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:440(td) +msgid "notification_driver=quantum.openstack.common.notifier.list_notifier" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:442(td) +msgid "(MultiStrOpt) Driver or drivers to handle sending notifications. The default is set as notifier as the DHCP agent makes use of the notifications." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:448(td) +msgid "default_notification_level=INFO" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:449(td) +msgid "(StrOpt) Default notification level for outgoing notifications" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:453(td) +msgid "default_publisher_id=$host" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:454(td) +msgid "(StrOpt) Default publisher_id for outgoing notifications" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:458(td) +msgid "list_notifier_drivers='quantum.openstack.common.notifier.no_op_notifier'" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:460(td) +msgid "(MultiStrOpt) List of drivers to send notifications" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:464(td) +msgid "notification_topics='notifications'" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:465(td) +msgid "(ListOpt) AMQP topic used for openstack notifications" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:472(caption) +msgid "Quota Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:481(td) +msgid "quota_driver=quantum.quota.ConfDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:482(td) +msgid "(StrOpt) Default driver to use for quota checks. If the default driver is used then the configuration values below are in effect. To limit quotas per tenant then use: quantum.db.quota_db.DbQuotaDriver" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:491(td) +msgid "quota_items=network,subnet,port" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:492(td) +msgid "(ListOpt) Resource names that are supported by the Quotas feature." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:496(td) +msgid "default_quota=-1" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:497(td) +msgid "(IntOpt) Default number of resources allowed per tenant, minus for unlimited" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:502(td) +msgid "quota_network=10" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:503(td) +msgid "(IntOpt) Number of networks allowed per tenant, and minus means unlimited" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:507(td) +msgid "quota_subnet=10" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:508(td) +msgid "(IntOpt) Number of subnets allowed per tenant, and minus means unlimited" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:512(td) +msgid "quota_port=50" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:513(td) +msgid "(IntOpt) Number of ports allowed per tenant, and minus means unlimited" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:520(title) +msgid "ovs_quantum_plugin.ini:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:521(para) +msgid "For information about the Open vSwitch plugin configurations, see http://wiki.openstack.org/ConfigureOpenvswitch." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:526(caption) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:681(caption) +msgid "Database Access by Plugin" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:535(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:690(td) +msgid "sql_connection=sqlite://" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:536(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:691(para) +msgid "(StrOpt) The details of the database connection. For example mysql://root:nova@127.0.0.1:3306/ovs_quantum. Replace 127.0.0.1 above with the IP address of the database used by the main OpenStack Networking server. (Leave it as is if the database runs on this host.)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:545(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:700(para) +msgid "This line must be changed to ensure that the database values are persistent. The sqlite is used for testing." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:552(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:707(td) +msgid "sql_max_retries=10" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:553(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:708(td) +msgid "(IntOpt) Database re-connection retry times. This is in the event connectivity is lost with the database. -1 implies an infinite retry count." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:559(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:714(td) +msgid "reconnect_interval=2" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:560(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:715(td) +msgid "(IntOpt) Database reconnection interval in seconds - in event connectivity is lost." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:566(para) +msgid "OVS Options (This is in the section OVS)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:568(para) +msgid "This section deals with the specific OVS options common to the plugin and agent." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:572(caption) +msgid "OVS Options Common to Plugin and Agent" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:582(td) +msgid "network_vlan_ranges=default:2000:3999" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:583(td) +msgid "(ListOpt) Comma-separated list of  <physical_network>:<vlan_min>:<vlan_max> tuples enumerating ranges of VLAN IDs on named physical networks that are available for allocation." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:590(td) +msgid "tunnel_id_ranges=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:591(td) +msgid "(ListOpt) Comma-separated list of <tun_min>:<tun_max> tuples enumerating ranges of GRE tunnel IDs that are available for allocation." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:597(td) +msgid "integration_bridge=br-int" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:598(td) +msgid "(StrOpt) This is the name of the OVS integration bridge. There is one per hypervisor. The integration bridge acts as a virtual \"patch port\". All VM VIFs are attached to this bridge and then \"patched\" according to their network connectivity. Do not change this parameter unless you have a good reason to." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:608(td) +msgid "tunnel_bridge=br-tun" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:609(td) +msgid "(StrOpt) Specifies the name of the OVS tunnel bridge used by the agent for GRE tunnels. Only used if tunnel_id_ranges is not empty." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:615(td) +msgid "bridge_mappings=default:br-eth1" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:616(td) +msgid "(ListOpt) Comma-separated list of <physical_network>:<bridge> tuples mapping physical network names to agent's node-specific OVS bridge names. Each bridge must exist, and should have physical network # interface configured as a port." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:625(td) +msgid "local_ip=10.0.0.3" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:626(td) +msgid "(StrOpt) Set local-ip to be the local IP address of this hypervisor. This is used only when tunnel_id_ranges are used." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:631(td) +msgid "enable_tunneling=False" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:632(td) +msgid "(BoolOpt) A flag indicating if tunneling is supported. Not all systems that support Open vSwitch support its GRE tunneling feature, that is, it is not supported in the Linux kernel source tree. This applies to both the server and agent" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:641(para) +msgid "(This is in the section AGENT)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:642(para) +msgid "
Agent Options
Configuration option=Default value(Type) Description
rpc=True (BoolOpt) If this is True then the agent will communicate with the plugin via the OpenStack RPC (configured in quantum.conf). If this is False then the agent will poll the database for changes. In the event that this is False then please update the relevant database settings on the agent so that it is able to access the database.
polling_interval=2 (IntOpt) Agent's polling interval in seconds.
root_helper=sudo (StrOpt) This enables limiting commands that can be run. Please refer to rootwrap section for more details.
   " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:679(title) +msgid "linuxbridge_conf.ini:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:722(para) +msgid " 
VLAN Configurations
Configuration option=Default value(Type) Description
network_vlan_ranges=default:1000:2999 (ListOpt) Comma-separated list of <physical_network>:<vlan_min>:<vlan_max> tuples enumerating ranges of VLAN IDs on named physical networks that are available for allocation.
" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:743(caption) +msgid "Networking Options on the Agent" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:752(td) +msgid "physical_interface_mappings=default:eth1" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:753(td) +msgid "(ListOpt) Comma-separated list of <physical_network>:<physical_interface> tuples mapping physical network names to agent's node-specific physical network interfaces. Server uses physical network names for validation but ignores interfaces." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:763(para) +msgid "
Agent Options
Configuration option=Default value(Type) Description
rpc=True (BoolOpt) If this is True then the agent will communicate with the plugin via the OpenStack RPC (configured in quantum.conf). If this is False then the agent will poll the database for changes. In the event that this is False then please update the relevant database settings on the agent so that it is able to access the database.
polling_interval=2 (IntOpt) Agent's polling interval in seconds.
root_helper=sudo (StrOpt) This enables limiting commands that can be run. Please refer to rootwrap section for more details.
 " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:800(title) +msgid "dhcp_agent.ini" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:801(para) +msgid "
DHCP Specific Options
Configuration option=Default value(Type) Description
root_helper=sudo (StrOpt) This enables limiting commands that can be run. Please refer to rootwrap section for more details.
dhcp_driver=quantum.agent.linux.dhcp.Dnsmasq (StrOpt) The driver used to manage the DHCP server.
use_namespaces=True (BoolOpt) Allow overlapping IP. (Note: If running multiple agents with different IP addresses on the same host this should be \"True\" if not you will get routing problems.)
 " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:831(para) +msgid "
Device Manager Options
Configuration option=Default value(Type) Description
admin_user= (StrOpt) Name of the admin user for OpenStack Networking, which is defined in OpenStack Identity (keystone)
admin_password= (StrOpt) The users password
admin_tenant_name= (StrOpt) The admin tenant name
auth_url= (StrOpt) The URL used to validate tokens. `auth_protocol`://`auth_host`:`auth_port`/v2.0
auth_strategy=keystone (StrOpt) The strategy to use for authentication. Supports noauth or keystone.
auth_region= (StrOpt) The authentication region
interface_driver= (StrOpt) The driver used to manage the virtual interface.
dhcp_lease_relay_socket=$state_path/dhcp/lease_relay (StrOpt) Location to DHCP lease relay UNIX domain socket
ovs_integration_bridge=br-int (StrOpt) Name of Open vSwitch bridge to use. Only relevant if using Open vSwitch.
network_device_mtu= (StrOpt) MTU setting for device. Only relevant if using Open vSwitch.
ryu_api_host=127.0.0.1:8080 (StrOpt) OpenFlow Ryu REST API host:port. Only relevant if using Ryu.
meta_flavor_driver_mappings= (StrOpt). Mappings between flavors and drivers. Only relevant if using MetaPlugin.
resync_interval=30 (IntOpt) If there is an exception on the quantum-server service, then the DHCP agent will ensure that it syncs with the quantum.conf configuration. The validation about syncing is done every resync_interval seconds.
   " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:916(caption) +msgid "dnsmasq Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:925(td) +msgid "dhcp_confs=$state_path/dhcp" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:926(td) +msgid "(StrOpt) Location to store DHCP server config files" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:930(td) +msgid "dhcp_lease_time=120" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:931(td) +msgid "(IntOpt) Lifetime of a DHCP lease in seconds" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:935(td) +msgid "dhcp_domain=openstacklocal" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:936(td) +msgid "(StrOpt) Domain to use for building the hostnames" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:940(td) +msgid "dnsmasq_config_file=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:941(td) +msgid "(StrOpt) Override the default dnsmasq settings with this file" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:945(td) +msgid "dnsmasq_dns_server=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:946(td) +msgid "(StrOpt) Use another DNS server before any in /etc/resolv.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:953(title) +msgid "l3_agent.ini" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:956(caption) +msgid "L3 Specific Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:965(td) +msgid "root_helper=sudo" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:966(td) +msgid "(StrOpt) This enables limiting commands that can be run. Please refer to rootwrap section for more details." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:971(td) +msgid "external_network_bridge=br-ex" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:972(td) +msgid "(StrOpt) Name of bridge used for external network traffic." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:976(td) +msgid "use_namespaces=True" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:977(td) +msgid "(BoolOpt) Allow overlapping IP. (Note: If running multiple agents with different IP addresses on the same host this should be \"True\" if not you will get routing problems.)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:984(td) +msgid "polling_interval=3" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:985(td) +msgid "(IntOpt) The time in seconds between state poll requests." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:989(td) +msgid "metadata_ip=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:990(td) +msgid "(StrOpt) IP address used by OpenStack Compute metadata server." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:994(td) +msgid "metadata_port=8775" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:995(td) +msgid "(IntOpt) TCP Port used by OpenStack Compute metadata server." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:999(td) +msgid "router_id=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1000(td) +msgid "(StrOpt) If namespaces is disabled, the l3 agent can only configure a router whose ID matches this parameter." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1005(td) +msgid "handle_internal_only_routers=True" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1006(td) +msgid "(BoolOpt) Agent should implement routers with no gateway." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1010(td) +msgid "gateway_external_network_id=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1011(td) +msgid "(StrOpt) UUID of external network for routers implemented by the agents." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1018(caption) +msgid "Device Manager Options" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1027(td) +msgid "admin_user=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1029(link) +msgid "OpenStack Identity" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1028(td) +msgid "(StrOpt) Name of the admin user for OpenStack Networking, which is defined in (keystone)" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1032(td) +msgid "admin_password=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1033(td) +msgid "(StrOpt) The users password" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1036(td) +msgid "admin_tenant_name=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1037(td) +msgid "(StrOpt) The admin tenant name" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1040(td) +msgid "auth_url=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1041(td) +msgid "(StrOpt) The URL used to validate tokens. `auth_protocol`://`auth_host`:`auth_port`/v2.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1047(td) +msgid "(StrOpt) The strategy to use for authentication. Supports noauth or keystone." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1052(td) +msgid "auth_region=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1053(td) +msgid "(StrOpt) The authentication region" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1056(td) +msgid "interface_driver=" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1057(td) +msgid "(StrOpt) The driver used to manage the virtual interface." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:347(None) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:350(None) +msgid "@@image: '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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:364(None) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:367(None) +msgid "@@image: '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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:388(None) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:391(None) +msgid "@@image: 'figures/UseCase-MixedFlatPrivate.png'; md5=8da4ceb5a1e5a2357394478645af7449" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:424(None) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:427(None) +msgid "@@image: 'figures/UseCase-SingleRouter.png'; md5=63d21d52d32ed7fa1c1dad1a1fd88eb5" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:6(title) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:174(title) +msgid "Overview" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:7(para) +msgid "This chapter describes the high-level concepts and components of an OpenStack Networking deployment." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:10(title) +msgid "What is OpenStack Networking?" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:11(para) +msgid "The OpenStack Networking project was created to provide 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.  " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:16(para) +msgid "For a detailed description of the OpenStack Networking API abstractions and their attributes, see the OpenStack Networking API Guide (v2.0)." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:26(title) +msgid "A Rich Network API" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:27(para) +msgid "OpenStack Networking 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.  " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:37(para) +msgid "Network. An isolated L2 segment, analogous to VLAN in the physical networking world." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:43(para) +msgid "Subnet. A block of v4 or v6 IP addresses and associated configuration state." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:48(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:31(para) +msgid "The OpenStack Compute API has a virtual server abstraction to describe compute resources. Similarly, the OpenStack Networking API has virtual  network, subnet, and port abstractions to describe network resources. In more detail: 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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:69(para) +msgid "Even if a cloud administrator does not intend to expose these capabilities to tenants directly, the OpenStack Networking API can be very useful even when used as an admin API because it provides significantly more flexibility for the cloud administrator to customize network offerings.  " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:75(para) +msgid "The OpenStack Networking API also provides a mechanism that lets cloud administrators expose additional API capabilities through API extensions.  Commonly, new capabilities are first introduced as an API extension, and over time become part of the core OpenStack Networking API." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:84(title) +msgid "Flexibility to Choose Different Network Technologies" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:86(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:90(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:103(para) +msgid "Open vSwitch. http://www.openvswitch.org/openstack/documentation" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:110(para) +msgid "Cisco. quantum/plugins/cisco/README and http://wiki.openstack.org/cisco-quantum" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:120(para) +msgid "Linux Bridge. quantum/plugins/linuxbridge/README and http://wiki.openstack.org/Quantum-Linux-Bridge-Plugin  " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:130(para) +msgid "Nicira NVP. quantum/plugins/nicira/nicira_nvp_plugin/README and http://www.nicira.com/support." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:140(para) +msgid "Ryu. quantum/plugins/ryu/README and http://www.osrg.net/ryu/using_with_openstack.html" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:150(para) +msgid "NEC OpenFlow. http://wiki.openstack.org/Quantum-NEC-OpenFlow-Plugin" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:157(para) +msgid "Big Switch, Floodlight REST Proxy. http://www.openflowhub.org/display/floodlightcontroller/Quantum+REST+Proxy+Plugin" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:101(para) +msgid "The current set of plugins include: " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:164(para) +msgid "Plugins enable the cloud administrator to weigh different options and decide which networking technology is right for the deployment." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:170(title) +msgid "OpenStack Networking Architecture" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:171(para) +msgid "This section describes the high-level components of an OpenStack Networking deployment." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:175(para) +msgid "Before you 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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:179(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:186(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:201(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:211(para) +msgid "dhcp agent (quantum-dhcp-agent). Provides DHCP services to tenant networks. This agent is the same across all plugins." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:219(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:193(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:231(para) +msgid "Through RPC. For example, rabbitmq or qpid." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:235(para) +msgid "Through the standard OpenStack Networking API.   " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:228(para) +msgid "These agents interact with the main quantum-server process in the following ways: OpenStack Networking relies on the OpenStack Identity Project (Keystone) for authentication and authorization of all API request.   " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:241(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:245(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.  See the Horizon Administrator Guide." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:252(title) +msgid "Place Services on Physical Hosts" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:253(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. See  " +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:260(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:270(title) +msgid "Network Connectivity for Physical Hosts" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:280(para) +msgid "A standard OpenStack Networking setup has up to four distinct physical data center networks:" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:283(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:291(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:298(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:306(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 "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:318(para) +msgid "If the OpenStack Compute metadata service is being used, any address space used on tenant networks must be routable on both the API network and on the External network, since the host running nova-api must be able to reply to HTTP requests with the un-SNATed IP address of a VM." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:324(title) +msgid "OpenStack Networking Deployment Use Cases" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:325(para) +msgid "This section describes some of the common use cases for OpenStack Networking. These examples are not exhaustive and can be combined with each other to create more complex use cases." +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:329(title) +msgid "Use Case: Single Flat Network" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:330(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:337(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:356(title) +msgid "Use Case: Multiple Flat Network" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:357(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:373(title) +msgid "Use Case: Mixed Flat and Private Network" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:374(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:397(title) +msgid "Use Case: Provider Router with Private Networks" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:398(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:406(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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:415(para) +msgid "The router provides L3 connectivity between private networks, meaning that different tenants can reach each others instances unless additional filtering (e.g., 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/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:433(title) +msgid "Use Case: Per-tenant Routers with Private Networks" +msgstr "" + +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:434(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 "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/src/docbkx/openstack-object-storage-admin/locale/openstack-object-storage-admin.pot b/doc/src/docbkx/openstack-object-storage-admin/locale/openstack-object-storage-admin.pot new file mode 100644 index 0000000000..f84781ff03 --- /dev/null +++ b/doc/src/docbkx/openstack-object-storage-admin/locale/openstack-object-storage-admin.pot @@ -0,0 +1,3288 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2013-03-12 15:10+0800\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/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:5(title) +msgid "Introduction to OpenStack Object Storage" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:6(para) +msgid "OpenStack Object Storage is a scalable object storage system - it is not a file system in the traditional sense. You will not be able to mount this system like traditional SAN or NAS volumes. Since OpenStack Object Storage is a different way of thinking when it comes to storage, take a few moments to review the key concepts listed below." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:11(title) +msgid "Accounts and Account Servers" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:12(para) +msgid "The OpenStack Object Storage system is designed to be used by many different storage consumers or customers. Each user must identify themselves using an authentication system." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:15(para) +msgid "Nodes that run the Account service are a separate concept from individual accounts. Account servers are part of the storage system and must be configured along with Container servers and Object servers." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:20(title) +msgid "Authentication and Access Permissions" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:21(para) +msgid "You must authenticate against an Authentication service to receive OpenStack Object Storage connection parameters and an authentication token. The token must be passed in for all subsequent container/object operations. One authentication service that you can use as a middleware example is called swauth and you can download it from https://github.com/gholt/swauth. You can also integrate with the OpenStack Identity Service, code-named Keystone, which you can download from https://github.com/openstack/keystone." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:27(para) +msgid "Typically the language-specific APIs handle authentication, token passing, and HTTPS request/response communication." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:31(para) +msgid "You can implement access control for objects either for users or accounts using X-Container-Read: accountname and X-Container-Write: accountname:username, which allows any user from the accountname account to read but only allows the username user from the accountname account to write. You can also grant public access to objects stored in OpenStack Object Storage but also limit public access using the Referer header to prevent site-based content theft such as hot-linking (for example, linking to an image file from off-site and therefore using other's bandwidth). The public container settings are used as the default authorization over access control lists. For example, using X-Container-Read: referer:any allows anyone to read from the container regardless of other authorization settings." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:41(para) +msgid "Generally speaking, each user has their own storage account and has full access to that account. Users must authenticate with their credentials as described above, but once authenticated they can create/delete containers and objects within that account. The only way a user can access the content from another account is if they share an API access key or a session token provided by your authentication system." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:48(title) +msgid "Containers and Objects" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:49(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/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:55(para) +msgid "The only restrictions on container names is that they cannot contain a forward slash (/) and must be less than 256 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/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:61(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/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:68(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/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:72(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/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:75(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/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:77(title) +msgid "Warning" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:77(para) +msgid "The Object Storage API uses HTTP which specifies that header fields, such as those used to send metadata are case insensitive. Please do not expect the case of metadata items being preserved." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:82(title) +msgid "Operations" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:83(para) +msgid "Operations are the actions you perform within an OpenStack Object Storage system such as creating or deleting containers, uploading or downloading objects, and so on. The full list of operations is documented in the Developer Guide. Operations may be performed via the REST web service API or a language-specific API; currently, we support Python, PHP, Java, Ruby, and C#/.NET." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:89(para) +msgid "All operations must include a valid authorization token from your authorization system." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:94(title) +msgid "Language-Specific API Bindings" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:95(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/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:104(para) +msgid "The API bindings for Rackspace Cloud Files are hosted at http://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/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:109(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/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:114(para) +msgid "PHP (requires 5.x and the modules: cURL, FileInfo, mbstring)" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:117(para) +msgid "Python (requires 2.4 or newer)" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:120(para) +msgid "Java (requires JRE v1.5 or newer)" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:123(para) +msgid "C#/.NET (requires .NET Framework v3.5)" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:126(para) +msgid "Ruby (requires 1.8 or newer and mime-tools module)" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/aboutobjectstorage.xml:129(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:6(title) +msgid "System Administration for OpenStack Object Storage" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:7(para) +msgid "By understanding the concepts inherent to the Object Storage system you can better monitor and administer your storage solution." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:11(title) +msgid "Understanding How Object Storage Works" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:12(para) +msgid "This section offers a brief overview of each concept in administering Object Storage." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:13(title) +msgid "The Ring" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:15(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:17(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 handoff in failure scenarios." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:19(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 datacenter." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:21(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 (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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:23(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:25(para) +msgid "The ring is used by the Proxy server and several background processes (like replication)." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:26(title) +msgid "Proxy Server" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:27(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:29(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:32(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:33(para) +msgid "You can use a proxy server with account management enabled by configuring it in the proxy server configuration file." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:36(title) +msgid "Object Server" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:38(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:40(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:43(title) +msgid "Container Server" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:45(para) +msgid "The Container Server’s primary job is to handle listings of objects. It doesn’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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:47(title) +msgid "Account Server" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:48(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:51(title) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:649(title) +msgid "Replication" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:53(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:55(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:57(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:59(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:61(title) +msgid "Updaters" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:63(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:73(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:75(title) +msgid "Auditors" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:77(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 can’t be found on any container server it should be)." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:85(title) +msgid "Object Layout on Storage" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:86(para) +msgid "Swift uses the underlying filesystem to store the data on disk. An administrator can use normal filesystem tools to find and inspect this data. Swift uses the following convention for storing objects:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:90(replaceable) +msgid "path_to_mount_points" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:90(replaceable) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:444(td) +msgid "device" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:90(replaceable) +msgid "partition" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:90(replaceable) +msgid "hash_suffix" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:90(replaceable) +msgid "hash/" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:89(filename) +msgid "///objects///" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:91(para) +msgid "Accounts and containers are stored similarly, with the \"objects\" part of the path replaced with \"accounts\" or \"containers\"." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:93(para) +msgid "The directory is where all of the data for the object is stored. Inside the directory, there is normally just one file (named <timestamp>.data). The object's data is stored in the file, and the object's metadata is stored in the extended attributes (xattrs) of the file." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:98(para) +msgid "If a user deletes the object, the .data file is deleted and a <timestamp>.ts (\"ts\" for \"tombstone\") file is created as a zero-byte file. This is a delete marker that will be eventually reaped, but it exists to ensure that the delete properly propagates to all replicas in the cluster." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:103(para) +msgid "Swift uses this scheme of timestamps in the file name to implement conflict resolution. Each piece of data is assigned a timestamp by the proxy server when the request comes to the cluster, and that timestamp is what's used to name the file on disk on the object (or account or container) server. For the common case, there will be a single file in the directory. If Swift receives multiple, concurrent requests to write to the same object, it can happen that multiple .data files are written to this directory. Swift uses \"last-write-wins\" to resolve such conflicts, choosing the most recent file by timestamp." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:115(title) +msgid "Configuring and Tuning OpenStack Object Storage" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:116(para) +msgid "This section walks through deployment options and considerations." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:118(para) +msgid "You have multiple deployment options to choose from. The swift services run completely autonomously, which provides for a lot of flexibility when designing the hardware deployment for swift. The 4 main services are:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:122(para) +msgid "Proxy Services" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:123(para) +msgid "Object Services" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:124(para) +msgid "Container Services" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:125(para) +msgid "Account Services" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:128(para) +msgid "The Proxy Services are more CPU and network I/O intensive. If you are using 10g networking to the proxy, or are terminating SSL traffic at the proxy, greater CPU power will be required." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:131(para) +msgid "The Object, Container, and Account Services (Storage Services) are more disk and network I/O intensive." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:133(para) +msgid "The easiest deployment is to install all services on each server. There is nothing wrong with doing this, as it scales each service out horizontally." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:135(para) +msgid "At Rackspace, we put the Proxy Services on their own servers and all of the Storage Services on the same server. This allows us to send 10g networking to the proxy and 1g to the storage servers, and keep load balancing to the proxies more manageable. Storage Services scale out horizontally as storage servers are added, and we can scale overall API throughput by adding more Proxies." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:141(para) +msgid "If you need more throughput to either Account or Container Services, they may each be deployed to their own servers. For example you might use faster (but more expensive) SAS or even SSD drives to get faster disk I/O to the databases." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:144(para) +msgid "Load balancing and network design is left as an exercise to the reader, but this is a very important part of the cluster, so time should be spent designing the network for a Swift cluster." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:150(title) +msgid "Preparing the Ring" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:151(title) +msgid "Note" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:151(para) +msgid "\"Partition\" in this section refers to the logical partitions of the swift ring - not physical partitions on Storage node drives. You should setup your Storage Node disk partitions with one physical partition per disk, as per the installation instructions ." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:157(para) +msgid "The first step is to determine the number of partitions that will be in the ring. We recommend that there be a minimum of 100 partitions per drive to insure even distribution across the drives. A good starting point might be to figure out the maximum number of drives the cluster will contain, and then multiply by 100, and then round up to the nearest power of two." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:162(para) +msgid "For example, imagine we are building a cluster that will have no more than 5,000 drives. That would mean that we would have a total number of 500,000 partitions, which is pretty close to 2^19, rounded up." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:165(para) +msgid "It is also a good idea to keep the number of partitions small (relatively). The more partitions there are, the more work that has to be done by the replicators and other backend jobs and the more memory the rings consume in process. The goal is to find a good balance between small rings and maximum cluster size." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:170(para) +msgid "The next step is to determine the number of replicas to store of the data. Currently it is recommended to use 3 (as this is the only value that has been tested). The higher the number, the more storage that is used but the less likely you are to lose data." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:175(para) +msgid "It is also important to determine how many zones the cluster should have. It is recommended to start with a minimum of 5 zones. You can start with fewer, but our testing has shown that having at least five zones is optimal when failures occur. We also recommend trying to configure the zones at as high a level as possible to create as much isolation as possible. Some example things to take into consideration can include physical location, power availability, and network connectivity. For example, in a small cluster you might decide to split the zones up by cabinet, with each cabinet having its own power and network connectivity. The zone concept is very abstract, so feel free to use it in whatever way best isolates your data from failure. Zones are referenced by number, beginning with 1." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:186(para) +msgid "You can now start building the ring with:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:189(para) +msgid "This will start the ring build process creating the <builder_file> with 2^<part_power> partitions. <min_part_hours> is the time in hours before a specific partition can be moved in succession (24 is a good value for this)." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:193(para) +msgid "Devices can be added to the ring with:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:197(para) +msgid "This will add a device to the ring where <builder_file> is the name of the builder file that was created previously, <zone> is the number of the zone this device is in, <ip> is the ip address of the server the device is in, <port> is the port number that the server is running on, <device_name> is the name of the device on the server (for example: sdb1), <meta> is a string of metadata for the device (optional), and <weight> is a float weight that determines how many partitions are put on the device relative to the rest of the devices in the cluster (a good starting point is 100.0 x TB on the drive). Add each device that will be initially in the cluster." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:207(para) +msgid "Once all of the devices are added to the ring, run:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:210(para) +msgid "This will distribute the partitions across the drives in the ring. It is important whenever making changes to the ring to make all the changes required before running rebalance. This will ensure that the ring stays as balanced as possible, and as few partitions are moved as possible." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:214(para) +msgid "The above process should be done to make a ring for each storage service (Account, Container and Object). The builder files will be needed in future changes to the ring, so it is very important that these be kept and backed up. The resulting .tar.gz ring file should be pushed to all of the servers in the cluster. For more information about building rings, running swift-ring-builder with no options will display help text with available commands and options." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:224(title) +msgid "Considerations and Tuning" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:224(para) +msgid "Fine-tuning your deployment and installation may take some time and effort. Here are some considerations for improving performance of an OpenStack Object Storage installation." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:226(title) +msgid "Memcached Considerations" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:228(para) +msgid "Several of the Services rely on Memcached for caching certain types of lookups, such as auth tokens, and container/account existence. Swift does not do any caching of actual object data. Memcached should be able to run on any servers that have available RAM and CPU. At Rackspace, we run Memcached on the proxy servers. The memcache_servers config option in the proxy-server.conf should contain all memcached servers." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:236(title) +msgid "System Time" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:237(para) +msgid "Time may be relative but it is relatively important for Swift! Swift uses timestamps to determine which is the most recent version of an object. It is very important for the system time on each server in the cluster to by synced as closely as possible (more so for the proxy server, but in general it is a good idea for all the servers). At Rackspace, we use NTP with a local NTP server to ensure that the system times are as close as possible. This should also be monitored to ensure that the times do not vary too much." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:247(title) +msgid "General Service Tuning" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:248(para) +msgid "Most services support either a worker or concurrency value in the settings. This allows the services to make effective use of the cores available. A good starting point to set the concurrency level for the proxy and storage services to 2 times the number of cores available. If more than one service is sharing a server, then some experimentation may be needed to find the best balance." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:254(para) +msgid "At Rackspace, our Proxy servers have dual quad core processors, giving us 8 cores. Our testing has shown 16 workers to be a pretty good balance when saturating a 10g network and gives good CPU utilization." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:257(para) +msgid "Our Storage servers all run together on the same servers. These servers have dual quad core processors, for 8 cores total. We run the Account, Container, and Object servers with 8 workers each. Most of the background jobs are run at a concurrency of 1, with the exception of the replicators which are run at a concurrency of 2." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:262(para) +msgid "The above configuration setting should be taken as suggestions and testing of configuration settings should be done to ensure best utilization of CPU, network connectivity, and disk I/O." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:267(title) +msgid "RAID Considerations" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:268(para) +msgid "We recommend that you do not use RAID with Swift." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:269(para) +msgid "The workload for Swift is very write-heavy, with small random IO accesses. This type of workload performs very poorly for most parity RAID (e.g., RAID 2-6). Testing done by Rackspace suggests that under heavy workloads, the overall RAID performance can degrade to be as slow as a single drive." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:273(para) +msgid "Furthermore, a drive failure in a RAID array can result in very poor performance on the node until the RAID rebuilds, which can take a long time. Testing at Rackspace, using nodes with 24 2T drives, revealed that a RAID rebuild after a drive failure could take on the order of two weeks, during which time the node performance suffered dramatically as the RAID array functioned in a degraded state. This kind of significantly degraded performance can potentially have ripple effects across the rest of the cluster." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:282(title) +msgid "Filesystem Considerations" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:283(para) +msgid "Swift is designed to be mostly filesystem agnostic–the only requirement being that the filesystem supports extended attributes (xattrs). After thorough testing with our use cases and hardware configurations, XFS was the best all-around choice. If you decide to use a filesystem other than XFS, we highly recommend thorough testing." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:289(para) +msgid "If you are using XFS, some settings that can dramatically impact performance. We recommend the following when creating the XFS partition:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:292(code) +msgid "mkfs.xfs -i size=1024 -f /dev/sda1" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:294(para) +msgid "Setting the inode size is important, as XFS stores xattr data in the inode. If the metadata is too large to fit in the inode, a new extent is created, which can cause quite a performance problem. Upping the inode size to 1024 bytes provides enough room to write the default metadata, plus a little headroom. We do not recommend running Swift on RAID, but if you are using RAID it is also important to make sure that the proper sunit and swidth settings get set so that XFS can make most efficient use of the RAID array." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:301(para) +msgid "We also recommend the following example mount options when using XFS:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:302(code) +msgid "mount -t xfs -o noatime,nodiratime,nobarrier,logbufs=8 /dev/sda1 /srv/node/sda" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:304(para) +msgid "For a standard swift install, all data drives are mounted directly under /srv/node (as can be seen in the above example of mounting /dev/sda1 as /srv/node/sda). If you choose to mount the drives in another directory, be sure to set the devices config option in all of the server configs to point to the correct directory." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:312(title) +msgid "General System Tuning" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:313(para) +msgid "Rackspace currently runs Swift on Ubuntu Server 10.04, and the following changes have been found to be useful for our use cases." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:315(para) +msgid "The following settings should be in /etc/sysctl.conf:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:330(para) +msgid "To load the updated sysctl settings, run sudo sysctl -p " +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:331(para) +msgid "A note about changing the TIME_WAIT values. By default the OS will hold a port open for 60 seconds to ensure that any remaining packets can be received. During high usage, and with the number of connections that are created, it is easy to run out of ports. We can change this since we are in control of the network. If you are not in control of the network, or do not expect high loads, then you may not want to adjust those values." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:337(para) +msgid "Another helpful tuning parameter on slower systems that helps to ensure enough time is allowed for service restarts is the -k N (or --kill-wait N ) parameter of . This allows you to change the default (15 second) time (N, in seconds) that swift waits for processes to die and notably you can pass flag with to set where PID's will be stored." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:347(title) +msgid "Logging Considerations" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:348(para) +msgid "Swift is set up to log directly to syslog. Every service can be configured with the log_facility option to set the syslog log facility destination. We recommend using syslog-ng to route the logs to specific log files locally on the server and also to remote log collecting servers." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:355(title) +msgid "Working with Rings" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:356(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:361(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:368(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:375(title) +msgid "Managing Rings with the Ring Builder" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:376(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, pickled 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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:384(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:395(title) +msgid "About the Ring Data Structure" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:396(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:401(title) +msgid "List of Devices in the Ring" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:403(para) +msgid "The list of devices is known internally to the Ring class as devs. Each item in the list of devices is a dictionary with the following keys:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:406(caption) +msgid "List of Devices and Keys" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:409(td) +msgid "Key" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:410(td) +msgid "Type" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:411(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:846(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:953(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:988(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1044(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1144(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1182(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1212(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1372(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:25(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:141(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:234(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:341(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:392(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:449(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:505(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:615(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:669(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:739(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:795(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:832(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:873(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:961(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1002(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1085(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1122(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1179(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1234(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1327(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1398(td) +msgid "Description" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:413(td) +msgid "id" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:414(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:419(td) +msgid "integer" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:415(td) +msgid "The index into the list devices." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:417(td) +msgid "zone" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:420(td) +msgid "The zone the devices resides in." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:422(td) +msgid "weight" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:423(td) +msgid "float" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:424(td) +msgid "The relative weight of the device in comparison to other devices. This usually corresponds directly to the amount of disk space the device has compared to other devices. For instance a device with 1 terabyte of space might have a weight of 100.0 and another device with 2 terabytes of space might have a weight of 200.0. This weight can also be used to bring back into balance a device that has ended up with more or less data than desired over time. A good average weight of 100.0 allows flexibility in lowering the weight later if necessary." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:434(td) +msgid "ip" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:435(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:445(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:451(td) +msgid "string" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:436(td) +msgid "The IP address of the server containing the device." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:439(td) +msgid "port" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:440(td) +msgid "int" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:441(td) +msgid "The TCP port the listening server process uses that serves requests for the device." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:446(td) +msgid "The on disk name of the device on the server. For example: sdb1" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:449(td) +msgid "meta" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:452(td) +msgid "A general-use field for storing additional information for the device. This information isn't used directly by the server processes, but can be useful in debugging. For example, the date and time of installation and hardware manufacturer could be stored here." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:460(para) +msgid "Note: The list of devices may contain holes, or indexes set to None, for devices that have been removed from the cluster. Generally, device ids are not reused. Also, some devices may be temporarily disabled by setting their weight to 0.0." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:468(title) +msgid "Partition Assignment List" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:469(para) +msgid "This is a list of array(‘I') of devices ids. The outermost list contains an array(‘I') for each replica. Each array(‘I') has a length equal to the partition count for the ring. Each integer in the array(‘I') is an index into the above list of devices. The partition list is known internally to the Ring class as _replica2part2dev_id." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:475(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:477(para) +msgid "array(‘I') is used for memory conservation as there may be millions of partitions." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:482(title) +msgid "Partition Shift Value" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:483(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:491(title) +msgid "Building the Ring" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:492(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, if the 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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:498(para) +msgid "Then, the ring builder assigns each partition's replica to the device that desires the most partitions at that point, with the restriction that the device is not in the same zone as any other replica for that partition. Once assigned, the device's desired partition count is decremented and moved to its new sorted location in the list of devices and the process continues." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:503(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 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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:510(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:518(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:526(title) +msgid "History of the Ring Design" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:527(para) +msgid "The ring code went through many iterations before arriving at what it is now and while it has been stable for a while now, the algorithm may be tweaked or perhaps even fundamentally changed if new ideas emerge. This section will try to describe the previous ideas attempted and attempt to explain why they were discarded." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:532(para) +msgid "A “live ring” option was considered where each server could maintain its own copy of the ring and the servers would use a gossip protocol to communicate the changes they made. This was discarded as too complex and error prone to code correctly in the project time span available. One bug could easily gossip bad data out to the entire cluster and be difficult to recover from. Having an externally managed ring simplifies the process, allows full validation of data before it's shipped out to the servers, and guarantees each server is using a ring from the same timeline. It also means that the servers themselves aren't spending a lot of resources maintaining rings." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:542(para) +msgid "A couple of “ring server” options were considered. One was where all ring lookups would be done by calling a service on a separate server or set of servers, but this was discarded due to the latency involved. Another was much like the current process but where servers could submit change requests to the ring server to have a new ring built and shipped back out to the servers. This was discarded due to project time constraints and because ring changes are currently infrequent enough that manual control was sufficient. However, lack of quick automatic ring changes did mean that other parts of the system had to be coded to handle devices being unavailable for a period of hours until someone could manually update the ring." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:552(para) +msgid "The current ring process has each replica of a partition independently assigned to a device. A version of the ring that used a third of the memory was tried, where the first replica of a partition was directly assigned and the other two were determined by “walking” the ring until finding additional devices in other zones. This was discarded as control was lost as to how many replicas for a given partition moved at once. Keeping each replica independent allows for moving only one partition replica within a given time window (except due to device failures). Using the additional memory was deemed a good tradeoff for moving data around the cluster much less often." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:561(para) +msgid "Another ring design was tried where the partition to device assignments weren't stored in a big list in memory but instead each device was assigned a set of hashes, or anchors. The partition would be determined from the data item's hash and the nearest device anchors would determine where the replicas should be stored. However, to get reasonable distribution of data each device had to have a lot of anchors and walking through those anchors to find replicas started to add up. In the end, the memory savings wasn't that great and more processing power was used, so the idea was discarded." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:569(para) +msgid "A completely non-partitioned ring was also tried but discarded as the partitioning helps many other parts of the system, especially replication. Replication can be attempted and retried in a partition batch with the other replicas rather than each data item independently attempted and retried. Hashes of directory structures can be calculated and compared with other replicas to reduce directory walking and network traffic." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:576(para) +msgid "Partitioning and independently assigning partition replicas also allowed for the best balanced cluster. The best of the other strategies tended to give +-10% variance on device balance with devices of equal weight and +-15% with devices of varying weights. The current strategy allows us to get +-3% and +-8% respectively." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:581(para) +msgid "Various hashing algorithms were tried. SHA offers better security, but the ring doesn't need to be cryptographically secure and SHA is slower. Murmur was much faster, but MD5 was built-in and hash computation is a small percentage of the overall request handling time. In all, once it was decided the servers wouldn't be maintaining the rings themselves anyway and only doing hash lookups, MD5 was chosen for its general availability, good distribution, and adequate speed." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:590(title) +msgid "The Account Reaper" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:591(para) +msgid "The Account Reaper removes data from deleted accounts in the background." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:592(para) +msgid "An account is marked for deletion by a reseller through the services server's remove_storage_account XMLRPC call. 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. There is no set retention time and no undelete; it is assumed the reseller will implement such features and only call remove_storage_account once it is truly desired the account's data be removed." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:600(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:607(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:618(title) +msgid "Account Reaper Background and History" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:619(para) +msgid "At first, a simple approach of deleting an account through completely external calls was considered as it required no changes to the system. All data would simply be deleted in the same way the actual user would, through the public REST API. However, the downside was that it would use proxy resources and log everything when it didn't really need to. Also, it would likely need a dedicated server or two, just for issuing the delete requests." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:626(para) +msgid "A completely bottom-up approach was also considered, where the object and container servers would occasionally scan the data they held and check if the account was deleted, removing the data if so. The upside was the speed of reclamation with no impact on the proxies or logging, but the downside was that nearly 100% of the scanning would result in no action creating a lot of I/O load for no reason." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:632(para) +msgid "A more container server centric approach was also considered, where the account server would mark all the containers for deletion and the container servers would delete the objects in each container and then themselves. This has the benefit of still speedy reclamation for accounts with a lot of containers, but has the downside of a pretty big load spike. The process could be slowed down to alleviate the load spike possibility, but then the benefit of speedy reclamation is lost and what's left is just a more complex process. Also, scanning all the containers for those marked for deletion when the majority wouldn't be seemed wasteful. The db_replicator could do this work while performing its replication scan, but it would have to spawn and track deletion processes which seemed needlessly complex." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:643(para) +msgid "In the end, an account server centric approach seemed best, as described above." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:650(para) +msgid "Since each replica in OpenStack Object Storage 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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:651(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:653(para) +msgid "Every deleted record or file in the system is marked by a tombstone, so that deletions can be replicated alongside creations. These tombstones are cleaned up by the replication process after a period of time referred to as the consistency window, which is related to replication duration and how long transient failures can remove a node from the cluster. Tombstone cleanup must be tied to replication to reach replica convergence." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:654(para) +msgid "If a replicator detects that a remote drive has failed, it will use the ring's “get_more_nodes” interface to choose an alternate node to synchronize with. The replicator can generally maintain desired levels of replication in the face of hardware failures, though some replicas may not be in an immediately usable location." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:655(para) +msgid "Replication is an area of active development, and likely rife with potential improvements to speed and correctness." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:656(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:658(title) +msgid "Database Replication" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:659(para) +msgid "The first step performed by db replication is a low-cost hash comparison to find out whether or not 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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:661(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 knows it's now in sync with everyone the local database has previously synchronized with." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:662(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:663(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:666(title) +msgid "Object Replication" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:667(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:668(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:669(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:675(title) +msgid "Managing Large Objects (Greater than 5 GB)" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:676(para) +msgid "OpenStack Object Storage has a limit on the size of a single uploaded object; by default this is 5GB. However, the download size of a single object is virtually unlimited with the concept of segmentation. Segments of the larger object are uploaded and a special manifest file is created that, when downloaded, sends all the segments concatenated as a single object. This also offers much greater upload speed with the possibility of parallel uploads of the segments." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:683(title) +msgid "Using swift to Manage Segmented Objects" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:685(para) +msgid "The quickest way to try out this feature is use the included swift OpenStack Object Storage client tool. You can use the -S option to specify the segment size to use when splitting a large file. For example:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:690(para) +msgid "This would split the large_file into 1G segments and begin uploading those segments in parallel. Once all the segments have been uploaded, swift will then create the manifest file so the segments can be downloaded as one." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:693(para) +msgid "So now, the following st command would download the entire large object:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:697(para) +msgid "The swift CLI uses a strict convention for its segmented object support. In the above example it will upload all the segments into a second container named test_container_segments. These segments will have names like large_file/1290206778.25/21474836480/00000000, large_file/1290206778.25/21474836480/00000001, etc." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:702(para) +msgid "The main benefit for using a separate container is that the main container listings will not be polluted with all the segment names. The reason for using the segment name format of <name>/<timestamp>/<size>/<segment> is so that an upload of a new file with the same name won't overwrite the contents of the first until the last moment when the manifest file is updated." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:708(para) +msgid "The swift CLI will manage these segment files for you, deleting old segments on deletes and overwrites, etc. You can override this behavior with the --leave-segments option if desired; this is useful if you want to have multiple versions of the same large object available." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:714(title) +msgid "Direct API Management of Large Objects" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:715(para) +msgid "You can also work with the segments and manifests directly with HTTP requests instead of having swift do that for you. You can just upload the segments like you would any other object and the manifest is just a zero-byte file with an extra X-Object-Manifest header." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:720(para) +msgid "All the object segments need to be in the same container, have a common object name prefix, and their names sort in the order they should be concatenated. They don't have to be in the same container as the manifest file will be, which is useful to keep container listings clean as explained above with st." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:724(para) +msgid "The manifest file is simply a zero-byte file with the extra X-Object-Manifest:<container>/<prefix> header, where <container> is the container the object segments are in and <prefix> is the common prefix for all the segments." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:729(para) +msgid "It is best to upload all the segments first and then create or update the manifest. In this way, the full object won't be available for downloading until the upload is complete. Also, you can upload a new set of segments to a second location and then update the manifest to point to this new location. During the upload of the new segments, the original manifest will still be available to download the first set of segments." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:735(para) +msgid "Here's an example using curl with tiny 1-byte segments:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:736(para) +msgid "# First, upload the segments # Next, create the manifest file curl -X PUT -H 'X-Auth-Token: <token>' \\ -H 'X-Object-Manifest: container/myobject/' \\ http://<storage_url>/container/myobject --data-binary '' # And now we can download the segments as a single object curl -H 'X-Auth-Token: <token>' \\ http://<storage_url>/container/myobject" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:750(title) +msgid "Additional Notes on Large Objects" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:752(para) +msgid "With a GET or HEAD of a manifest file, the X-Object-Manifest: <container>/<prefix> header will be returned with the concatenated object so you can tell where it's getting its segments from." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:756(para) +msgid "The response's Content-Length for a GET or HEAD on the manifest file will be the sum of all the segments in the <container>/<prefix> listing, dynamically. So, uploading additional segments after the manifest is created will cause the concatenated object to be that much larger; there's no need to recreate the manifest file." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:762(para) +msgid "The response's Content-Type for a GET or HEAD on the manifest will be the same as the Content-Type set during the PUT request that created the manifest. You can easily change the Content-Type by reissuing the PUT." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:767(para) +msgid "The response's ETag for a GET or HEAD on the manifest file will be the MD5 sum of the concatenated string of ETags for each of the segments in the <container>/<prefix> listing, dynamically. Usually in OpenStack Object Storage the ETag is the MD5 sum of the contents of the object, and that holds true for each segment independently. But, it's not feasible to generate such an ETag for the manifest itself, so this method was chosen to at least offer change detection." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:777(title) +msgid "Large Object Storage History and Background" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:778(para) +msgid "Large object support has gone through various iterations before settling on this implementation." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:780(para) +msgid "The primary factor driving the limitation of object size in OpenStack Object Storage is maintaining balance among the partitions of the ring. To maintain an even dispersion of disk usage throughout the cluster the obvious storage pattern was to simply split larger objects into smaller segments, which could then be glued together during a read." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:785(para) +msgid "Before the introduction of large object support some applications were already splitting their uploads into segments and re-assembling them on the client side after retrieving the individual pieces. This design allowed the client to support backup and archiving of large data sets, but was also frequently employed to improve performance or reduce errors due to network interruption. The major disadvantage of this method is that knowledge of the original partitioning scheme is required to properly reassemble the object, which is not practical for some use cases, such as CDN origination." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:793(para) +msgid "In order to eliminate any barrier to entry for clients wanting to store objects larger than 5GB, initially we also prototyped fully transparent support for large object uploads. A fully transparent implementation would support a larger max size by automatically splitting objects into segments during upload within the proxy without any changes to the client API. All segments were completely hidden from the client API." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:799(para) +msgid "This solution introduced a number of challenging failure conditions into the cluster, wouldn't provide the client with any option to do parallel uploads, and had no basis for a resume feature. The transparent implementation was deemed just too complex for the benefit." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:804(para) +msgid "The current “user manifest” design was chosen in order to provide a transparent download of large objects to the client and still provide the uploading client a clean API to support segmented uploads." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:807(para) +msgid "Alternative “explicit” user manifest options were discussed which would have required a pre-defined format for listing the segments to “finalize” the segmented upload. While this may offer some potential advantages, it was decided that pushing an added burden onto the client which could potentially limit adoption should be avoided in favor of a simpler “API” (essentially just the format of the ‘X-Object-Manifest' header)." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:814(para) +msgid "During development it was noted that this “implicit” user manifest approach which is based on the path prefix can be potentially affected by the eventual consistency window of the container listings, which could theoretically cause a GET on the manifest object to return an invalid whole object for that short term. In reality you're unlikely to encounter this scenario unless you're running very high concurrency uploads against a small testing environment which isn't running the object-updaters or container-replicators." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:821(para) +msgid "Like all of OpenStack Object Storage, Large Object Support is living feature which will continue to improve and may change over time." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:828(title) +msgid "Throttling Resources by Setting Rate Limits" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:830(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 dbs. 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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:837(title) +msgid "Configuration for Rate Limiting" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:838(para) +msgid "All configuration is optional. If no account or container limits are provided there will be no rate limiting. Configuration available:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:841(caption) +msgid "Configuration options for rate limiting in proxy-server.conf file" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:844(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:951(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:986(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1042(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1142(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1180(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1210(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1370(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:23(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:139(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:232(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:339(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:390(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:447(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:503(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:613(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:667(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:737(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:793(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:830(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:871(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:959(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1000(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1083(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1120(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1177(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1232(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1325(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1396(td) +msgid "Option" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:845(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:952(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:987(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1043(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1143(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1181(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1211(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1371(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:24(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:140(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:233(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:340(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:391(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:448(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:504(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:614(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:668(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:738(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:794(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:831(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:872(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:960(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1001(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1084(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1121(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1178(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1233(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1326(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1397(td) +msgid "Default" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:849(td) +msgid "clock_accuracy" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:850(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:926(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:688(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1021(td) +msgid "1000" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:851(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:858(td) +msgid "max_sleep_time_seconds" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:859(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:276(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:783(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:851(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1068(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1264(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1269(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1294(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1304(td) +msgid "60" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:860(td) +msgid "App will immediately return a 498 response if the necessary sleep time ever exceeds the given max_sleep_time_seconds." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:865(td) +msgid "log_sleep_time_seconds" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:866(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:872(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:117(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:203(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:565(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:938(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1126(td) +msgid "0" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:867(td) +msgid "To allow visibility into rate limiting set this value > 0 and all sleeps greater than the number will be logged." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:871(td) +msgid "account_ratelimit" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:873(td) +msgid "If set, will limit all requests to /account_name and PUTs to /account_name/container_name. Number is in requests per second" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:879(td) +msgid "account_whitelist" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:880(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:885(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:890(td) +msgid "‘'" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:881(td) +msgid "Comma separated lists of account names that will not be rate limited." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:884(td) +msgid "account_blacklist" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:886(td) +msgid "Comma separated lists of account names that will not be allowed. Returns a 497 response." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:889(td) +msgid "container_ratelimit_size" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:891(td) +msgid "When set with container_limit_x = r: for containers of size x, limit requests per second to r. Will limit GET and HEAD requests to /account_name/container_name and PUTs and DELETEs to /account_name/container_name/object_name" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:901(para) +msgid "The container rate limits are linearly interpolated from the values given. A sample container rate limiting could be:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:903(para) +msgid "container_ratelimit_100 = 100" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:904(para) +msgid "container_ratelimit_200 = 50" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:905(para) +msgid "container_ratelimit_500 = 20" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:906(para) +msgid "This would result in" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:908(caption) +msgid "Values for Rate Limiting with Sample Configuration Settings" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:910(td) +msgid "Container Size" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:911(td) +msgid "Rate Limit" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:913(td) +msgid "0-99" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:914(td) +msgid "No limiting" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:916(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:917(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:723(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1026(td) +msgid "100" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:920(td) +msgid "150" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:921(td) +msgid "75" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:923(td) +msgid "500" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:924(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:927(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:416(td) +msgid "20" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:936(title) +msgid "Additional Features" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:937(para) +msgid "This section aims to detail a number of additional features in Swift and their configuration." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:941(title) +msgid "Health Check" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:942(para) +msgid "Health Check provides a simple way to monitor if the swift proxy server is alive. If the proxy is access with the path /healthcheck, it will respond with “OK” in the body, which can be used by monitoring tools." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:948(caption) +msgid "Configuration options for filter:healthcheck in proxy-server.conf file" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:957(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:992(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1048(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:78(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:151(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:237(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:344(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:395(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:467(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:581(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:625(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:672(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:742(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:798(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:835(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:970(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1005(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1088(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1131(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1243(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1337(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1401(td) +msgid "log_name" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:958(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:993(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1049(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:79(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:94(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:172(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:545(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:582(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:913(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1208(td) +msgid "swift" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:959(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:994(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1050(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:80(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:153(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:239(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:346(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:397(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:583(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:627(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:674(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:744(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:800(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:837(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:972(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1007(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1090(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1133(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1245(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1339(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1403(td) +msgid "Label used when logging" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:962(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:997(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1053(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:83(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:156(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:242(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:349(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:400(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:457(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:586(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:630(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:677(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:747(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:803(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:840(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:975(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1010(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1093(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1136(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1248(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1342(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1406(td) +msgid "log_facility" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:963(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:998(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1054(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:84(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:157(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:243(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:350(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:401(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:458(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:483(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:587(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:631(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:678(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:748(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:804(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:841(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:976(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1011(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1094(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1137(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1249(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1343(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1407(td) +msgid "LOG_LOCAL0" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:964(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:999(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1055(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:85(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:158(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:244(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:351(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:402(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:588(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:632(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:679(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:749(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:805(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:842(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:977(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1012(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1095(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1138(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1250(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1344(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1408(td) +msgid "Syslog log facility" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:967(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1002(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1058(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:88(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:161(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:247(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:354(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:405(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:462(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:591(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:635(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:682(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:752(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:808(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:845(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:980(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1015(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1098(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1141(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1253(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1347(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1411(td) +msgid "log_level" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:968(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1003(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1059(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:89(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:162(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:248(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:355(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:406(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:463(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:592(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:636(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:683(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:753(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:809(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:846(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:981(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1016(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1099(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1142(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1254(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1348(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1412(td) +msgid "INFO" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:969(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1004(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1060(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:90(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:163(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:249(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:356(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:407(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:593(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:637(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:684(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:754(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:810(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:847(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:982(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1017(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1100(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1143(td) +msgid "Logging level" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:977(title) +msgid "Domain Remap" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:978(para) +msgid "Domain Remap is middleware that translates container and account parts of a domain to path parameters that the proxy server understands." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:983(caption) +msgid "Configuration options for filter:domain_remap in proxy-server.conf file" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1007(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1063(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:472(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1258(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1352(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1416(td) +msgid "log_headers" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1008(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1064(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1417(td) +msgid "False" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1009(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1065(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1260(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1354(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1418(td) +msgid "If True, log headers in each request" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1012(td) +msgid "path_root" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1013(td) +msgid "v1" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1014(td) +msgid "Root path" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1017(td) +msgid "reseller_prefixes" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1018(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1358(td) +msgid "AUTH" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1019(td) +msgid "Reseller prefix" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1022(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1073(td) +msgid "storage_domain" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1023(td) +msgid "example.com" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1024(td) +msgid "Domain to use for remap" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1032(title) +msgid "CNAME Lookup" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1033(para) +msgid "CNAME Lookup is 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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1039(caption) +msgid "Configuration options for filter:cname_lookup in proxy-server.conf file" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1068(td) +msgid "lookup_depth" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1069(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1382(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:62(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:265(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:365(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:540(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:908(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1203(td) +msgid "1" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1070(td) +msgid "As CNAMEs can be recursive, how many levels to search through." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1074(td) +msgid "example.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1081(title) +msgid "Temporary URL" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1082(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 will provide GET access for a limited time to the resource. When the web browser user clicks on the link, the browser will download the object directly from Swift, obviating the need for the website to act as a proxy for the request. If the user were to share the link with all his friends, or accidentally post it on a forum, etc. the direct access would be limited to the expiration time set when the website created the link. To create such temporary URLs, first an X-Account-Meta-Temp-URL-Key header must be set on the Swift account. Then, an HMAC-SHA1 (RFC 2104) signature is generated using the HTTP method to allow (GET or PUT), the Unix timestamp the access should be allowed until, the full path to the object, and the key set on the account. For example, here is code generating the signature for a GET for 60 seconds on /v1/AUTH_account/container/object: " +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1116(para) +msgid "Be certain to use the full path, from the /v1/ onward. Let's say the sig ends up equaling da39a3ee5e6b4b0d3255bfef95601890afd80709 and expires ends up 1323479485. Then, for example, the website could provide a link to: " +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1126(para) +msgid "Any alteration of the resource path or query arguments would result in 401 Unauthorized. Similary, a PUT where GET was the allowed method would 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 changing the X-Account-Meta-Temp-URL-Key will invalidate any previously generated temporary URLs within 60 seconds (the memcache time for the key)." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1139(caption) +msgid "Configuration options for filter:tempurl in proxy-server.conf file" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1148(td) +msgid "incoming_allow_headers" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1153(td) +msgid "incoming_remove_headers" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1154(td) +msgid "x-timestamp" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1158(td) +msgid "outgoing_allow_headers" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1159(td) +msgid "x-object-meta-public-*" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1163(td) +msgid "outgoing_remove_headers" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1164(td) +msgid "x-object-meta-*" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1172(title) +msgid "Name Check Filter" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1173(para) +msgid "Name Check is a filter that disallows any paths that contain defined forbidden characters or that exceed a defined length." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1177(caption) +msgid "Configuration options for filter:name_check in proxy-server.conf file" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1186(td) +msgid "forbidden_chars" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1188(td) +msgid "Characters that are not allowed in a name" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1191(td) +msgid "max_length" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1192(td) +msgid "255" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1193(td) +msgid "Maximum length of a name" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1196(td) +msgid "forbidden_regexp" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1197(td) +msgid "\"/\\./|/\\.\\./|/\\.$|/\\.\\.$\"" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1198(td) +msgid "Substrings to forbid, using regular expression syntax" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1205(title) +msgid "Constraints" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1206(para) +msgid "The swift-constraints section in swift.conf allows modification of internal limits within swift. These are advanced features for tuning the performance of the cluster and should be altered with caution." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1208(caption) +msgid "Configuration options for swift-constraints in swift.conf" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1216(td) +msgid "max_file_size" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1217(td) +msgid "5368709122" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1218(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1226(td) +msgid "max_meta_name_length" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1227(td) +msgid "128" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1228(td) +msgid "the max number of bytes in the utf8 encoding of the name portion of a metadata header." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1232(td) +msgid "max_meta_value_lenth" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1233(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1259(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1264(td) +msgid "256" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1234(td) +msgid "the max number of bytes in the utf8 encoding of a metadata value" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1237(td) +msgid "max_meta_count" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1238(td) +msgid "90" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1239(td) +msgid "the max number of metadata keys that can be stored on a single account, container, or object" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1243(td) +msgid "max_meta_overall_size" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1244(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:67(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:603(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:918(td) +msgid "4096" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1245(td) +msgid "the max number of bytes in the utf8 encoding of the metadata (keys + values)" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1248(td) +msgid "max_object_name_length" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1249(td) +msgid "1024" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1250(td) +msgid "the max number of bytes in the utf8 encoding of an object name" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1253(td) +msgid "container_listing_limit" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1254(td) +msgid "10000" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1255(td) +msgid "the default (and max) number of items returned for a container listing request" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1258(td) +msgid "max_account_name_length" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1260(td) +msgid "the max number of bytes in the utf8 encoding of an account name" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1263(td) +msgid "max_container_name_length" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1265(td) +msgid "the max number of bytes in the utf8 encoding of a container name" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1272(title) +msgid "Cluster Health" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1273(para) +msgid "There is a swift-dispersion-report tool for measuring overall cluster health. This is accomplished by checking 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 heath 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 we make enough objects on a distinct percentage of the partitions in the cluster, we can get a pretty valid 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, we 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, we need to run the swift-dispersion-report 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 will probably do). Both swift-dispersion-populate and swift-dispersion-report use the same configuration file, /etc/swift/dispersion.conf. Example dispersion.conf file: There are also options for the conf file for specifying the dispersion coverage (defaults to 1%), retries, concurrency, etc. though usually the defaults are fine. Once the configuration is in place, run swift-dispersion-populate to populate the containers and objects throughout the cluster. Now that those containers and objects are in place, you can run swift-dispersion-report to get a dispersion report, or the overall health of the cluster. Here is an example of a cluster in perfect health: Now, deliberately double the weight of a device in the object ring (with replication turned off) and rerun the dispersion report to show what impact that has: 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 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: Alternatively, the dispersion report can also be output in json format. This allows it to be more easily consumed by third party utilities: " +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1367(caption) +msgid "Configuration options for dispersion in proxy-server.conf file" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1376(td) +msgid "auth_version" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1377(td) +msgid "1.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1378(td) +msgid "Swift authentication API version" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1381(td) +msgid "dispersion_coverage" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1386(td) +msgid "dump_json" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1387(td) +msgid "'no'" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1391(td) +msgid "retries" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1392(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:177(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:768(td) +msgid "3" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1396(td) +msgid "auth_url" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1401(td) +msgid "auth_user" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1406(td) +msgid "auth_key" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1411(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:28(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:508(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:876(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1197(td) +msgid "swift_dir" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1412(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:29(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:509(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:877(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1198(td) +msgid "/etc/swift" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1425(title) +msgid "Configuring Object Storage with the S3 API" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1426(para) +msgid "The Swift3 middleware emulates the S3 REST API on top of Object Storage." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1428(para) +msgid "The following operations are currently supported:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1431(para) +msgid "GET Service" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1432(para) +msgid "DELETE Bucket" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1433(para) +msgid "GET Bucket (List Objects)" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1434(para) +msgid "PUT Bucket" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1435(para) +msgid "DELETE Object" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1436(para) +msgid "GET Object" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1437(para) +msgid "HEAD Object" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1438(para) +msgid "PUT Object" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1439(para) +msgid "PUT Object (Copy)" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1440(para) +msgid "To use this middleware, first download the latest version from its repository to your proxy server(s)." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1443(para) +msgid "Optional: To use this middleware with Swift 1.7.0 and previous versions, you'll need to use the v1.7 tag of the fujita/swift3 repository. Clone the repo as above and then:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1446(para) +msgid "Then, install it using standard python mechanisms, such as:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1448(para) +msgid "Alternatively, if you have configured the Ubuntu Cloud Archive, you may use: " +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1450(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1454(para) +msgid "Ensure that your proxy-server.conf file contains swift3 in the pipeline and the [filter:swift3] section, as shown below:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1463(para) +msgid "Next, configure the tool that you use to connect to the S3 API. For S3curl, for example, you'll need to add your host IP information by adding y our host IP to the @endpoints array (line 33 in s3curl.pl):" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1468(para) +msgid "Now you can send commands to the endpoint, such as:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1472(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/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1490(title) +msgid "Managing OpenStack Object Storage with CLI Swift" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1490(para) +msgid "In the Object Store (swift) project there is a tool that can perform a variety of tasks on your storage cluster named swift. This client utility can be used for adhoc processing, to gather statistics, list items, update metadata, upload, download and delete files. It is based on the native swift client library client.py. Incorporating client.py into swift provides many benefits such as seamlessly re-authorizing if the current token expires in the middle of processing, retrying operations up to five times and a processing concurrency of 10. All of these things help make the swift tool robust and great for operational use." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1499(title) +msgid "Swift ACLs" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1500(para) +msgid "Swift ACLs work with users and accounts. Users have roles on accounts - such as '.admin', which allows full access to all containers and objects under the account. ACLs are set at the container level and support lists for read and write access, which are set with the X-Container-Read and X-Container-Write header respectively." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1507(para) +msgid "The swift client can be used to set the acls, using the post subcommand with the option '-r' for the read ACL, and '-w' for the write ACL. This example allows the user 'testuser' to read objects in the container: This could instead be a list of users." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1516(para) +msgid "If you are using the StaticWeb middleware to allow OpenStack Object Storage to serve public web content, you should also be aware of the ACL syntax for managing allowed referrers. The syntax is '.r:' followed by a list of allowed referrers. For example, this command allows all referring domains access to the object: " +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1529(title) +msgid "Swift CLI Basics" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1530(para) +msgid "The command line usage for swift, the CLI tool is: " +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1533(para) +msgid "Here are the available commands for swift." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1534(title) +msgid "stat [container] [object]" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1535(para) +msgid "Displays information for the account, container, or object depending on the args given (if any)." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1537(title) +msgid "list [options] [container]" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1538(para) +msgid "Lists the containers for the account or the objects for a container. -p or -prefix is an option that will only list items beginning with that prefix. -d or -delimiter is option (for container listings only) that will roll up items with the given delimiter, or character that can act as a nested directory organizer." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1543(title) +msgid "upload [options] container file_or_directory [file_or_directory] […]" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1543(para) +msgid "Uploads to the given container the files and directories specified by the remaining args. -c or -changed is an option that will only upload files that have changed since the last upload." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1546(title) +msgid "post [options] [container] [object]" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1547(para) +msgid "Updates meta information for the account, container, or object depending on the args given. If the container is not found, it will be created automatically; but this is not true for accounts and objects. Containers also allow the -r (or -read-acl) and -w (or -write-acl) options. The -m or -meta option is allowed on all and used to define the user meta data items to set in the form Name:Value. This option can be repeated." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1553(para) +msgid "Example: post -m Color:Blue -m Size:Large" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1554(title) +msgid "download —all OR download container [object] [object] …" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1555(para) +msgid "Downloads everything in the account (with —all), or everything in a container, or a list of objects depending on the args given. For a single object download, you may use the -o [—output] (filename) option to redirect the output to a specific file or if “-” then just redirect to stdout." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1560(title) +msgid "delete —all OR delete container [object] [object] …" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1561(para) +msgid "Deletes everything in the account (with —all), or everything in a container, or a list of objects depending on the args given." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1564(para) +msgid "Example: swift -A https://auth.api.rackspacecloud.com/v1.0 -U user -K key stat" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1566(title) +msgid "Options for swift" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1567(para) +msgid "-version show program’s version number and exit" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1568(para) +msgid "-h, -help show this help message and exit" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1569(para) +msgid "-s, -snet Use SERVICENET internal network" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1570(para) +msgid "-v, -verbose Print more info" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1571(para) +msgid "-q, -quiet Suppress status output" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1572(para) +msgid "-A AUTH, -auth=AUTH URL for obtaining an auth token" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1573(para) +msgid "-U USER, -user=USER User name for obtaining an auth token" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1574(para) +msgid "-K KEY, -key=KEY Key for obtaining an auth token" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1576(title) +msgid "Analyzing Log Files with Swift CLI" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1577(para) +msgid "When you want quick, command-line answers to questions about logs, you can use swift with the -o or -output option. The -o —output option can only be used with a single object download to redirect the data stream to either a different file name or to STDOUT (-). The ability to redirect the output to STDOUT allows you to pipe “|” data without saving it to disk first. One common use case is being able to do some quick log file analysis. First let’s use swift to setup some data for the examples. The “logtest” directory contains four log files with the following line format." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1597(para) +msgid "The swift tool can easily upload the four log files into a container named “logtest”:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1599(para) +msgid " Get statistics on the account: Get statistics on the container: List all the objects in the container: " +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1633(para) +msgid "These next three examples use the -o —output option with (-) to help answer questions about the uploaded log files. The swift command will download an object, stream it to awk to determine the breakdown of requests by return code for everything during 2200 on November 16th, 2010. Based on the log line format column 9 is the type of request and column 12 is the return code. After awk processes the data stream it is piped to sort and then uniq -c to sum up the number of occurrences for each combination of request type and return code." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1677(para) +msgid "This example uses a bash for loop with awk, swift with its -o —output option with a hyphen (-) to find out how many PUT requests are in each log file. First create a list of objects by running swift with the list command on the “logtest” container; then for each item in the list run swift with download -o - then pipe the output into grep to filter the put requests and finally into wc -l to count the lines." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1695(para) +msgid "By adding the -p —prefix option a prefix query is performed on the list to return only the object names that begin with a specific string. Let’s determine out how many PUT requests are in each object with a name beginning with “2010-11-15”. First create a list of objects by running swift with the list command on the “logtest” container with the prefix option -p 2010-11-15. Then on each of item(s) returned run swift with the download -o - then pipe the output to grep and wc as in the previous example. The echo command is added to display the object name." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml:1711(para) +msgid "The swift utility is simple, scalable, flexible and provides useful solutions all of which are core principles of cloud computing; with the -o output option being just one of its many features." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:5(title) +msgid "OpenStack Object Storage Monitoring" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:7(para) +msgid "Excerpted from a blog post by Darrell Bishop" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:10(para) +msgid "An OpenStack Object Storage cluster is a complicated beast—a collection of many daemons across many nodes, all working together. With so many “moving parts” it’s important to be able to tell what’s going on inside the cluster. Tracking server-level metrics like CPU utilization, load, memory consumption, disk usage and utilization, etc. is necessary, but not sufficient. We need to know what the different daemons are doing on each server. What’s the volume of object replication on node8? How long is it taking? Are there errors? If so, when did they happen?" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:20(para) +msgid "In such a complex ecosystem, it’s no surprise that there are multiple approaches to getting the answers to these kinds of questions. Let’s examine some of the existing approaches to OpenStack Object Storage monitoring." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:25(title) +msgid "Swift Recon" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:26(para) +msgid "The Swift Recon middleware can provide general machine stats (load average, socket stats, /proc/meminfo contents, etc.) as well as Swift-specific metrics:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:34(para) +msgid "The MD5 sum of each ring file." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:37(para) +msgid "The most recent object replication time." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:40(para) +msgid "Count of each type of quarantined file: account, container, or object." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:44(para) +msgid "Count of “async_pendings” (deferred container updates) on disk." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:48(para) +msgid "Swift Recon is middleware installed in the object server’s pipeline and takes one required option: a local cache directory. Tracking of async_pendings requires an additional cron job per object server. Data is then accessed by sending HTTP requests to the object server directly, or by using the swift-recon command-line tool." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:55(para) +msgid "There are some good Object Storage cluster stats in there, but the general server metrics overlap with existing server monitoring systems and to get the Swift-specific metrics into a monitoring system, they must be polled. Swift Recon is essentially acting as a middle-man metrics collector. The process actually feeding metrics to your stats system, like collectd, gmond, etc., is probably already running on the storage node. So it could either talk to Swift Recon or just collect the metrics itself." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:65(para) +msgid "There’s an upcoming update to Swift Recon which broadens support to the account and container servers. The auditors, replicators, and updaters can also report statistics, but only for the most recent run." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:73(title) +msgid "Swift-Informant" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:74(para) +msgid "Florian Hines developed the Swift-Informant middleware to get real-time visibility into Object Storage client requests. It sits in the proxy server’s pipeline and after each request to the proxy server, sends three metrics to a StatsD server:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:83(para) +msgid "A counter increment for a metric like obj.GET.200 or cont.PUT.404." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:85(para) +msgid "Timing data for a metric like acct.GET.200 or obj.GET.200. [The README says the metrics will look like duration.acct.GET.200, but I don’t see the “duration” in the code. I’m not sure what Etsy’s server does, but our StatsD server turns timing metrics into 5 derivative metrics with new segments appended, so it probably works as coded. The first metric above would turn 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/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:91(para) +msgid "A counter increase by the bytes transferred for a metric like tfer.obj.PUT.201." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:93(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 since it is implemented as middleware. However, because of this, it gives you no insight into the workings of the cluster past the proxy server. If one storage node’s responsiveness degrades for some reason, you’ll only see that some of your requests are bad—either as high latency or error status codes. You won’t 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/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:111(title) +msgid "Statsdlog" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:112(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/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:123(para) +msgid "Currently, only the first matching regex triggers a StatsD counter increment, and the counter is always incremented by 1. There’s 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 per line and data extraction, including timing data. But even then, there would still be a coupling between the log textual format and the log parsing regexes, which would themselves be more complex in order to support multiple matches per line and data extraction. Also, log processing introduces a delay between the triggering event and sending the data to StatsD. We would prefer to increment error counters where they occur, send timing data as soon as it is known, avoid coupling between a log string and a parsing regex, and not introduce a time delay between events and sending data to StatsD. And that brings us to the next method of gathering Object Storage operational metrics." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:143(title) +msgid "Swift StatsD Logging" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:144(para) +msgid "StatsD was designed for application code to be deeply instrumented; metrics are sent in real-time by the code which just noticed something 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 will approximate the actual number when flushing metrics upstream." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:145(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 currently reports 124 metrics across 15 Object Storage daemons and the tempauth middleware. Details of the metrics tracked are in the Swift Administration Guide." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:156(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’s conceivable that some metrics may require accuracy (sample_rate == 1) while others may not." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:162(para) +msgid "Then the LogAdapter object returned by get_logger(), usually stored in self.logger, has the following new methods:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:164(para) +msgid "set_statsd_prefix(self, prefix) Sets the client library’s stat prefix value which gets prepended to every metric. The default prefix is the “name” of the logger (eg. “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/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:165(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/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:166(para) +msgid "increment(self, metric, sample_rate=1) Increments the given counter metric by one." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:167(para) +msgid "decrement(self, metric, sample_rate=1) Lowers the given counter metric by one." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:168(para) +msgid "timing(self, metric, timing_ms, sample_rate=1) Record that the given metric took the supplied number of milliseconds." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:169(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/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:171(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. Here’s two example usages of the new logging methods:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragemonitoring.xml:215(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/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:6(title) +msgid "Server Configuration Reference" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:7(para) +msgid "Swift uses paste.deploy to manage server configurations. Default configuration options are set in the [DEFAULT] section, and any options specified there can be overridden in any of the other sections." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:11(title) +msgid "Object Server Configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:12(para) +msgid "An example Object Server configuration can be found at etc/object-server.conf-sample in the source code repository." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:15(para) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:498(para) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:866(para) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1172(para) +msgid "The following configuration options are available:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:19(caption) +msgid "object-server.conf Default Options in the [DEFAULT] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:30(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:510(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:878(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1199(td) +msgid "Swift configuration directory" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:33(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:513(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:881(td) +msgid "devices" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:34(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:514(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:882(td) +msgid "/srv/node" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:35(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:515(td) +msgid "Parent directory of where devices are mounted" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:39(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:518(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:886(td) +msgid "mount_check" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:40(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:99(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:519(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:550(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:641(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:887(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:923(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:986(td) +msgid "true" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:41(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:520(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:888(td) +msgid "Whether or not check if the devices are mounted to prevent accidentally writing to the root device" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:46(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:524(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:892(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1182(td) +msgid "bind_ip" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:47(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:525(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:893(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1183(td) +msgid "0.0.0.0" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:48(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:526(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:894(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1184(td) +msgid "IP Address for server to bind to" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:51(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:529(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:897(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1187(td) +msgid "bind_port" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:52(td) +msgid "6000" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:53(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:531(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:899(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1189(td) +msgid "Port for server to bind to" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:56(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:534(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:902(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1192(td) +msgid "bind_timeout" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:57(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:259(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:316(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:535(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:698(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:718(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:903(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1038(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1063(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1193(td) +msgid "30" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:58(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:536(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:904(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1194(td) +msgid "Seconds to attempt bind before giving up" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:61(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:539(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:907(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1202(td) +msgid "workers" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:63(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:541(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:909(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1204(td) +msgid "Number of workers to fork" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:66(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:602(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:917(td) +msgid "backlog" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:68(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:604(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:919(td) +msgid "Maximum number of allowed pending TCP connections." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:72(td) +msgid "expiring_objects_container_divisor" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:73(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:198(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1376(td) +msgid "86400" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:93(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:171(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:544(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:912(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1207(td) +msgid "user" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:95(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:173(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:546(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:914(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1209(td) +msgid "User to run as" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:98(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:549(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:922(td) +msgid "db_preallocation" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:100(td) +msgid "Preallocate disk space for new SQLite databases to decrease fragmentation" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:104(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:554(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:927(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1222(td) +msgid "eventlet_debug" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:105(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:110(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:555(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:560(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:646(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:928(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:933(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1223(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1315(td) +msgid "false" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:106(td) +msgid "Turn on debug logging for eventlet" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:109(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:559(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:932(td) +msgid "disable_fallocate" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:111(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:561(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:934(td) +msgid "Disable \"fast fail\" fallocate checks if the underlying filesystem does not support it." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:116(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:564(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:937(td) +msgid "fallocate_reserve" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:118(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:566(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:939(td) +msgid "The number of bytes for fallocate to reserve, whether there is space for the given file size or not. The default fallocate_reserve is 0, meaning \"no reserve\". Some systems behave badly when they completely run out of space. To alleviate this problem, you can set fallocate_reserve. When the disk free space falls at or below this amount, fallocate calls will fail, even if the underlying OS fallocate call would succeed. For example, a fallocate_reserve of 10737418240 (10G) would make all fallocate calls fail, even for zero-byte files, when the disk free space falls under 10G." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:135(caption) +msgid "object-server.conf Server Options in the [object-server] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:144(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:618(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:964(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1237(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1330(td) +msgid "use" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:148(code) +msgid "egg:swift#object" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:146(td) +msgid "The paste.deploy entry point for the object server. For most cases, this should be ." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:152(td) +msgid "object-server" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:166(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:640(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:985(td) +msgid "log_requests" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:167(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1259(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1353(td) +msgid "True" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:168(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:642(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:987(td) +msgid "Whether or not to log each request" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:176(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:369(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:652(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:702(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:767(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1042(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1156(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1288(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1380(td) +msgid "node_timeout" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:178(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:371(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:654(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:704(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:769(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1044(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1158(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1290(td) +msgid "Request timeout to external services" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:181(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:374(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:657(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:707(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:772(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1047(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1161(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1298(td) +msgid "conn_timeout" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:182(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:375(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:658(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:708(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:773(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1048(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1162(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1299(td) +msgid "0.5" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:183(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:376(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:659(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:709(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:774(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1049(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1163(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1300(td) +msgid "Connection timeout to external services" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:186(td) +msgid "network_chunk_size" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:187(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:193(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1274(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1279(td) +msgid "65536" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:188(td) +msgid "Size of chunks to read/write over the network" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:192(td) +msgid "disk_chunk_size" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:194(td) +msgid "Size of chunks to read/write to disk" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:197(td) +msgid "max_upload_time" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:199(td) +msgid "Maximum time allowed to upload an object" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:202(td) +msgid "slow" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:204(td) +msgid "If > 0, Minimum time in seconds for a PUT or DELETE request to complete" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:208(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:596(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:990(td) +msgid "auto_create_account_prefix" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:209(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:597(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:991(td) +msgid "." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:210(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:598(td) +msgid "Prefix used when automatically creating accounts" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:214(td) +msgid "allowed_headers" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:215(td) +msgid "content-disposition, content-encoding, x-delete-at, x-object-manifest," +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:217(td) +msgid "Comma-separated list of headers that can be set in metadata of an object" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:221(td) +msgid "mb_per_sync" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:222(td) +msgid "512" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:223(td) +msgid "On PUTs, sync data every n MB" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:228(caption) +msgid "object-server.conf Replicator Options in the [object-replicator] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:238(td) +msgid "object-replicator" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:252(td) +msgid "daemonize" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:253(td) +msgid "yes" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:254(td) +msgid "Whether or not to run replication as a daemon" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:258(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:697(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1037(td) +msgid "run_pause" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:260(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:699(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1039(td) +msgid "Time in seconds to wait between replication passes" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:264(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:364(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:692(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:762(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1032(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1146(td) +msgid "concurrency" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:266(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:694(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1034(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1148(td) +msgid "Number of replication workers to spawn" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:269(td) +msgid "timeout" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:270(td) +msgid "5" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:271(td) +msgid "Timeout value sent to rsync –timeout and –contimeout options" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:275(td) +msgid "http_timeout" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:277(td) +msgid "Maximum duration for an HTTP request" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:280(td) +msgid "lockup_timeout" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:281(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:814(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1104(td) +msgid "1800" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:282(td) +msgid "Attempts to kill all workers if nothing replicates for lockup_timeout seconds." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:286(td) +msgid "stats_interval" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:287(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:360(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:453(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:758(td) +msgid "300" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:288(td) +msgid "Interval in seconds between logging replication statistics" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:292(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:712(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1052(td) +msgid "reclaim_age" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:293(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:713(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1053(td) +msgid "604800" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:294(td) +msgid "Time elapsed in seconds before an object can be reclaimed" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:298(td) +msgid "recon_cache_path" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:299(td) +msgid "/var/cache/swift" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:300(td) +msgid "Directory where stats for a few items will be stored" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:304(td) +msgid "recon_enable" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:305(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:328(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:728(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1058(td) +msgid "no" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:306(td) +msgid "Enable logging of replication stats for recon" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:310(td) +msgid "ring_check_interval" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:311(td) +msgid "15" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:312(td) +msgid "How often (in seconds) to check the ring" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:315(td) +msgid "rsync_io_timeout" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:317(td) +msgid "Passed to rsync for max duration (seconds) of an I/O op" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:321(td) +msgid "rsync_timeout" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:322(td) +msgid "900" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:323(td) +msgid "Max duration (seconds) of a partition rsync" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:327(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:727(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1057(td) +msgid "vm_test_mode" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:329(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:729(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1059(td) +msgid "Indicates that you are using a VM environment" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:335(caption) +msgid "object-server.conf Updater Options in the [object-updater] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:345(td) +msgid "object-updater" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:359(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:717(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:757(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:813(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1062(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1103(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1151(td) +msgid "interval" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:361(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:759(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:815(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1064(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1105(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1153(td) +msgid "Minimum time for a pass to take" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:366(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:764(td) +msgid "Number of updater workers to spawn" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:370(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:653(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:703(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1043(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1074(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1157(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1289(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1310(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1381(td) +msgid "10" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:379(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:777(td) +msgid "slowdown" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:380(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:778(td) +msgid "0.01" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:381(td) +msgid "Time in seconds to wait between objects" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:386(caption) +msgid "object-server.conf Auditor Options in the [object-auditor] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:396(td) +msgid "object-auditor" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:410(td) +msgid "log_time" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:411(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1152(td) +msgid "3600" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:412(td) +msgid "Frequency of status logs in seconds." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:415(td) +msgid "files_per_second" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:417(td) +msgid "Maximum files audited per second. Should be tuned according to individual system specs. 0 is unlimited." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:422(td) +msgid "bytes_per_second" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:423(td) +msgid "10000000" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:424(td) +msgid "Maximum bytes audited per second. Should be tuned according to individual system specs. 0 is unlimited." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:429(td) +msgid "zero_byte_files_per_second" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:430(td) +msgid "50" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:431(td) +msgid "Maximum zero byte files audited per second." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:438(para) +msgid "When configured, the StaticWeb WSGI 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/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:443(caption) +msgid "object-server.conf staticweb Options in the [filter:staticweb] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:452(td) +msgid "cache_timeout" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:454(td) +msgid "Number of seconds to cache container x-container-meta-web-* header values." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:459(td) +msgid "Indicate which facility to use for logging staticweb requests." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:464(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:469(td) +msgid "Indicate which level of logging to use for staticweb requests." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:468(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:488(td) +msgid "staticweb" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:473(td) +msgid "f" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:474(td) +msgid "Indicate which headers to use for logging staticweb requests." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:477(td) +msgid "access_log_level" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:478(td) +msgid "'INFO'" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:479(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:489(td) +msgid "Indicate which level of logging to use for staticweb container access." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:482(td) +msgid "access_log_facility" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:484(td) +msgid "Indicate which facility to use for logging access to staticweb containers." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:487(td) +msgid "access_log_name" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:495(title) +msgid "Container Server Configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:496(para) +msgid "An example Container Server configuration can be found at etc/container-server.conf-sample in the source code repository." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:500(caption) +msgid "container-server.conf Default Options in the [DEFAULT] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:530(td) +msgid "6001" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:551(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:924(td) +msgid "preallocate disk space for new SQLite databases to decrease fragmentation" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:556(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:929(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1224(td) +msgid "turn on debug logging for eventlet" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:610(caption) +msgid "container-server.conf Server Options in the [container-server] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:622(code) +msgid "egg:swift#container" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:620(td) +msgid "The paste.deploy entry point for the container server. For most cases, this should be ." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:626(td) +msgid "container-server" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:645(td) +msgid "allow_versions" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:647(td) +msgid "Whether to allow versions of containers" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:664(caption) +msgid "container-server.conf Replicator Options in the [container-replicator] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:673(td) +msgid "container-replicator" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:687(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1020(td) +msgid "per_diff" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:689(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1022(td) +msgid "Limit number of items to get per diff" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:693(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1033(td) +msgid "8" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:714(td) +msgid "Time elapsed in seconds before a container can be reclaimed" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:719(td) +msgid "Minimum time for a pass to take (s)" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:722(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1025(td) +msgid "max_diffs" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:724(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1027(td) +msgid "Caps how long the replicator spends trying to sync a database per pass" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:734(caption) +msgid "container-server.conf Updater Options in the [container-updater] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:743(td) +msgid "container-updater" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:763(td) +msgid "4" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:779(td) +msgid "Time in seconds to wait between containers" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:782(td) +msgid "account_supression_time" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:784(td) +msgid "Seconds to suppress updating an account that has generated an error (timeout, not yet found, etc.)" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:790(caption) +msgid "container-server.conf Auditor Options in the [container-auditor] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:799(td) +msgid "container-auditor" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:818(td) +msgid "containers_per_second" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:819(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1109(td) +msgid "200" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:820(td) +msgid "Maximum containers audited per second. Should be tuned according to individual system specs. 0 is unlimited." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:827(caption) +msgid "container-server.conf Sync Options in the [container-sync] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:836(td) +msgid "container-sync" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:850(td) +msgid "container_time" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:852(td) +msgid "Maximum amount of time to spend syncing each container" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:855(td) +msgid "sync_proxy" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:857(td) +msgid "If you need to use an HTTP Proxy, set it here (eg http://127.0.0.1:8888); defaults to no proxy." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:863(title) +msgid "Account Server Configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:864(para) +msgid "An example Account Server configuration can be found at etc/account-server.conf-sample in the source code repository." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:868(caption) +msgid "account-server.conf Default Options in the [DEFAULT] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:883(td) +msgid "Parent directory or where devices are mounted" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:898(td) +msgid "6002" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:956(caption) +msgid "account-server.conf Server Options in the [account-server] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:967(code) +msgid "egg:swift#account" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:966(td) +msgid "Entry point for paste.deploy for the account server. For most cases, this should be ." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:971(td) +msgid "account-server" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:992(td) +msgid "prefix used when automatically creating accounts" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:997(caption) +msgid "account-server.conf Replicator Options in the [account-replicator] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1006(td) +msgid "account-replicator" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1054(td) +msgid "Time elapsed in seconds before an account can be reclaimed" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1067(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1303(td) +msgid "error_suppression_interval" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1069(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1305(td) +msgid "Time in seconds that must elapse since the last error for a node to be considered no longer error limited" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1073(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1309(td) +msgid "error_suppression_limit" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1075(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1311(td) +msgid "Error count to consider a node error limited" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1080(caption) +msgid "account-server.conf Auditor Options in the [account-auditor] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1089(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1132(td) +msgid "account-auditor" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1108(td) +msgid "accounts_per_second" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1110(td) +msgid "Maximum accounts audited per second. Should be tuned according to individual system specs. 0 is unlimited." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1117(caption) +msgid "account-server.conf Reaper Options in the [account-reaper] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1125(td) +msgid "delay_reaping" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1127(td) +msgid "Number of seconds to delay reaper from deleting account info for deleted accounts. 2592000 = 30 days, for example" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1147(td) +msgid "25" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1169(title) +msgid "Proxy Server Configuration" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1170(para) +msgid "An example Proxy Server configuration can be found at etc/proxy-server.conf-sample in the source code repository." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1174(caption) +msgid "proxy-server.conf Default Options in the [DEFAULT] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1188(td) +msgid "80" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1212(td) +msgid "cert_file" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1214(td) +msgid "Path to the ssl .crt" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1217(td) +msgid "key_file" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1219(td) +msgid "Path to the ssl .key" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1229(caption) +msgid "proxy-server.conf Server Options in the [proxy-server] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1240(code) +msgid "egg:swift#proxy" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1239(td) +msgid "Entry point for paste.deploy for the proxy server. For most cases, this should be ." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1244(td) +msgid "proxy-server" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1255(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1349(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1413(td) +msgid "Log level" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1263(td) +msgid "recheck_account_existence" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1265(td) +msgid "Cache timeout in seconds to send memcached for account existence" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1268(td) +msgid "recheck_container_existence" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1270(td) +msgid "Cache timeout in seconds to send memcached for container existence" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1273(td) +msgid "object_chunk_size" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1275(td) +msgid "Chunk size to read from object servers" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1278(td) +msgid "client_chunk_size" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1280(td) +msgid "Chunk size to read from clients" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1283(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1421(td) +msgid "memcache_servers" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1284(td) ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1422(td) +msgid "127.0.0.1:11211" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1285(td) +msgid "Comma separated list of memcached servers ip:port." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1293(td) +msgid "client_timeout" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1295(td) +msgid "Timeout to read one chunk from a client" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1314(td) +msgid "allow_account_management" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1316(td) +msgid "Whether account PUTs and DELETEs are even callable" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1322(caption) +msgid "proxy-server.conf Paste.deploy Options in the [filter:swauth] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1333(code) +msgid "egg:swauth#swauth" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1332(td) +msgid "Entry point for paste.deploy to use for auth, set to: to use the swauth downloaded from https://github.com/gholt/swauth" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1338(td) +msgid "auth-server" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1357(td) +msgid "reseller_prefix" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1359(td) +msgid "The naming scope for the auth service. Swift storage accounts and auth tokens will begin with this prefix." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1363(td) +msgid "auth_prefix" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1364(td) +msgid "/auth/" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1366(code) +msgid "v" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1365(td) +msgid "The HTTP request path prefix for the auth service. Swift itself reserves anything beginning with the letter ." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1369(td) +msgid "default_swift_cluster" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1370(td) +msgid "local#http://127.0.0.1:8080/v1" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1371(td) +msgid "The default Swift cluster to place newly created accounts on; only needed if you are using Swauth for authentication." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1375(td) +msgid "token_life" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1377(td) +msgid "The number of seconds a token is valid." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1382(td) +msgid "Request timeout" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1385(td) +msgid "super_admin_key" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1386(td) +msgid "None" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1387(td) +msgid "The key for the .super_admin account." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1393(caption) +msgid "proxy-server.conf Server Options in the [filter:cache] section" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1402(td) +msgid "cache" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml:1423(td) +msgid "Comma separated list of memcached servers ip:port. Note: the value in here will be ignored if it is also specified in /etc/swift/proxy-server.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/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:146(None) +msgid "@@image: 'figures/cyberduck_swift_connection.png'; md5=dc937c99fd4448174485c22f7cfdaefd" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:176(None) +msgid "@@image: 'figures/cyberduck_swift_uploads.png'; md5=693641aacfa7ccc1514cac5fb5c8f315" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:7(title) +msgid "OpenStack Object Storage Tutorials" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:8(para) +msgid "We want people to use OpenStack for practical problem solving, and the increasing size and density of web content makes for a great use-case for object storage. These tutorials show you how to use your OpenStack Object Storage installation for practical purposes, and it assumes Object Storage is already installed." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:14(title) +msgid "Storing Large Photos or Videos on the Cloud" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:16(para) +msgid "In this OpenStack tutorial, we’ll walk through using an Object Storage installation to back up all your photos or videos. As the sensors on consumer-grade and pro-sumer grade cameras generate more and more megapixels, we all need a place to back our files to and know they are safe." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:21(para) +msgid "We'll go through this tutorial in parts:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:24(para) +msgid "Setting up secure access to Object Storage." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:25(para) +msgid "Configuring Cyberduck for connecting to OpenStack Object Storage." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:26(para) +msgid "Copying files to the cloud." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:29(title) +msgid "Part I: Setting Up Secure Access" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:30(para) +msgid "In this part, we'll get the proxy server running with SSL on the Object Storage installation. It's a requirement for using Cyberduck as a client interface to Object Storage." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:33(para) +msgid "You will need a key and certificate to do this, which we can create as a self-signed for the tutorial since we can do the extra steps to have Cyberduck accept it. Creating a self-signed cert can usually be done with these commands on the proxy server:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:40(para) +msgid "Ensure these generated files are in /etc/swift/cert.crt and /etc/swift/cert.key." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:41(para) +msgid "You also should configure your iptables to enable https traffic. Here's an example setup that works." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:58(para) +msgid "If you don't have access to the Object Storage installation to configure these settings, ask your service provider to set up secure access for you." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:59(para) +msgid "Then, edit your proxy-server.conf file to include the following in the [DEFAULT] sections." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:67(para) +msgid "Also, make sure you use https: for all references to the URL for the server in the .conf files as needed." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:69(para) +msgid "Verify that you can connect using the Public URL to Object Storage by using the \"swift\" tool:" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:75(para) +msgid "Okay, you've created the access that Cyberduck expects for your Object Storage installation. Let's start configuring the Cyberduck side of things." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:81(title) +msgid "Part II: Configuring Cyberduck" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:83(para) +msgid "See the Cyberduck website for further details." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:88(para) +msgid "After installing Cyberduck you'll need to change the path/context used for the authentication URL. The default value shipped with Cyberduck is incorrect." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:93(para) +msgid "On OS X open a Terminal window and execute, " +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:97(para) +msgid "On Windows open the preferences file in a text editor. The exact location of this file is described here. If this path doesn't exist you may need to start and stop Cyberduck to have it generate the config file. Once you've opened the file add the setting, " +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:115(term) +msgid "Server" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:117(para) +msgid "your proxy server's hostname or IP address" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:121(term) +msgid "Port" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:122(para) +msgid "443" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:125(term) +msgid "Username" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:127(para) +msgid "account name followed by a colon and then the user name, for example test:tester" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:134(term) +msgid "Password" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:136(para) +msgid "password for the account and user name entered above" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:143(title) +msgid "Example Cyberduck Swift Connection" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:107(para) +msgid "To connect to Swift start Cyberduck and click the Open Connection toolbar button or choose File > Open Connection. Select Swift (OpenStack Object Storage) in the dropdown and enter your cluster details. " +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:153(title) +msgid "Connecting to a Unsecured Swift Cluster" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:154(para) +msgid "An Unsecured Swift Cluster does not use https connections. Download the Unsecured Swift profile file and double click it to import it into Cyberduck." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:159(para) +msgid "When creating a new connection select Swift (HTTP). Enter your connection details as described above. You'll need to change the port since presumably you won't want to use 443." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:167(title) +msgid "Part III: Creating Containers (Folders) and Uploading Files" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:168(para) +msgid "Now you want to create containers to hold your files. Without containers, Object Storage doesn't know where to put the files. In the Action menu, choose New Folder and name the folder." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:173(title) +msgid "Example Cyberduck Swift Showing Uploads" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:171(para) +msgid "Next you can drag and drop files into the created folder or select File > Upload to select files to upload to the OpenStack Object Storage service. " +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/objectstoragetutorials.xml:179(para) +msgid "Et voila! You can back up terabytes of data if you just have the space and the data. That's a lot of pictures or video, so get snapping and rolling!" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:10(title) +msgid "OpenStack Object Storage Administration Manual" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:18(orgname) +msgid "OpenStack" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:22(year) +msgid "2010" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:23(year) +msgid "2011" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:24(year) +msgid "2012" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:25(year) +msgid "2013" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:26(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:28(releaseinfo) +msgid "trunk" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:29(productname) +msgid "OpenStack Object Storage" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:30(pubdate) ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:43(date) +msgid "2012-12-06" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:33(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:37(para) +msgid "OpenStack™ Object Storage offers open source software for cloud-based object storage for any organization. This manual provides guidance for installing, managing, and understanding the software that runs OpenStack Object Storage." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:47(para) +msgid "Bug fixes and cleanup. Fix bug 1034144" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:48(para) +msgid "Add section about cluster health." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:49(para) +msgid "Add a note about the apt-get install for swift3 from Ubuntu Cloud Archive." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:55(date) +msgid "2012-11-09" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:59(para) +msgid "Folsom release of this document." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:65(date) +msgid "2012-08-21" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:69(para) +msgid "Add note to the [filter:cache] section of the proxy-server.conf file reference indicating that the memcache_servers value is ignored if it is specified in /etc/swift/memcache.conf." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:77(para) +msgid "Update Cyberduck tutorial." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:83(date) +msgid "2012-06-05" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:87(para) +msgid "Fix bug 1009170." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:93(date) +msgid "2012-05-03" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:97(para) +msgid "Begin trunk designation." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:103(date) +msgid "2012-05-02" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:107(para) +msgid "Essex release." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:113(date) +msgid "2012-04-27" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:117(para) +msgid "Adds ring copy example." +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:123(date) +msgid "2012-01-01" +msgstr "" + +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:127(para) +msgid "Formatting updates." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/src/docbkx/openstack-object-storage-admin/bk-objectstorage-adminguide.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/src/docbkx/openstack-ops/locale/openstack-ops.pot b/doc/src/docbkx/openstack-ops/locale/openstack-ops.pot new file mode 100644 index 0000000000..11e6539615 --- /dev/null +++ b/doc/src/docbkx/openstack-ops/locale/openstack-ops.pot @@ -0,0 +1,280 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2013-03-12 14:42+0800\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/src/docbkx/openstack-ops/ch_ops-manual-how-to-use.xml:5(title) +msgid "How to use this manual" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-manual-how-to-use.xml:6(para) +msgid "Intended Audience Conventions" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-diagnostic-troubleshooting.xml:5(title) +msgid "Diagnostics and Troubleshooting" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-diagnostic-troubleshooting.xml:6(para) +msgid "If this happens, then do this" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-diagnostic-troubleshooting.xml:10(title) +msgid "Tips, Tricks, and Traps" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-diagnostic-troubleshooting.xml:11(para) +msgid "Configuration settings that should not remain defaults Making sensible scheduler choices Figuring out how to find out what flags do" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-diagnostic-troubleshooting.xml:19(title) +msgid "Monitoring" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-diagnostic-troubleshooting.xml:20(para) +msgid "Sources of information and alerts Monitoring Hardware Monitoring the Network Monitoring the Cloud" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:5(title) +msgid "Day to Day Operations" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:6(para) +msgid "This chapter aims to describe \"A day in the life of an operator, by detailing the common tasks that every OpeStack administrator could expect to perform." +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:11(title) +msgid "Watch the Queues" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:15(para) +msgid "Something!" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:12(para) +msgid "A core part of OpenStack Compute is the message queue, provided by RabbitMQ, or QPID. The queue is responsible for: " +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:18(para) +msgid "In general, if the queue has no messages this means that they are reaching their destination. One of the common signs of trouble in Compute is if there are pileups of messages for certain destinations. In cases like this, unless you are actively checking the queues, tasks can sit silently without being processed." +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:26(para) +msgid "You can check the state of the queues with: " +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:33(title) +msgid "Network issues" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:34(para) +msgid "Openstack provides and relies on broad access to the network, so when trouble occurs here the issues can be wide reaching. Thankfully there are some common tools you can use to determine the location of problems." +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:38(para) +msgid "Pings, traceroutes, nslookups for networking issues TCP dumps Look for pings with high latency" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:46(title) +msgid "Resource Utilisation" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:47(para) +msgid "Disk I/O - look for 100% utilization spots CPU Straces" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:55(title) +msgid "Working with Instances" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:60(para) +msgid "Instances stuck in \"build\" state" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:61(para) +msgid "Instances can't be \"ping\"ed" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:62(para) +msgid "Instances can't be accessed through a VNC console" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:56(para) +msgid "Running virtual machines is a complex business, and many different points of failure can be realised. It is worth paying attention to these common cases: " +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:68(title) +msgid "Working with Users" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:69(para) +msgid "Direct users of OpenStack's Infrastructure-as-a-Service and Object Storage capabilities are likely to be technically competent developers. You may find your Tier 1 support (if any!) relies on you more to provide user support for these cases." +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:73(para) +msgid "Here are some example types of \"tickets\" generated by OpenStack users, and some tips for working the service into your support workflow" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:79(title) +msgid "Daily monitoring practices" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:80(para) +msgid "No one likes a spammy nagios, or having tail -f of a log file scroll past like the matrix. Metrics to follow with alarm settting Syslog trolling" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:87(title) +msgid "Summary of Operational Tools" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:88(para) +msgid "Available tools modified or used in Openstack Euca Nova.conf Curl etc. Nagios" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-quick-start.xml:5(title) +msgid "Operations Quick Start" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-quick-start.xml:6(para) +msgid "Administrative starting tasks - first time operator on an OpenStack cloud, what do they need to know? New Hire Operator who needs to get up to speed quickly." +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-periodic.xml:5(title) +msgid "Periodic Operations" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-periodic.xml:6(para) +msgid "Things that need to be done sometimes Cleanup of databases Rebuilding/Balancing the ring Log file rotation checks Capacity planning" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:10(title) +msgid "OpenStack Operations Manual - Red HatUbuntu" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:20(orgname) ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:29(productname) +msgid "OpenStack" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:24(year) +msgid "2012" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:25(year) +msgid "2013" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:26(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:28(releaseinfo) +msgid "trunk" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:30(pubdate) +msgid "2012-09-10" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:33(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:37(para) +msgid "The OpenStack™ system has several key projects that are separate installations but can work together depending on your cloud needs: OpenStack Compute, OpenStack Object Storage, OpenStack Identity Service, and OpenStack Image Service. This manual provides operational pointers using packages available through Ubuntu 12.04.This manual provides operational pointers using packages available through Fedora 17 as well as on RHEL and derivatives through the EPEL repository. It offers suggestions for common operational practices and aims to get new operators quickly up to speed." +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:58(date) +msgid "2012-07-29" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:62(para) +msgid "Initial structure." +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:5(title) +msgid "Operations Management Practices" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:6(para) +msgid "This chapter discusses best practices for operations management." +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:11(title) +msgid "Starting Up" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:12(para) ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:17(para) ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:29(para) ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:50(para) +msgid "Text" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:16(title) +msgid "Database Management" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:21(title) +msgid "Storage Management" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:22(para) +msgid "- volumes attached to compute instances Backups for volumes" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:28(title) +msgid "User Management" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:33(title) +msgid "Security Management" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:34(para) +msgid "Security is important!" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:38(title) +msgid "DevOps principles" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:39(para) +msgid "Dev/Ops principals and how they work in the Ops environment" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:44(title) +msgid "Migration and Upgrades" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:45(para) +msgid "Migrations are hard!" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:49(title) +msgid "Failover Planning" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:54(title) +msgid "Disaster Recovery, Business Continuity Planning" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:55(para) +msgid "DCs in flames" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:59(title) +msgid "Automation" +msgstr "" + +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:60(para) +msgid "Automation - What to automate and how to do it" +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/tools/generatedocbook b/tools/generatedocbook new file mode 100755 index 0000000000..7790e39b7c --- /dev/null +++ b/tools/generatedocbook @@ -0,0 +1,149 @@ +#!/usr/bin/env python +# -*- coding: utf-8 -*- + +''' +Created on 2012-7-3 + +@author: daisy +''' +import os, sys +import tempfile +import shutil +import xml.dom.minidom +from optparse import OptionParser +import codecs + +from xml2po import Main +default_mode = 'docbook' +operation = 'merge' +options = { + 'mark_untranslated' : False, + 'expand_entities' : True, + 'expand_all_entities' : False, +} + +ignore_folder = {"docbkx-example"} +root = "./doc/src/docbkx" + +def mergeback (folder, language): + if (folder==None) : + path = root + else : + outputFiles = mergeSingleDocument(folder, language) + if ((outputFiles != None) and (len(outputFiles)>0)) : + for outXML in outputFiles : + changeXMLLangSetting (outXML, language) + return + + if (not os.path.isdir(path)) : + return + + files = os.listdir(path) + for aFile in files : + if (not (aFile in ignore_folder)): + outputFiles = mergeSingleDocument (aFile, language) + if ((outputFiles != None) and (len(outputFiles)>0)) : + for outXML in outputFiles : + changeXMLLangSetting (outXML, language) + +def mergeSingleDocument(folder, language): + xmlfiles = [] + outputfiles = [] + abspath = os.path.join(root, folder) + if (os.path.isdir(abspath)) : + os.path.walk(abspath, get_xml_list, xmlfiles) + else: + return None + + if len(xmlfiles)>0 : + popath = os.path.join(abspath,"locale",language+".po") + #generate MO file + mofile_handler, mofile_tmppath = tempfile.mkstemp() + os.close(mofile_handler) + os.system("msgfmt -o %s %s" % (mofile_tmppath, popath)) + + for aXML in xmlfiles : + #(filename, ext) = os.path.splitext(os.path.basename(aXML)) + relpath = os.path.relpath(aXML, root) + outputpath = os.path.join(os.path.curdir, "generated", language, relpath) + try: + xml2po_main = Main(default_mode, operation, outputpath, options) + xml2po_main.merge(mofile_tmppath, aXML) + outputfiles.append(outputpath) + except IOError: + print "Error: cannot open aFile %s for writing." + sys.exit(5) + except : + print ("Exception happen") + if mofile_tmppath : + os.remove(mofile_tmppath) + + return outputfiles + +def changeXMLLangSetting(xmlFile, language): + dom = xml.dom.minidom.parse(xmlFile) + root = dom.documentElement + root.setAttribute("xml:lang", language[:2]) + fileObj = codecs.open(xmlFile, "wb", encoding="utf-8") + + #add namespace to link + nodelists = root.getElementsByTagName("link") + for node in nodelists : + if (node.hasAttribute("href")) : + node.setAttribute("xlink:href", node.getAttribute("href")) + + dom.writexml(fileObj) + +def get_xml_list (sms, dr, flst): + if ((flst == "target") or (flst == "wadls")) : + return + if (dr.find("target")>-1) : + return + if (dr.find("wadls")>-1) : + return + + for f in flst: + if ((f.endswith(".xml") and (f != "pom.xml"))) : + sms.append(os.path.join(dr,f)) + +def main(argv): + + usage = "usage: %prog [options] command [cmd_options]" + description = "This is the tool to generate translated docbooks, which"\ + " will be stored in 'generated/[language]/" + + parser = OptionParser( + usage=usage, version="0.6", description=description + ) + parser.disable_interspersed_args() + parser.add_option( + "-l", "--language", dest="language", help=("specified language") + ) + parser.add_option( + "-b", "--book", dest="book", help=("specified docbook") + ) + (options, args) = parser.parse_args() + if (options.language == None) : + print "must specify language" + return + + #change working directory + + #copy folders + folder = options.book + language = options.language + sourcepath = os.path.join(root, folder) + destpath = os.path.join(os.path.curdir, "generated", language) + if (not os.path.exists(destpath)) : + os.makedirs(destpath) + + destfolder = os.path.join(destpath, folder) + if (os.path.exists(destfolder)) : + shutil.rmtree(destfolder) + + os.system("cp -r %s %s" % (sourcepath, destpath)) + mergeback(folder, language) + +if __name__ == '__main__': + main(sys.argv[1:]) + diff --git a/tools/generatepot b/tools/generatepot new file mode 100755 index 0000000000..992c6bc0f7 --- /dev/null +++ b/tools/generatepot @@ -0,0 +1,93 @@ +#!/usr/bin/env python +# -*- coding: utf-8 -*- + +''' +Created on 2012-7-3 + +@author: daisy +''' +import os, sys +from xml2po import Main +from xml2po.modes.docbook import docbookXmlMode + +class myDocbookXmlMode(docbookXmlMode): + def __init__(self): + self.lists = ['itemizedlist', 'orderedlist', 'variablelist', + 'segmentedlist', 'simplelist', 'calloutlist', 'varlistentry', 'userinput', + 'computeroutput','prompt','command','screen'] + self.objects = [ 'figure', 'textobject', 'imageobject', 'mediaobject', + 'screenshot','literallayout', 'programlisting' ] + +default_mode = 'docbook' +operation = 'pot' +options = { + 'mark_untranslated' : False, + 'expand_entities' : True, + 'expand_all_entities' : False, +} + +ignore_folder = {"docbkx-example"} +ignore_file = {"api-examples.xml"} + +root = "./doc/src/docbkx" + +def generatePoT (folder): + if (folder==None) : + path = root + else : + generateSinglePoT(folder) + return + + if (not os.path.isdir(path)) : + return + + files = os.listdir(path) + for aFile in files : + if (not (aFile in ignore_folder)): + generateSinglePoT (aFile) + +def generateSinglePoT(folder): + xmlfiles = [] + abspath = os.path.join(root, folder) + if (os.path.isdir(abspath)) : + os.path.walk(abspath, get_all_xml, xmlfiles) + else: + return + + if len(xmlfiles)>0 : + output = os.path.join(abspath,"locale") + if (not os.path.exists(output)) : + os.mkdir(output) + output = os.path.join(output, folder+".pot") + try: + xml2po_main = Main(default_mode, operation, output, options) + xml2po_main.current_mode = myDocbookXmlMode() + except IOError: + print "Error: cannot open aFile %s for writing." % (output) + sys.exit(5) + #print(xmlfiles) + #print(">>>outout: %s ", output) + xml2po_main.to_pot(xmlfiles) + +def get_all_xml (sms, dr, flst): + if ((flst == "target") or (flst == "wadls")) : + return + if (dr.find("target")>-1) : + return + if (dr.find("wadls")>-1) : + return + + for f in flst: + if (f.endswith(".xml") and (f != "pom.xml") and (not (f in ignore_file))) : + sms.append(os.path.join(dr,f)) + +def main(): + try: + folder = sys.argv[1] + except: + folder = None + generatePoT(folder) + +if __name__ == '__main__': + main() +