openstack/openstack-manuals
Code Issues Proposed changes
d49d27d085
openstack-manuals/doc/common/locale/common.pot
Diane Fleming 64b6c9261e Folder rename, file rename, flattening of directories 
Current folder name	New folder name	        Book title
----------------------------------------------------------
basic-install 	        DELETE
cli-guide	        DELETE
common	                common
NEW	                admin-guide-cloud	Cloud Administrators Guide
docbkx-example	        DELETE
openstack-block-storage-admin 	DELETE
openstack-compute-admin 	DELETE
openstack-config 	config-reference	OpenStack Configuration Reference
openstack-ha 	        high-availability-guide	OpenStack High Availabilty Guide
openstack-image	        image-guide	OpenStack Virtual Machine Image Guide
openstack-install 	install-guide	OpenStack Installation Guide
openstack-network-connectivity-admin 	admin-guide-network 	OpenStack Networking Administration Guide
openstack-object-storage-admin 	DELETE
openstack-security 	security-guide	OpenStack Security Guide
openstack-training 	training-guide	OpenStack Training Guide
openstack-user 	        user-guide	OpenStack End User Guide
openstack-user-admin 	user-guide-admin	OpenStack Admin User Guide
glossary	        NEW        	OpenStack Glossary

bug: #1220407

Change-Id: Id5ffc774b966ba7b9a591743a877aa10ab3094c7
author: diane fleming
2013-09-08 15:15:50 -07:00

11334 lines
509 KiB
Plaintext
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

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 <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\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 <literal>--file &lt;dst-path=src-path&gt;</literal> option. You may store up to 5 files. For example if you have a special authorized_keys file named <filename>special_authorized_keysfile</filename> that you want to put on the instance rather than using the regular <link linkend=\"nova_cli_associatekey\">ssh key injection</link> for some reason you can use the following command:<placeholder-1/>"
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 <filename>/lib/udev/rules.d/45-qemu-kvm.rules</filename>, 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. <placeholder-1/>"
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 <filename>/etc/nova/nova.conf</filename>:<placeholder-1/> The KVM hypervisor supports the following virtual machine image formats:<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/common/kvm.xml:38(para)
msgid "<link href=\"http://fedoraproject.org/wiki/Getting_started_with_virtualization\">Fedora: Getting started with virtualization</link> from the Fedora project wiki."
msgstr ""
#: ./doc/src/docbkx/common/kvm.xml:44(para)
msgid "<link href=\"https://help.ubuntu.com/community/KVM/Installation\">Ubuntu: KVM/Installation</link> from the Community Ubuntu documentation."
msgstr ""
#: ./doc/src/docbkx/common/kvm.xml:48(para)
msgid "<link href=\"http://static.debian-handbook.info/browse/stable/sect.virtualization.html#idp11279352\">Debian: Virtualization with KVM</link> from the Debian handbook."
msgstr ""
#: ./doc/src/docbkx/common/kvm.xml:53(para)
msgid "<link href=\"http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Host_Configuration_and_Guest_Installation_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html\">RHEL: Installing virtualization packages on an existing Red Hat Enterprise Linux system</link> from the Red Hat Enterprise Linux Virtualization Host Configuration and Guest Installation Guide."
msgstr ""
#: ./doc/src/docbkx/common/kvm.xml:62(para)
msgid "<link href=\"http://doc.opensuse.org/documentation/html/openSUSE/opensuse-kvm/cha.kvm.requires.html#sec.kvm.requires.install\">openSUSE: Installing KVM</link> from the openSUSE Virtualization with KVM manual."
msgstr ""
#: ./doc/src/docbkx/common/kvm.xml:68(para)
msgid "<link href=\"http://doc.opensuse.org/products/draft/SLES/SLES-kvm_sd_draft/cha.kvm.requires.html#sec.kvm.requires.install\">SLES: Installing KVM</link> 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:<placeholder-1/>"
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 <placeholder-1/> command to check if your processor has VT support, it is enabled in the BIOS, and KVM is installed properly, as root:<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/common/kvm.xml:82(para)
msgid "If KVM is enabled, the output should look something like:<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/kvm.xml:85(para)
msgid "If KVM is not enabled, the output should look something like:<placeholder-1/>"
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 <link linkend=\"qemu\">QEMU</link> or <link linkend=\"introduction-to-xen\">Xen</link>."
msgstr ""
#: ./doc/src/docbkx/common/kvm.xml:91(para)
msgid "On distributions that don't have <placeholder-1/>, you can check if your processor has VT support by looking at the processor flags in the <filename>/proc/cpuinfo</filename> file. For Intel processors, look for the <literal>vmx</literal> flag, and for AMD processors, look for the <literal>svm</literal> flag. A simple way to check is to run the following command and see if there is any output:<placeholder-2/>"
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 <literal>kvm </literal>and either <literal>kvm-intel</literal> or <literal>kvm-amd</literal> 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 <placeholder-1/>, as follows, with expected output for Intel-based processors:<placeholder-2/>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:<placeholder-1/> Add the following lines to <filename>/etc/modules</filename> so that these modules will load on reboot:<placeholder-2/>"
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:<placeholder-1/> Add the following lines to <filename>/etc/modules</filename> so that these modules will load on reboot:<placeholder-2/>"
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:<placeholder-1/>"
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 <filename>/usr/share/libvirt/cpu_map.xml</filename>. 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, <literal>libvirt_cpu_mode</literal> and <literal>libvirt_cpu_model</literal>."
msgstr ""
#: ./doc/src/docbkx/common/kvm.xml:164(para)
msgid "The <literal>libvirt_cpu_mode</literal> option can take one of four values: <literal>none</literal>, <literal>host-passthrough</literal>, <literal>host-model</literal> and <literal>custom</literal>."
msgstr ""
#: ./doc/src/docbkx/common/kvm.xml:168(title)
msgid "Host model (default for KVM &amp; QEMU)"
msgstr ""
#: ./doc/src/docbkx/common/kvm.xml:169(para)
msgid "If your <filename>nova.conf</filename> contains <literal>libvirt_cpu_mode=host-model</literal>, libvirt will identify the CPU model in <filename>/usr/share/libvirt/cpu_map.xml</filename> 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 <filename>nova.conf</filename> contains <literal>libvirt_cpu_mode=host-passthrough</literal>, 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 <literal>libvirt_cpu_mode=custom</literal>, 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 &amp; QEMU)"
msgstr ""
#: ./doc/src/docbkx/common/kvm.xml:201(para)
msgid "If your nova.conf contains <literal>libvirt_cpu_mode=none</literal>, 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 <literal>ERROR</literal> state, and the following error appears in <filename>/var/log/nova/nova-compute.log</filename><placeholder-1/> 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 <placeholder-1/> to see whether the group is set to kvm. If not, run <placeholder-2/>."
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 <link href=\"http://wiki.openstack.org/HypervisorSupportMatrix\"> hypervisor support matrix</link> 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 <filename>/etc/nova/nova.conf</filename> on your <systemitem class=\"service\">nova-compute</systemitem> hosts. <placeholder-1/>"
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 <link href=\"https://wiki.openstack.org/wiki/GeneralBareMetalProvisioningFramework\"> main wiki page</link> 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 "<literal>enable</literal>: True enables SSL. Defaults to False."
msgstr ""
#: ./doc/src/docbkx/common/keystone-ssl-config.xml:103(para)
msgid "<literal>certfile</literal>: Path to Keystone public certificate file."
msgstr ""
#: ./doc/src/docbkx/common/keystone-ssl-config.xml:109(para)
msgid "<literal>keyfile</literal>: 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 "<literal>ca_certs</literal>: Path to CA trust chain."
msgstr ""
#: ./doc/src/docbkx/common/keystone-ssl-config.xml:121(para)
msgid "<literal>cert_required</literal>: 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 <placeholder-1/> commands. Refer to \"<uri href=\"http://docs.openstack.org/trunk/openstack-compute/admin/content/associating-public-ip.html\">Configuring Public (Floating) IP Addresses</uri>\" in the <emphasis>OpenStack Compute Administration Manual</emphasis> for more information."
msgstr ""
#: ./doc/src/docbkx/common/nova_cli_floatingip.xml:18(para)
msgid "Before you begin, use <placeholder-1/> to determine what floating IP pools are available. <placeholder-2/>In this example, the only available pool is <literal>nova</literal>."
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 <placeholder-1/> command. This command reserves the addresses for the tenant, but does not immediately associate that address with an instance. <placeholder-2/>"
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 <placeholder-1/> command. For this example, we'll associate this IP address with an image called <literal>smallimage</literal>. <placeholder-2/> After the command is complete, you can confirm that the IP address has been associated with the <placeholder-3/> and <placeholder-4/> commands. <placeholder-5/> The first table shows that the 50.56.12.232 is now associated with the <literal>smallimage</literal> instance ID, and the second table shows the IP address included under <literal>smallimage</literal>'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 <placeholder-1/> command.<placeholder-2/> After the command is complete, you can confirm that the IP address has been associated with the <placeholder-3/> and <placeholder-4/> commands. <placeholder-5/> You can now de-allocate the floating IP address, returning it to the pool so that it can be used by another tenant. <placeholder-6/> In this example, 50.56.12.232 was the only IP address allocated to this tenant. Running <placeholder-7/> 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 "&lt;name&gt;"
msgstr ""
#: ./doc/src/docbkx/common/host_aggregates.xml:30(replaceable)
msgid "&lt;availability-zone&gt;"
msgstr ""
#: ./doc/src/docbkx/common/host_aggregates.xml:32(para)
msgid "Create a new aggregate named <replaceable>&lt;name&gt;</replaceable> in availability zone <replaceable>&lt;availability-zone&gt;</replaceable>. 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 "&lt;id&gt;"
msgstr ""
#: ./doc/src/docbkx/common/host_aggregates.xml:41(para)
msgid "Delete an aggregate with id <replaceable>&lt;id&gt;</replaceable>."
msgstr ""
#: ./doc/src/docbkx/common/host_aggregates.xml:48(para)
msgid "Show details of the aggregate with id <replaceable>&lt;id&gt;</replaceable>."
msgstr ""
#: ./doc/src/docbkx/common/host_aggregates.xml:54(replaceable) ./doc/src/docbkx/common/host_aggregates.xml:62(replaceable)
msgid "&lt;host&gt;"
msgstr ""
#: ./doc/src/docbkx/common/host_aggregates.xml:56(para)
msgid "Add host with name <replaceable>&lt;host&gt;</replaceable> to aggregate with id <replaceable>&lt;id&gt;</replaceable>."
msgstr ""
#: ./doc/src/docbkx/common/host_aggregates.xml:64(para)
msgid "Remove the host with name <replaceable>&lt;host&gt;</replaceable> from the aggregate with id <replaceable>&lt;id&gt;</replaceable>."
msgstr ""
#: ./doc/src/docbkx/common/host_aggregates.xml:70(replaceable) ./doc/src/docbkx/common/host_aggregates.xml:71(replaceable)
msgid "&lt;key=value&gt;"
msgstr ""
#: ./doc/src/docbkx/common/host_aggregates.xml:73(para)
msgid "Add or update metadata (key-value pairs) associated with the aggregate with id <replaceable>&lt;id&gt;</replaceable>."
msgstr ""
#: ./doc/src/docbkx/common/host_aggregates.xml:80(replaceable)
msgid "&lt;availability_zone&gt;"
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 <placeholder-1/> command-line tool supports the following aggregate-related commands. <placeholder-2/>"
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 <literal>admin</literal> role, or have not been explicitly granted the appropriate privileges, you will see one of the following errors when trying to use these commands:<placeholder-1/><placeholder-2/>"
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 <literal>scheduler_default_filters</literal> configuration option must contain the <literal>AggregateInstanceExtraSpecsFilter</literal> in addition to the other filters used by the scheduler. Add the following line to <filename>/etc/nova/nova.conf</filename> on the host that runs the nova-scheduler service to enable host aggregates filtering, as well as the other filters that are typically enabled:<placeholder-1/>"
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 <literal>fast-io</literal> in the availability zone called <literal>nova</literal>, we add the key-value pair <literal>ssd=true</literal> to the aggregate, and then we add compute nodes <literal>node1</literal>, and <literal>node2</literal> to it.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/host_aggregates.xml:157(para)
msgid "Next, we use the <placeholder-1/> command to create a new flavor called <literal>ssd.large</literal> with an ID of 6, 8GB of RAM, 80GB root disk, and 4 vCPUs. <placeholder-2/>"
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, <literal>ssd=true</literal>. Setting a key-value pair on a flavor is done using the <placeholder-1/> command.<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/common/host_aggregates.xml:171(para)
msgid "Once it is set, you should see the <literal>extra_specs</literal> property of the <literal>ssd.large</literal> flavor populated with a key of <literal>ssd</literal> and a corresponding value of <literal>true</literal>.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/host_aggregates.xml:190(para)
msgid "Now, when a user requests an instance with the <literal>ssd.large</literal> flavor, the scheduler will only consider hosts with the <literal>ssd=true</literal> key-value pair. In this example, that would only be <literal>node1</literal> and <literal>node2</literal>."
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 <link linkend=\"configuring-migrations-xenserver-shared-storage\">Configuring Migrations</link> 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 <link href=\"http://www.nist.gov/itl/cloud/\"> http://www.nist.gov/itl/cloud/</link>, 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 <link href=\"https://launchpad.net/~openstack\"> https://launchpad.net/~openstack</link> or by filing a bug at <link href=\"https://bugs.launchpad.net/openstack-manuals/+filebug\"> https://bugs.launchpad.net/openstack-manuals/+filebug</link> 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 <link href=\"http://swift.openstack.org\">\"Swift\"</link>) 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 <link href=\"http://glance.openstack.org\">\"Glance\"</link>) 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 <link href=\"http://nova.openstack.org/\">\"Nova\"</link>) provides virtual servers upon demand. <link href=\"http://www.rackspace.com/\">Rackspace</link> and <link href=\"https://www.hpcloud.com/\">HP</link> 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 <link href=\"http://horizon.openstack.org/\">\"Horizon\"</link>) 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 <link href=\"http://keystone.openstack.org/\">\"Keystone\"</link>) 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 <link href=\"http://quantum.openstack.org/\">\"Quantum\"</link>) 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 <link href=\"http://cinder.openstack.org\">\"Cinder\"</link>) 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 <link href=\"https://www.djangoproject.com/\">Django web application</link> 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 <link href=\"http://code.google.com/p/modwsgi/\">mod_wsgi</link> 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 "<code>nova-api</code> 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 <code>nova-compute</code> 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 <code>nova-network</code> worker daemon is very similar to <code>nova-compute</code>. 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 <code>nova-schedule</code> 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 <link href=\"http://www.rabbitmq.com/\">RabbitMQ</link> today, but could be any AMPQ message queue (such as <link href=\"http://qpid.apache.org/\">Apache Qpid</link>). New to the Folsom release is support for <link href=\"http://www.zeromq.org/\">Zero MQ</link>."
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 (<code>nova-console</code>, <code>nova-novncproxy</code> and <code>nova-consoleauth</code>)."
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 <code>nova-compute</code> 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 (<code>swift-proxy-server</code>) 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 "<code>glance-api</code> accepts Image API calls for image discovery, image retrieval and image storage."
msgstr ""
#: ./doc/src/docbkx/common/getstart.xml:494(para)
msgid "<code>glance-registry</code> 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 "<code>keystone</code> 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 "<code>quantum-server</code> 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 "<code>cinder-api</code> accepts API requests and routes them to cinder-volume for action."
msgstr ""
#: ./doc/src/docbkx/common/getstart.xml:588(para)
msgid "<code>cinder-volume</code> acts upon the requests by reading or writing to the Cinder database to maintain state, interacting with other processes (like <code>cinder-scheduler</code>) 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 <code>nova-scheduler</code>, the <code>cinder-scheduler</code> 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 <placeholder-1/> command to add a new virtual machine image to glance, and use <placeholder-2/> to modify properties of an image that has been updated. The <literal>image-create</literal> command takes several optional arguments, but you should specify a name for your image using the <literal>--name</literal> flag, as well as the disk format with <literal>--disk-format</literal> and container format with <literal>--container-format</literal>. 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 "<placeholder-1/> or <placeholder-2/>"
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 "<link href=\"http://en.wikipedia.org/wiki/X86\">Intel sixth-generation x86</link> (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. <literal>x86_64</literal>, <literal>arm</literal>, <literal>ppc64</literal>. Run <placeholder-1/> to get the architecture of a machine. We strongly recommend using the architecture data vocabulary defined by the <link href=\"http://libosinfo.org\">libosinfo project</link> for this purpose. Recognized values for this field are: <placeholder-2/>"
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: <literal>xen</literal>, <literal>qemu</literal>, <literal>kvm</literal>, <literal>lxc</literal>, <literal>uml</literal>, <literal>vmware</literal>, <literal>hyperv</literal>, <literal>powervm</literal>."
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:<placeholder-1/>"
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. <literal>linux</literal>, <literal>windows</literal>. 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 <literal>os_type=windows</literal>, 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 <literal>--property <replaceable>key</replaceable>=<replaceable>value</replaceable></literal> argument to <placeholder-1/>or <placeholder-2/>.For example:<placeholder-3/> 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: <placeholder-4/>The following metadata properties are specific to the XenAPI driver:<placeholder-5/>"
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: <literal>lsiLogic</literal>, <literal>busLogic</literal>, <literal>ide</literal>"
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 <link href=\"http://www.thinkvirt.com/?q=node/181\">thinkvirt.com</link> for a list of valid values. If this is not specified, it will default to <literal>otherGuest</literal>."
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 <literal>1</literal>."
msgstr ""
#: ./doc/src/docbkx/common/adding-images.xml:380(para)
msgid "The following metadata properties are specific to the VMware API driver: <placeholder-1/><placeholder-2/>"
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: <literal>archlinux</literal>, or <literal>org.archlinux</literal>"
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: <literal>org.centos</literal><literal>CentOS</literal>"
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: <literal>Debian</literal>, or <literal>org.debian</literal>"
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: <literal>Fedora</literal>, <literal>org.fedora</literal>, or <literal>org.fedoraproject</literal>"
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: <literal>org.freebsd</literal>, <literal>freeBSD</literal>, or <literal>FreeBSD</literal>"
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: <literal>Gentoo</literal>, or <literal>org.gentoo</literal>"
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: <literal>mandrakelinux</literal>, or <literal>MandrakeLinux</literal>"
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: <literal>mandrivalinux</literal>"
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: <literal>mandrivaent</literal>, or <literal>mandrivaES</literal>"
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: <literal>ms-dos</literal>"
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: <literal>NetBSD</literal>, or <literal>org.netbsd</literal>"
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: <literal>novell</literal>, or <literal>NetWare</literal>"
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: <literal>OpenBSD</literal>, or <literal>org.openbsd</literal>"
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: <literal>OpenSolaris</literal>,or <literal>org.opensolaris</literal>"
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: <literal>suse</literal>, <literal>SuSE</literal>, or <literal>org.opensuse</literal>"
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: <literal>redhat</literal>, <literal>RedHat</literal>, or <literal>com.redhat</literal>"
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: <literal>com.suse</literal>"
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: <literal>Ubuntu</literal>, <literal>com.ubuntu</literal>, <literal>org.ubuntu</literal>, or <literal>canonical</literal>"
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: <literal>com.microsoft.server</literal>, or <literal>windoze</literal>"
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 <link href=\"http://libosinfo.org\">libosinfo project</link>. 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: <placeholder-1/>"
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. <placeholder-1/>"
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 <placeholder-1/> to view the available security groups (specify <literal>--all-tenants</literal> if you are a cloud administrator wanting to view all tenants' groups) . You can also view the rules for a security group with <placeholder-2/>. <placeholder-3/> 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 <placeholder-1/>."
msgstr ""
#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:41(para)
msgid "The following example shows the creation of the security group <literal>secure1</literal>. 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 <placeholder-1/>. The default security group cannot be deleted. The default security group contains these initial settings:<placeholder-2/><placeholder-3/>"
msgstr ""
#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:83(para)
msgid "In the following example, the group <literal>secure1</literal> 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 "&lt;secgroup&gt; 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 "&lt;ip_proto&gt; 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 "&lt;from_port&gt; 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 "&lt;to_port&gt; 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 "&lt;cidr&gt; 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. <placeholder-1/>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 : <placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:133(para)
msgid "&lt;ip_proto&gt; IP protocol (with icmp specified)."
msgstr ""
#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:136(para)
msgid "&lt;ICMP_code&gt; The ICMP code."
msgstr ""
#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:139(para)
msgid "&lt;ICMP_type&gt; The ICMP type."
msgstr ""
#: ./doc/src/docbkx/common/nova_cli_secgroups.xml:142(para)
msgid "&lt;cidr&gt; 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: <placeholder-1/><placeholder-2/>"
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 <emphasis role=\"bold\">base IP</emphasis> and 27 as the <emphasis role=\"bold\">suffix</emphasis>. 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:<placeholder-1/>"
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.):<placeholder-1/>"
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:<placeholder-1/><placeholder-2/>"
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 <link href=\"https://github.com/jamesc/nagios-plugins-rabbitmq\">nagios rabbitmq plugin</link> --------------------- ------------------------- 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<placeholder-1/>"
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:<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/qemu.xml:31(para)
msgid "For some operations you may also have to install the <placeholder-1/> 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, <placeholder-1/>, 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: <placeholder-1/>"
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 <placeholder-1/> 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 <literal>[signing]</literal> section of the configuration file. The configuration values are:"
msgstr ""
#: ./doc/src/docbkx/common/certificates-for-pki.xml:26(para)
msgid "<literal>token_format</literal> - Determines the algorithm used to generate tokens. Can be either <literal>UUID</literal> or <literal>PKI</literal>. Defaults to <literal>PKI</literal>."
msgstr ""
#: ./doc/src/docbkx/common/certificates-for-pki.xml:33(para)
msgid "<literal>certfile</literal> - Location of certificate used to verify tokens. Default is <literal>/etc/keystone/ssl/certs/signing_cert.pem</literal>."
msgstr ""
#: ./doc/src/docbkx/common/certificates-for-pki.xml:39(para)
msgid "<literal>keyfile</literal> - Location of private key used to sign tokens. Default is <literal>/etc/keystone/ssl/private/signing_key.pem</literal>."
msgstr ""
#: ./doc/src/docbkx/common/certificates-for-pki.xml:45(para)
msgid "<literal>ca_certs</literal> - Location of certificate for the authority that issued the above certificate. Default is <literal>/etc/keystone/ssl/certs/ca.pem</literal>."
msgstr ""
#: ./doc/src/docbkx/common/certificates-for-pki.xml:52(para)
msgid "<literal>key_size</literal> - Default is <literal>1024</literal>."
msgstr ""
#: ./doc/src/docbkx/common/certificates-for-pki.xml:57(para)
msgid "<literal>valid_days</literal> - Default is <literal>3650</literal>."
msgstr ""
#: ./doc/src/docbkx/common/certificates-for-pki.xml:62(para)
msgid "<literal>ca_password</literal> - Password required to read the <literal>ca_file</literal>. Default is <literal>None</literal>."
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 <placeholder-1/>. 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 <literal>key_size</literal>, <literal>valid_days</literal>, and <literal>ca_password</literal> 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. <literal>cert_req.conf</literal>):"
msgstr ""
#: ./doc/src/docbkx/common/certificates-for-pki.xml:138(para)
msgid "Then generate a CRS with OpenSSL CLI. <emphasis role=\"strong\">Do not encrypt the generated private key. Must use the -nodes option.</emphasis>"
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 <literal>signing_cert_req.pem</literal> and <literal>signing_key.pem</literal>. Send <literal>signing_cert_req.pem</literal> 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 "<literal>signing_cert.pem</literal> - (Keystone token) signing certificate in PEM format"
msgstr ""
#: ./doc/src/docbkx/common/certificates-for-pki.xml:172(para)
msgid "<literal>signing_key.pem</literal> - corresponding (non-encrypted) private key in PEM format"
msgstr ""
#: ./doc/src/docbkx/common/certificates-for-pki.xml:178(para)
msgid "<literal>cacert.pem</literal> - 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 <literal>/etc/keystone/ssl/certs</literal>, make sure it is reflected in the <literal>[signing]</literal> 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: <link href=\"https://answers.launchpad.net/nova\">https://answers.launchpad.net/nova</link>"
msgstr ""
#: ./doc/src/docbkx/common/support.xml:25(para)
msgid "OpenStack Object Storage: <link href=\"https://answers.launchpad.net/swift\">https://answers.launchpad.net/swift</link>"
msgstr ""
#: ./doc/src/docbkx/common/support.xml:28(para)
msgid "OpenStack Image Delivery and Registration: <link href=\"https://answers.launchpad.net/glance\">https://answers.launchpad.net/glance</link>"
msgstr ""
#: ./doc/src/docbkx/common/support.xml:31(para)
msgid "OpenStack Identity: <link href=\"https://answers.launchpad.net/keystone\">https://answers.launchpad.net/keystone</link>"
msgstr ""
#: ./doc/src/docbkx/common/support.xml:34(para)
msgid "OpenStack Dashboard: <link href=\"https://answers.launchpad.net/horizon\">https://answers.launchpad.net/horizon</link>"
msgstr ""
#: ./doc/src/docbkx/common/support.xml:37(para)
msgid "OpenStack Network Connectivity: <link href=\"https://answers.launchpad.net/quantum\">https://answers.launchpad.net/quantum</link>"
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 <link href=\"https://launchpad.net/~openstack\">https://launchpad.net/~openstack</link> and click \"Subscribe to mailing list\" or view the archives at <link href=\"https://lists.launchpad.net/openstack/\">https://lists.launchpad.net/openstack/</link>. You may be interested in the other mailing lists for specific projects or development - these can be found <link href=\"http://wiki.openstack.org/MailingLists\">on the wiki</link>."
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 <link href=\"http://wiki.openstack.org/\">OpenStack wiki</link> 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: <link href=\"https://bugs.launchpad.net/nova\">https://bugs.launchpad.net/nova</link>"
msgstr ""
#: ./doc/src/docbkx/common/support.xml:85(para)
msgid "OpenStack Object Storage: <link href=\"https://bugs.launchpad.net/swift\">https://bugs.launchpad.net/swift</link>"
msgstr ""
#: ./doc/src/docbkx/common/support.xml:88(para)
msgid "OpenStack Image Delivery and Registration: <link href=\"https://bugs.launchpad.net/glance\">https://bugs.launchpad.net/glance</link>"
msgstr ""
#: ./doc/src/docbkx/common/support.xml:91(para)
msgid "OpenStack Identity: <link href=\"https://bugs.launchpad.net/keystone\">https://bugs.launchpad.net/keystone</link>"
msgstr ""
#: ./doc/src/docbkx/common/support.xml:94(para)
msgid "OpenStack Dashboard: <link href=\"https://bugs.launchpad.net/horizon\">https://bugs.launchpad.net/horizon</link>"
msgstr ""
#: ./doc/src/docbkx/common/support.xml:97(para)
msgid "OpenStack Network Connectivity: <link href=\"https://bugs.launchpad.net/quantum\">https://bugs.launchpad.net/quantum</link>"
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 &amp; 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: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/keystone-concepts.xml:202(para)
msgid "A <emphasis>user</emphasis> 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 <emphasis>tenant</emphasis> 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 <emphasis>project</emphasis> was used instead of <emphasis>tenant</emphasis> in earlier versions of OpenStack Compute, some command-line tools use <literal>--project_id</literal> instead of <literal>--tenant-id</literal> or <literal>--os-tenant-id</literal> to refer to a tenant ID."
msgstr ""
#: ./doc/src/docbkx/common/keystone-concepts.xml:227(para)
msgid "A <emphasis>role</emphasis> 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 <filename>/etc/<replaceable>[SERVICE_CODENAME]</replaceable>/policy.json</filename> controls what users are allowed to do for a given service. For example, <filename>/etc/nova/policy.json</filename> specifies the access policy for the Compute service, <filename>/etc/glance/policy.json</filename> specifies the access policy for the Image service, and <filename>/etc/keystone/policy.json</filename> specifies the access policy for the Identity service."
msgstr ""
#: ./doc/src/docbkx/common/keystone-concepts.xml:289(para)
msgid "The default <filename>policy.json</filename> files in the Compute, Identity, and Image service recognize only the <literal>admin</literal> role: all operations that do not require the <literal>admin</literal> 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 <filename>/etc/nova/policy.json</filename> 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 <filename>/etc/nova/policy.json</filename> 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 <literal>compute-user</literal> role in a particular tenant, we would add <literal>\"role:compute-user\"</literal>, 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 <emphasis>nova</emphasis>, for the Compute service) and a special service tenant, which is called <emphasis>service</emphasis>."
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 <literal>apache-httpd</literal> 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 <literal>REMOTE_USER</literal> 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 <literal>apache-httpd</literal>."
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: <placeholder-1/>"
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 <literal>--meta</literal> 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. <placeholder-1/>"
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 <literal>metadata</literal> line: <placeholder-1/>"
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 "<placeholder-1/> / <placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/common/nova_cli_startstop.xml:9(para)
msgid "There are two methods for stopping and starting an instance: <placeholder-1/>"
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 "<placeholder-1/> 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 "<placeholder-1/> 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: <placeholder-1/>"
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 <code>m1.tiny</code> flavor and resize it to <code>m1.small</code>."
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 <placeholder-1/> 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 <placeholder-2/> 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 <literal>tinyimage</literal>, which is experiencing an error condition.<placeholder-1/>"
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 <link href=\"https://docs.djangoproject.com/en/dev/topics/http/sessions/\">Django’s sessions framework</link> 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 <literal>mysql&gt;</literal> prompt to exit MySQL."
msgstr ""
#: ./doc/src/docbkx/common/dashboard_sessions.xml:83(para)
msgid "In the <filename>/etc/openstack-dashboard/local_settings.py</filename> file, change these options:"
msgstr ""
#: ./doc/src/docbkx/common/dashboard_sessions.xml:100(para)
msgid "After configuring the <filename>local_settings.py</filename> as shown, you can run the <placeholder-1/> 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 <link href=\"https://docs.djangoproject.com/en/dev/topics/http/sessions/#using-cookie-based-sessions\">cookie-based sessions.</link>"
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 <filename>glance-api.conf</filename> 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 <filename>glance-api.conf</filename> 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 <filename>/etc/nova/nova.conf</filename>."
msgstr ""
#: ./doc/src/docbkx/common/compute-options.xml:12(para)
msgid "The configuration file is in <link href=\"https://en.wikipedia.org/wiki/INI_file\">INI file format</link>, with options specified as <literal>key=value</literal> pairs, grouped into sections. Almost all of the configuration options are in the <literal>DEFAULT</literal> section. Here's a brief example:<placeholder-1/>"
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 <literal>true</literal> or <literal>false</literal> . Example:<placeholder-1/>"
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:<placeholder-1/>"
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: <placeholder-1/>"
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:<placeholder-1/>"
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:<placeholder-1/>"
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:<placeholder-1/>"
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:<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/compute-options.xml:77(para)
msgid "Nova options should <emphasis>not</emphasis> 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 <literal>cells</literal> section is used for options for configuring cells functionality. See the <link linkend=\"ch_cells\">Cells</link> 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 <literal>conductor</literal> 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 <literal>trusted_computing</literal> 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.<placeholder-1/>"
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 <literal>$</literal>. Consider the following example where <literal>my_ip</literal> is defined and then <literal>$my_ip</literal> is used as a variable.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/compute-options.xml:135(para)
msgid "If you need a value to contain the <literal>$</literal> symbol, escape it by doing <literal>$$</literal>. For example, if your LDAP DNS password was <literal>$xkj432</literal>, you would do:<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/compute-options.xml:139(para)
msgid "The Compute code uses Python's <literal>string.Template.safe_substitute()</literal> method to implement variable substitution. For more details on how variable substitution is resolved, see <link href=\"http://docs.python.org/2/library/string.html#template-strings\">Python documentation on template strings</link> and <link href=\"http://www.python.org/dev/peps/pep-0292/\">PEP 292</link>."
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:<placeholder-1/>"
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 <placeholder-1/> command-line tool. To specify an alternate location for the configuration file, pass the <literal>--config-file <replaceable>/path/to/nova.conf</replaceable></literal> argument when starting a nova-* service or calling <placeholder-2/>."
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:<placeholder-1/>"
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: <link href=\"http://technet.microsoft.com/en-us/library/hh831823.aspx\">http://technet.microsoft.com/en-us/library/hh831823.aspx</link>"
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: <link href=\"http://technet.microsoft.com/en-us/library/jj134199.aspx\">http://technet.microsoft.com/en-us/library/jj134199.aspx</link>"
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 <filename>nova.conf</filename> on the Hyper-V compute node:<placeholder-1/>"
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\"&gt;"
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:<placeholder-1/>"
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 <filename>nova.conf</filename> file must be placed in <literal>C:\\etc\\nova</literal> for running OpenStack on Hyper-V. Below is a sample <filename>nova.conf</filename> 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 <literal>nova-manage service list</literal> 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 <placeholder-1/>"
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 <literal>BUILD</literal> 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 <literal>id</literal> 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 <literal>adminPass</literal> 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 <filename>/etc/nova/nova.conf</filename> and restart the nova-compute service: <placeholder-1/> 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: <placeholder-1/>"
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 <filename>/etc/nova/nova.conf</filename>: <placeholder-1/>"
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 "<emphasis role=\"bold\">Xen</emphasis> 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 "<emphasis role=\"bold\">Xen Cloud Platform (XCP)</emphasis> 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 <link href=\"http://packages.ubuntu.com/precise/xcp-xapi\">xcp-xapi</link> 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 "<emphasis role=\"bold\">Citrix XenServer</emphasis> 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 <link href=\"http://wiki.xen.org/wiki/XCP/XenServer_Feature_Matrix\"> XCP Feature Matrix</link>."
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 <emphasis role=\"bold\">xapi</emphasis>."
msgstr ""
#: ./doc/src/docbkx/common/introduction-to-xen.xml:94(para)
msgid "The API shared between XCP and XenServer is called <emphasis role=\"bold\">XenAPI</emphasis>. 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 <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/sdk.html#object_model_overview\"> XenAPI Object Model Overview</link> 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 <emphasis role=\"bold\">driver domains</emphasis> and <emphasis role=\"bold\">stub domains</emphasis>. 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 <emphasis role=\"bold\">paravirtualized (PV)</emphasis> or <emphasis role=\"bold\">hardware virtualized (HVM)</emphasis>. 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) <emphasis role=\"bold\">must</emphasis> 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: <placeholder-1/>"
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: <placeholder-1/>"
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: <placeholder-1/>"
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 <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#sys_requirements\"> an appropriate server</link>. 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: <placeholder-1/> When installing many servers, you may find it easier to perform <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#pxe_boot_install\"> PXE boot installations of XenServer or XCP</link>. You can also package up any post install changes you wish to make to your XenServer by <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/supplemental_pack_ddk.html\"> creating your own XenServer supplimental pack</link>."
msgstr ""
#: ./doc/src/docbkx/common/introduction-to-xen.xml:262(para)
msgid "It is also possible to get XCP by installing the <emphasis role=\"bold\">xcp-xenapi</emphasis> 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: <link href=\"http://wiki.xen.org/wiki/Project_Kronos\"> http://wiki.xen.org/wiki/Project_Kronos </link>"
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 <link href=\"http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-resize.html#xenserver-resize\"> Configuring Resize</link> 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: <placeholder-1/>"
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: <placeholder-1/> 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 <link href=\"https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md\"> DevStack and XenServer Readme</link>. More information on the first step can be found in the <link href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst\"> XenServer mutli-tenancy protection doc</link>. More information on how to install the XenAPI plugins can be found in the <link href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README\"> XenAPI plugins Readme</link>."
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. <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/introduction-to-xen.xml:350(para)
msgid "Next, locate the uuid of the NFS ISO library: <placeholder-1/>"
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\". <placeholder-1/>"
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 <placeholder-1/>"
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 <literal>disk-format=iso</literal>, and boot them in OpenStack Compute. <placeholder-1/>"
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:<link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/\"> http://docs.vmd.citrix.com/XenServer</link>."
msgstr ""
#: ./doc/src/docbkx/common/introduction-to-xen.xml:386(para)
msgid "What is Xen? by Xen.org: <link href=\"http://xen.org/files/Marketing/WhatisXen.pdf\"> http://xen.org/files/Marketing/WhatisXen.pdf</link>."
msgstr ""
#: ./doc/src/docbkx/common/introduction-to-xen.xml:392(para)
msgid "Xen Hypervisor project: <link href=\"http://xen.org/products/xenhyp.html\"> http://xen.org/products/xenhyp.html</link>."
msgstr ""
#: ./doc/src/docbkx/common/introduction-to-xen.xml:398(para)
msgid "XCP project: <link href=\"http://xen.org/products/cloudxen.html\"> http://xen.org/products/cloudxen.html</link>."
msgstr ""
#: ./doc/src/docbkx/common/introduction-to-xen.xml:404(para)
msgid "Further XenServer and OpenStack information: <link href=\"http://wiki.openstack.org/XenServer\"> http://wiki.openstack.org/XenServer</link>."
msgstr ""
#: ./doc/src/docbkx/common/introduction-to-xen.xml:376(para)
msgid "Here are some of the resources available to learn more about Xen: <placeholder-1/>"
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 (<filename>etc/keystone.conf</filename>), 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 <link href=\"http://memcached.org/\">memcached</link> with Keystone - e.g. using the memcache token driver or the <literal>auth_token</literal> 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 <literal>user_crud_extension</literal> filter, insert it after the <literal>*_body</literal> middleware and before the <literal>public_service</literal> app in the public_api WSGI pipeline in <filename>keystone.conf</filename> 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 <link href=\"http://pythonpaste.org/\">Paste</link>, a common system used to configure python WSGI based applications. In addition to the paste config entries, general configuration values are stored under <literal>[DEFAULT]</literal>, <literal>[sql]</literal>, <literal>[ec2]</literal> 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 "<literal>[DEFAULT]</literal> - general configuration"
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:79(para)
msgid "<literal>[sql]</literal> - optional storage backend configuration"
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:85(para)
msgid "<literal>[ec2]</literal> - Amazon EC2 authentication driver configuration"
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:91(para)
msgid "<literal>[s3]</literal> - Amazon S3 authentication driver configuration."
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:97(para)
msgid "<literal>[identity]</literal> - identity system driver configuration"
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:103(para)
msgid "<literal>[catalog]</literal> - service catalog driver configuration"
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:109(para)
msgid "<literal>[token]</literal> - token driver configuration"
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:114(para)
msgid "<literal>[policy]</literal> - policy system driver configuration for RBAC"
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:120(para)
msgid "<literal>[signing]</literal> - cryptographic signatures for PKI based tokens"
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:126(para)
msgid "<literal>[ssl]</literal> - SSL configuration"
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:131(para)
msgid "The configuration file is expected to be named <filename>keystone.conf</filename>. When starting Identity, you can specify a different configuration file to use with <literal>--config-file</literal>. If you do <emphasis role=\"strong\">not</emphasis> 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 <literal>[DEFAULT]</literal> section of the <filename>keystone.conf</filename> file under <literal>log_config</literal>. If you wish to route all your logging through syslog, set <literal>use_syslog=true</literal> option in the <literal>[DEFAULT]</literal> 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 <filename>etc/logging.conf.sample</filename>. 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 <filename>etc/keystone.conf</filename> 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 <filename>nova.conf</filename>. 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 <filename>nova.conf</filename> 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 <literal>stats_monitoring</literal> 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 <literal>stats_reporting</literal> filter and including it near the end of your <literal>admin_api</literal> WSGI pipeline (After <literal>*_body</literal> middleware and before <literal>*_extension</literal> 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 <filename>keystone.conf</filename> file as described above. One of these wsgi 'servers' is <literal>admin</literal> (the administration API) and the other is <literal>main</literal> (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 "<placeholder-1/> 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 "<literal>db_sync</literal>: Sync the database."
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:308(para)
msgid "<literal>import_nova_auth</literal>: 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 "<literal>--endpoint SERVICE_ENDPOINT</literal> : allows you to specify the keystone endpoint to communicate with. The default endpoint is <link href=\"http://localhost:35357/v2.0'\">http://localhost:35357/v2.0'</link>"
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:351(para)
msgid "<literal>--token SERVICE_TOKEN</literal> : 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 "<literal>--username OS_USERNAME</literal> : allows you to specify the administrator username"
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:368(para)
msgid "<literal>--password OS_PASSWORD</literal> : Your administrator password"
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:374(para)
msgid "<literal>--tenant_name OS_TENANT_NAME</literal> : Name of your tenant"
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:380(para)
msgid "<literal>--auth_url OS_AUTH_URL</literal> : url of your keystone auth server, for example <link href=\"http://localhost:5000/v2.0'\">http://localhost:5000/v2.0'</link>"
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 <literal>keystone</literal> client is set up to expect commands in the general form of <literal>keystone</literal><literal>command</literal><literal>argument</literal>, followed by flag-like keyword arguments to provide additional (often optional) information. For example, the command <literal>user-list</literal> and <literal>tenant-create</literal> 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 <filename>keystone.conf</filename> file under the section <literal>[DEFAULT]</literal>. 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 <literal>auth_token</literal> 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 <link linkend=\"adding-users-tenants-and-roles-with-python-keystoneclient\">configuration section</link> 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 <emphasis role=\"strong\">must</emphasis> 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 <literal>etc/default_catalog.templates</literal>. 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, <filename>/etc/swift/proxy-server.conf</filename>."
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 <emphasis>uid</emphasis> field should probably be <emphasis>uidNumber</emphasis> and <emphasis>username</emphasis> field either <emphasis>uid</emphasis> or <emphasis>cn</emphasis>. 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 <emphasis>user_enabled_mask</emphasis> is different from 0, it gets the value from the field <emphasis>user_enabled_attribute</emphasis> and it makes an ADD operation with the value indicated on <emphasis>user_enabled_mask</emphasis> 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 <emphasis>enabled_nomask</emphasis>. 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 <emphasis>user_enabled_mask</emphasis> 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 "<filename>ca.pem</filename> - Certificate Authority chain to validate against."
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1482(para)
msgid "<filename>keystone.pem</filename> - Public certificate for Keystone server."
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1486(para)
msgid "<filename>middleware.pem</filename> - Public and private certificate for Keystone middleware/client."
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1490(para)
msgid "<filename>cakey.pem</filename> - Private key for the CA."
msgstr ""
#: ./doc/src/docbkx/common/ch_identity_mgmt.xml:1494(para)
msgid "<filename>keystonekey.pem</filename> - 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 <literal>examples/ssl</literal> directory with the Keystone distribution for testing. Here is the description of each of them and their purpose: <placeholder-1/> 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 <literal>etc/keystone.conf</literal> file accordingly under the <literal>[ssl]</literal> section. SSL configuration example using the included sample certificates: <placeholder-1/> Example: <placeholder-2/>"
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 <link href=\"http://www.prestonlee.com/2012/05/09/how-to-custom-brand-the-openstack-horizon-dashboard/\">blog post by Preston Lee</link>."
msgstr ""
#: ./doc/src/docbkx/common/dashboard_customizing.xml:8(para)
msgid "When deploying OpenStack on <link href=\"http://www.ubuntu.com/\">Ubuntu Server</link> 12.04, you can have the <literal>openstack-dashboard</literal> package installed to provide the web-based “Horizon” GUI component. Canonical also provides an <literal>openstack-dashboard-ubuntu-theme</literal> package that brands the Python-based Django GUI."
msgstr ""
#: ./doc/src/docbkx/common/dashboard_customizing.xml:14(para)
msgid "<link href=\"http://horizon.openstack.org/topics/branding.html\">The Horizon documents briefly mention branding customization</link> 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 <filename>/etc/openstack-dashboard/local_settings.py</filename>: <code>SITE_BRANDING = \"Example, Inc. Cloud\"</code>"
msgstr ""
#: ./doc/src/docbkx/common/dashboard_customizing.xml:51(para)
msgid "Upload your new graphic files to: <placeholder-1/>"
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: <placeholder-1/>"
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. <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/dashboard_customizing.xml:94(para)
msgid "Open the following HTML template in an editor: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/dashboard_customizing.xml:100(emphasis)
msgid "&lt;link href='{{ STATIC_URL }}dashboard/css/custom.css' media='screen' rel='stylesheet' /&gt;"
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 <emphasis>bold</emphasis>.) <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/dashboard_customizing.xml:103(para)
msgid "Restart apache just for good measure: <code os=\"ubuntu\">sudo service apache2 restart</code><code os=\"centos;fedora;rhel\">sudo service httpd restart</code>"
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: <link href=\"http://www.redbooks.ibm.com/abstracts/sg247940.html\"> IBM PowerVM Virtualization Introduction and Configuration</link>."
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 <filename>/etc/nova/nova.conf</filename>: <placeholder-1/>"
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 <link href=\"http://wiki.openstack.org/HypervisorSupportMatrix\">hypervisor support matrix</link> for details."
msgstr ""
#: ./doc/src/docbkx/common/lxc.xml:25(para)
msgid "To enable LXC, ensure the following options are set in <filename>/etc/nova/nova.conf</filename> on all hosts running the <systemitem class=\"service\">nova-compute</systemitem> service.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/lxc.xml:30(para)
msgid "On Ubuntu 12.04, enable LXC support in OpenStack by installing the <literal>nova-compute-lxc</literal> 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 "<literal>User Data</literal> 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 <link href=\"https://help.ubuntu.com/community/CloudInit\">cloudinit</link> system is an open source package from Ubuntu that handles early initialization of a cloud instance that makes use of this <literal>user data</literal>."
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 <literal>--user-data &lt;user-data-file&gt;</literal> for example:<placeholder-1/>"
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 <literal>--user-data <replaceable>/path/to/filename</replaceable></literal> option when calling <placeholder-1/>. 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 <link href=\"http://launchpad.net/cloud-init\">Launchpad</link>. 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 <literal>ubuntu</literal> account by default on Ubuntu instances, the <literal>ec2-user</literal> 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 <link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/userdata.txt\">doc/userdata.txt</link> file the <link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/files/head:/doc/examples/\">examples</link> directory as well as the <link href=\"https://help.ubuntu.com/community/CloudInit\">Ubuntu community documentation</link> 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 <literal>#!</literal>)"
msgstr ""
#: ./doc/src/docbkx/common/user-data.xml:82(para)
msgid "Cloud config files (starts with <literal>#cloud-config</literal>)"
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:<placeholder-1/>"
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 <literal>#!</literal> in order for cloud-init to recognize it as a shell script. Here's an example of a script that creates an account called <literal>clouduser</literal>."
msgstr ""
#: ./doc/src/docbkx/common/user-data.xml:93(para)
msgid "<placeholder-1/>Sending a shell script as user data has a similar effect to writing an <filename>/etc/rc.local</filename> 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 <literal>#cloud-config</literal> 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 <filename>/etc/hosts</filename> 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 <link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config-puppet.txt\">doc/examples/cloud-config-puppet.txt</link>, would configure the instance to contact a Puppet server at puppetmaster.example.org and verify its identity using a certificate. <placeholder-1/>"
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 <link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config-chef.txt\">doc/examples/cloud-config/chef.txt</link>, 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.<placeholder-1/>"
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 <literal>min_part_hours</literal> 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 <literal>swift-ring-builder account.builder write_ring</literal> 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 <literal>_replica2part2dev_id</literal> and <literal>devs</literal> 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 <literal>container.ring.gz</literal> and <literal>object.ring.gz</literal>, 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 <link href=\"https://github.com/openstack-dev/devstack/blob/master/exercises/boot_from_volume.sh\">exercises/boot_from_volume.sh</link>. This example assumes that you have a running instance with a 1GB volume mounted at <literal>/dev/vdc</literal>. These commands will make the mounted volume bootable using a CirrOS image. As root:<placeholder-1/>"
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 <placeholder-1/> command with use the <literal>--block-device-mapping</literal> flag. The output for <placeholder-2/> shows the following documentation about this flag:<placeholder-3/>"
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 <filename>/dev/<replaceable>dev_name</replaceable></filename>. This value is typically <literal>vda</literal>."
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 <placeholder-1/>."
msgstr ""
#: ./doc/src/docbkx/common/boot_from_volume.xml:66(para)
msgid "This is either <literal>snap</literal>, which means that the volume was created from a snapshot, or anything other than <literal>snap</literal> (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 <literal>True</literal> or <literal>1</literal>. False can be specified as <literal>False</literal> or <literal>0</literal>."
msgstr ""
#: ./doc/src/docbkx/common/boot_from_volume.xml:47(para)
msgid "The command arguments are:<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/boot_from_volume.xml:92(para)
msgid "Because of bug <link href=\"https://bugs.launchpad.net/nova/+bug/1008622\">#1008622</link>, 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 "<placeholder-1/>The following example will attempt boot from volume with ID=<literal>13</literal>, it will not delete on terminate. Replace the <literal>--image</literal> flag with a valid image on your system, and the <literal>--key-name</literal> with a valid keypair name:<placeholder-2/>"
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 <placeholder-1/> 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 "<placeholder-1/> 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 <literal>--password &lt;pwd&gt;</literal> 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. <placeholder-1/>"
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 <link href=\"http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-migrations.html\">Configure migrations guide</link> 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:<placeholder-1/> will create a key named <literal>mykey</literal> which you can associate with instances. Save the file <filename>mykey.pem</filename> to a secure location as it will allow root access to instances the <literal>mykey</literal>key 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:<placeholder-1/> will upload the existing public key <literal>mykey.pub</literal> and associate it with the name <literal>mykey</literal>. 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 <literal>--key_name mykey</literal> to your command line for example:<placeholder-1/>"
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 <literal>cirros</literal> as the login user. They are hosted under the CirrOS project on Launchpad and<link href=\"https://launchpad.net/cirros/+download\">are available for download</link>."
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 <link href=\"https://launchpad.net/cirros/trunk/0.3.0/+download/cirros-0.3.0-x86_64-disk.img\">cirros-0.3.0-x86_64-disk.img</link>"
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 <link href=\"http://uec-images.ubuntu.com\">official set of Ubuntu-based images</link> These accounts use <literal>ubuntu</literal> 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 <link href=\"http://uec-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img\">precise-server-cloudimg-amd64-disk1.img</link>."
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 <link href=\"http://berrange.fedorapeople.org/images\">http://berrange.fedorapeople.org/images </link>."
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:88(para)
msgid "A 64-bit QCOW2 image for Fedora 16, <link href=\"http://berrange.fedorapeople.org/images/2012-02-29/f16-x86_64-openstack-sda.qcow2\"> f16-x86_64-openstack-sda.qcow2</link>, 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 "<link href=\"http://susestudio.com\">SUSE Studio</link> 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 <link href=\"http://susestudio.com/a/YRUrwO/testing-instance-for-openstack-opensuse-121\">a test openSUSE 12.1 (JeOS) image</link>."
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 <link href=\"https://github.com/rackerjoe/oz-image-build\">rackerjoe/oz-image-build on Github</link>."
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 "<link href=\"http://aeolusproject.org/oz.html\">Oz</link> 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 <link href=\"https://github.com/rackerjoe/oz-image-build\">rackerjoe/oz-image-build on Github</link> for their Oz templates. For an example from the Fedora Project wiki, see <link href=\"https://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova#Building_an_Image_With_Oz\"> Building an image with Oz</link>."
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 "<link href=\"https://launchpad.net/vmbuilder\">VMBuilder</link> can be used to create virtual machine images for different hypervisors."
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:132(para)
msgid "The <link href=\"https://help.ubuntu.com/12.04/serverguide/jeos-and-vmbuilder.html\"> Ubuntu 12.04 server guide</link> 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 "<link href=\"http://boxgrinder.org\">BoxGrinder</link> 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 "<link href=\"https://github.com/jedi4ever/veewee\"> VeeWee</link> is often used to build <link href=\"http://vagrantup.com\">Vagrant</link> 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 <link href=\"https://github.com/jedi4ever/veewee/blob/master/doc/definition.md\">doc/definition.md</link> and <link href=\"https://github.com/jedi4ever/veewee/blob/master/doc/template.md\">doc/template.md</link> 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 "<link href=\"http://imgfac.org/\">imagefactory</link> is a new tool from the <link href=\"http://www.aeolusproject.org/\">Aeolus</link> 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 ""
#. <para>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 <link linkend="instance-building-blocks-flavors"
#. >flavors</link>. For example, if your image was created with a 5 GB disk, and
#. you launch an instance with a flavor of <literal>m1.small</literal>, 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.</para>
#: ./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:<placeholder-1/>"
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 <filename>/</filename>."
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:206(para)
msgid "Ubuntu cloud images and cirros images use a tool called <placeholder-1/> that is part of the <link href=\"http://launchpad.net/cloud-utils\">cloud-utils</link> 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 "<literal>auto_disk_config=True</literal> in <filename>nova.conf</filename>."
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:<placeholder-1/>"
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.<placeholder-1/>"
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. <link href=\"http://isoredirect.centos.org/centos/6/isos/x86_64/\">64-bit ISO images of CentOS 6.2</link> 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 <placeholder-1/> command: <placeholder-2/>"
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 <placeholder-1/> command: <placeholder-2/>"
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 <literal>:N</literal> correspond to TCP port 5900+N, so that <literal>:0</literal> corresponds to port 5900). Check which ones are currently in use with the <placeholder-1/> command, as root:<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:263(para)
msgid "This shows that vnc displays <literal>:0</literal> and <literal>:1</literal> are in use. In this example, we will use VNC display <literal>:2</literal>."
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 <filename>/tmp/file.mon</filename>, but make sure it doesn't exist yet. If it does, use a different file name for the <literal>MONITOR</literal> variable defined below:<placeholder-1/>"
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., <link href=\"http://projects.gnome.org/vinagre/\">Vinagre</link> on Gnome, <link href=\"http://userbase.kde.org/Krdc\">Krdc</link> on KDE, xvnc4viewer from <link href=\"http://www.realvnc.com\">RealVNC</link>, xtightvncviewer from <link href=\"http://www.tightvnc.com\">TightVNC</link>) 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: <literal>mirror.umd.edu</literal> (consider using other mirrors as an alternative)"
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:296(para)
msgid "CentOS directory: <literal>centos/6.2/os/x86_64</literal>"
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. <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:299(para)
msgid "See <link href=\"http://www.centos.org/modules/tinycontent/index.php?id=30\">CentOS mirror page</link> 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 (<filename>/boot</filename>, <filename>/</filename>, swap). The simplest approach is to create a single ext4 partition, mounted to \"<literal>/</literal>\"."
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:<placeholder-1/>"
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 <filename>/etc/sysconfig/network-scripts/ifcfg-eth0</filename> during the instance process. However, each time the image boots up, the virtual ethernet card will have a different MAC address, so this information must be deleted from the configuration file."
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:347(para)
msgid "Edit <filename>/etc/sysconfig/network-scripts/ifcfg-eth0</filename> and remove the <literal>HWADDR=</literal> 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 <link href=\"http://koji.fedoraproject.org/koji/packageinfo?packageID=12620\">cloud-init RPM</link> , which is a port of the Ubuntu <link href=\"https://launchpad.net/cloud-init\">cloud-init</link> 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 <filename>/etc/rc.local</filename> 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:<placeholder-1/>"
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 <filename>/etc/cloud/cloud.cfg</filename> 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:<placeholder-1/>"
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 <filename>/etc/rc.local</filename> 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 <emphasis role=\"italic\">user data</emphasis>, 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 <link href=\"http://docs.amazonwebservices.com/AWSEC2/2009-04-04/UserGuide/AESDG-chapter-instancedata.html\">Using Instance Metadata</link> 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:<placeholder-1/>"
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., <filename>/dev/loop0</filename>, <filename>/dev/loop1</filename>). To identify the next unused loop device, as root:<placeholder-1/>In the example above, <filename>/dev/loop0</filename> is available for use. Associate it to the image using <placeholder-2/>, and expose the partitions as device files using <placeholder-3/>, 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:<placeholder-1/>"
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:<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:437(para)
msgid "You can now modify the files in the image by going to <filename>/mnt/image</filename>. When done, unmount the image and release the loop device, as root:<placeholder-1/>"
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 <literal>max_part=0</literal>, 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:<placeholder-1/>"
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:<placeholder-1/><placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:454(para)
msgid "Connect your image to one of the network block devices (e.g., <filename>/dev/nbd0</filename>, <filename>/dev/nbd1</filename>). In this example, we use <filename>/dev/nbd3</filename>. As root:<placeholder-1/>"
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 <placeholder-1/> command will fail silently, and the <filename>/dev/nbd3p{1,2,3}</filename> 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:<placeholder-1/><placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:473(para)
msgid "You can now modify the files in the image by going to <filename>/mnt/image</filename>. When done, unmount the image and release the network block device, as root:<placeholder-1/>"
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 "<literal>--image</literal>: the name or ID of the image we want to launch, as shown in the output of <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:548(para)
msgid "<literal>--flavor</literal>: 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 <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:554(para)
msgid "<literal>-key_name</literal>: 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: <literal>cubswin:)</literal>"
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 <placeholder-1/> 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 <placeholder-2/>. 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 <link href=\"https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1061665\">1061665</link> 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 <link href=\"http://www.csscorp.com/\">CSS Corp Open Source Services</link>"
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 <link href=\"http://docs.openstack.org/trunk/openstack-compute/admin/content/starting-images.html\">http://docs.openstack.org/trunk/openstack-compute/admin/content/starting-images.html</link> 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 &amp; 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 <link href=\"http://koji.fedoraproject.org/koji/packageinfo?packageID=12620\">cloud-initRPM </link> , which is a port of the Ubuntu cloud-init package."
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:916(para)
msgid "Install <link href=\"https://github.com/yahoo/Openstack-Condense\">Condenser</link>, 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:<placeholder-1/>"
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 <placeholder-1/> 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 <placeholder-1/> 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 : <placeholder-1/>"
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 <filename>nova.conf</filename>: <placeholder-1/>"
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 <placeholder-1/> 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 : <placeholder-1/><placeholder-2/> Based on the output, we run : <placeholder-3/> The command will then perform the image creation (by creating qemu snapshot) and will automatically upload the image to your repository. <placeholder-4/>"
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. <placeholder-1/> will allow you to check the progress : <placeholder-2/><placeholder-3/>"
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 :<placeholder-1/>"
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 : <placeholder-1/>"
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 <placeholder-1/> 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:<placeholder-2/>"
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 "<replaceable>fromserver:port</replaceable>: the location of the master glance instance"
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1257(para)
msgid "<replaceable>toserver:port</replaceable>: 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 <replaceable>fromserver </replaceable>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 "<replaceable>server:port</replaceable>: the location of the glance instance."
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1280(para)
msgid "<replaceable>path</replaceable>: a directory on disk to contain the data."
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1274(para)
msgid "<placeholder-1/>Do the same thing as <placeholder-2/>, 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 <placeholder-3/> 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 "<replaceable>path</replaceable>: 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 <placeholder-1/> and <placeholder-2/> 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 "<replaceable>fromserver:port</replaceable>: the location of the master glance instance."
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1318(para)
msgid "<replaceable> toserver:port</replaceable>: the location of the slave glance instance."
msgstr ""
#: ./doc/src/docbkx/common/ch_image_mgmt.xml:1312(para)
msgid "<placeholder-1/><placeholder-2/>The <placeholder-3/> command will show you the differences between the two servers, which is effectively a dry run of the <placeholder-4/> 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 "<placeholder-1/><placeholder-2/>The <placeholder-3/> command will tell you how much disk is going to be used by image data in either a <placeholder-4/> or a <placeholder-5/>. 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 <literal>primary.example.com</literal> with glance-api service running on port <literal>9292</literal> (the default port) and you want to replicate its contents to a secondary glance service running on a node called <literal>secondary.example.com</literal>, 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 <literal>glance-replicator livecopy</literal> 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 <filename>primary.openrc</filename> and one for your secondary cloud called <filename>secondary.openrc</filename>.<placeholder-1/>"
msgstr ""
#. When image changes, this message 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 <link href=\"http://www.vmware.com/support/developer/vc-sdk/\">http://www.vmware.com/support/developer/vc-sdk/</link> and copy it into <filename>/var/lib/tomcat6/webapps</filename>. You should ensure that the WSDL is available, in eg <filename> /var/lib/tomcat6/webapps/vmware/SDK/wsdl/vim25/vimService.wsdl</filename>."
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:<placeholder-1/>"
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 <link href=\"https://github.com/OpenAttestation/OpenAttestation\">Open Attestation</link> 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 <literal>trusted_computing</literal> section of nova.conf. Specify the following parameters in this section.<placeholder-1/>Add the following lines to <filename>/etc/nova/nova.conf</filename> in the <literal>DEFAULT</literal> and <literal>trusted_computing</literal> sections to enable scheduling support for Trusted Compute Pools, and edit the details of the <literal>trusted_computing</literal> section based on the details of your attestation service.<placeholder-2/>"
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 <placeholder-1/> 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 <placeholder-1/> 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 <code>virsh create libvirt.xml</code> 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 <placeholder-1/> command. This will reset it to an error state, which you can then delete. For example:<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/common/support-compute.xml:47(para)
msgid "You can also use the <literal>--active</literal> to force the instance back into an active state instead of an error state, for example:<placeholder-1/>"
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 <literal>libvirt_injection_partition</literal> 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 <literal>disk format</literal> and <literal>container format</literal> 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 "<emphasis>OpenStack Object Storage is not used like a traditional hard drive.</emphasis> 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 "<emphasis>The OpenStack Image Service is used to manage the virtual machine images in an OpenStack cluster, not store them. </emphasis> 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 "<emphasis>OpenStack Object Storage can function on its own.</emphasis> 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: <placeholder-1/>"
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 <link href=\"https://launchpad.net/ceilometer\">Ceilometer</link> project, which is currently under development. You may also wish to consider installing tools such as <link href=\"http://ganglia.info/\">Ganglia</link> or <link href=\"http://graphite.wikidot.com/\">Graphite</link> 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 <placeholder-1/> command to list the hosts and the nova-related services that are running on them:<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/common/nova_cli_usage_statistics.xml:31(para)
msgid "Use the <placeholder-1/> 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.<placeholder-1/>"
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 <placeholder-1/> command to retrieve CPU, memory, I/O and network statistics from an instance:<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/common/nova_cli_usage_statistics.xml:76(para)
msgid "Use the <placeholder-1/> command to get summary statistics for each tenant:<placeholder-2/>"
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 <link linkend=\"metadata-service\">metadata service</link> 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 <literal>--config-drive=true</literal> parameter when calling <placeholder-1/>. 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 <filename>/etc/nova/nova.conf</filename>: <placeholder-1/>"
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 <literal>--config-drive=true</literal> flag to the <placeholder-1/> 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 <literal>config-2</literal>. If your guest OS supports accessing disk by label, you should be able to mount the config drive as the <filename>/dev/disk/by-label/config-2</filename> device. For example:<placeholder-1/>"
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 <literal>udev</literal>, then the <filename>/dev/disk/by-label</filename> directory will not be present. The <placeholder-1/> 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 <filename>/dev/vdb</filename>:"
msgstr ""
#: ./doc/src/docbkx/common/config-drive.xml:62(para)
msgid "<placeholder-1/>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 <placeholder-1/>. 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 <filename>ec2</filename> 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 <filename>openstack</filename> 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 <filename>openstack/2012-08-10/meta_data.json</filename>, <filename>openstack/latest/meta_data.json</filename> (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 <literal>--file /etc/network/interfaces=/home/myuser/instance-interfaces</literal> argument passed to the original <placeholder-1/> command. The contents of this file are contained in the file <filename>openstack/content/0000</filename> file on the config drive, and the path is specified as <filename>/etc/network/interfaces</filename> in the <filename>meta_data.json</filename> 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 <filename>ec2/2009-04-04/meta-data.json</filename>, <filename>latest/meta-data.json</filename> (these two files are identical) formatted to improve readbility:"
msgstr ""
#: ./doc/src/docbkx/common/config-drive.xml:182(para)
msgid "The files <filename>openstack/2012-08-10/user_data</filename>, <filename>openstack/latest/user_data</filename>, <filename>ec2/2009-04-04/user-data</filename>, and <filename>ec2/latest/user-data</filename>, will only be present if the <literal>--user-data</literal> flag was passed to <placeholder-1/> 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 <filename>/etc/nova/nova.conf</filename>:"
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 <filename>/etc/nova/nova.conf</filename> 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 &amp; 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 <filename>MyKey.pem</filename> 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 <placeholder-1/> command to ensure that the keypair is known to SSH:<placeholder-2/>"
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:<placeholder-1/>"
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, <filename>example.com/nova/v1/foobar</filename>."
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 <literal>openstack-manuals</literal> 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 <EMAIL>, YEAR1, YEAR2
#: ./doc/src/docbkx/common/glossary/openstack-glossary.xml:0(None)
msgid "translator-credits"
msgstr ""
View Git Blame Copy Permalink