msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-11-27 06:12+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: ./doc/user-guide/section_cli_nova_reboot.xml:7(title)
msgid "Reboot an instance"
msgstr ""

#: ./doc/user-guide/section_cli_nova_reboot.xml:8(para)
msgid "You can soft or hard reboot a running instance. A soft reboot attempts a graceful shut down and restart of the instance. A hard reboot power cycles the instance."
msgstr ""

#: ./doc/user-guide/section_cli_nova_reboot.xml:11(para)
msgid "By default, when you reboot a server, it is a soft reboot."
msgstr ""

#: ./doc/user-guide/section_cli_nova_reboot.xml:12(replaceable) ./doc/user-guide/section_cli_nova_reboot.xml:14(replaceable) ./doc/user-guide/app_cheat_sheet.xml:176(replaceable)
msgid "SERVER"
msgstr ""

#: ./doc/user-guide/section_cli_nova_reboot.xml:13(para)
msgid "To perform a hard reboot, pass the <parameter>--hard</parameter> parameter, as follows:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:7(title)
msgid "Launch instances"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:8(para) ./doc/user-guide/section_dashboard_launch_instances.xml:8(para)
msgid "Instances are virtual machines that run inside the cloud."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:10(para)
msgid "Before you can launch an instance, gather the following parameters:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:14(para)
msgid "The <emphasis role=\"bold\">instance source</emphasis> can be an image, snapshot, or block storage volume that contains an image or snapshot."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:19(para)
msgid "A <emphasis role=\"bold\">name</emphasis> for your instance."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:22(para)
msgid "The <emphasis role=\"bold\">flavor</emphasis> for your instance, which defines the compute, memory, and storage capacity of nova computing instances. A flavor is an available hardware configuration for a server. It defines the size of a virtual server that can be launched."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:30(para)
msgid "Any <emphasis role=\"bold\">user data</emphasis> files. A user data file is a special key in the metadata service that holds a file that cloud-aware applications in the guest instance can access. For example, one application that uses user data is the <link href=\"https://help.ubuntu.com/community/CloudInit\">cloud-init</link> system, which is an open-source package from Ubuntu that is available on various Linux distributions and that handles early initialization of a cloud instance."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:43(para)
msgid "Access and security credentials, which include one or both of the following credentials:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:47(para)
msgid "A <emphasis role=\"bold\">key pair</emphasis> for your instance, which are SSH credentials that are injected into images when they are launched. For the key pair to be successfully injected, the image must contain the <literal>cloud-init</literal> package. Create at least one key pair for each project. If you already have generated a key pair with an external tool, you can import it into OpenStack. You can use the key pair for multiple instances that belong to that project."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:61(para)
msgid "A <emphasis role=\"bold\">security group</emphasis> that defines which incoming network traffic is forwarded to instances. Security groups hold a set of firewall policies, known as <emphasis role=\"italic\">security group rules</emphasis>."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:72(para)
msgid "If needed, you can assign a <emphasis role=\"bold\">floating (public) IP address</emphasis> to a running instance."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:77(para)
msgid "You can also attach a block storage device, or <emphasis role=\"bold\">volume</emphasis>, for persistent storage."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:83(para) ./doc/user-guide/section_cli_nova_configure_instances.xml:62(para)
msgid "Instances that use the default security group cannot, by default, be accessed from any IP address outside of the cloud. If you want those IP addresses to access the instances, you must modify the rules for the default security group."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:88(para) ./doc/user-guide/section_cli_nova_configure_instances.xml:66(para)
msgid "You can also assign a floating IP address to a running instance to make it accessible from outside the cloud. See <xref linkend=\"manage_ip_addresses\"/>."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:92(para)
msgid "After you gather the parameters that you need to launch an instance, you can launch it from an <link linkend=\"launch_from_image\">image</link> or a <link linkend=\"boot_from_volume\">volume</link>. You can launch an instance directly from one of the available OpenStack images or from an image that you have copied to a persistent volume. The OpenStack Image Service provides a pool of images that are accessible to members of different projects."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:102(title)
msgid "Gather parameters to launch an instance"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:104(para)
msgid "Before you begin, source the OpenStack RC file."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:107(para)
msgid "List the available flavors:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:109(para)
msgid "Note the ID of the flavor that you want to use for your instance:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:122(para)
msgid "List the available images:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:124(para)
msgid "Note the ID of the image from which you want to boot your instance:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:132(para)
msgid "You can also filter the image list by using <placeholder-1/> to find a specific image, as follows:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:139(para)
msgid "List the available security groups:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:141(para)
msgid "If you are an admin user, specify the <parameter>--all-tenants</parameter> parameter to list groups for all tenants."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:146(para)
msgid "Note the ID of the security group that you want to use for your instance:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:152(para)
msgid "If you have not created any security groups, you can assign the instance to only the default security group."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:155(para)
msgid "You can view rules for a specified security group:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:160(para)
msgid "List the available key pairs and note the name of the key pair that you use for SSH access."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:169(title)
msgid "Launch an instance from an image"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:172(para)
msgid "After you gather required parameters, run the following command to launch an instance. Specify the server name, flavor ID, and image ID."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:175(para)
msgid "Optionally, you can provide a key name for access control and a security group for security. You can also include metadata key and value pairs. For example, you can add a description for your server by providing the <parameter>--meta description=\"My Server\"</parameter> parameter."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:182(para)
msgid "You can pass user data in a local file at instance launch by using the <parameter>--user-data <replaceable>USER-DATA-FILE</replaceable></parameter> parameter."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:187(replaceable)
msgid "FLAVOR_ID"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:187(replaceable)
msgid "IMAGE_ID"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:187(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:77(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:99(replaceable)
msgid "KEY_NAME"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:188(replaceable)
msgid "USER_DATA_FILE"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:188(replaceable)
msgid "SEC_GROUP"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:188(replaceable)
msgid "KEY=VALUE"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:189(replaceable) ./doc/user-guide/app_cheat_sheet.xml:167(replaceable) ./doc/user-guide/section_cli_nova_startstop.xml:15(replaceable) ./doc/user-guide/section_cli_nova_startstop.xml:19(replaceable) ./doc/user-guide/section_cli_nova_startstop.xml:36(replaceable) ./doc/user-guide/section_cli_nova_startstop.xml:41(replaceable) ./doc/user-guide/section_cli_nova_get_console.xml:30(replaceable)
msgid "INSTANCE_NAME"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:190(para)
msgid "The following command launches the <literal>MyCirrosServer</literal> instance with the <literal>m1.small</literal> flavor (ID of <literal>1</literal>), <literal>cirros-0.3.2-x86_64-uec</literal> image (ID of <literal>397e713c-b95b-4186-ad46-6126863ea0a9</literal>), <literal>default</literal> security group, <literal>KeyPair01</literal> key, and a user data file called <filename>cloudinit.file</filename>:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:203(replaceable)
msgid "myCirrosServer"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:204(para)
msgid "Depending on the parameters that you provide, the command returns a list of server properties."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:207(para)
msgid "A status of <literal>BUILD</literal> indicates that the instance has started, but is not yet online."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:210(para)
msgid "A status of <literal>ACTIVE</literal> indicates that the instance is active."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:242(para)
msgid "Copy the server ID value from the <literal>id</literal> field in the output. You use this ID to get details for or delete your server."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:246(para)
msgid "Copy the administrative password value from the <literal>adminPass</literal> field. You use this value to log in to your server."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:250(para)
msgid "You can also place arbitrary local files into the instance file system at creation time by using the <parameter>--file &lt;dst-path=src-path&gt;</parameter> option. You can store up to five 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 SSH key injection, you can use the <parameter>--file</parameter> option as shown in the following example:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:267(para)
msgid "Check if the instance is online:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:269(para)
msgid "The list shows the ID, name, status, and private (and if assigned, public) IP addresses for all instances in the project to which you belong:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:279(para)
msgid "If the status for the instance is ACTIVE, the instance is online."
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:281(para)
msgid "To view the available options for the <placeholder-1/> command, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_boot.xml:288(para)
msgid "If you did not provide a key pair, security groups, or rules, you can access the instance only from inside the cloud through VNC. Even pinging the instance is not possible."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:7(title)
msgid "Manage bare-metal nodes"
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:8(para)
msgid "The bare-metal driver for OpenStack Compute manages provisioning of physical hardware by using common cloud APIs and tools such as Orchestration (Heat). The use case for this driver is for single tenant clouds such as a high-performance computing cluster or for deploying OpenStack itself."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:12(para)
msgid "If you use the bare-metal driver, you must create a network interface and add it to a bare-metal node. Then, you can launch an instance from a bare-metal image."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:15(para)
msgid "Development efforts are focused on moving the driver out of the Compute code base in the Icehouse release."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:17(para)
msgid "You can list and delete bare-metal nodes. When you delete a node, any associated network interfaces are removed. You can list and remove network interfaces that are associated with a bare-metal node."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:21(title)
msgid "Commands"
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:22(para)
msgid "The following commands can be used to manage bare-metal nodes."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:24(para)
msgid "<placeholder-1/>. Adds a network interface to a bare-metal node."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:28(para)
msgid "<placeholder-1/>. Lists network interfaces associated with a bare-metal node."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:32(para)
msgid "<placeholder-1/>. Removes a network interface from a bare-metal node."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:36(para)
msgid "<placeholder-1/>. Creates a bare-metal node."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:40(para)
msgid "<placeholder-1/>. Removes a bare-metal node and any associated interfaces."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:44(para)
msgid "<placeholder-1/>. Lists available bare-metal nodes."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:48(para)
msgid "<placeholder-1/>. Shows information about a bare-metal node."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:53(title)
msgid "Create a bare-metal node"
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:54(para)
msgid "When you create a bare-metal node, your PM address, user name, and password should match those that are configured in your hardware's BIOS/IPMI configuration."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:59(para)
msgid "The following example shows the command and results from creating a node with the PM address <filename>1.2.3.4</filename>, the PM user name <systemitem class=\"username\">ipmi</systemitem>, and password <literal>ipmi</literal>."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:81(title)
msgid "Add a network interface to the node:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:82(para)
msgid "For each NIC on the node, you must create an interface, specifying the interface's MAC address."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:94(title)
msgid "Launch an instance from a bare-metal image:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:96(para)
msgid "A bare-metal instance is an instance created directly on a physical machine without any virtualization layer running underneath it. Nova retains power control via IPMI. In some situations, Nova may retain network control via Neutron and OpenFlow."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:109(para)
msgid "Set the <parameter>--availability_zone</parameter> parameter to specify which zone or node to use to start the server. Separate the zone from the host name with a comma. For example:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:112(replaceable)
msgid "HOST"
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:112(replaceable)
msgid "NODE"
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:113(para)
msgid "<literal>host</literal> is optional for the <literal>--availability_zone</literal> parameter. You can specify simply <literal>zone:,node</literal>. You must still use the comma."
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:120(title)
msgid "List bare-metal nodes and interfaces:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:122(para)
msgid "Use the <placeholder-1/> command to view all bare-metal nodes and interfaces. When a node is in use, its status includes the UUID of the instance that runs on it:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:132(title)
msgid "Show details for a bare-metal node:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_baremetal.xml:133(para)
msgid "Use the <placeholder-1/> command to view the details for a bare-metal node."
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:8(title)
msgid "Create and manage stacks"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:9(para)
msgid "The Orchestration module enables you to orchestrate multiple composite cloud applications. This module supports use of both the Amazon Web Services (AWS) CloudFormation template format through both a Query API that is compatible with CloudFormation and the native OpenStack <glossterm>Heat Orchestration Template (HOT)</glossterm> format through a REST API."
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:14(para) ./doc/user-guide/section_dashboard_stacks.xml:17(para)
msgid "These flexible template languages enable application developers to describe and automate the deployment of infrastructure, services, and applications. The templates enable creation of most OpenStack resource types, such as instances, floating IP addresses, volumes, security groups, and users. The resources, once created, are referred to as stacks."
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:19(para) ./doc/user-guide/section_dashboard_stacks.xml:24(para)
msgid "The template languages are described in <link href=\"http://docs.openstack.org/developer/heat/template_guide/index.html\">the Template Guide</link> in the <link href=\"http://docs.openstack.org/developer/heat/\">Heat developer documentation</link>."
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:25(title)
msgid "Create a stack from an example template file"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:28(para)
msgid "To create a stack, or template, from an <link href=\"https://github.com/openstack/heat-templates\">example template file</link>, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:32(replaceable) ./doc/user-guide/section_cli_heat.xml:59(replaceable)
msgid "PATH_TO_HEAT_TEMPLATES"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:33(replaceable)
msgid "USERNAME"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:33(replaceable) ./doc/user-guide/app_cheat_sheet.xml:48(replaceable)
msgid "PASSWORD"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:33(replaceable)
msgid "HEAT_KEY"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:34(para)
msgid "The <literal>--parameters</literal> values that you specify depend on the parameters that are defined in the template. If a website hosts the template file, you can specify the URL with the <literal>--template-url</literal> parameter instead of the <literal>--template-file</literal> parameter."
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:40(para)
msgid "The command returns the following output:"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:48(para)
msgid "You can also use the <placeholder-1/> command to validate a template file without creating a stack from it."
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:52(para)
msgid "Previous versions of the heat client used <placeholder-1/> instead of <placeholder-2/>, but it has been deprecated in favor of <placeholder-3/>."
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:58(para)
msgid "To do so, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:60(para)
msgid "If validation fails, the response returns an error message."
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:66(title)
msgid "Get information about stacks"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:67(para)
msgid "To explore the state and history of a particular stack, you can run a number of commands."
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:71(para)
msgid "To see which stacks are visible to the current user, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:82(para)
msgid "To show the details of a stack, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:87(para)
msgid "A stack consists of a collection of resources. To list the resources and their status, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:97(para)
msgid "To show the details for a specific resource in a stack, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:100(para)
msgid "Some resources have associated metadata which can change throughout the life cycle of a resource. Show the metadata by running the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:105(para)
msgid "A series of events is generated during the life cycle of a stack. To display life cycle events, run the following command::"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:116(para)
msgid "To show the details for a particular event, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:123(title)
msgid "Update a stack"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:124(para)
msgid "To update an existing stack from a modified template file, run a command like the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_heat.xml:135(para)
msgid "Some resources are updated in-place, while others are replaced with new resources."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:7(title)
msgid "Create and manage networks"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:9(para)
msgid "The OpenStack Networking service provides a scalable system for managing the network connectivity within an OpenStack cloud deployment. It can easily and quickly react to changing network needs (for example, creating and assigning new IP addresses)."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:14(para)
msgid "Networking in OpenStack is complex. This section provides the basic instructions for creating a network and a router. For detailed information about managing networks, refer to the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html\"><emphasis role=\"italic\">OpenStack Cloud Administrator Guide</emphasis></link>."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:21(title)
msgid "Create a network"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:24(para)
msgid "Log in to the dashboard, choose a project, and click <guibutton>Networks</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:28(para)
msgid "Click <guibutton>Create Network</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:31(para)
msgid "In the Create Network dialog box, specify the following values."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:39(guilabel)
msgid "Network"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:39(th) ./doc/user-guide/section_dashboard_create_networks.xml:48(th) ./doc/user-guide/section_dashboard_create_networks.xml:81(th) ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:56(th) ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:156(th) ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:179(th) ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:189(th) ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:197(th)
msgid "<placeholder-1/> tab"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:44(guilabel)
msgid "Network Name"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:45(para)
msgid "Specify a name to identify the network."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:49(guilabel) ./doc/user-guide/section_dashboard_create_networks.xml:154(guilabel)
msgid "Subnet"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:52(guilabel)
msgid "Create Subnet"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:53(para)
msgid "Select this check box to create a subnet"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:54(para)
msgid "You do not have to specify a subnet when you create a network, but if you do not, any attached instance receives an Error status."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:59(guilabel)
msgid "Subnet Name"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:60(para)
msgid "Specify a name for the subnet."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:63(guilabel)
msgid "Network Address"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:64(para)
msgid "Specify the IP address for the subnet."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:67(guilabel)
msgid "IP Version"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:68(para)
msgid "Select IPv4 or IPv6."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:71(guilabel)
msgid "Gateway IP"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:72(para)
msgid "Specify an IP address for a specific gateway. This parameter is optional."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:76(guilabel)
msgid "Disable Gateway"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:77(para)
msgid "Select this check box to disable a gateway IP address."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:81(guilabel)
msgid "Subnet Detail"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:84(guilabel)
msgid "Enable DHCP"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:85(para)
msgid "Select this check box to enable DHCP."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:88(guilabel)
msgid "Allocation Pools"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:89(para)
msgid "Specify IP address pools."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:92(guilabel)
msgid "DNS Name Servers"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:93(para)
msgid "Specify a name for the DNS server."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:96(guilabel)
msgid "Host Routes"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:97(para)
msgid "Specify the IP address of host routes."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:103(para)
msgid "Click <guilabel>Create</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:104(para)
msgid "The dashboard shows the network on the <guilabel>Networks</guilabel> tab."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:110(title)
msgid "Create a router"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:113(para)
msgid "Log in to the dashboard, choose a project, and click <guibutton>Routers</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:117(para)
msgid "Click <guibutton>Create Router</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:119(para)
msgid "In the Create Router dialog box, specify a name for the router and click <guibutton>Create Router</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:121(para)
msgid "The new router is now displayed in the <guilabel>Routers</guilabel> tab."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:125(para)
msgid "Click the new router's <guibutton>Set Gateway</guibutton> button."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:129(para)
msgid "In the <guilabel>External Network</guilabel> field, specify the network to which the router will connect, and then click <guibutton>Set Gateway</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:134(para)
msgid "To connect a private network to the newly created router, perform the following steps:"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:138(para)
msgid "On the <guilabel>Routers</guilabel> tab, click the name of the router."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:142(para)
msgid "On the Router Details page, click <guilabel>Add Interface</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:146(para)
msgid "In the Add Interface dialog box, specify the following information:"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:158(para)
msgid "Select a subnet."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:163(guilabel)
msgid "IP Address (optional)"
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:166(para)
msgid "Enter the router interface IP address for the selected subnet."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:168(para)
msgid "Note: If this value is not set, then by default, the first host IP address in the subnet is used by OpenStack Networking."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:175(para)
msgid "The <guilabel>Router Name</guilabel> and <guilabel>Router ID</guilabel> fields are automatically updated."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:181(para)
msgid "Click <guilabel>Add Interface</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_create_networks.xml:184(para)
msgid "You have successfully created the router. You can view the new topology from the <guilabel>Network Topology</guilabel> tab."
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:7(title)
msgid "Compute"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:9(para)
msgid "To use the information in this section, you must be familiar with OpenStack Compute."
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:11(title) ./doc/user-guide/section_sdk_neutron.xml:15(title)
msgid "Set environment variables"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:12(para)
msgid "To set up environmental variables and authenticate against Compute API endpoints, see <xref linkend=\"sdk_auth\"/>."
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:17(title)
msgid "Get OpenStack credentials (API v2)"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:18(para)
msgid "These example use the <code>get_nova_credentials_v2</code> method:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:28(para) ./doc/user-guide/section_sdk_neutron.xml:36(para) ./doc/user-guide/section_sdk_neutron.xml:54(para)
msgid "This code resides in the <filename>credentials.py</filename> file, which all samples import."
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:31(para)
msgid "Use the <code>get_nova_credentials_v2()</code> method to populate and get a dictionary:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:37(title)
msgid "List servers (API v2)"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:38(para)
msgid "The following program lists servers by using the Compute API v2."
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:41(title)
msgid "To list servers"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:43(para) ./doc/user-guide/section_sdk_nova.xml:85(para) ./doc/user-guide/section_sdk_nova.xml:161(para) ./doc/user-guide/section_sdk_nova.xml:251(para) ./doc/user-guide/section_sdk_nova.xml:338(para) ./doc/user-guide/section_sdk_nova.xml:399(para) ./doc/user-guide/section_sdk_nova.xml:462(para) ./doc/user-guide/section_sdk_neutron.xml:246(para) ./doc/user-guide/section_sdk_neutron.xml:341(para) ./doc/user-guide/section_sdk_neutron.xml:416(para) ./doc/user-guide/section_sdk_neutron.xml:466(para) ./doc/user-guide/section_sdk_neutron.xml:515(para)
msgid "Import the following modules:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:48(para) ./doc/user-guide/section_sdk_nova.xml:167(para)
msgid "Get Nova credentials. See <xref linkend=\"sdk_compute_get_openstack_credentials_v2\"/>."
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:53(para) ./doc/user-guide/section_sdk_nova.xml:96(para) ./doc/user-guide/section_sdk_nova.xml:172(para) ./doc/user-guide/section_sdk_nova.xml:275(para) ./doc/user-guide/section_sdk_nova.xml:358(para) ./doc/user-guide/section_sdk_nova.xml:422(para) ./doc/user-guide/section_sdk_nova.xml:483(para) ./doc/user-guide/section_sdk_neutron.xml:259(para)
msgid "Instantiate the <literal>nova_client</literal> client object by using the <literal>credentials</literal> dictionary object:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:60(para)
msgid "List servers by calling <literal>servers.list</literal> on <literal>nova_client</literal> object:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:67(title)
msgid "List servers code listing"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:79(title)
msgid "Create server (API v2)"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:80(para)
msgid "The following program creates a server (VM) by using the Compute API v2."
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:83(title)
msgid "To create a server"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:91(para) ./doc/user-guide/section_sdk_nova.xml:353(para) ./doc/user-guide/section_sdk_nova.xml:417(para) ./doc/user-guide/section_sdk_nova.xml:478(para)
msgid "Get OpenStack credentials. See <xref linkend=\"sdk_compute_get_openstack_credentials_v2\"/>."
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:103(para)
msgid "Get the flavor and image to use to create a server. This code uses the <literal>cirros</literal> image, the <literal>m1.tiny</literal> flavor, and the <literal>private</literal> network:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:113(para)
msgid "To create the server, use the network, image, and flavor:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:120(para)
msgid "Sleep for five seconds and determine whether the server/vm was created by calling <literal>nova_client.servers.list()</literal>:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:130(title)
msgid "Create server code listing"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:155(title)
msgid "Delete server (API v2)"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:156(para)
msgid "The following program deletes a server (VM) by using the Compute API v2."
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:159(title)
msgid "To delete a server"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:179(para)
msgid "Determine whether the <literal>vm1</literal> server exists:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:183(para)
msgid "List servers: <literal>servers_list</literal>."
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:187(para)
msgid "Iterate over <literal>servers_list</literal> and compare name with <literal>vm1</literal>."
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:193(para)
msgid "If true, set the variable name <literal>server_exists</literal> to <literal>True</literal> and break from the for loop:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:210(para)
msgid "If the server exists, run the <literal>delete</literal> method of the <literal>nova_client.servers</literal> object:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:219(title)
msgid "Delete server code listing"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:245(title)
msgid "Update server (API v2)"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:246(para)
msgid "The following program updates the name of a server (VM) by using the Compute API v2."
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:249(title)
msgid "To update a server"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:255(para)
msgid "<literal>print_server</literal> is a method defined in <filename>utils.py</filename> and prints the server details as shown in the code listing below:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:270(para)
msgid "Get OpenStack Credentials. See <xref linkend=\"sdk_compute_get_openstack_credentials_v2\"/>."
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:282(para)
msgid "Get the server instance using <literal>server_id</literal> and print the details by calling <literal>print_server</literal> method:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:292(para)
msgid "Call <code>server.update</code> on the server object with the new value for <literal>name</literal> variable:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:298(para)
msgid "Get the updated instance of the server:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:302(para)
msgid "Call <literal>print_server</literal> again to check the update server details:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:309(title)
msgid "Update server code listing"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:332(title)
msgid "List flavors (API v2)"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:333(para)
msgid "The following program lists flavors and their details by using the Compute API v2."
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:336(title)
msgid "To list flavors"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:342(para)
msgid "The <literal>print_flavors</literal> method is defined in <filename>utils.py</filename> and prints the flavor details:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:365(para)
msgid "List flavors by calling <literal>list()</literal> on <literal>nova_client.flavors</literal> object:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:372(para)
msgid "Print the flavor details, id and name by calling <literal>print_flavors</literal>:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:378(title)
msgid "List flavors code listing"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:393(title)
msgid "List floating IPs (API v2)"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:394(para)
msgid "The following program lists the floating IPs and their details by using the Compute API v2."
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:397(title)
msgid "To list floating IPs"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:403(para)
msgid "The <literal>print_values_ip</literal> method is defined in <filename>utils.py</filename> and prints the floating_ip object details:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:429(para)
msgid "List floating IPs by calling <literal>list()</literal> on <literal>nova_client.floating_ips</literal> object:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:436(para)
msgid "Print the floating IP object details by calling <literal>print_values_ip</literal>:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:442(title)
msgid "List floating IPs code listing"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:456(title)
msgid "List hosts (API v2)"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:457(para)
msgid "The following program lists the hosts by using the Compute API v2."
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:460(title)
msgid "To list hosts"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:466(para)
msgid "The <literal>print_hosts</literal> method is defined in <filename>utils.py</filename> and prints the host object details:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:490(para)
msgid "List hosts by calling <literal>list()</literal> on <literal>nova_client.hosts</literal> object:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:496(para)
msgid "Print the host object details by calling <literal>print_hosts(host_list)</literal>:"
msgstr ""

#: ./doc/user-guide/section_sdk_nova.xml:502(title)
msgid "List hosts code listing"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:11(title)
msgid "Launch an instance"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:13(para)
msgid "When you launch an instance from an image, OpenStack creates a local copy of the image on the compute node where the instance starts."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:15(para)
msgid "When you launch an instance from a volume, note the following steps:"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:19(para)
msgid "To select the volume to from which to launch, launch an instance from an arbitrary image on the volume. The image that you select does not boot. Instead, it is replaced by the image on the volume that you choose in the next steps."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:23(para)
msgid "To boot a Xen image from a volume, the image you launch in must be the same type, fully virtualized or paravirtualized, as the one on the volume."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:28(para)
msgid "Select the volume or volume snapshot from which to boot. Enter a device name. Enter <literal>vda</literal> for KVM images or <literal>xvda</literal> for Xen images."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:35(para)
msgid "Log in to the dashboard, choose a project, and click <guilabel>Images</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:37(para)
msgid "The dashboard shows the images that have been uploaded to OpenStack Image Service and are available for this project."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:40(para)
msgid "For details on creating images, see <link href=\"http://docs.openstack.org/image-guide/content/ch_creating_images_manually.html\">Creating images manually</link> in the <citetitle>OpenStack Virtual Machine Image Guide</citetitle>."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:46(para)
msgid "Select an image and click <guibutton>Launch</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:49(para)
msgid "In the Launch Instance dialog box, specify the following values:"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:56(guilabel) ./doc/user-guide/section_dashboard_databases.xml:62(guilabel)
msgid "Details"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:61(guilabel)
msgid "Availability Zone"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:63(para)
msgid "By default, this value is set to the availability zone given by the cloud provider (for example, <literal>us-west</literal> or <literal>apac-south</literal>). For some cases, it could be <literal>nova</literal>."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:70(guilabel)
msgid "Instance Name"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:71(para)
msgid "Assign a name to the virtual machine."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:72(para)
msgid "The name you assign here becomes the initial host name of the server. After the server is built, if you change the server name in the API or change the host name directly, the names are not updated in the dashboard."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:76(para)
msgid "Server names are not guaranteed to be unique when created so you could have two instances with the same host name."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:83(guilabel) ./doc/user-guide/section_dashboard_databases.xml:71(guilabel)
msgid "Flavor"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:84(para)
msgid "Specify the size of the instance to launch."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:85(para)
msgid "The flavor is selected based on the size of the image selected for launching an instance. For example, while creating an image, if you have entered the value in the <guilabel>Minimum RAM (MB)</guilabel> field as 2048, then on selecting the image, the default flavor is <guilabel>m1.small</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:95(guilabel)
msgid "Instance Count"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:96(para)
msgid "To launch multiple instances, enter a value greater than 1. The default is 1."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:100(guilabel)
msgid "Instance Boot Source"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:101(para)
msgid "Your options are:"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:104(guilabel)
msgid "Boot from image"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:105(para)
msgid "If you choose this option, a new field for <guilabel>Image Name</guilabel> displays. You can select the image from the list."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:110(guilabel)
msgid "Boot from snapshot"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:111(para)
msgid "If you choose this option, a new field for <guilabel>Instance Snapshot</guilabel> displays. You can select the snapshot from the list."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:116(guilabel)
msgid "Boot from volume"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:117(para)
msgid "If you choose this option, a new field for <guilabel>Volume</guilabel> displays. You can select the volume from the list."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:122(guilabel)
msgid "Boot from image (creates a new volume)"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:123(para)
msgid "With this option, you can boot from an image and create a volume by entering the <guilabel>Device Size</guilabel> and <guilabel>Device Name</guilabel> for your volume. Click the <guilabel>Delete on Terminate</guilabel> option to delete the volume on terminating the instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:131(guilabel)
msgid "Boot from volume snapshot (creates a new volume)"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:133(para)
msgid "Using this option, you can boot from a volume snapshot and create a new volume by choosing <guilabel>Volume Snapshot</guilabel> from a list and adding a <guilabel>Device Name</guilabel> for your volume. Click the <guilabel>Delete on Terminate</guilabel> option to delete the volume on terminating the instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:142(para)
msgid "Since you are launching an instance from an image, <guilabel>Boot from image</guilabel> is chosen by default."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:148(guilabel)
msgid "Image Name"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:149(para)
msgid "This field changes based on your previous selection. Since you have chosen to launch an instance using an image, the <guilabel>Image Name</guilabel> field displays. Select the image name from the dropdown list."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:156(guilabel)
msgid "Access &amp; Security"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:160(guilabel)
msgid "Keypair"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:161(para)
msgid "Specify a key pair."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:162(para)
msgid "If the image uses a static root password or a static key set (neither is recommended), you do not need to provide a key pair to launch the instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:167(guilabel)
msgid "Security Groups"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:168(para)
msgid "Activate the security groups that you want to assign to the instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:170(para)
msgid "Security groups are a kind of cloud firewall that define which incoming network traffic is forwarded to instances. For details, see <xref linkend=\"security_groups_add_rule\"/>."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:174(para)
msgid "If you have not created any security groups, you can assign only the default security group to the instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:179(guilabel) ./doc/user-guide/section_sdk_neutron.xml:7(title) ./doc/user-guide/hot/section_advanced_topics.xml:7(title)
msgid "Networking"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:182(guilabel)
msgid "Selected Networks"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:183(para)
msgid "To add a network to the instance, click the <guibutton>+</guibutton> in the <guilabel>Available Networks</guilabel> field."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:189(guilabel)
msgid "Post-Creation"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:192(guilabel)
msgid "Customization Script"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:193(para)
msgid "Specify a customization script that runs after your instance launches."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:197(guilabel)
msgid "Advanced Options"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:200(guilabel)
msgid "Disk Partition"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:201(para)
msgid "Select the type of disk partition from the dropdown list."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:205(guilabel)
msgid "Automatic"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:207(para)
msgid "Entire disk is single partition and automatically resizes."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:211(guilabel)
msgid "Manual"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:213(para)
msgid "Faster build times but requires manual partitioning."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:232(para)
msgid "Click <guibutton>Launch</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:233(para)
msgid "The instance starts on a compute node in the cloud."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:236(para)
msgid "The <guilabel>Instances</guilabel> tab shows the instance's name, its private and public IP addresses, size, status, task, and power state."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:239(para)
msgid "If you did not provide a key pair, security groups, or rules, users can access the instance only from inside the cloud through VNC. Even pinging the instance is not possible without an ICMP rule configured. To access the instance through a VNC console, see <xref linkend=\"instance_console\"/>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:7(title)
msgid "Upload and manage images"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:8(para)
msgid "A virtual machine image, referred to in this document simply as an image, is a single file that contains a virtual disk that has a bootable operating system installed on it. Images are used to create virtual machine instances within the cloud. For information about creating image files, see the <link href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>OpenStack Virtual Machine Image Guide</citetitle></link>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:16(para)
msgid "Depending on your role, you may have permission to upload and manage virtual machine images. Operators might restrict the upload and management of images to cloud administrators or operators only. If you have the appropriate privileges, you can use the dashboard to upload and manage images in the <guilabel>admin</guilabel> project."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:23(para)
msgid "You can also use the <placeholder-1/> and <placeholder-2/> command-line clients or the Image Service and Compute APIs to manage images. See <xref linkend=\"cli_manage_images\"/>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:29(title) ./doc/user-guide/section_sdk_manage_images.xml:102(title)
msgid "Upload an image"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:30(para)
msgid "Follow this procedure to upload an image to a project."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:34(para) ./doc/user-guide/section_dashboard_manage_images.xml:160(para) ./doc/user-guide/section_dashboard_manage_images.xml:207(para)
msgid "Log in to the dashboard."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:37(para) ./doc/user-guide/section_dashboard_manage_images.xml:163(para) ./doc/user-guide/section_dashboard_manage_images.xml:210(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:217(para)
msgid "From the <guilabel>CURRENT PROJECT</guilabel> on the <guilabel>Project</guilabel> tab, select the appropriate project."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:42(para) ./doc/user-guide/section_dashboard_manage_images.xml:168(para) ./doc/user-guide/section_dashboard_manage_images.xml:214(para)
msgid "On the <guilabel>Project</guilabel> tab, click <guilabel>Images</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:46(para) ./doc/user-guide/section_dashboard_manage_images.xml:149(para)
msgid "Click <guibutton>Create Image</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:47(para)
msgid "The Create An Image dialog box appears."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:50(para)
msgid "Enter the following values:"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:57(guilabel) ./doc/user-guide/section_dashboard_databases.xml:136(guilabel)
msgid "Name"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:60(para)
msgid "Enter a name for the image."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:65(guilabel) ./doc/user-guide/section_dashboard_databases.xml:144(guilabel) ./doc/user-guide/app_cheat_sheet.xml:21(th) ./doc/user-guide/app_cheat_sheet.xml:67(th) ./doc/user-guide/app_cheat_sheet.xml:141(th) ./doc/user-guide/app_cheat_sheet.xml:335(th) ./doc/user-guide/app_cheat_sheet.xml:376(th) ./doc/user-guide/app_cheat_sheet.xml:460(th) ./doc/user-guide/section_dashboard_manage_volumes.xml:44(guilabel)
msgid "Description"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:68(para)
msgid "Optionally, enter a brief description of the image."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:74(guilabel)
msgid "Image Source"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:77(para)
msgid "Choose the image source from the list. Your choices are <guilabel>Image Location</guilabel> and <guilabel>Image File</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:84(para)
msgid "<guilabel>Image File</guilabel> or <guilabel>Image Location</guilabel>"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:89(para)
msgid "Based on your selection for <guilabel>Image Source</guilabel>, you either enter the location URL of the image in the <guilabel>Image Location</guilabel> field. or browse to the image file on your system and add it."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:98(guilabel)
msgid "Format"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:101(para)
msgid "Select the correct format (for example, QCOW2) for the image."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:108(guilabel)
msgid "Architecture"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:112(para)
msgid "Specify the architecture. For example, <literal>i386</literal> for a 32-bit architecture or <literal>x86-64</literal> for a 64-bit architecture."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:119(para)
msgid "<guilabel>Minimum Disk (GB)</guilabel> and <guilabel>Minimum RAM (MB)</guilabel>"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:123(para)
msgid "Leave these optional fields empty."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:128(guilabel)
msgid "Public"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:131(para)
msgid "Select this check box to make the image public to all users with access to the current project."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:138(guilabel)
msgid "Protected"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:141(para)
msgid "Select this check box to ensure that only users with permissions can delete the image."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:150(para)
msgid "The image is queued to be uploaded. It might take some time before the status changes from Queued to Active."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:156(title)
msgid "Update an image"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:157(para)
msgid "Follow this procedure to update an existing image."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:172(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:226(para)
msgid "Select the image that you want to edit."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:175(para)
msgid "In the <guilabel>Actions</guilabel> column, click <guilabel>More</guilabel> and then select <guilabel>Edit</guilabel> from the list."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:183(para)
msgid "Change the name of the image."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:186(para)
msgid "Select the <guilabel>Public</guilabel> check box to make the image public."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:190(para)
msgid "Clear the <guilabel>Public</guilabel> check box to make the image private."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:180(para)
msgid "In the Update Image dialog box, you can perform the following actions: <placeholder-1/>"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:196(para)
msgid "Click <guibutton>Update Image</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:201(title)
msgid "Delete an image"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:202(para)
msgid "Deletion of images is permanent and <emphasis role=\"bold\">cannot</emphasis> be reversed. Only users with the appropriate permissions can delete images."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:218(para)
msgid "Select the images that you want to delete."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:221(para)
msgid "Click <guibutton>Delete Images</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_images.xml:224(para)
msgid "In the <guilabel>Confirm Delete Image</guilabel> dialog box, click <guibutton>Delete Images</guibutton> to confirm the deletion."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:7(title) ./doc/user-guide/section_cli_trove.xml:8(title)
msgid "Create and manage databases"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:9(para) ./doc/user-guide/section_cli_trove.xml:9(para)
msgid "The Database service provides scalable and reliable cloud provisioning functionality for both relational and non-relational database engines. Users can quickly and easily use database features without the burden of handling complex administrative tasks."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:11(title) ./doc/user-guide/section_cli_trove.xml:157(title)
msgid "Create a database instance"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:13(title)
msgid "Prerequisites"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:14(para)
msgid "Before you create a database instance, you need to configure a default datastore and make sure you have an appropriate flavor for the type of database instance you want."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:18(title)
msgid "Configure a default datastore."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:19(para)
msgid "Because the dashboard does not let you choose a specific datastore to use with an instance, you need to configure a default datastore. The dashboard then uses the default datastore to create the instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:22(para)
msgid "Add the following line to <filename>/etc/trove/trove.conf</filename>:"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:23(replaceable) ./doc/user-guide/section_cli_trove.xml:630(replaceable)
msgid "DATASTORE_NAME"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:24(para)
msgid "Replace <replaceable>DATASTORE_NAME</replaceable> with the name that the administrative user set when issuing the <placeholder-1/> command to create the datastore. You can use the trove <placeholder-2/> command to display the datastores that are available in your environment."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:25(para)
msgid "For example, if your MySQL datastore name is set to <literal>mysql</literal>, your entry would look like this:"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:29(para)
msgid "Restart Database services on the controller node:"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:37(title)
msgid "Verify flavor."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:38(para)
msgid "Make sure an <link linkend=\"create_db\">appropriate flavor exists</link> for the type of database instance you want."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:42(title)
msgid "Create database instance"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:43(para)
msgid "Once you have configured a default datastore and verified that you have an appropriate flavor, you can create a database instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:47(para) ./doc/user-guide/section_dashboard_databases.xml:121(para) ./doc/user-guide/section_dashboard_databases.xml:161(para)
msgid "Log in to the dashboard, choose a project, and click <guilabel>Databases</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:50(para)
msgid "Click <guilabel>Database Instances</guilabel>. This lists the instances that already exist in your environment."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:53(para)
msgid "Click <guibutton>Launch Instance</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:56(para)
msgid "In the <guilabel>Launch Database</guilabel> dialog box, specify the following values."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:67(guilabel)
msgid "Database Name"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:68(para)
msgid "Specify a name for the database instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:72(para)
msgid "Select an appropriate flavor for the instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:75(guilabel)
msgid "Volume Size"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:76(para)
msgid "Select a volume size. Volume size is expressed in GB."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:80(guilabel)
msgid "Initialize Databases"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:83(guilabel)
msgid "Initial Database"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:85(para)
msgid "Optionally provide a comma separated list of databases to create, for example:"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:86(para)
msgid "<literal>database1</literal>, <literal>database2</literal>, <literal>database3</literal>"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:90(guilabel)
msgid "Initial Admin User"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:91(para)
msgid "Create an initial admin user. This user will have access to all the databases you create."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:94(guilabel)
msgid "Password"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:95(para)
msgid "Specify a password associated with the initial admin user you just named."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:98(guilabel)
msgid "Host"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:99(para)
msgid "Optionally, allow the user to connect only from this host. If you do not specify a host, this user will be allowed to connect from anywhere."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:105(para)
msgid "Click the <guibutton>Launch</guibutton> button. The new database instance appears in the databases list."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:110(title) ./doc/user-guide/section_cli_trove.xml:243(title)
msgid "Backup and restore a database"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:111(para) ./doc/user-guide/section_cli_trove.xml:244(para)
msgid "You can use Database services to backup a database and store the backup artifact in the Object Storage module. Later on, if the original database is damaged, you can use the backup artifact to restore the database. The restore process creates a database instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:114(para) ./doc/user-guide/section_cli_trove.xml:247(para)
msgid "This example shows you how to back up and restore a MySQL database."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:116(title) ./doc/user-guide/section_cli_trove.xml:249(title)
msgid "To backup and restore a database"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:118(title)
msgid "Backup the database instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:124(para)
msgid "Click <guilabel>Database Instances</guilabel>. This displays the existing instances in your system."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:127(para)
msgid "Click <guibutton>Create Backup</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:130(para)
msgid "In the Backup Database dialog box, specify the following values:"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:137(para)
msgid "Specify a name for the backup."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:140(guilabel)
msgid "Database Instance"
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:141(para)
msgid "Select the instance you want to back up."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:145(para)
msgid "Specify an optional description."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:151(para)
msgid "Click <guibutton>Backup</guibutton>. The new backup appears in the backup list."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:156(title)
msgid "Restore a database instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:157(para)
msgid "Now assume that your original database instance is damaged and you need to restore it. You do the restore by using your backup to create a new database instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:164(para)
msgid "Click <guilabel>Database Backups</guilabel>. This lists the available backups."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:167(para)
msgid "Check the backup you want to use and click <guibutton>Restore Backup</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:170(para)
msgid "In the <guilabel>Launch Database</guilabel> dialog box, specify the <link linkend=\"dashboard_create_db_instance\">values you want to use for the new database instance</link>. Click the <guilabel>Restore From Database</guilabel> tab and make sure that this new instance is based on the correct backup."
msgstr ""

#: ./doc/user-guide/section_dashboard_databases.xml:173(para)
msgid "Click <guibutton>Launch</guibutton>. The new instance appears in the database instances list."
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:7(title)
msgid "Measure cloud resources"
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:8(para)
msgid "Telemetry measures cloud resources in OpenStack. It collects data related to billing. Currently, this metering service is available through only the <placeholder-1/> command-line client."
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:10(para)
msgid "To model data, Telemetry uses the following abstractions:"
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:13(emphasis)
msgid "Meter"
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:15(para)
msgid "Measures a specific aspect of resource usage, such as the existence of a running instance, or ongoing performance, such as the CPU utilization for an instance. Meters exist for each type of resource. For example, a separate <literal>cpu_util</literal> meter exists for each instance. The life cycle of a meter is decoupled from the existence of its related resource. The meter persists after the resource goes away."
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:25(para)
msgid "A meter has the following attributes:"
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:28(para)
msgid "String name"
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:31(para)
msgid "A unit of measurement"
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:34(para)
msgid "A type, which indicates whether values increase monotonically (cumulative), are interpreted as a change from the previous value (delta), or are stand-alone and relate only to the current duration (gauge)"
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:42(emphasis)
msgid "Sample"
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:44(para)
msgid "An individual data point that is associated with a specific meter. A sample has the same attributes as the associated meter, with the addition of time stamp and value attributes. The value attribute is also known as the sample <emphasis role=\"italic\">volume</emphasis>."
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:50(emphasis)
msgid "Statistic"
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:52(para)
msgid "A set of data point aggregates over a time duration. (In contrast, a sample represents a single data point.) The Telemetry service employs the following aggregation functions:"
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:56(para)
msgid "<emphasis role=\"bold\">count</emphasis>. The number of samples in each period."
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:61(para)
msgid "<emphasis role=\"bold\">max</emphasis>. The maximum number of sample volumes in each period."
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:66(para)
msgid "<emphasis role=\"bold\">min</emphasis>. The minimum number of sample volumes in each period."
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:71(para)
msgid "<emphasis role=\"bold\">avg</emphasis>. The average of sample volumes over each period."
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:76(para)
msgid "<emphasis role=\"bold\">sum</emphasis>. The sum of sample volumes over each period."
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:84(emphasis)
msgid "Alarm"
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:86(para)
msgid "A set of rules that define a monitor and a current state, with edge-triggered actions associated with target states. Alarms provide user-oriented Monitoring-as-a-Service and a general purpose utility for OpenStack. Orchestration auto scaling is a typical use case. Alarms follow a tristate model of <literal>ok</literal>, <literal>alarm</literal>, and <literal>insufficient data</literal>. For conventional threshold-oriented alarms, a static threshold value and comparison operator govern state transitions. The comparison operator compares a selected meter statistic against an evaluation window of configurable length into the recent past."
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:96(para)
msgid "This example uses the <placeholder-1/> client to create an auto-scaling stack and the <placeholder-2/> client to measure resources."
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:102(para)
msgid "Create an auto-scaling stack by running the following command. The <literal>-f</literal> option specifies the name of the stack template file, and the <literal>-P</literal> option specifies the <literal>KeyName</literal> parameter as <literal>heat_key</literal>."
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:108(para)
msgid "List the heat resources that were created:"
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:125(para)
msgid "List the alarms that are set:"
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:135(para)
msgid "List the meters that are set:"
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:146(para)
msgid "List samples:"
msgstr ""

#: ./doc/user-guide/section_cli_ceilometer.xml:155(para)
msgid "View statistics:"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:8(title)
msgid "OpenStack command-line interface cheat sheet"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:10(para)
msgid "The following tables give a quick reference of the most used command-line commands."
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:16(caption)
msgid "Identity (keystone)"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:22(th) ./doc/user-guide/app_cheat_sheet.xml:68(th) ./doc/user-guide/app_cheat_sheet.xml:142(th) ./doc/user-guide/app_cheat_sheet.xml:336(th) ./doc/user-guide/app_cheat_sheet.xml:377(th) ./doc/user-guide/app_cheat_sheet.xml:461(th)
msgid "Command"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:27(td)
msgid "List all users"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:33(td)
msgid "List Identity service catalog"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:39(td)
msgid "List all services in service catalog"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:45(td)
msgid "Create new user"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:47(replaceable) ./doc/user-guide/app_cheat_sheet.xml:54(replaceable) ./doc/user-guide/app_cheat_sheet.xml:187(replaceable) ./doc/user-guide/app_cheat_sheet.xml:216(replaceable) ./doc/user-guide/app_cheat_sheet.xml:223(replaceable) ./doc/user-guide/app_cheat_sheet.xml:229(replaceable) ./doc/user-guide/app_cheat_sheet.xml:235(replaceable) ./doc/user-guide/app_cheat_sheet.xml:241(replaceable) ./doc/user-guide/app_cheat_sheet.xml:247(replaceable) ./doc/user-guide/app_cheat_sheet.xml:253(replaceable) ./doc/user-guide/app_cheat_sheet.xml:254(replaceable) ./doc/user-guide/app_cheat_sheet.xml:260(replaceable) ./doc/user-guide/app_cheat_sheet.xml:268(replaceable) ./doc/user-guide/app_cheat_sheet.xml:275(replaceable) ./doc/user-guide/app_cheat_sheet.xml:343(replaceable) ./doc/user-guide/app_cheat_sheet.xml:387(replaceable) ./doc/user-guide/section_cli_trove.xml:630(replaceable)
msgid "NAME"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:47(replaceable)
msgid "TENANT"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:48(replaceable)
msgid "EMAIL"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:48(replaceable)
msgid "BOOL"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:52(td)
msgid "Create new tenant"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:54(replaceable)
msgid "DESCRIPTION"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:62(caption)
msgid "Image Service (glance)"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:73(td)
msgid "List images you can access"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:79(td)
msgid "Delete specified image"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:81(replaceable) ./doc/user-guide/app_cheat_sheet.xml:87(replaceable) ./doc/user-guide/app_cheat_sheet.xml:93(replaceable) ./doc/user-guide/app_cheat_sheet.xml:167(replaceable) ./doc/user-guide/app_cheat_sheet.xml:268(replaceable)
msgid "IMAGE"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:85(td)
msgid "Describe a specific image"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:91(td)
msgid "Update image"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:97(th) ./doc/user-guide/section_sdk_manage_images.xml:8(title)
msgid "Manage images"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:100(td)
msgid "Kernel image"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:108(td)
msgid "RAM image"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:116(td)
msgid "Three-part image"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:125(td)
msgid "Register raw image"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:136(caption)
msgid "Compute (nova)"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:147(td)
msgid "List instances, notice status of instance"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:153(td) ./doc/user-guide/section_sdk_manage_images.xml:12(title)
msgid "List images"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:159(td)
msgid "List flavors"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:165(td)
msgid "Boot an instance using flavor and image names (if names are unique)"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:167(replaceable) ./doc/user-guide/app_cheat_sheet.xml:260(replaceable)
msgid "FLAVOR"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:173(td)
msgid "Login to instance"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:176(replaceable)
msgid "NETNS_NAME"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:176(replaceable)
msgid "USER"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:179(para)
msgid "Note, in CirrOS the password for user <literal>cirros</literal> is \"cubswin:)\" without the quotes."
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:185(td)
msgid "Show details of instance"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:192(td)
msgid "View console log of instance"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:198(td)
msgid "Set metadata on an instance"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:204(td) ./doc/user-guide/section_dashboard_launch_instances.xml:70(title)
msgid "Create an instance snapshot"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:211(th)
msgid "Pause, suspend, stop, rescue, resize, rebuild, reboot an instance"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:214(td)
msgid "Pause"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:221(td)
msgid "Unpause"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:227(td)
msgid "Suspend"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:233(td)
msgid "Unsuspend"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:239(td)
msgid "Stop"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:245(td)
msgid "Start"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:251(td)
msgid "Rescue"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:254(replaceable)
msgid "RESCUE_IMAGE"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:258(td)
msgid "Resize"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:266(td)
msgid "Rebuild"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:273(td)
msgid "Reboot"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:280(td)
msgid "Inject user data and files into an instance"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:282(replaceable)
msgid "FILE"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:282(replaceable)
msgid "INSTANCE"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:286(para)
msgid "To validate that the file is there, ssh into the instance, and look in <filename>/var/lib/cloud</filename> for the file."
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:292(th)
msgid "Inject a keypair into an instance and access the instance with that keypair"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:296(td)
msgid "Create keypair"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:303(td)
msgid "Boot"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:310(td)
msgid "Use ssh to connect to the instance"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:317(th)
msgid "Manage security groups"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:320(td)
msgid "Add rules to default security group allowing ping and SSH between instances in the default security group"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:330(caption)
msgid "Networking (neutron)"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:341(td) ./doc/user-guide/section_sdk_neutron.xml:99(title)
msgid "Create network"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:347(td)
msgid "Create a subnet"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:349(replaceable)
msgid "NETWORK_NAME"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:349(replaceable) ./doc/user-guide/section_dashboard_access_and_security.xml:84(literal) ./doc/user-guide/section_dashboard_access_and_security.xml:88(guilabel) ./doc/user-guide/section_dashboard_access_and_security.xml:126(literal) ./doc/user-guide/section_dashboard_access_and_security.xml:129(guilabel)
msgid "CIDR"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:354(td)
msgid "List network and subnet"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:361(td)
msgid "Examine details of network and subnet"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:363(replaceable) ./doc/user-guide/app_cheat_sheet.xml:364(replaceable)
msgid "ID_OR_NAME_OF_NETWORK"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:371(caption)
msgid "Block Storage (cinder)"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:382(th)
msgid "Manage volumes and volume snapshots"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:385(td)
msgid "Create a new volume"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:387(replaceable)
msgid "SIZE_IN_GB"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:392(td)
msgid "Boot an instance and attach to volume"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:398(td)
msgid "List volumes, notice status of volume"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:404(td)
msgid "Attach volume to instance after instance is active, and volume is available"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:407(replaceable) ./doc/user-guide/section_cli_trove.xml:216(replaceable) ./doc/user-guide/section_cli_trove.xml:287(replaceable) ./doc/user-guide/section_cli_trove.xml:381(replaceable) ./doc/user-guide/section_cli_trove.xml:402(replaceable) ./doc/user-guide/section_cli_trove.xml:413(replaceable) ./doc/user-guide/section_cli_trove.xml:431(replaceable) ./doc/user-guide/section_cli_trove.xml:483(replaceable) ./doc/user-guide/section_cli_trove.xml:508(replaceable)
msgid "INSTANCE_ID"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:407(replaceable)
msgid "VOLUME_ID"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:412(th)
msgid "Manage volumes after login into the instance"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:415(td)
msgid "List storage devices"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:421(td)
msgid "Make filesystem on volume"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:427(td)
msgid "Create a mountpoint"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:433(td)
msgid "Mount the volume at the mountpoint"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:439(td)
msgid "Create a file on the volume"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:446(td)
msgid "Unmount the volume"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:455(caption)
msgid "Object Storage (swift)"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:466(td)
msgid "Display information for the account, container, or object"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:469(replaceable)
msgid "ACCOUNT"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:470(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:27(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:46(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:95(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:97(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:102(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:116(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:121(replaceable)
msgid "CONTAINER"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:471(replaceable)
msgid "OBJECT"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:475(td)
msgid "List containers"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:481(td) ./doc/user-guide/section_dashboard_manage_containers.xml:20(title)
msgid "Create a container"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:483(replaceable) ./doc/user-guide/app_cheat_sheet.xml:489(replaceable) ./doc/user-guide/app_cheat_sheet.xml:502(replaceable) ./doc/user-guide/app_cheat_sheet.xml:508(replaceable)
msgid "CONTAINER_NAME"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:487(td)
msgid "Upload file to a container"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:489(replaceable) ./doc/user-guide/app_cheat_sheet.xml:502(replaceable) ./doc/user-guide/app_cheat_sheet.xml:508(replaceable)
msgid "FILE_NAME"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:494(td)
msgid "List objects in container"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:500(td)
msgid "Download object from container"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:506(td)
msgid "Upload with chunks, for large file"
msgstr ""

#: ./doc/user-guide/app_cheat_sheet.xml:508(replaceable)
msgid "SIZE"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:7(title)
msgid "Create and manage object containers"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:9(para)
msgid "OpenStack Object Storage provides a distributed, API-accessible storage platform that can be integrated directly into an application or used to store any type of file, including VM images, backups, archives, or media files. In the OpenStack Dashboard, you can only manage containers and objects."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:14(para)
msgid "In OpenStack Object Storage, containers provide storage for objects in a manner similar to a Windows folder or Linux file directory, though they cannot be nested. An object in OpenStack consists of the file to be stored in the container and any accompanying metadata."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:23(para) ./doc/user-guide/section_dashboard_manage_containers.xml:45(para) ./doc/user-guide/section_dashboard_manage_containers.xml:80(para) ./doc/user-guide/section_dashboard_manage_containers.xml:104(para) ./doc/user-guide/section_dashboard_manage_containers.xml:145(para) ./doc/user-guide/section_dashboard_manage_containers.xml:172(para)
msgid "Log in to the dashboard, choose a project, and click <guilabel>Containers</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:27(para)
msgid "Click <guibutton>Create Container</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:30(para)
msgid "In the Create Container dialog box, enter a name for the container, and then click <guibutton>Create Container</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:35(para)
msgid "You have successfully created a container."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:36(para)
msgid "To delete a container, click the <guibutton>More</guibutton> button and select <guilabel>Delete Container</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:42(title)
msgid "Upload an object"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:49(para) ./doc/user-guide/section_dashboard_manage_containers.xml:84(para) ./doc/user-guide/section_dashboard_manage_containers.xml:108(para) ./doc/user-guide/section_dashboard_manage_containers.xml:149(para) ./doc/user-guide/section_dashboard_manage_containers.xml:176(para)
msgid "Select the container in which you want to store your object."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:52(para) ./doc/user-guide/section_dashboard_manage_containers.xml:67(para) ./doc/user-guide/section_dashboard_manage_containers.xml:152(para)
msgid "Click <guibutton>Upload Object</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:53(para) ./doc/user-guide/section_dashboard_manage_containers.xml:153(para)
msgid "The Upload Object To Container: <replaceable>&lt;name&gt;</replaceable> dialog box is displayed. <replaceable>&lt;name&gt;</replaceable> is the name of the container to which you are uploading the object."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:60(para) ./doc/user-guide/section_dashboard_manage_containers.xml:160(para)
msgid "Enter a name for the object."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:63(para) ./doc/user-guide/section_dashboard_manage_containers.xml:91(para)
msgid "Browse to and select the file that you want to upload."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:70(para)
msgid "You have successfully uploaded an object to the container."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:71(para) ./doc/user-guide/section_dashboard_manage_containers.xml:98(para)
msgid "To delete an object, click the <guibutton>More</guibutton> button and select <guilabel>Delete Object</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:76(title)
msgid "Manage an object"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:78(title)
msgid "To edit an object"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:87(para)
msgid "Click <guibutton>More</guibutton> and choose <guilabel>Edit</guilabel> from the dropdown list."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:88(para)
msgid "The Edit Object dialog box is displayed."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:94(para) ./doc/user-guide/section_dashboard_manage_containers.xml:163(para)
msgid "Click <guibutton>Update Object</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:102(title)
msgid "To copy an object from one container to another"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:111(para)
msgid "Click <guibutton>More</guibutton> and choose <guilabel>Copy</guilabel> from the dropdown list."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:115(para)
msgid "In the Copy Object: launch dialog box, enter the following values:"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:120(para)
msgid "<guilabel>Destination Container</guilabel>: Choose the destination container from the list."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:124(para)
msgid "<guilabel>Path</guilabel>: Specify a path in which the new copy should be stored inside of the selected container."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:129(para)
msgid "<guilabel>Destination object name</guilabel>: Enter a name for the object in the new container."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:137(para)
msgid "Click <guibutton>Copy Object</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:141(title)
msgid "To create a metadata-only object without a file"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:142(para)
msgid "You can create a new object in container without a file available and can upload the file later when it is ready. This temporary object acts a place-holder for a new object, and enables the user to share object metadata and URL info in advance."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:167(title)
msgid "To create a pseudo-folder"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:168(para)
msgid "Pseudo-folders are similar to folders in your desktop operating system. They are virtual collections defined by a common prefix on the object's name."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:179(para)
msgid "Click <guibutton>Create Pseudo-folder</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:181(para)
msgid "The Create Pseudo-Folder in Container <replaceable>&lt;name&gt; </replaceable> dialog box is displayed. <replaceable>&lt;name&gt; </replaceable> is the name of the container to which you are uploading the object."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:188(para)
msgid "Enter a name for the pseudo-folder."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:190(para)
msgid "A slash (/) character is used as the delimiter for pseudo-folders in the Object Store."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_containers.xml:194(para)
msgid "Click <guibutton>Create</guibutton>."
msgstr ""

#: ./doc/user-guide/section_sdk_auth_glance.xml:7(title)
msgid "Authenticate against an Image Service endpoint"
msgstr ""

#: ./doc/user-guide/section_sdk_auth_glance.xml:8(para)
msgid "To authenticate against an Image Service endpoint, instantiate a <link href=\"http://docs.openstack.org/developer/python-glanceclient/api/glanceclient.v2.client.html#glanceclient.v2.client.Client\"> glanceclient.v2.client.Client</link> object:"
msgstr ""

#: ./doc/user-guide/ch_dashboard.xml:10(title)
msgid "OpenStack dashboard"
msgstr ""

#: ./doc/user-guide/ch_dashboard.xml:12(para)
msgid "As a cloud end user, you can use the OpenStack dashboard to provision your own resources within the limits set by administrators. You can modify the examples provided in this section to create other types and sizes of server instances."
msgstr ""

#: ./doc/user-guide/section_sdk_auth_keystone.xml:7(title)
msgid "Authenticate against an Identity endpoint"
msgstr ""

#: ./doc/user-guide/section_sdk_auth_keystone.xml:8(para)
msgid "To authenticate against the Identity v2.0 endpoint, instantiate a <link href=\"http://docs.openstack.org/developer/python-keystoneclient/api/keystoneclient.v2_0.client.html#keystoneclient.v2_0.client.Client\"> keystoneclient.v_20.client.Client</link> object:"
msgstr ""

#: ./doc/user-guide/section_sdk_auth_keystone.xml:19(para)
msgid "After you instantiate a <classname>Client</classname> object, you can retrieve the token by accessing its <literal>auth_token</literal> attribute object:"
msgstr ""

#: ./doc/user-guide/section_sdk_auth_keystone.xml:25(para)
msgid "If the OpenStack cloud is configured to use public-key infrastructure (PKI) tokens, the Python script output looks something like this:"
msgstr ""

#: ./doc/user-guide/section_sdk_auth_keystone.xml:36(para)
msgid "This example shows a subset of a PKI token. A complete token is over 5000 characters long."
msgstr ""

#: ./doc/user-guide/section_sdk_auth_neutron.xml:7(title)
msgid "Authenticate against a Networking endpoint"
msgstr ""

#: ./doc/user-guide/section_sdk_auth_neutron.xml:8(para)
msgid "To authenticate against a Networking endpoint, instantiate a <classname>neutronclient.v_2_0.client.Client</classname> object:"
msgstr ""

#: ./doc/user-guide/section_sdk_auth_neutron.xml:19(para)
msgid "You can also authenticate by explicitly specifying the endpoint and token:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:11(title) ./doc/user-guide/section_dashboard_access_and_security.xml:7(title) ./doc/user-guide/section_sdk_configure_instances.xml:7(title)
msgid "Configure access and security for instances"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:13(para)
msgid "When you launch a virtual machine, you can inject a <emphasis role=\"italic\">key pair</emphasis>, which provides SSH access to your instance. For this to work, the image must contain the <literal>cloud-init</literal> package."
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:17(para)
msgid "You create at least one key pair for each project. You can use the key pair for multiple instances that belong to that project. If you generate a key pair with an external tool, you can import it into OpenStack."
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:20(para)
msgid "If an image uses a static root password or a static key setneither is recommendedyou must not provide a key pair when you launch the instance."
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:21(para)
msgid "A <emphasis role=\"italic\">security group</emphasis> is a named collection of network access rules that you use to limit the types of traffic that have access to instances. When you launch an instance, you can assign one or more security groups to it. If you do not create security groups, new instances are automatically assigned to the default security group, unless you explicitly specify a different security group."
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:28(para)
msgid "The associated <emphasis role=\"italic\">rules</emphasis> in each security group control the traffic to instances in the group. Any incoming traffic that is not matched by a rule is denied access by default. You can add rules to or remove rules from a security group, and you can modify rules for the default and any other security group."
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:34(para)
msgid "You can modify the rules in a security group to allow access to instances through different ports and protocols. For example, you can modify rules to allow access to instances through SSH, to ping instances, or to allow UDP traffic; for example, for a DNS server running on an instance. You specify the following parameters for rules:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:42(para)
msgid "<emphasis role=\"bold\">Source of traffic</emphasis>. Enable traffic to instances from either IP addresses inside the cloud from other group members or from all IP addresses."
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:48(para)
msgid "<emphasis role=\"bold\">Protocol</emphasis>. Choose TCP for SSH, ICMP for pings, or UDP."
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:52(para)
msgid "<emphasis role=\"bold\">Destination port on virtual machine</emphasis>. Define a port range. To open a single port only, enter the same value twice. ICMP does not support ports; instead, you enter values to define the codes and types of ICMP traffic to be allowed."
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:59(para)
msgid "Rules are automatically enforced as soon as you create or modify them."
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:71(title) ./doc/user-guide/section_dashboard_access_and_security.xml:142(title)
msgid "Add a key pair"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:73(para)
msgid "You can generate a key pair or upload an existing public key."
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:76(para)
msgid "To generate a key pair, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:77(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:88(replaceable)
msgid "MY_KEY"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:78(para)
msgid "The command generates a key pair with the name that you specify fir <replaceable>KEY_NAME</replaceable>, writes the private key to the <filename>.pem</filename> file that you specify, and registers the public key at the Nova database."
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:85(para)
msgid "To set the permissions of the <filename>.pem</filename> file so that only you can read and write to it, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:93(title) ./doc/user-guide/section_dashboard_access_and_security.xml:172(title)
msgid "Import a key pair"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:96(para)
msgid "If you have already generated a key pair and the public key is located at <filename>~/.ssh/id_rsa.pub</filename>, run the following command to upload the public key:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:100(para)
msgid "The command registers the public key at the Nova database and names the key pair the name that you specify for <literal><replaceable>KEY_NAME</replaceable></literal>."
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:105(para)
msgid "To ensure that the key pair has been successfully imported, list key pairs as follows:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:112(title) ./doc/user-guide/section_sdk_configure_instances.xml:73(title)
msgid "Create and manage security groups"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:115(para)
msgid "To list the security groups for the current project, including descriptions, enter the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:120(para)
msgid "To create a security group with a specified name and description, enter the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:123(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:128(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:148(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:158(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:165(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:178(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:185(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:203(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:215(replaceable)
msgid "SECURITY_GROUP_NAME"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:123(replaceable)
msgid "GROUP_DESCRIPTION"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:126(para)
msgid "To delete a specified group, enter the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:130(para)
msgid "You cannot delete the default security group for a project. Also, you cannot delete a security group that is assigned to a running instance."
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:139(title) ./doc/user-guide/section_sdk_configure_instances.xml:98(title)
msgid "Create and manage security group rules"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:141(para)
msgid "Modify security group rules with the <placeholder-1/> commands. Before you begin, source the OpenStack RC file. For details, see <xref linkend=\"cli_openrc\"/>."
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:146(para)
msgid "To list the rules for a security group, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:151(para)
msgid "To allow SSH access to the instances, choose one of the following options:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:155(para)
msgid "Allow access from all IP addresses, specified as IP subnet <filename>0.0.0.0/0</filename> in CIDR notation:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:161(para)
msgid "Allow access only from IP addresses from other security groups (source groups) to access the specified port:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:165(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:185(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:203(replaceable)
msgid "SOURCE_GROUP_NAME"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:170(para)
msgid "To allow pinging of the instances, choose one of the following options:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:174(para)
msgid "Allow pinging from all IP addresses, specified as IP subnet <filename>0.0.0.0/0</filename> in CIDR notation:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:178(para)
msgid "This allows access to all codes and all types of ICMP traffic."
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:182(para)
msgid "Allow only members of other security groups (source groups) to ping instances:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:190(para)
msgid "To allow access through a UDP port, such as allowing access to a DNS server that runs on a VM, choose one of the following options:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:195(para)
msgid "Allow UDP access from IP addresses, specified as IP subnet <filename>0.0.0.0/0</filename> in CIDR notation:<placeholder-1/>"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:200(para)
msgid "Allow only IP addresses from other security groups (source groups) to access the specified port:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:209(title)
msgid "Delete a security group rule"
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:210(para)
msgid "To delete a security group rule, specify the same arguments that you used to create the rule."
msgstr ""

#: ./doc/user-guide/section_cli_nova_configure_instances.xml:213(para)
msgid "For example, to delete the security group rule that permits SSH access from all IP addresses, run the following command."
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:7(title)
msgid "Manage IP addresses"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:8(para)
msgid "Each instance has a private, fixed IP address and can also have a public, or floating, address. Private IP addresses are used for communication between instances, and public addresses are used for communication with networks outside the cloud, including the Internet."
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:12(para)
msgid "When you launch an instance, it is automatically assigned a private IP address that stays the same until you explicitly terminate the instance. Rebooting an instance has no effect on the private IP address."
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:16(para)
msgid "A pool of floating IP addresses, configured by the cloud administrator, is available in OpenStack Compute. The project quota defines the maximum number of floating IP addresses that you can allocate to the project. After you allocate a floating IP address to a project, you can:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:23(para)
msgid "Associate the floating IP address with an instance of the project. Only one floating IP address can be allocated to an instance at any given time."
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:27(para)
msgid "Disassociate a floating IP address from an instance in the project."
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:30(para)
msgid "Delete a floating IP from the project; deleting a floating IP automatically deletes that IP's associations."
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:35(para)
msgid "Use the <placeholder-1/> commands to manage floating IP addresses."
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:38(title)
msgid "List floating IP address information"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:41(para)
msgid "To list all pools that provide floating IP addresses, run:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:49(para)
msgid "If this list is empty, the cloud administrator must configure a pool of floating IP addresses."
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:52(para)
msgid "To list all floating IP addresses that are allocated to the current project, run:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:60(para)
msgid "For each floating IP address that is allocated to the current project, the command outputs the floating IP address, the ID for the instance to which the floating IP address is assigned, the associated fixed IP address, and the pool from which the floating IP address was allocated."
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:68(title)
msgid "Associate floating IP addresses"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:69(para)
msgid "You can assign a floating IP address to a project and to an instance."
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:72(para)
msgid "Run the following command to allocate a floating IP address to the current project. By default, the floating IP address is allocated from the <systemitem>public</systemitem> pool. The command outputs the allocated IP address."
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:82(para)
msgid "If more than one IP address pool is available, you can specify the pool from which to allocate the IP address, using the pool's name. For example, to allocate a floating IP address from the <literal>test</literal> pool, run:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:89(para)
msgid "List all project instances with which a floating IP address could be associated:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:100(para)
msgid "Associate an IP address with an instance in the project, as follows:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:101(replaceable) ./doc/user-guide/section_cli_nova_floating_ips.xml:119(replaceable) ./doc/user-guide/section_cli_nova_floating_ips.xml:129(replaceable)
msgid "INSTANCE_NAME_OR_ID"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:101(replaceable) ./doc/user-guide/section_cli_nova_floating_ips.xml:119(replaceable) ./doc/user-guide/section_cli_nova_floating_ips.xml:129(replaceable) ./doc/user-guide/section_cli_nova_floating_ips.xml:133(replaceable)
msgid "FLOATING_IP_ADDRESS"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:102(para) ./doc/user-guide/hot/section_hot_spec.xml:311(para) ./doc/user-guide/hot/section_hot_spec.xml:330(para) ./doc/user-guide/hot/section_hot_spec.xml:351(para) ./doc/user-guide/hot/section_hot_spec.xml:702(para) ./doc/user-guide/hot/section_basic_resources.xml:320(para)
msgid "For example:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:106(para)
msgid "Notice that the instance is now associated with two IP addresses:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:114(para)
msgid "After you associate the IP address and configure security group rules for the instance, the instance is publicly available at the floating IP address."
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:116(para)
msgid "If an instance is connected to multiple networks, you can associate a floating IP address with a specific fixed IP address using the optional <parameter>--fixed-address</parameter> parameter:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:119(replaceable)
msgid "FIXED_IP_ADDRESS"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:125(title)
msgid "Disassociate floating IP addresses"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:128(para)
msgid "Release a floating IP address from an instance, as follows:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:132(para)
msgid "Release the floating IP address from the current project, as follows:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_floating_ips.xml:134(para)
msgid "The IP address is returned to the pool of IP addresses that is available for all projects. If the IP address is still associated with a running instance, it is automatically disassociated from that instance."
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:7(title)
msgid "Stop and start an instance"
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:8(para)
msgid "Use one of the following methods to stop and start an instance."
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:11(title)
msgid "Pause and unpause an instance"
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:14(para)
msgid "To pause an instance, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:16(para)
msgid "This command stores the state of the VM in RAM. A paused instance continues to run in a frozen state."
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:18(para)
msgid "To unpause the instance, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:24(title)
msgid "Suspend and resume an instance"
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:26(para)
msgid "Administrative users might want to suspend an instance if it is infrequently used or to perform system maintenance. When you suspend an instance, its VM state is stored on disk, all memory is written to disk, and the virtual machine is stopped. Suspending an instance is similar to placing a device in hibernation; memory and vCPUs become available to create other instances."
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:34(para)
msgid "To initiate a hypervisor-level suspend operation, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:39(para)
msgid "To resume a suspended instance, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:46(title)
msgid "Shelve and unshelve an instance"
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:47(para)
msgid "Shelving is useful if you have an instance that you are not using, but would like retain in your list of servers. For example, you can stop an instance at the end of a work week, and resume work again at the start of the next week. All associated data and resources are kept; however, anything still in memory is not retained. If a shelved instance is no longer needed, it can also be entirely removed."
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:52(para)
msgid "You can complete the following shelving tasks:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:54(term)
msgid "Shelve an instance"
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:55(para)
msgid "Shuts down the instance, and stores it together with associated data and resources (a snapshot is taken if not volume backed). Anything in memory is lost. Use the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:58(replaceable) ./doc/user-guide/section_cli_nova_startstop.xml:63(replaceable) ./doc/user-guide/section_cli_nova_startstop.xml:70(replaceable)
msgid "SERVERNAME"
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:61(term)
msgid "Unshelve an instance"
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:62(para)
msgid "Restores the instance:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:66(term)
msgid "Remove a shelved instance"
msgstr ""

#: ./doc/user-guide/section_cli_nova_startstop.xml:67(para)
msgid "Removes the instance from the server; data and resource associations are deleted. If an instance is no longer needed, you can move that instance off the hypervisor in order to minimize resource usage:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_manage_instances.xml:7(title)
msgid "Manage instances and hosts"
msgstr ""

#: ./doc/user-guide/section_cli_nova_manage_instances.xml:8(para)
msgid "Instances are virtual machines that run inside the cloud on physical compute nodes. The Compute service manages instances. A host is the node on which a group of instances resides."
msgstr ""

#: ./doc/user-guide/section_cli_nova_manage_instances.xml:12(para)
msgid "This section describes how to perform the different tasks involved in instance management, such as adding floating IP addresses, stopping and starting instances, and terminating instances. This section also discusses node management tasks."
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:9(title)
msgid "OpenStack End User Guide"
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:10(titleabbrev)
msgid "End User Guide"
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:18(orgname) ./doc/user-guide/bk-user-guide.xml:23(holder)
msgid "OpenStack Foundation"
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:22(year)
msgid "2014"
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:25(releaseinfo)
msgid "current"
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:26(productname)
msgid "OpenStack"
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:30(remark)
msgid "Copyright details are filled in by the template."
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:35(para)
msgid "OpenStack is an open-source cloud computing platform for public and private clouds. A series of interrelated projects deliver a cloud infrastructure solution. This guide shows OpenStack end users how to create and manage resources in an OpenStack cloud with the OpenStack dashboard and OpenStack client commands."
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:42(para)
msgid "This guide documents OpenStack Juno, OpenStack Icehouse and OpenStack Havana releases."
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:47(date)
msgid "2014-10-15"
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:51(para)
msgid "For the Juno release, this guide has been updated with information about the Database Service for OpenStack (trove)."
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:61(date)
msgid "2014-05-09"
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:65(para)
msgid "Add a command line cheat sheet."
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:72(date)
msgid "2014-04-17"
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:76(para)
msgid "For the Icehouse release, this guide has been updated with changes to the dashboard plus the moving of the command reference appendix as indicated below."
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:86(date)
msgid "2014-01-31"
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:90(para)
msgid "Removed the command reference appendix. This information is now in the <link href=\"http://docs.openstack.org/cli-reference/content/\"><citetitle>OpenStack Command-Line Interface Reference</citetitle></link>."
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:100(date)
msgid "2013-12-30"
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:104(para)
msgid "Added the OpenStack Python SDK chapter."
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:111(date)
msgid "2013-10-17"
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:115(para)
msgid "Havana release."
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:121(date)
msgid "2013-08-19"
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:125(para)
msgid "Editorial changes."
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:131(date)
msgid "2013-07-29"
msgstr ""

#: ./doc/user-guide/bk-user-guide.xml:135(para)
msgid "First edition of this document."
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:8(title)
msgid "Use snapshots to migrate instances"
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:9(para)
msgid "To use snapshots to migrate instances from OpenStack projects to clouds, complete these steps."
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:12(para)
msgid "In the source project, perform the following steps:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:15(link)
msgid "Create a snapshot of the instance."
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:18(link)
msgid "Download the snapshot as an image."
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:22(para)
msgid "In the destination project, perform the following steps:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:25(link)
msgid "Import the snapshot to the new environment."
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:28(link)
msgid "Boot a new instance from the snapshot."
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:33(para)
msgid "Some cloud providers allow only administrators to perform this task."
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:36(title)
msgid "Create a snapshot of the instance"
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:39(para)
msgid "Shut down the source VM before you take the snapshot to ensure that all data is flushed to disk. If necessary, list the instances to view get the instance name."
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:50(para)
msgid "Use the <placeholder-1/> command to confirm that the instance shows a <literal>SHUTOFF</literal> status."
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:60(para)
msgid "Use the <placeholder-1/> command to take a snapshot. Use the <placeholder-2/> command to check the status until the status is <literal>ACTIVE</literal>:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:79(title)
msgid "Download the snapshot as an image"
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:82(para)
msgid "Get the image ID:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:91(para)
msgid "Download the snapshot by using the image ID that was returned in the previous step:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:95(para)
msgid "The <placeholder-1/> command requires the image ID and cannot use the image name."
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:98(para)
msgid "Ensure there is sufficient space on the destination file system for the image file."
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:104(para)
msgid "Make the image available to the new environment, either through HTTP or with direct upload to a machine (<placeholder-1/>)."
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:110(title)
msgid "Import the snapshot to new environment"
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:111(para)
msgid "In the new project or cloud environment, import the snapshot:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:113(replaceable)
msgid "IMAGE_URL"
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:116(title)
msgid "Boot a new instance from the snapshot"
msgstr ""

#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:117(para)
msgid "In the new project or cloud environment, use the snapshot to create the new instance:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:11(title)
msgid "Store metadata on a configuration drive"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:12(para)
msgid "You can configure OpenStack to write metadata to a special configuration drive that attaches to the instance when it boots. The instance can mount this drive and read files from it to get information that is normally available through the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/section_metadata-service.html\">metadata service</link>. This metadata is different from the user data."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:19(para)
msgid "One use case for using the configuration drive is to pass a networking configuration when you do not use DHCP to assign IP addresses to instances. For example, you might pass the IP address configuration for the instance through the configuration drive, which the instance can mount and access before you configure the network settings for the instance."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:25(para)
msgid "Any modern guest operating system that is capable of mounting an ISO 9660 or VFAT file system can use the configuration drive."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:28(title)
msgid "Requirements and guidelines"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:29(para)
msgid "To use the configuration drive, you must follow the following requirements for the compute host and image."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:32(title)
msgid "Compute host requirements"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:34(para)
msgid "The following hypervisors support the configuration drive: libvirt, XenServer, Hyper-V, and VMware."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:38(para)
msgid "To use configuration drive with libvirt, XenServer, or VMware, you must first install the <package>genisoimage</package> package on each compute host. Otherwise, instances do not boot properly."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:43(para)
msgid "Use the <literal>mkisofs_cmd</literal> flag to set the path where you install the <package>genisoimage</package> program. If <package>genisoimage</package> is in same path as the <systemitem class=\"service\">nova-compute</systemitem> service, you do not need to set this flag."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:52(para)
msgid "To use configuration drive with Hyper-V, you must set the <literal>mkisofs_cmd</literal> value to the full path to an <literal>mkisofs.exe</literal> installation. Additionally, you must set the <literal>qemu_img_cmd</literal> value in the <literal>hyperv</literal> configuration section to the full path to an <literal>qemu-img</literal> command installation."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:63(title)
msgid "Image requirements"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:65(para)
msgid "An image built with a recent version of the <package>cloud-init</package> package can automatically access metadata passed through the configuration drive. The <package>cloud-init</package> package version 0.7.1 works with Ubuntu and Fedora based images, such as Red Hat Enterprise Linux."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:73(para)
msgid "If an image does not have the <package>cloud-init</package> package installed, you must customize the image to run a script that mounts the configuration drive on boot, reads the data from the drive, and takes appropriate action such as adding the public key to an account. See <xref linkend=\"config_drive_contents\"/> for details about how data is organized on the configuration drive."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:83(para)
msgid "If you use Xen with a configuration drive, use the <literal>xenapi_disable_agent</literal> configuration parameter to disable the agent."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:90(title)
msgid "Guidelines"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:92(para)
msgid "Do not rely on the presence of the EC2 metadata in the configuration drive, because this content might be removed in a future release. For example, do not rely on files in the <filename>ec2</filename> directory."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:98(para)
msgid "When you create images that access configuration drive data and multiple directories are under the <filename>openstack</filename> directory, always select the highest API version by date that your consumer supports. For example, if your guest image supports the 2012-03-05, 2012-08-05, and 2013-04-13 versions, try 2013-04-13 first and fall back to a previous version if 2013-04-13 is not present."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:110(title)
msgid "Enable and access the configuration drive"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:113(para)
msgid "To enable the configuration drive, pass the <literal>--config-drive true</literal> parameter to the <placeholder-1/> command."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:117(para)
msgid "The following example enables the configuration drive and passes user data, two files, and two key/value metadata pairs, all of which are accessible from the configuration drive:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:122(para)
msgid "You can also configure the Compute service to always create a configuration drive by setting the following option in the <filename>/etc/nova/nova.conf</filename> file:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:127(para)
msgid "If a user passes the <literal>--config-drive true</literal> flag to the <placeholder-1/> command, an administrator cannot disable the configuration drive."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:135(para)
msgid "If your guest operating system supports accessing disk by label, you can mount the configuration drive as the <filename>/dev/disk/by-label/<replaceable>configurationDriveVolumeLabel</replaceable></filename> device. In the following example, the configuration drive has the <filename>config-2</filename> volume label."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:143(para)
msgid "Ensure that you use at least version 0.3.1 of CirrOS for configuration drive support."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:146(para)
msgid "If your guest operating system does not use <literal>udev</literal>, the <filename>/dev/disk/by-label</filename> directory is not present."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:150(para)
msgid "You can use the <placeholder-1/> command to identify the block device that corresponds to the configuration drive. For example, when you boot the CirrOS image with the <literal>m1.tiny</literal> flavor, the device is <filename>/dev/vdb</filename>:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:158(para)
msgid "Once identified, you can mount the device:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:165(title)
msgid "Configuration drive contents"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:166(para)
msgid "In this example, the contents of the configuration drive are as follows:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:179(para)
msgid "The files that appear on the configuration drive depend on the arguments that you pass to the <placeholder-1/> command."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:184(title)
msgid "OpenStack metadata format"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:185(para)
msgid "The following example shows the contents of the <filename>openstack/2012-08-10/meta_data.json</filename> and <filename>openstack/latest/meta_data.json</filename> files. These files are identical. The file contents are formatted for readability."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:191(para)
msgid "Note the effect of the <literal>--file /etc/network/interfaces=/home/myuser/instance-interfaces</literal> argument that was passed to the <placeholder-1/> command. The contents of this file are contained in the <filename>openstack/content/0000</filename> file on the configuration drive, and the path is specified as <filename>/etc/network/interfaces</filename> in the <filename>meta_data.json</filename> file."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:202(title)
msgid "EC2 metadata format"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:203(para)
msgid "The following example shows the contents of the <filename>ec2/2009-04-04/meta-data.json</filename> and the <filename>ec2/latest/meta-data.json</filename> files. These files are identical. The file contents are formatted to improve readability."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:211(title)
msgid "User data"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:212(para)
msgid "The <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> file are present only if the <literal>--user-data</literal> flag and the contents of the user data file are passed to the <placeholder-1/> command."
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:222(title)
msgid "Configuration drive format"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:223(para)
msgid "The default format of the configuration drive as an ISO 9660 file system. To explicitly specify the ISO 9660 format, add the following line to the <filename>/etc/nova/nova.conf</filename> file:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:229(para)
msgid "By default, you cannot attach the configuration drive image as a CD drive instead of as a disk drive. To attach a CD drive, add the following line to the <filename>/etc/nova/nova.conf</filename> file:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:234(para)
msgid "For legacy reasons, you can configure the configuration drive to use VFAT format instead of ISO 9660. It is unlikely that you would require VFAT format because ISO 9660 is widely supported across operating systems. However, to use the VFAT format, add the following line to the <filename>/etc/nova/nova.conf</filename> file:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_config-drive.xml:243(para)
msgid "If you choose VFAT, the configuration drive is 64MB."
msgstr ""

#: ./doc/user-guide/section_cli_nova_terminate.xml:7(title)
msgid "Delete an instance"
msgstr ""

#: ./doc/user-guide/section_cli_nova_terminate.xml:8(para)
msgid "When you no longer need an instance, you can delete it."
msgstr ""

#: ./doc/user-guide/section_cli_nova_terminate.xml:10(para)
msgid "List all instances:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_terminate.xml:20(para)
msgid "Run the <placeholder-1/> command to delete the instance. The following example shows deletion of the <filename>newServer</filename> instance, which is in <literal>ERROR</literal> state:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_terminate.xml:23(para)
msgid "The command does not notify that your server was deleted."
msgstr ""

#: ./doc/user-guide/section_cli_nova_terminate.xml:24(para)
msgid "To verify that the server was deleted, run the <placeholder-1/> command:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_terminate.xml:32(para)
msgid "The deleted instance does not appear in the list."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:13(title)
msgid "Create and access a database"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:14(para)
msgid "Assume that you have installed the Database service and populated your data store with images for the type and versions of databases that you want, and that you can create and access a database."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:17(para)
msgid "This example shows you how to create and access a MySQL 5.5 database."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:19(title)
msgid "To create and access a database"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:21(title)
msgid "Determine which flavor to use for your database"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:22(para)
msgid "When you create a database instance, you must specify a nova flavor. The flavor indicates various characteristics of the instance, such as RAM, root volume size, and so on. The default nova flavors are not sufficient to create database instances. You might need to create or obtain some new nova flavors that work for databases."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:26(para)
msgid "The first step is to list flavors by using the nova <placeholder-1/> command."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:28(para)
msgid "Here are the default flavors, although you may have additional custom flavors in your environment:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:40(para)
msgid "Now take a look at the minimum requirements for various database instances:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:49(th)
msgid "Database"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:50(th)
msgid "RAM (MB)"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:51(th)
msgid "Disk (GB)"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:52(th)
msgid "VCPUs"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:58(para)
msgid "MySQL"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:61(para) ./doc/user-guide/section_cli_trove.xml:103(para)
msgid "512"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:64(para) ./doc/user-guide/section_cli_trove.xml:78(para) ./doc/user-guide/section_cli_trove.xml:92(para) ./doc/user-guide/section_cli_trove.xml:106(para)
msgid "5"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:67(para) ./doc/user-guide/section_cli_trove.xml:81(para) ./doc/user-guide/section_cli_trove.xml:95(para) ./doc/user-guide/section_cli_trove.xml:109(para)
msgid "1"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:72(para)
msgid "Cassandra"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:75(para)
msgid "2048"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:86(para)
msgid "MongoDB"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:89(para)
msgid "1024"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:100(para)
msgid "Redis"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:116(para)
msgid "If you have a custom flavor that meets the needs of the database that you want to create, proceed to <xref linkend=\"create-database-instance\"/> and use that flavor."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:121(para)
msgid "If your environment does not have a suitable flavor, an administrative user must create a custom flavor by using the nova <placeholder-1/> command."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:127(title)
msgid "MySQL example"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:128(para)
msgid "This example creates a flavor that you can use with a MySQL database. This example has the following attributes:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:133(para)
msgid "Flavor name: <literal>mysql_minimum</literal>"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:136(para)
msgid "Flavor ID: You must use an ID that is not already in use. In this example, IDs 1 through 5 are in use, so use ID <literal>6</literal>."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:140(para)
msgid "RAM: <literal>512</literal>"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:143(para)
msgid "Root volume size in GB: <literal>5</literal>"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:146(para)
msgid "Virtual CPUs: <literal>1</literal>"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:158(para)
msgid "This example creates a database instance with the following characteristics:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:161(para)
msgid "Name of the instance: <literal>mysql_instance_1</literal>"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:164(para)
msgid "Database flavor: <literal>6</literal>"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:167(para)
msgid "In addition, this command specifies these options for the instance:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:170(para)
msgid "A volume size of <literal>5</literal> (5 GB)."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:173(para)
msgid "The <literal>myDB</literal> database."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:176(para)
msgid "The database is based on the <literal>mysql</literal> data store and the <literal>mysql-5.5</literal> datastore_version."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:180(para)
msgid "The <literal>userA</literal> user with the <literal>password</literal> password."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:202(title)
msgid "Get the IP address of the database instance"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:203(para)
msgid "First, use the trove <placeholder-1/> command to list all instances and their IDs:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:211(para)
msgid "This command returns the instance ID of your new instance."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:212(para)
msgid "You can now pass in the instance ID with the trove <placeholder-1/> command to get the IP address of the instance. In this example, replace <replaceable>INSTANCE_ID</replaceable> with <literal>5599dad6-731e-44df-bb60-488da3da9cfe</literal>."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:231(para)
msgid "This command returns the IP address of the database instance."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:234(title)
msgid "Access the new database"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:235(para)
msgid "You can now access the new database you just created (myDB) by using typical database access commands. In this MySQL example, replace <replaceable>IP_ADDRESS</replaceable> with <literal>172.16.200.2</literal>."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:238(replaceable) ./doc/user-guide/section_cli_nova_search_ip.xml:11(replaceable)
msgid "IP_ADDRESS"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:251(title)
msgid "Backup the database instance"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:252(para)
msgid "As background, assume that you have <link linkend=\"create_db\">created a database instance</link> with the following characteristics:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:256(para)
msgid "Name of the database instance: <literal>guest1</literal>"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:259(para)
msgid "Flavor ID: <literal>10</literal>"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:262(para)
msgid "Root volume size: <literal>2</literal>"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:265(para)
msgid "Databases: <literal>db1</literal> and <literal>db2</literal>"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:268(para)
msgid "Users: The <literal>user1</literal> user with the <literal>password</literal> password"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:272(para)
msgid "First, get the ID of the <literal>guest1</literal> database instance by using the trove <placeholder-1/> command:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:280(para)
msgid "Back up the database instance by using the trove <placeholder-1/> command. In this example, the backup is called <literal>backup1</literal>. In this example, replace <replaceable>INSTANCE_ID</replaceable> with <literal>97b4b853-80f6-414f-ba6f-c6f455a79ae6</literal>:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:285(para)
msgid "This command syntax pertains only to python-troveclient version 1.0.6 and later. Earlier versions require you to pass in the backup name as the first argument."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:302(para)
msgid "Note that the command returns both the ID of the original instance (<literal>instance_id</literal>) and the ID of the backup artifact (<literal>id</literal>)."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:305(para)
msgid "Later on, use the trove <placeholder-1/> command to get this information:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:313(para)
msgid "You can get additional information about the backup by using the trove <placeholder-1/> command and passing in the <replaceable>BACKUP_ID</replaceable>, which is <literal>8af30763-61fd-4aab-8fe8-57d528911138</literal>."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:317(replaceable) ./doc/user-guide/section_cli_trove.xml:351(replaceable) ./doc/user-guide/section_cli_trove.xml:483(replaceable) ./doc/user-guide/section_cli_trove.xml:508(replaceable) ./doc/user-guide/section_cli_trove.xml:534(replaceable)
msgid "BACKUP_ID"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:334(title)
msgid "Restore a database instance"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:335(para)
msgid "Now assume that your <literal>guest1</literal> database instance is damaged and you need to restore it. In this example, you use the trove <placeholder-1/> command to create a new database instance called <literal>guest2</literal>."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:340(para)
msgid "You specify that the new <literal>guest2</literal> instance has the same flavor (<literal>10</literal>) and the same root volume size (<literal>2</literal>) as the original <literal>guest1</literal> instance."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:345(para)
msgid "You use the <code>--backup</code> argument to indicate that this new instance is based on the backup artifact identified by <replaceable>BACKUP_ID</replaceable>. In this example, replace <replaceable>BACKUP_ID</replaceable> with <literal>8af30763-61fd-4aab-8fe8-57d528911138</literal>."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:367(title)
msgid "Verify backup"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:368(para)
msgid "Now check that the new <literal>guest2</literal> instance has the same characteristics as the original <literal>guest1</literal> instance."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:370(para)
msgid "Start by getting the ID of the new <literal>guest2</literal> instance."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:378(para)
msgid "Use the trove <placeholder-1/> command to display information about the new guest2 instance. Pass in guest2's <replaceable>INSTANCE_ID</replaceable>, which is <literal>ac7a2b35-a9b4-4ff6-beac-a1bcee86d04b</literal>."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:397(para)
msgid "Note that the data store, flavor ID, and volume size have the same values as in the original <literal>guest1</literal> instance."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:399(para)
msgid "Use the trove <placeholder-1/> command to check that the original databases (<literal>db1</literal> and <literal>db2</literal>) are present on the restored instance."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:411(para)
msgid "Use the trove <placeholder-1/> command to check that the original user (<literal>user1</literal>) is present on the restored instance."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:421(title)
msgid "Notify users"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:422(para)
msgid "Tell the users who were accessing the now-disabled <literal>guest1</literal> database instance that they can now access <literal>guest2</literal>. Provide them with <literal>guest2</literal>'s name, IP address, and any other information they might need. (You can get this information by using the trove <placeholder-1/> command.)"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:428(title)
msgid "Clean up"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:429(para)
msgid "At this point, you might want to delete the disabled <literal>guest1</literal> instance, by using the trove <placeholder-1/> command."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:436(title)
msgid "Use incremental backups"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:437(para)
msgid "Incremental backups let you chain together a series of backups. You start with a regular backup. Then, when you want to create a subsequent incremental backup, you specify the parent backup."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:440(para)
msgid "Restoring a database instance from an incremental backup is the same as creating a database instance from a regular backupthe Database service handles the complexities of applying the chain of incremental backups."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:443(para)
msgid "This example shows you how to use incremental backups with a MySQL database."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:445(title)
msgid "Assumptions"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:446(para)
msgid "Assume that you have <link linkend=\"backup_db\">created a regular backup</link> for the following database instance:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:451(para)
msgid "Instance name: <literal>guest1</literal>"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:454(para)
msgid "ID of the instance (<replaceable>INSTANCE_ID</replaceable>): <literal>792a6a56-278f-4a01-9997-d997fa126370</literal>"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:458(para)
msgid "ID of the regular backup artifact (<replaceable>BACKUP_ID</replaceable>): <literal>6dc3a9b7-1f3e-4954-8582-3f2e4942cddd</literal>"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:463(title)
msgid "To create and use incremental backups"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:465(title)
msgid "Create your first incremental backup"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:466(para)
msgid "Use the trove <placeholder-1/> command and specify:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:469(para)
msgid "The <replaceable>INSTANCE_ID</replaceable> of the database instance you are doing the incremental backup for (in this example, <literal>792a6a56-278f-4a01-9997-d997fa126370</literal>)"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:474(para)
msgid "The name of the incremental backup you are creating: <literal>backup1.1</literal>"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:478(para)
msgid "The <replaceable>BACKUP_ID</replaceable> of the parent backup. In this case, the parent is the regular backup, with an ID of <literal>6dc3a9b7-1f3e-4954-8582-3f2e4942cddd</literal>"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:498(para)
msgid "Note that this command returns both the ID of the database instance you are incrementally backing up (<literal>instance_id</literal>) and a new ID for the new incremental backup artifact you just created (<literal>id</literal>)."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:503(title)
msgid "Create your second incremental backup"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:504(para)
msgid "The name of your second incremental backup is <literal>backup1.2</literal>. This time, when you specify the parent, pass in the ID of the incremental backup you just created in the previous step (<literal>backup1.1</literal>). In this example, it is <literal>1d474981-a006-4f62-b25f-43d7b8a7097e</literal>."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:525(title)
msgid "Restore using incremental backups"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:526(para)
msgid "Now assume that your <literal>guest1</literal> database instance is damaged and you need to restore it from your incremental backups. In this example, you use the trove <placeholder-1/> command to create a new database instance called <literal>guest2</literal>."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:530(para)
msgid "To incorporate your incremental backups, you simply use the <code>--backup</code> parameter to pass in the <replaceable>BACKUP_ID</replaceable> of your most recent incremental backup. The Database service handles the complexities of applying the chain of all previous incremental backups."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:556(title)
msgid "Manage database configuration"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:557(para)
msgid "You can manage database configuration tasks by using configuration groups. Configuration groups let you set configuration options, in bulk, on one or more databases."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:559(para)
msgid "This example assumes you have <link linkend=\"create_db\">created a MySQL database</link> and shows you how to use a configuration group to configure it. Although this example sets just one option on one database, you can use these same procedures to set multiple options on multiple database instances throughout your environment. This can provide significant time savings in managing your cloud."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:565(title)
msgid "To bulk-configure a database or databases"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:567(title)
msgid "List available options"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:568(para)
msgid "First, determine which configuration options you can set. Different data store versions have different configuration options."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:570(para)
msgid "List the names and IDs of all available versions of the <literal>mysql</literal> data store:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:578(para)
msgid "Pass in the data store version ID with the trove <placeholder-1/> command to get the available options:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:581(replaceable)
msgid "DATASTORE_VERSION_ID"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:620(para)
msgid "In this example, the <placeholder-1/> command returns a list of options that work with MySQL 5.5."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:624(title)
msgid "Create a configuration group"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:625(para)
msgid "A configuration group contains a comma-separated list of key-value pairs. Each pair consists of a configuration option and its value."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:627(para)
msgid "You can create a configuration group by using the trove <placeholder-1/> command. The general syntax for this command is:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:630(replaceable)
msgid "VALUES"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:633(para)
msgid "<replaceable>NAME</replaceable>. The name you want to use for this group."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:636(para)
msgid "<replaceable>VALUES</replaceable>. The list of key-value pairs."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:639(para)
msgid "<replaceable>DATASTORE_NAME</replaceable>. The name of the associated data store."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:643(para)
msgid "Set <replaceable>VALUES</replaceable> as a JSON dictionary, for example:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:645(para)
msgid "This example creates a configuration group called <literal>group1</literal>. <literal>group1</literal> contains just one key and value pair, and this pair sets the <option>sync_binlog</option> option to <literal>1</literal>."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:660(title)
msgid "Examine your existing configuration"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:661(para)
msgid "Before you use the newly-created configuration group, look at how the <option>sync_binlog</option> option is configured on your database. Replace the following sample connection values with values that connect to your database:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:673(para)
msgid "As you can see, the <option>sync_binlog</option> option is currently set to <literal>0</literal> for the <literal>myDB7</literal> database."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:677(title)
msgid "Change the database configuration using a configuration group"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:678(para)
msgid "You can change a database's configuration by attaching a configuration group to a database instance. You do this by using the trove <placeholder-1/> command and passing in the ID of the database instance and the ID of the configuration group."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:681(para)
msgid "Get the ID of the database instance:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:688(para)
msgid "Get the ID of the configuration group:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:695(para)
msgid "Attach the configuration group to the database instance:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:697(para)
msgid "This command syntax pertains only to python-troveclient version 1.0.6 and later. Earlier versions require you to pass in the configuration group ID as the first argument."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:699(replaceable)
msgid "DB_INSTANCE_ID"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:699(replaceable)
msgid "CONFIG_GROUP_ID"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:702(title)
msgid "Re-examine the database configuration"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:703(para)
msgid "Display the <option>sync_binlog</option> setting again:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:710(para)
msgid "As you can see, the <option>sync_binlog</option> option is now set to <literal>1</literal>, as specified in the <literal>group1</literal> configuration group."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:716(title)
msgid "Conclusion"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:717(para)
msgid "Using a configuration group to set a single option on a single database is obviously a trivial example. However, configuration groups can provide major efficiencies when you consider that:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:723(para)
msgid "A configuration group can specify a large number of option values."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:726(para)
msgid "You can apply a configuration group to hundreds or thousands of database instances in your environment."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:730(para)
msgid "Used in this way, configuration groups let you modify your database cloud configuration, on the fly, on a massive scale."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:733(title)
msgid "Maintenance"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:734(para)
msgid "There are also a number of useful maintenance features for working with configuration groups. You can:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:739(para)
msgid "Disassociate a configuration group from a database instance, using the trove <placeholder-1/> command."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:743(para)
msgid "Modify a configuration group on the fly, using the trove <placeholder-1/> command."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:747(para)
msgid "Find out what instances are using a configuration group, using the trove <placeholder-1/> command."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:751(para)
msgid "Delete a configuration group, using the trove <placeholder-1/> command. You might want to do this if no instances use a group."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:757(title)
msgid "Set up database replication"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:758(para)
msgid "You can create a replica of an existing database instance. When you make subsequent changes to the original instance, the system automatically applies those changes to the replica."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:761(para)
msgid "Replicas are read-only."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:764(para)
msgid "When you create a replica, do not specify the <option>--users</option> or <option>--databases</option> options."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:767(para)
msgid "You can choose a smaller volume or flavor for a replica than for the original, but the replica's volume must be big enough to hold the data snapshot from the original."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:770(para)
msgid "This example shows you how to replicate a MySQL database instance."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:772(title)
msgid "To set up replication"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:774(title)
msgid "Get the instance ID"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:775(para)
msgid "Get the ID of the original instance you want to replicate:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:784(title)
msgid "Create the replica"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:785(para)
msgid "Create a new instance that will be a replica of the original instance. You do this by passing in the <option>--replica_of</option> option with the trove <placeholder-1/> command. This example creates a replica called <literal>replica_1</literal>. <literal>replica_1</literal> is a replica of the original instance, <literal>base_1</literal>:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:786(replaceable)
msgid "ID_OF_ORIGINAL_INSTANCE"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:789(title)
msgid "Verify replication status"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:790(para)
msgid "Pass in <literal>replica_1</literal>'s instance ID with the trove <placeholder-1/> command to verify that the newly created <literal>replica_1</literal> instance is a replica of the original <literal>base_1</literal>. Note that the <literal>replica_of</literal> property is set to the ID of <literal>base_1</literal>."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:791(replaceable)
msgid "INSTANCE_ID_OF_REPLICA_1"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:806(para)
msgid "Now pass in <literal>base_1</literal>'s instance ID with the trove <placeholder-1/> command to list the replica(s) associated with the original instance. Note that the <literal>replicas</literal> property is set to the ID of <literal>replica_1</literal>. If there are multiple replicas, they appear as a comma-separated list."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:807(replaceable)
msgid "INSTANCE_ID_OF_BASE_1"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:826(title)
msgid "Detach the replica"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:827(para)
msgid "If the original instance goes down, you can detach the replica. The replica becomes a standalone database instance. You can then take the new standalone instance and create a new replica of that instance."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:828(para)
msgid "You detach a replica using the trove <placeholder-1/> command:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:829(replaceable)
msgid "INSTANCE_ID_OF_REPLICA"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:834(title)
msgid "Set up database clustering"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:835(para)
msgid "You can store data across multiple machines by setting up MongoDB sharded clusters."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:836(para)
msgid "Each cluster includes:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:839(para)
msgid "One or more <emphasis>shards</emphasis>. Each shard consists of a three member replica set (three instances organized as a replica set)."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:842(para)
msgid "One or more <emphasis>query routers</emphasis>. A query router is the machine that your application actually connects to. This machine is responsible for communicating with the config server to figure out where the requested data is stored. It then accesses and returns the data from the appropriate shard(s)."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:845(para)
msgid "One or more <emphasis>config servers</emphasis>. Config servers store the metadata that links requested data with the shard that contains it."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:848(para)
msgid "This example shows you how to set up a MongoDB sharded cluster."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:851(title)
msgid "Before you begin"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:852(para)
msgid "Make sure that:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:856(para)
msgid "The administrative user has registered a MongoDB datastore type and version."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:859(para)
msgid "The administrative user has created an appropriate <link linkend=\"create_db\">flavor that meets the MongoDB minimum requirements</link>."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:864(title)
msgid "To set up clustering"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:866(title)
msgid "Create a cluster"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:867(para)
msgid "Create a cluster by using the trove <placeholder-1/> command. This command creates a one-shard cluster. Pass in:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:870(para)
msgid "The name of the cluster."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:873(para)
msgid "The name and version of the datastore you want to use."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:876(para)
msgid "The three instances you want to include in the replication set for the first shard. Specify each instance by using the <option>--instance</option> argument and the associated flavor ID and volume size. Use the same flavor ID and volume size for each instance. In this example, flavor <literal>7</literal> is a custom flavor that meets the MongoDB minimum requirements."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:896(title)
msgid "Display cluster information"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:897(para)
msgid "Display information about a cluster by using the trove <placeholder-1/> command. Pass in the ID of the cluster."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:898(para)
msgid "The cluster ID display when you first create a cluster. (If you need to find it later on, use the trove <placeholder-1/> command to list the names and IDs of all the clusters in your system.)"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:899(replaceable) ./doc/user-guide/section_cli_trove.xml:924(replaceable) ./doc/user-guide/section_cli_trove.xml:965(replaceable)
msgid "CLUSTER_ID"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:916(title)
msgid "Your application connects to this IP address"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:917(para)
msgid "The trove <placeholder-1/> command displays the IP address of the query router. This is the IP address your application uses to retrieve data from the database."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:922(title)
msgid "List cluster instances"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:923(para)
msgid "List the instances in a cluster by using the trove <placeholder-1/> command."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:933(title)
msgid "Naming conventions for replication sets and instances"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:934(para)
msgid "Note that the <literal>Name</literal> column displays an instance name that includes the replication set name. The replication set names and instance names are automatically generated, following these rules:"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:939(title)
msgid "Replication set name"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:940(para)
msgid "This name consists of the cluster name, followed by the string -rs<replaceable>n</replaceable>, where <replaceable>n</replaceable> is 1 for the first replication set you create, 2 for the second replication set, and so on. In this example, the cluster name is <literal>cluster1</literal>, and there is only one replication set, so the replication set name is <literal>cluster1-rs1</literal>."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:945(title)
msgid "Instance name"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:946(para)
msgid "This name consists of the replication set name followed by the string -<replaceable>n</replaceable>, where <replaceable>n</replaceable> is 1 for the first instance in a replication set, 2 for the the second instance, and so on. In this example, the instance names are <literal>cluster1-rs1-1</literal>, <literal>cluster1-rs1-2</literal>, and <literal>cluster1-rs1-3</literal>."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:952(title)
msgid "List clusters"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:953(para)
msgid "List all the clusters in your system, using the trove <placeholder-1/> command."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:963(title)
msgid "Delete a cluster"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:964(para)
msgid "Delete a cluster, using the trove <placeholder-1/> command."
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:969(title)
msgid "Query routers and config servers"
msgstr ""

#: ./doc/user-guide/section_cli_trove.xml:970(para)
msgid "Each cluster includes at least one query router and one config server. Query routers and config servers count against your quota. When you delete a cluster, the system deletes the associated query router(s) and config server(s)."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:7(title)
msgid "Launch and manage instances"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:10(para)
msgid "You can <link linkend=\"dashboard_launch_instances_from_image\">launch an instance</link> from the following sources:"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:13(para)
msgid "Images uploaded to the OpenStack Image Service, as described in <xref linkend=\"dashboard_manage_images\"/>."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:15(para)
msgid "Image that you have copied to a persistent volume. The instance launches from the volume, which is provided by the <systemitem class=\"service\">cinder-volume</systemitem> API through iSCSI."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:24(title)
msgid "Connect to your instance by using SSH"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:25(para)
msgid "To use SSH to connect to your instance, you use the downloaded keypair file."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:28(para)
msgid "The user name is <literal>ubuntu</literal> for the Ubuntu cloud images on TryStack."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:33(para)
msgid "Copy the IP address for your instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:36(para)
msgid "Use the <placeholder-1/> command to make a secure connection to the instance. For example:"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:42(para)
msgid "At the prompt, type <literal>yes</literal>."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:48(title)
msgid "Track usage for instances"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:49(para)
msgid "You can track usage for instances for each project. You can track costs per month by showing metrics like number of vCPUs, disks, RAM, and uptime for all your instances."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:55(para)
msgid "Log in to the dashboard, choose a project, and click <guilabel>Overview</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:59(para)
msgid "To query the instance usage for a month, select a month and click <guibutton>Submit</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:64(para)
msgid "To download a summary, click <guibutton>Download CSV Summary</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:73(para) ./doc/user-guide/section_dashboard_launch_instances.xml:99(para)
msgid "Log in to the dashboard, choose a project, and click <guilabel>Instances</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:77(para)
msgid "Select the instance from which to create a snapshot."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:80(para)
msgid "In the <guilabel>Actions</guilabel> column, click <guilabel>Create Snapshot</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:84(para)
msgid "In the Create Snapshot dialog box, enter a name for the snapshot, and click <guibutton>Create Snapshot</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:86(para)
msgid "The <guilabel>Images</guilabel> category shows the instance snapshot."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:90(para)
msgid "To launch an instance from the snapshot, select the snapshot and click <guibutton>Launch</guibutton>. Proceed with <xref linkend=\"dashboard_launch_instances_from_image\"/>."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:96(title)
msgid "Manage an instance"
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:103(para)
msgid "Select an instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:106(para)
msgid "In the <guilabel>More</guilabel> list in the <guilabel>Actions</guilabel> column, select the state."
msgstr ""

#: ./doc/user-guide/section_dashboard_launch_instances.xml:108(para)
msgid "You can resize or rebuild an instance. You can also choose to view the instance console log, edit instance or the security groups. Depending on the current state of the instance, you can pause, resume, suspend, soft or hard reboot, or terminate it."
msgstr ""

#: ./doc/user-guide/section_cli_nova_userdata.xml:7(title)
msgid "Provide user data to instances"
msgstr ""

#: ./doc/user-guide/section_cli_nova_userdata.xml:8(para)
msgid "A <glossterm baseform=\"user data\">user data</glossterm> file is a special key in the metadata service that holds a file that cloud-aware applications in the guest instance can access. For example, one application that uses user data is the <link href=\"https://help.ubuntu.com/community/CloudInit\">cloud-init</link> system, which is an open-source package from Ubuntu that is available on various Linux distributions and which handles early initialization of a cloud instance."
msgstr ""

#: ./doc/user-guide/section_cli_nova_userdata.xml:15(para)
msgid "You can place user data in a local file and pass it through the <parameter>--user-data &lt;user-data-file&gt;</parameter> parameter at instance creation:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_get_console.xml:7(title)
msgid "Access an instance through a console"
msgstr ""

#: ./doc/user-guide/section_cli_nova_get_console.xml:8(para)
msgid "In order to see the console output of an instance, regardless of whether or not the console log has output, either VNC or SPICE is used. This allows for relaying keyboard and mouse activity to and from the instance in question."
msgstr ""

#: ./doc/user-guide/section_cli_nova_get_console.xml:12(para)
msgid "There are three common remote console access methods in use with OpenStack:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_get_console.xml:15(term)
msgid "novnc"
msgstr ""

#: ./doc/user-guide/section_cli_nova_get_console.xml:16(para)
msgid "An in-browser VNC client implemented using HTML5 Canvas and WebSockets"
msgstr ""

#: ./doc/user-guide/section_cli_nova_get_console.xml:19(term)
msgid "spice"
msgstr ""

#: ./doc/user-guide/section_cli_nova_get_console.xml:20(para)
msgid "A complete in-browser client solution for interaction with virtualized instances"
msgstr ""

#: ./doc/user-guide/section_cli_nova_get_console.xml:23(term)
msgid "xvpvnc"
msgstr ""

#: ./doc/user-guide/section_cli_nova_get_console.xml:24(para)
msgid "A Java client offering console access to an instance"
msgstr ""

#: ./doc/user-guide/section_cli_nova_get_console.xml:28(para)
msgid "Example:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_get_console.xml:29(para)
msgid "To access an instance through a remote console, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_get_console.xml:30(replaceable)
msgid "VNC_TYPE"
msgstr ""

#: ./doc/user-guide/section_cli_nova_get_console.xml:31(para)
msgid "The command returns a URL from which you can access your instance:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_get_console.xml:37(para)
msgid "<replaceable>VNC_TYPE</replaceable> can be replaced by any of the above values as connection types."
msgstr ""

#: ./doc/user-guide/section_cli_nova_get_console.xml:39(para)
msgid "When using SPICE to view the console of an instance, a browser plugin can be used directly on the instance page, or the <placeholder-1/> command can be used with it, as well, by returning a token-authenticated address such as the one above."
msgstr ""

#: ./doc/user-guide/section_cli_nova_get_console.xml:44(para)
msgid "For further information and comparisons (including security considerations, please see the <link href=\"http://docs.openstack.org/security-guide/content/ch026_compute.html\">security guide</link>."
msgstr ""

#: ./doc/user-guide/ch_cli.xml:10(title)
msgid "OpenStack command-line clients"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:9(para)
msgid "To use the information in this section, you should have a general understanding of OpenStack Networking, OpenStack Compute, and the integration between the two. You should also have access to a plug-in that implements the Networking API v2.0."
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:16(para)
msgid "Make sure that you set the relevant environment variables."
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:18(para)
msgid "As an example, see the sample shell file that sets these variables to get credentials:"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:21(replaceable)
msgid "password"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:23(replaceable)
msgid "IPADDRESS"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:26(title)
msgid "Get credentials"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:27(para)
msgid "The examples in this section use the <code>get_credentials</code> method:"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:39(para)
msgid "Use the <code>get_credentials()</code> method to populate and get a dictionary:"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:44(title)
msgid "Get Nova credentials"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:45(para)
msgid "Few examples in this section use the <code>get_nova_credentials</code> method:"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:57(para)
msgid "Use the <code>get_nova_credentials()</code> method to populate and get a dictionary:"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:63(title)
msgid "Print values"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:64(para)
msgid "The examples in this section use the <code>print_values</code> and <code>print_values_server</code> methods:"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:95(para)
msgid "This code resides in the <filename>utils.py</filename> file, which all samples import."
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:100(para)
msgid "The following program creates a network:"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:126(title)
msgid "List networks"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:127(para)
msgid "The following program lists networks:"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:138(para) ./doc/user-guide/section_sdk_neutron.xml:197(para) ./doc/user-guide/section_sdk_neutron.xml:438(para)
msgid "For <code>print_values</code> see <xref linkend=\"sdk_neutron_print_values\"/>."
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:143(title)
msgid "Create ports"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:144(para)
msgid "The following program creates a port:"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:175(para)
msgid "For <code>get_nova_credentials</code> see <xref linkend=\"sdk_neutron_get_nova_credentials\"/>."
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:178(para) ./doc/user-guide/section_sdk_neutron.xml:194(para)
msgid "For <code>get_credentials</code> see <xref linkend=\"sdk_neutron_get_credentials\"/>."
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:183(title)
msgid "List ports"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:184(para)
msgid "The following program lists ports:"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:202(title)
msgid "List server ports"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:203(para)
msgid "The following program lists the ports for a server:"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:239(title)
msgid "Create router and add port to subnet"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:240(para)
msgid "This example queries OpenStack Networking to create a router and add a port to a subnet."
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:243(title)
msgid "To create a router and add a port to a subnet"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:254(para)
msgid "Get Nova Credentials. See <xref linkend=\"sdk_neutron_get_nova_credentials\"/>."
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:266(para)
msgid "Create a router and add a port to the subnet:"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:296(title)
msgid "Create router: complete code listing"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:335(title)
msgid "Delete a network"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:336(para)
msgid "This example queries OpenStack Networking to delete a network."
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:339(title)
msgid "To delete a network"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:346(para) ./doc/user-guide/section_sdk_neutron.xml:422(para) ./doc/user-guide/section_sdk_neutron.xml:472(para) ./doc/user-guide/section_sdk_neutron.xml:521(para)
msgid "Get credentials. See <xref linkend=\"sdk_neutron_get_credentials\"/>."
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:351(para) ./doc/user-guide/section_sdk_neutron.xml:427(para) ./doc/user-guide/section_sdk_neutron.xml:477(para) ./doc/user-guide/section_sdk_neutron.xml:526(para)
msgid "Instantiate the <literal>neutron</literal> client object by using the <literal>credentials</literal> dictionary object:"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:358(para)
msgid "Delete the network:"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:380(title)
msgid "Delete network: complete code listing"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:410(title)
msgid "List routers"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:411(para)
msgid "This example queries OpenStack Networking to list all routers."
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:414(title)
msgid "To list routers"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:434(para)
msgid "List the routers"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:444(title)
msgid "List routers: complete code listing"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:460(title)
msgid "List security groups"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:461(para)
msgid "This example queries OpenStack Networking to list security groups."
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:464(title)
msgid "To list security groups"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:484(para)
msgid "List Security groups"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:490(title)
msgid "List security groups: complete code listing"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:502(para)
msgid "OpenStack Networking security groups are case-sensitive while the <systemitem class=\"service\">nova-network</systemitem> security groups are case-insensitive."
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:509(title)
msgid "List subnets"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:510(para)
msgid "This example queries OpenStack Networking to list subnets."
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:513(title)
msgid "To list subnets"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:533(para)
msgid "List subnets:"
msgstr ""

#: ./doc/user-guide/section_sdk_neutron.xml:539(title)
msgid "List subnets: complete code listing"
msgstr ""

#: ./doc/user-guide/section_sdk_auth_nova.xml:7(title)
msgid "Authenticate against a Compute endpoint"
msgstr ""

#: ./doc/user-guide/section_sdk_auth_nova.xml:8(para)
msgid "To authenticate against a Compute endpoint, instantiate a <link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.client.html#novaclient.v1_1.client.Client\"> novaclient.v_1_1.client.Client</link> object:"
msgstr ""

#: ./doc/user-guide/section_sdk_auth_nova.xml:19(para)
msgid "Alternatively, you can instantiate a <classname>novaclient.client.Client</classname> object and pass the version number:"
msgstr ""

#: ./doc/user-guide/section_sdk_auth_nova.xml:29(para)
msgid "If you authenticate against an endpoint that uses a custom authentication back end, you must load the authentication plug-in and pass it to the constructor."
msgstr ""

#: ./doc/user-guide/section_sdk_auth_nova.xml:32(para)
msgid "The Rackspace public cloud is an OpenStack deployment that uses a custom authentication back end. To authenticate against this cloud, you must install the <link href=\"https://pypi.python.org/pypi/rackspace-novaclient/\"> rackspace-novaclient</link> library that contains the Rackspace authentication plug-in, called <literal>rackspace</literal>. The following Python code shows the additional modifications required to instantiate a <classname>Client</classname> object that can authenticate against the Rackspace custom authentication back end."
msgstr ""

#: ./doc/user-guide/section_sdk_auth_nova.xml:54(para)
msgid "If you set the <literal>OS_AUTH_SYSTEM</literal> environment variable, check for this variable in your Python script to determine whether you need to load a custom authentication back end:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_search_ip.xml:7(title)
msgid "Search for an instance using IP address"
msgstr ""

#: ./doc/user-guide/section_cli_nova_search_ip.xml:8(para)
msgid "You can search for an instance using the IP address parameter, <literal>--ip</literal>, with the <placeholder-1/> command."
msgstr ""

#: ./doc/user-guide/section_cli_nova_search_ip.xml:11(parameter) ./doc/user-guide/section_cli_nova_search_ip.xml:14(parameter)
msgid "ip"
msgstr ""

#: ./doc/user-guide/section_cli_nova_search_ip.xml:12(para)
msgid "The following example shows the results of a search on <filename>10.0.0.4</filename>."
msgstr ""

#: ./doc/user-guide/section_cli_nova_search_ip.xml:14(replaceable)
msgid "10.0.0.4"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:7(title)
msgid "Launch and manage stacks"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:9(para)
msgid "OpenStack Orchestration is a service that you can use to orchestrate multiple composite cloud applications. This service supports use of both the Amazon Web Services (AWS) CloudFormation template format through both a Query API that is compatible with CloudFormation and the native OpenStack <glossterm>Heat Orchestration Template (HOT)</glossterm> format through a REST API."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:31(title)
msgid "Launch a stack"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:34(para)
msgid "Log in to the dashboard, choose a project, and click <guibutton>Stacks</guibutton> in the <guilabel>Orchestration</guilabel> category on the <guilabel>Projects</guilabel> tab."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:40(para)
msgid "Click <guibutton>Launch Stack</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:44(para)
msgid "In the <guilabel>Select Template</guilabel> dialog box, specify the following values."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:51(guilabel)
msgid "Template Source"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:52(para)
msgid "Choose the source of the template from the list."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:55(guilabel)
msgid "Template URL/File/Data"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:56(para)
msgid "Depending on the source that you selected, enter the URL, browse to the file location, or directly include the template."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:61(guilabel)
msgid "Environment Source"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:62(para)
msgid "Choose the source of the environment from the list. The environment files contain additional settings for the stack."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:67(guilabel)
msgid "Environment URL/File/Data"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:68(para)
msgid "Depending on the source that you selected, enter the URL, browse to the file location, or directly include the environment."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:76(para) ./doc/user-guide/section_dashboard_stacks.xml:194(para)
msgid "Click <guibutton>Next</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:80(para)
msgid "In the <guilabel>Launch Stack</guilabel> dialog box, specify the following values."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:87(guilabel)
msgid "Stack Name"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:88(para)
msgid "Enter a name to identify the stack."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:91(guilabel)
msgid "Creation Timeout (minutes)"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:92(para)
msgid "Specify the number of minutes that can elapse before the launch of the stack times out."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:96(guilabel)
msgid "Rollback On Failure"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:97(para)
msgid "Select this check box if you want if you want the service to roll back changes if the stack fails to launch."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:102(guilabel)
msgid "Password for user \"demo\""
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:103(para)
msgid "Specify the password that the default user uses when the stack is created."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:107(guilabel)
msgid "DBUsername"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:108(para)
msgid "Specify the name of the database user."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:111(guilabel)
msgid "LinuxDistribution"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:112(para)
msgid "Specify the Linux distribution that is used in the stack."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:116(guilabel)
msgid "DBRootPassword"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:117(para)
msgid "Specify the root password for the database."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:120(guilabel)
msgid "KeyName"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:121(para)
msgid "Specify the name of the key pair to use to log in to the stack."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:125(guilabel)
msgid "DBName"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:126(para)
msgid "Specify the name of the database."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:129(guilabel)
msgid "DBPassword"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:130(para)
msgid "Specify the password for the database."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:133(guilabel)
msgid "InstanceType"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:134(para)
msgid "Specify the flavor for the instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:140(para)
msgid "Click <guilabel>Launch</guilabel> to create a stack."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:144(para)
msgid "The <guilabel>Stacks</guilabel> tab shows the stack."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:147(para)
msgid "After the stack is created, click on the stack name to see the following details:"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:151(guilabel)
msgid "Topology"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:153(para)
msgid "The topology of the stack."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:157(guilabel)
msgid "Overview"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:159(para)
msgid "The parameters and details of the stack."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:163(guilabel)
msgid "Resources"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:165(para)
msgid "The resources used by the stack."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:169(guilabel)
msgid "Events"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:171(para)
msgid "The events related to the stack."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:177(title)
msgid "Manage a stack"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:180(para) ./doc/user-guide/section_dashboard_stacks.xml:210(para)
msgid "Log in to the dashboard, choose a project, and click <guilabel>Stacks</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:184(para)
msgid "Select the stack that you want to update."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:187(para)
msgid "Click <guibutton>Change Stack Template</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:190(para)
msgid "In the <guilabel>Select Template</guilabel> dialog box, select the new template source or environment source."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:195(para)
msgid "The <guilabel>Update Stack Parameters</guilabel> window appears."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:198(para)
msgid "Enter new values for any parameters that you want to update."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:201(para)
msgid "Click <guibutton>Update</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:206(title)
msgid "Delete a stack"
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:207(para)
msgid "When you delete a stack, you cannot undo this action."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:214(para)
msgid "Select the stack that you want to delete."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:217(para)
msgid "Click <guibutton>Delete Stack</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_stacks.xml:221(para)
msgid "In the confirmation dialog box, click <guibutton>Delete Stack</guibutton> to confirm the deletion."
msgstr ""

#: ./doc/user-guide/section_sdk_authenticate.xml:7(title)
msgid "Authenticate"
msgstr ""

#: ./doc/user-guide/section_sdk_authenticate.xml:8(para)
msgid "When using the SDK, you must authenticate against an OpenStack endpoint before you can use OpenStack services. Each project uses a slightly different syntax for authentication."
msgstr ""

#: ./doc/user-guide/section_sdk_authenticate.xml:11(para)
msgid "You must typically authenticate against a specific version of a service. For example, a client might need to authenticate against Identity v2.0."
msgstr ""

#: ./doc/user-guide/section_sdk_authenticate.xml:14(para)
msgid "Python scripts that use the OpenStack SDK must have access to the credentials contained in the <link linkend=\"cli_openrc\">OpenStack RC file</link>. Because credentials are sensitive information, do not include them in your scripts. This guide assumes that users source the <filename><replaceable>PROJECT</replaceable>-openrc.sh</filename> file and access the credentials by using the environment variables in the Python scripts."
msgstr ""

#: ./doc/user-guide/section_sdk_manage_images.xml:9(para)
msgid "When working with images in the SDK, you will call both <literal>glance</literal> and <literal>nova</literal> methods."
msgstr ""

#: ./doc/user-guide/section_sdk_manage_images.xml:13(para)
msgid "To list the available images, call the <methodname>glanceclient.v2.images.Controller.list</methodname> method:"
msgstr ""

#: ./doc/user-guide/section_sdk_manage_images.xml:19(para)
msgid "The <methodname>images</methodname> method returns a Python generator, as shown in the following interaction with the Python interpreter:"
msgstr ""

#: ./doc/user-guide/section_sdk_manage_images.xml:78(title)
msgid "Get image by ID"
msgstr ""

#: ./doc/user-guide/section_sdk_manage_images.xml:79(para)
msgid "To retrieve an image object from its ID, call the <methodname> glanceclient.v2.images.Controller.get</methodname> method:"
msgstr ""

#: ./doc/user-guide/section_sdk_manage_images.xml:89(title)
msgid "Get image by name"
msgstr ""

#: ./doc/user-guide/section_sdk_manage_images.xml:90(para)
msgid "The Image Service Python bindings do not support the retrieval of an image object by name. However, the Compute Python bindings enable you to get an image object by name. To get an image object by name, call the <methodname> novaclient.v1_1.images.ImageManager.find</methodname> method:"
msgstr ""

#: ./doc/user-guide/section_sdk_manage_images.xml:103(para)
msgid "To upload an image, call the <methodname> glanceclient.v2.images.ImageManager.create</methodname> method:"
msgstr ""

#: ./doc/user-guide/section_sdk_install.xml:7(title)
msgid "Install the OpenStack SDK"
msgstr ""

#: ./doc/user-guide/section_sdk_install.xml:8(para)
msgid "Each OpenStack project has its own Python library. These libraries are bundled with the command-line clients. For example, the Python bindings for the Compute API are bundled with the <package>python-novaclient</package> package."
msgstr ""

#: ./doc/user-guide/section_sdk_install.xml:12(para)
msgid "For details about how to install the clients, see <link linkend=\"install_clients\">install the OpenStack command-line clients</link>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:9(para)
msgid "Before you launch an instance, you should add security group rules to enable users to ping and use SSH to connect to the instance. Security groups are sets of IP filter rules that define networking access and are applied to all instances within a project. To do so, you either <link linkend=\"security_groups_add_rule\">add rules to the default security group</link> or add a new security group with rules."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:15(para)
msgid "Key pairs are SSH credentials that are injected into an instance when it is launched. To use key pair injection, the image that the instance is based on must contain the <literal>cloud-init</literal> package. Each project should have at least one key pair. For more information, see <xref linkend=\"keypair_add\"/>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:21(para)
msgid "If you have generated a key pair with an external tool, you can import it into OpenStack. The key pair can be used for multiple instances that belong to a project. For more information, see <xref linkend=\"dashboard_import_keypair\"/>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:26(para)
msgid "When an instance is created in OpenStack, it is automatically assigned a fixed IP address in the network to which the instance is assigned. This IP address is permanently associated with the instance until the instance is terminated. However, in addition to the fixed IP address, a floating IP address can also be attached to an instance. Unlike fixed IP addresses, floating IP addresses are able to have their associations modified at any time, regardless of the state of the instances involved."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:36(title)
msgid "Add a rule to the default security group"
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:37(para)
msgid "This procedure enables SSH and ICMP (ping) access to instances. The rules apply to all instances within a given project, and should be set for every project unless there is a reason to prohibit SSH or ICMP access to the instances."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:43(para)
msgid "This procedure can be adjusted as necessary to add additional security group rules to a project, if your cloud requires them."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:48(para)
msgid "When adding a rule, you must specify the protocol used with the destination port or source port."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:52(para)
msgid "Log in to the dashboard, choose a project, and click <guilabel>Access &amp; Security</guilabel>. The <guilabel>Security Groups</guilabel> tab shows the security groups that are available for this project."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:59(para)
msgid "Select the <guilabel>default</guilabel> security group and click <guibutton>Edit Rules</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:64(para)
msgid "To allow SSH access, click <guibutton>Add Rule</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:68(para) ./doc/user-guide/section_dashboard_access_and_security.xml:111(para)
msgid "In the Add Rule dialog box, enter the following values:"
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:75(guilabel) ./doc/user-guide/section_dashboard_access_and_security.xml:117(guilabel)
msgid "Rule"
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:77(literal)
msgid "SSH"
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:81(guilabel) ./doc/user-guide/section_dashboard_access_and_security.xml:125(guilabel)
msgid "Remote"
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:90(literal) ./doc/user-guide/section_dashboard_access_and_security.xml:130(literal)
msgid "0.0.0.0/0"
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:96(para)
msgid "To accept requests from a particular range of IP addresses, specify the IP address block in the <guilabel>CIDR</guilabel> box."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:102(para) ./doc/user-guide/section_dashboard_access_and_security.xml:135(para)
msgid "Click <guibutton>Add</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:103(para)
msgid "Instances will now have SSH port 22 open for requests from any IP address."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:107(para)
msgid "To add an ICMP rule, click <guibutton>Add Rule</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:118(literal)
msgid "All ICMP"
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:121(guilabel)
msgid "Direction"
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:122(literal)
msgid "Ingress"
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:136(para)
msgid "Instances will now accept all incoming ICMP packets."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:143(para)
msgid "Create at least one key pair for each project."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:146(para) ./doc/user-guide/section_dashboard_access_and_security.xml:175(para) ./doc/user-guide/section_dashboard_access_and_security.xml:243(para)
msgid "Log in to the dashboard, choose a project, and click <guilabel>Access &amp; Security</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:151(para) ./doc/user-guide/section_dashboard_access_and_security.xml:180(para)
msgid "Click the <guilabel>Keypairs</guilabel> tab, which shows the key pairs that are available for this project."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:156(para)
msgid "Click <guibutton>Create Keypair</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:160(para)
msgid "In the Create Keypair dialog box, enter a name for your key pair, and click <guibutton>Create Keypair</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:166(para)
msgid "Respond to the prompt to download the key pair."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:185(para)
msgid "Click <guibutton>Import Keypair</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:189(para)
msgid "In the Import Keypair dialog box, enter the name of your key pair, copy the public key into the <guilabel>Public Key</guilabel> box, and then click <guibutton>Import Keypair</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:196(para)
msgid "Save the <filename>*.pem</filename> file locally."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:198(para)
msgid "To change its permissions so that only you can read and write to the file, run the following command:"
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:201(replaceable) ./doc/user-guide/section_dashboard_access_and_security.xml:217(replaceable)
msgid "yourPrivateKey"
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:203(para)
msgid "If you are using the dashboard from a Windows computer, use PuTTYgen to load the <filename>*.pem</filename> file and convert and save it as <filename>*.ppk</filename>. For more information see the <link href=\"http://winscp.net/eng/docs/ui_puttygen\">WinSCP web page for PuTTYgen</link>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:215(para)
msgid "To make the key pair known to SSH, run the <placeholder-1/> command."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:220(para)
msgid "The Compute database registers the public key of the key pair."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:222(para)
msgid "The dashboard lists the key pair on the <guilabel>Access &amp; Security</guilabel> tab."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:226(title)
msgid "Allocate a floating IP address to an instance"
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:227(para)
msgid "When an instance is created in OpenStack, it is automatically assigned a fixed IP address in the network to which the instance is assigned. This IP address is permanently associated with the instance until the instance is terminated."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:233(para)
msgid "However, in addition to the fixed IP address, a floating IP address can also be attached to an instance. Unlike fixed IP addresses, floating IP addresses can have their associations modified at any time, regardless of the state of the instances involved. This procedure details the reservation of a floating IP address from an existing pool of addresses and the association of that address with a specific instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:247(para)
msgid "Click the <guilabel>Floating IPs</guilabel> tab, which shows the floating IP addresses allocated to instances."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:252(para)
msgid "Click <guibutton>Allocate IP to Project</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:255(para)
msgid "Choose the pool from which to pick the IP address."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:259(para)
msgid "Click <guibutton>Allocate IP</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:262(para)
msgid "In the <guilabel>Floating IPs</guilabel> list, click <guibutton> Associate</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:270(para)
msgid "The <guilabel>IP Address</guilabel> field is filled automatically, but you can add a new IP address by clicking the <guibutton>+</guibutton> button."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:277(para)
msgid "In the <guilabel>Ports to be associated</guilabel> field, select a port from the list."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:280(para)
msgid "The list shows all the instances with their fixed IP addresses."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:266(para)
msgid "In the Manage Floating IP Associations dialog box, choose the following options: <placeholder-1/>"
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:287(para)
msgid "Click <guibutton>Associate</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:291(para)
msgid "To disassociate an IP address from an instance, click the <guibutton>Disassociate</guibutton> button."
msgstr ""

#: ./doc/user-guide/section_dashboard_access_and_security.xml:293(para)
msgid "To release the floating IP address back into the pool of addresses, click the <guibutton>More</guibutton> button and select the <guilabel>Release Floating IP</guilabel> option."
msgstr ""

#: ./doc/user-guide/ch_sdk.xml:8(title)
msgid "OpenStack Python SDK"
msgstr ""

#: ./doc/user-guide/ch_sdk.xml:10(para)
msgid "Use the OpenStack Python Software Development Kit (SDK) to write Python automation scripts that create and manage resources in your OpenStack cloud. The SDK implements Python bindings to the OpenStack API, which enables you to perform automation tasks in Python by making calls on Python objects rather than making REST calls directly. All OpenStack command-line tools are implemented using the Python SDK."
msgstr ""

#: ./doc/user-guide/ch_sdk.xml:17(para)
msgid "You should also be familiar with:"
msgstr ""

#: ./doc/user-guide/ch_sdk.xml:20(para)
msgid "RESTful web services"
msgstr ""

#: ./doc/user-guide/ch_sdk.xml:23(para)
msgid "HTTP/1.1"
msgstr ""

#: ./doc/user-guide/ch_sdk.xml:26(para)
msgid "JSON and XML data serialization formats"
msgstr ""

#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:7(title)
msgid "Change the size of your server"
msgstr ""

#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:8(para)
msgid "You change the size of a server by changing its flavor."
msgstr ""

#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:11(para)
msgid "Show information about your server, including its size, which is shown as the value of the flavor property."
msgstr ""

#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:44(para)
msgid "The size (flavor) of the server is <literal>m1.small (2)</literal>."
msgstr ""

#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:47(para)
msgid "List the available flavors with the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:60(para)
msgid "To resize the server, pass the server ID or name and the new flavor to the <placeholder-1/> command. Include the <literal>--poll</literal> parameter to report the resize progress."
msgstr ""

#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:68(para)
msgid "Show the status for your server:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:75(para)
msgid "When the resize completes, the status becomes VERIFY_RESIZE."
msgstr ""

#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:78(para)
msgid "Confirm the resize:"
msgstr ""

#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:80(para) ./doc/user-guide/section_cli_nova_resizerebuild.xml:86(para)
msgid "The server status becomes ACTIVE."
msgstr ""

#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:83(para)
msgid "If the resize fails or does not work as expected, you can revert the resize:"
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:7(title)
msgid "Manage objects and containers"
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:9(para)
msgid "The OpenStack Object Storage service provides the <placeholder-1/> client, which is a command-line interface (CLI). Use this client to list objects and containers, upload objects to containers, and download or delete objects from containers. You can also gather statistics and update metadata for accounts, containers, and objects."
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:15(para)
msgid "This client is based on the native swift client library, <literal>client.py</literal>, which seamlessly re-authenticates if the current token expires during processing, retries operations multiple times, and provides a processing concurrency of 10."
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:21(title)
msgid "Create and manage containers"
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:24(para)
msgid "To create a container, run the following command and replace <replaceable>CONTAINER</replaceable> with the name of your container."
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:29(para)
msgid "To list all containers: run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:33(para)
msgid "To check the status of containers, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:43(para)
msgid "You can also use the <placeholder-1/> command with the <replaceable>ACCOUNT</replaceable> or <replaceable>CONTAINER</replaceable> names as parameters."
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:62(title)
msgid "Manage access"
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:65(para)
msgid "Users have roles on accounts. For example, a user with the admin role has full access to all containers and objects in an account. You can set access control lists (ACLs) at the container level and support lists for read and write access, which you set with the <literal>X-Container-Read</literal> and <literal>X-Container-Write</literal> headers."
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:71(para)
msgid "To give a user read access, use the <placeholder-1/> command with the <parameter>-r</parameter> parameter. To give a user write access, use the <parameter>-w</parameter> parameter."
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:74(para)
msgid "The following example enables the <literal>testuser</literal> user to read objects in the container:"
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:77(para)
msgid "You can also use this command with a list of users."
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:80(para)
msgid "If you use StaticWeb middleware to enable Object Storage to serve public web content, use <literal>.r:</literal>, followed by a list of allowed referrers."
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:83(para)
msgid "The following command gives object access to all referring domains:"
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:90(title)
msgid "Manage objects"
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:93(para)
msgid "To upload an object to a container, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:95(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:97(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:102(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:121(replaceable)
msgid "OBJECT_FILENAME"
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:96(para)
msgid "To upload in chunks, for large files, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:97(replaceable)
msgid "CHUNK_SIZE"
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:100(para)
msgid "To check the status of the object, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:115(para)
msgid "To list the objects in a container, run the following command:"
msgstr ""

#: ./doc/user-guide/section_cli_swift_howto.xml:119(para)
msgid "To download an object from a container:, run the following command:"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:7(title)
msgid "Create and manage volumes"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:9(para)
msgid "Volumes are block storage devices that you attach to instances to enable persistent storage. You can attach a volume to a running instance or detach a volume and attach it to another instance at any time. You can also create a snapshot from or delete a volume. Only administrative users can create volume types."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:16(title) ./doc/user-guide/hot/section_basic_resources.xml:317(title)
msgid "Create a volume"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:19(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:137(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:171(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:213(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:252(para)
msgid "Log in to the dashboard, choose a project, and click <guibutton>Volumes</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:23(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:125(para)
msgid "Click <guibutton>Create Volume</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:24(para)
msgid "In the dialog box that opens, enter or select the following values."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:33(guilabel)
msgid "Volume Name"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:37(para)
msgid "Specify a name for the volume."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:48(para)
msgid "Optionally, provide a brief description for the volume."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:55(guilabel)
msgid "Type"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:59(para)
msgid "Leave this field blank."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:65(guilabel)
msgid "Size (GB)"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:69(para)
msgid "The size of the volume in gigabytes."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:76(guilabel)
msgid "Volume Source"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:80(para)
msgid "Select one of the following options:"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:83(guilabel)
msgid "No source, empty volume"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:84(para)
msgid "Creates an empty volume."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:85(para)
msgid "An empty volume does not contain a file system or a partition table."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:89(guilabel)
msgid "Snapshot"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:90(para)
msgid "If you choose this option, a new field for <guilabel>Use snapshot as a source</guilabel> displays. You can select the snapshot from the list."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:96(guilabel)
msgid "Image"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:97(para)
msgid "If you choose this option, a new field for <guilabel>Use image as a source</guilabel> displays. You can select the image from the list."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:100(para)
msgid "Select the <guilabel>Availability Zone</guilabel> from the list. By default, this value is set to the availability zone given by the cloud provider (for example, <literal>us-west</literal> or <literal>apac-south</literal>). For some cases, it could be <literal>nova</literal>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:108(guilabel)
msgid "Volume"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:109(para)
msgid "If you choose this option, a new field for <guilabel>Use volume as a source</guilabel> displays. You can select the volume from the list."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:115(para)
msgid "Options to use a snapshot or a volume as the source for a volume are displayed only if there are existing snapshots or volumes."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:128(para)
msgid "The dashboard shows the volume on the <guilabel>Volumes</guilabel> tab."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:132(title) ./doc/user-guide/hot/section_basic_resources.xml:347(title)
msgid "Attach a volume to an instance"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:133(para)
msgid "After you create one or more volumes, you can attach them to instances. You can attach a volume to one instance at a time."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:141(para)
msgid "Select the volume to add to an instance and click <guibutton>Edit Attachments</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:145(para)
msgid "In the <guilabel>Manage Volume Attachments</guilabel> dialog box, select an instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:149(para)
msgid "Enter the name of the device from which the volume is accessible by the instance."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:152(para)
msgid "The actual device name might differ from the volume name because of hypervisor settings."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:157(para)
msgid "Click <guibutton>Attach Volume</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:158(para)
msgid "The dashboard shows the instance to which the volume is now attached and the device name."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:162(para)
msgid "You can view the status of a volume in the <guilabel>Volumes</guilabel> tab of the dashboard. The volume is either Available or In-Use."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:164(para)
msgid "Now you can log in to the instance and mount, format, and use the disk."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:168(title)
msgid "Detach a volume from an instance"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:175(para)
msgid "Select the volume and click <guibutton>Edit Attachments</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:178(para)
msgid "Click <guibutton>Detach Volume</guibutton> and confirm your changes."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:182(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:262(para)
msgid "A message indicates whether the action was successful."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:185(title)
msgid "Create a snapshot from a volume"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:188(para)
msgid "Log in to the dashboard, choose a project, and click <guilabel>Volumes</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:192(para)
msgid "Select a volume from which to create a snapshot."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:195(para)
msgid "From the <guilabel>More</guilabel> list, select <guilabel>Create Snapshot</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:199(para)
msgid "In the dialog box that opens, enter a snapshot name and a brief description."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:203(para)
msgid "Confirm your changes."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:204(para)
msgid "The dashboard shows the new volume snapshot in <guilabel>Volume Snapshots</guilabel> tab."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:210(title)
msgid "Edit a volume"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:222(para)
msgid "On the <guilabel>Project</guilabel> tab, click <guilabel>Volumes</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:229(para)
msgid "In the <guilabel>Actions</guilabel> column, click <guilabel>Edit Volume</guilabel>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:233(para)
msgid "In the <guilabel>Edit Volume</guilabel> dialog box, update the name and description of the image."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:237(para)
msgid "Click <guibutton>Edit Volume</guibutton>."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:241(para)
msgid "You can extend a volume by using the <guilabel>Extend Volume</guilabel> option available in the <guibutton>More</guibutton> dropdown list and entering the new value for volume size."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:247(title)
msgid "Delete a volume"
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:248(para)
msgid "When you delete an instance, the data in its attached volumes is not destroyed."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:256(para)
msgid "Select the check boxes for the volumes that you want to delete."
msgstr ""

#: ./doc/user-guide/section_dashboard_manage_volumes.xml:260(para)
msgid "Click <guibutton>Delete Volumes</guibutton> and confirm your choice."
msgstr ""

#: ./doc/user-guide/section_sdk_configure_instances.xml:8(para)
msgid "When working with images in the SDK, you will call <literal>novaclient</literal> methods."
msgstr ""

#: ./doc/user-guide/section_sdk_configure_instances.xml:12(title)
msgid "Add a keypair"
msgstr ""

#: ./doc/user-guide/section_sdk_configure_instances.xml:13(para)
msgid "To generate a keypair, call the <methodname><link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.keypairs.html#novaclient.v1_1.keypairs.KeypairManager.create\">novaclient.v1_1.keypairs.KeypairManager.create</link></methodname> method:"
msgstr ""

#: ./doc/user-guide/section_sdk_configure_instances.xml:23(para)
msgid "The Python script output looks something like this:"
msgstr ""

#: ./doc/user-guide/section_sdk_configure_instances.xml:31(para)
msgid "You typically write the private key to a file to use it later. The file must be readable and writeable by only the file owner; otherwise, the SSH client will refuse to read the private key file. It is safest to create the file with the appropriate permissions, as shown in the following example:"
msgstr ""

#: ./doc/user-guide/section_sdk_configure_instances.xml:49(title)
msgid "Import a keypair"
msgstr ""

#: ./doc/user-guide/section_sdk_configure_instances.xml:50(para)
msgid "If you have already generated a keypair with the public key located at <filename>~/.ssh/id_rsa.pub</filename>, pass the contents of the file to the <methodname><link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.keypairs.html#novaclient.v1_1.keypairs.KeypairManager.create\"> novaclient.v1_1.keypairs.KeypairManager.create</link></methodname> method to import the public key to Compute:"
msgstr ""

#: ./doc/user-guide/section_sdk_configure_instances.xml:64(title)
msgid "List keypairs"
msgstr ""

#: ./doc/user-guide/section_sdk_configure_instances.xml:65(para)
msgid "To list keypairs, call the <methodname><link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.keypairs.html#novaclient.v1_1.keypairs.KeypairManager.list\">novaclient.v1_1.keypairs.KeypairManager.list</link></methodname> method:"
msgstr ""

#: ./doc/user-guide/section_sdk_configure_instances.xml:74(para)
msgid "To list security groups for the current project, call the <methodname><link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.security_groups.html#novaclient.v1_1.security_groups.SecurityGroupManager.list\">novaclient.v_1.security_groups.SecurityGroupManager.list</link></methodname> method:"
msgstr ""

#: ./doc/user-guide/section_sdk_configure_instances.xml:79(para)
msgid "To create a security group with a specified name and description, call the <methodname><link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.security_groups.html#novaclient.v1_1.security_groups.SecurityGroupManager.create\">novaclient.v_1.security_groups.SecurityGroupManager.create</link></methodname> method:"
msgstr ""

#: ./doc/user-guide/section_sdk_configure_instances.xml:84(para)
msgid "To delete a security group, call the <methodname><link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.security_groups.html#novaclient.v1_1.security_groups.SecurityGroupManager.delete\"> novaclient.v_1.security_groups.SecurityGroupManager.delete</link></methodname> method, passing either a <link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.security_groups.html#novaclient.v1_1.security_groups.SecurityGroup\">novaclient.v1_1.security_groups.SecurityGroup</link> object or group ID as an argument:"
msgstr ""

#: ./doc/user-guide/section_sdk_configure_instances.xml:99(para)
msgid "Access the security group rules from the <literal>rules</literal> attribute of a <link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.security_groups.html#novaclient.v1_1.security_groups.SecurityGroup\">novaclient.v1_1.security_groups.SecurityGroup</link> object:"
msgstr ""

#: ./doc/user-guide/section_sdk_configure_instances.xml:105(para)
msgid "To add a rule, to a security group, call the <methodname><link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.security_group_rules.html#novaclient.v1_1.security_group_rules.SecurityGroupRuleManager.create\">novaclient.v1_1.security_group_rules.SecurityGroupRuleManager.create</link></methodname> method:"
msgstr ""

#. WARNING: This file is automatically generated. Do not edit it.
#: ./doc/user-guide/hot/section_software_deployment.xml:4(title)
msgid "Software configuration"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:5(para)
msgid "There are a variety of options to configure the software which runs on the servers in your stack. These can be broadly divided into the following:"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:9(para)
msgid "Custom image building"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:12(para) ./doc/user-guide/hot/section_software_deployment.xml:59(title)
msgid "User-data boot scripts and cloud-init"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:15(para)
msgid "Software deployment resources"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:18(para)
msgid "This section will describe each of these options and provide examples for using them together in your stacks."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:22(title)
msgid "Image building"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:23(para)
msgid "The first opportunity to influence what software is configured on your servers is by booting them with a custom-built image. There are a number of reasons you might want to do this, including:"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:28(para)
msgid "<emphasis role=\"Boot speed\"/> - since the required software is already on the image there is no need to download and install anything at boot time."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:32(para)
msgid "<emphasis role=\"Boot reliability\"/> - software downloads can fail for a number of reasons including transient network failures and inconsistent software repositories."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:36(para)
msgid "<emphasis role=\"Test verification\"/> - custom built images can be verified in test environments before being promoted to production."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:40(para)
msgid "<emphasis role=\"Configuration dependencies\"/> - post-boot configuration may depend on agents already being installed and enabled"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:44(para)
msgid "A number of tools are available for building custom images, including:"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:47(para)
msgid "<link href=\"https://github.com/openstack/diskimage-builder\">diskimage-builder</link> image building tools for OpenStack"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:50(para)
msgid "<link href=\"http://imgfac.org/\">imagefactory</link> builds images for a variety of operating system/cloud combinations"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:54(para)
msgid "Examples in this guide which require custom images will use <link href=\"https://github.com/openstack/diskimage-builder\">diskimage-builder</link>."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:60(para)
msgid "When booting a server it is possible to specify the contents of the user-data to be passed to that server. This user-data is made available either from configured config-drive or from the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/section_metadata-service.html\">Metadata service</link>."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:63(para)
msgid "How this user-data is consumed depends on the image being booted, but the most commonly used tool for default cloud images is <link href=\"http://cloudinit.readthedocs.org/en/latest/\">Cloud-init</link>."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:65(para)
msgid "Whether the image is using <link href=\"http://cloudinit.readthedocs.org/en/latest/\">Cloud-init</link> or not, it should be possible to specify a shell script in the user_data property and have it be executed by the server during boot:"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:80(para)
msgid "<emphasis role=\"Tip\"/>: debugging these scripts it is often useful to view the boot log using <literal>nova console-log &lt;server-id&gt;</literal> to view the progress of boot script execution."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:84(para)
msgid "Often there is a need to set variable values based on parameters or resources in the stack. This can be done with the <literal>str_replace</literal> intrinsic function:"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:106(para)
msgid "<emphasis role=\"Warning\"/>: If a stack-update is performed and there are any changes at all to the content of user_data then the server will be replaced (deleted and recreated) so that the modified boot configuration can be run on a new server."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:111(para)
msgid "When these scripts grow it can become difficult to maintain them inside the template, so the <literal>get_file</literal> intrinsic function can be used to maintain the script in a separate file:"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:131(para)
msgid "<emphasis role=\"Tip\"/>: <literal>str_replace</literal> can replace any strings, not just strings starting with <literal>$</literal>. However doing this for the above example is useful because the script file can be executed for testing by passing in environment variables."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:137(title)
msgid "Choosing the user_data_format"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:138(para)
msgid "The <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Nova__Server.html\">OS::Nova::Server</link></literal> user_data_format property determines how the user_data should be formatted for the server. For the default value <literal>HEAT_CFNTOOLS</literal>, the user_data is bundled as part of the heat-cfntools cloud-init boot configuration data. While <literal>HEAT_CFNTOOLS</literal> is the default for <literal>user_data_format</literal>, it is considered legacy and <literal>RAW</literal> or <literal>SOFTWARE_CONFIG</literal> will generally be more appropriate."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:144(para)
msgid "For <literal>RAW</literal> the user_data is passed to Nova unmodified. For a <link href=\"http://cloudinit.readthedocs.org/en/latest/\">Cloud-init</link> enabled image, the following are both valid <literal>RAW</literal> user-data:"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:166(para)
msgid "For <literal>SOFTWARE_CONFIG</literal> user_data is bundled as part of the software config data, and metadata is derived from any associated software deployment resources."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:171(title)
msgid "Signals and wait conditions"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:172(para)
msgid "Often it is necessary to pause further creation of stack resources until the boot configuration script has notified that it has reached a certain state. This is usually either to notify that a service is now active, or to pass out some generated data which is needed by another resource. The resources <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__WaitCondition.html\">OS::Heat::WaitCondition</link></literal> and <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SwiftSignal.html\">OS::Heat::SwiftSignal</link></literal> both perform this function using different techniques and tradeoffs."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:178(para)
msgid "<literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__WaitCondition.html\">OS::Heat::WaitCondition</link></literal> is implemented as a call to the <link href=\"http://developer.openstack.org/api-ref-orchestration-v1.html\">Orchestration API</link> resource signal. The token is created using credentials for a user account which is scoped only to the wait condition handle resource. This user is created when the handle is created, and is associated to a project which belongs to the stack, in an identity domain which is dedicated to the orchestration service."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:184(para) ./doc/user-guide/hot/section_software_deployment.xml:267(para)
msgid "Sending the signal is a simple HTTP request, as with this example using <link href=\"http://curl.haxx.se/\">curl</link>:"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:188(para)
msgid "The JSON containing the signal data is expected to be of the following format:"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:195(para)
msgid "All of these values are optional, and if not specified will be set to the following defaults:"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:203(para)
msgid "If <literal>status</literal> is set to <literal>FAILURE</literal> then the resource (and the stack) will go into a <literal>FAILED</literal> state using the <literal>reason</literal> as failure reason."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:205(para)
msgid "The following template example uses the convenience attribute <literal>curl_cli</literal> which builds a curl command with a valid token:"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:263(para)
msgid "<literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SwiftSignal.html\">OS::Heat::SwiftSignal</link></literal> is implemented by creating an Object Storage API temporary URL which is populated with signal data with an HTTP PUT. The orchestration service will poll this object until the signal data is available. Object versioning is used to store multiple signals."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:269(para)
msgid "The above template example only needs to have the <literal>type</literal> changed to the swift signal resources:"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:281(para)
msgid "The decision to use <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__WaitCondition.html\">OS::Heat::WaitCondition</link></literal> or <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SwiftSignal.html\">OS::Heat::SwiftSignal</link></literal> will depend on a few factors:"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:285(para)
msgid "<literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SwiftSignal.html\">OS::Heat::SwiftSignal</link></literal> depends on the availability of an Object Storage API"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:289(para)
msgid "<literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__WaitCondition.html\">OS::Heat::WaitCondition</link></literal> depends on whether the orchestration service has been configured with a dedicated stack domain (which may depend on the availability of an Identity V3 API)."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:294(para)
msgid "The preference to protect signal URLs with token authentication or a secret webhook URL."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:300(title)
msgid "Software config resources"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:301(para)
msgid "Boot configuration scripts can also be managed as their own resources. This allows configuration to be defined once and run on multiple server resources. These software-config resources are stored and retrieved via dedicated calls to the <link href=\"http://developer.openstack.org/api-ref-orchestration-v1.html\">Orchestration API</link>. It is not possible to modify the contents of an existing software-config resource, so a stack-update which changes any existing software-config resource will result in API calls to create a new config and delete the old one."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:308(para)
msgid "The resource <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal> is used for storing configs represented by text scripts, for example:"
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:326(para)
msgid "The resource <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__CloudConfig.html\">OS::Heat::CloudConfig</link></literal> allows <link href=\"http://cloudinit.readthedocs.org/en/latest/\">Cloud-init</link> cloud-config to be represented as template YAML rather than a block string. This allows intrinsic functions to be included when building the cloud-config. This also ensures that the cloud-config is valid YAML, although no further checks for valid cloud-config are done."
msgstr ""

#: ./doc/user-guide/hot/section_software_deployment.xml:352(para)
msgid "The resource <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__MultipartMime.html\">OS::Heat::MultipartMime</link></literal> allows multiple <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal> and <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__CloudConfig.html\">OS::Heat::CloudConfig</link></literal> resources to be combined into a single <link href=\"http://cloudinit.readthedocs.org/en/latest/\">Cloud-init</link> multi-part message:"
msgstr ""

#. WARNING: This file is automatically generated. Do not edit it.
#: ./doc/user-guide/hot/index.xml:10(title)
msgid "HOT guide"
msgstr ""

#. WARNING: This file is automatically generated. Do not edit it.
#: ./doc/user-guide/hot/section_functions.xml:4(title)
msgid "HOT functions"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:7(title)
msgid "Link between resources"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:10(para) ./doc/user-guide/hot/section_hot_spec.xml:627(title)
msgid "get_param"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:13(para) ./doc/user-guide/hot/section_hot_spec.xml:673(title)
msgid "get_resource"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:16(para)
msgid "Ref"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:19(para)
msgid "Fn::GetAtt / get_attr"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:25(title)
msgid "String manipulations"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:28(para) ./doc/user-guide/hot/section_hot_spec.xml:587(title)
msgid "get_file"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:31(para) ./doc/user-guide/hot/section_hot_spec.xml:696(title)
msgid "list_join"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:34(para) ./doc/user-guide/hot/section_hot_spec.xml:717(title)
msgid "str_replace"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:37(para)
msgid "Fn::Base64"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:40(para)
msgid "Fn::Join"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:43(para)
msgid "Fn::Split"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:46(para)
msgid "Fn::Replace"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:52(title)
msgid "Lookup structured data"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:55(para)
msgid "Fn::FindInMap"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:58(para)
msgid "Fn::MemberListToMap"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:61(para)
msgid "Fn::Select"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:67(title)
msgid "Misc"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:70(para)
msgid "Fn::ResourceFacade / resource_facade"
msgstr ""

#: ./doc/user-guide/hot/section_functions.xml:73(para)
msgid "Fn::GetAZs"
msgstr ""

#. WARNING: This file is automatically generated. Do not edit it.
#: ./doc/user-guide/hot/section_hot_spec.xml:15(title)
msgid "Heat Orchestration Template (HOT) specification"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:18(title)
msgid "Template structure"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:19(para)
msgid "HOT templates are defined in YAML and use the following structure:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:38(term)
msgid "heat_template_version"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:40(para)
msgid "This key with value <literal>2013-05-23</literal> (or a later date) indicates that the YAML document is a HOT template of the specified version."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:45(term) ./doc/user-guide/hot/section_hot_spec.xml:111(term) ./doc/user-guide/hot/section_hot_spec.xml:173(term) ./doc/user-guide/hot/section_hot_spec.xml:247(term) ./doc/user-guide/hot/section_hot_spec.xml:507(term)
msgid "description"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:47(para)
msgid "This optional key gives a description of the template, or the workload that can be deployed using the template."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:52(term)
msgid "parameter_groups"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:54(para)
msgid "This section specifies how the input parameters should be grouped and the order to provide the parameters in."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:56(para) ./doc/user-guide/hot/section_hot_spec.xml:64(para) ./doc/user-guide/hot/section_hot_spec.xml:81(para) ./doc/user-guide/hot/section_hot_spec.xml:408(para) ./doc/user-guide/hot/section_hot_spec.xml:415(para)
msgid "This section is optional."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:60(term) ./doc/user-guide/hot/section_hot_spec.xml:117(term) ./doc/user-guide/hot/section_environment.xml:17(literal)
msgid "parameters"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:62(para)
msgid "This section specifies input parameters that have to be provided when instantiating the template."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:68(term)
msgid "resources"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:70(para)
msgid "This section contains the declaration of the resources of the template. This section with at least one resource must be defined in any HOT template, or the template would not really do anything when being instantiated."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:77(term)
msgid "outputs"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:79(para)
msgid "This section specifies output parameters available to users once the template has been instantiated."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:88(title)
msgid "Parameter groups section"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:89(para)
msgid "The <literal>parameter_groups</literal> section specifies how the input parameters should be grouped and the order to provide the parameters in. These groups are typically used to describe expected behavior for downstream user interfaces."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:92(para)
msgid "These groups are specified in a list with each group containing a list of associated parameters. The lists are used to denote the expected order of the parameters. A parameter can only be included in one group. Use the name of the parameter to add it to a group. The parameters details are defined in the <literal>parameters</literal> section."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:105(term) ./doc/user-guide/hot/section_hot_spec.xml:166(term)
msgid "label"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:107(para)
msgid "A human-readable label that defines the associated group of parameters."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:113(para)
msgid "A human-readable description of the parameter group."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:119(para)
msgid "A list of parameters that belong with this parameter group."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:123(term) ./doc/user-guide/hot/section_hot_spec.xml:151(term)
msgid "param name"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:125(para)
msgid "The name of a parameter defined in the <literal>parameters</literal> section."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:132(title)
msgid "Parameters section"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:133(para)
msgid "The <literal>parameters</literal> section defines input parameters that have to be provided when instantiating the template. Such parameters are typically used to customize each deployment, or for binding to environment specifics like certain images."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:137(para)
msgid "Each parameter is specified in a separated nested block with the name of the parameter defined in the first line and additional attributes such as a type or a default value defined as nested elements:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:153(para)
msgid "The name of the parameter."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:157(term) ./doc/user-guide/hot/section_hot_spec.xml:397(term)
msgid "type"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:159(para)
msgid "The type of the parameter. Supported types are <literal>string</literal>, <literal>number</literal>, <literal>comma_delimited_list</literal>, <literal>json</literal> and <literal>boolean</literal>."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:162(para) ./doc/user-guide/hot/section_hot_spec.xml:400(para) ./doc/user-guide/hot/section_hot_spec.xml:519(para)
msgid "This attribute is required."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:168(para)
msgid "A human readable name for the parameter."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:169(para) ./doc/user-guide/hot/section_hot_spec.xml:176(para) ./doc/user-guide/hot/section_hot_spec.xml:184(para) ./doc/user-guide/hot/section_hot_spec.xml:202(para) ./doc/user-guide/hot/section_hot_spec.xml:252(para) ./doc/user-guide/hot/section_hot_spec.xml:423(para) ./doc/user-guide/hot/section_hot_spec.xml:432(para) ./doc/user-guide/hot/section_hot_spec.xml:440(para) ./doc/user-guide/hot/section_hot_spec.xml:510(para)
msgid "This attribute is optional."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:175(para)
msgid "A human readable description for the parameter."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:180(term)
msgid "default"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:182(para)
msgid "A default value for the parameter. This value is used if the user doesn't specify his own value during deployment."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:188(term)
msgid "hidden"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:190(para)
msgid "Defines whether the parameters should be hidden when a user requests information about a stack created from the template. This attribute can be used to hide passwords specified as parameters."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:193(para)
msgid "This attribute is optional and defaults to <literal>false</literal>."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:197(term)
msgid "constraints"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:199(para)
msgid "A list of constraints to apply. The constraints are validated by the Orchestration engine when a user deploys a stack. The stack creation fails if the parameter value doesn't comply to the constraints."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:206(para)
msgid "The following example shows a minimalistic definition of two parameters:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:217(para)
msgid "The description and the label are optional, but defining these attributes is good practice to provide useful information about the role of the parameter to the user."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:222(title)
msgid "Parameter constraints"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:223(para)
msgid "The <literal>constraints</literal> block of a parameter definition defines additional validation constraints that apply to the value of the parameter. The parameter values provided by a user are validated against the contrainsts at instantiation time. The contrainsts are defined as a list with the following syntax:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:233(term)
msgid "constraint type"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:235(para)
msgid "Type of constraint to apply. The set of currently supported constraints is given below."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:240(term)
msgid "constraint definition"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:242(para)
msgid "The actual constraint, depending on the constraint type. The concrete syntax for each constraint type is given below."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:249(para)
msgid "A description of the constraint. The text is presented to the user when the value he defines violates the constraint. If ommitted, a default validation message is presented to the user."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:256(para)
msgid "The following example shows the definition of a string parameter with two constraints. Note that while the descriptions for each constraint are optional, it is good practice to provide concrete descriptions to present useful messages to the user at deployment time."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:271(para)
msgid "While the descriptions for each constraint are optional, it is good practice to provide concrete descriptions so useful messages can be presented to the user at deployment time."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:275(para)
msgid "The following sections list the supported types of parameter constraints, along with the syntax for each type."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:278(title)
msgid "length"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:279(para)
msgid "The <literal>length</literal> constraint applies to parameters of type <literal>string</literal>. It defines a lower and upper limit for the length of the string value."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:281(para)
msgid "The syntax of the <literal>length</literal> constraint is:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:283(para)
msgid "It is possible to define a length constraint with only a lower limit or an upper limit. However, at least one of <literal>min</literal> or <literal>max</literal> must be specified."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:287(title)
msgid "range"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:288(para)
msgid "The <literal>range</literal> constraint applies to parameters of type <literal>number</literal>. It defines a lower and upper limit for the numeric value of the parameter."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:290(para)
msgid "The syntax of the <literal>range</literal> constraint is:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:292(para)
msgid "It is possible to define a range constraint with only a lower limit or an upper limit. However, at least one of <literal>min</literal> or <literal>max</literal> must be specified."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:294(para)
msgid "The minimum and maximum boundaries are included in the range. For example, the following range constraint would allow for all numeric values between 0 and 10:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:299(title)
msgid "allowed_values"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:300(para)
msgid "The <literal>allowed_values</literal> constraint applies to parameters of type <literal>string</literal> or <literal>number</literal>. It specifies a set of possible values for a parameter. At deployment time, the user-provided value for the respective parameter must match one of the elements of the list."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:304(para)
msgid "The syntax of the <literal>allowed_values</literal> constraint is:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:306(para)
msgid "Alternatively, the following YAML list notation can be used:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:324(title)
msgid "allowed_pattern"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:325(para)
msgid "The <literal>allowed_pattern</literal> constraint applies to parameters of type <literal>string</literal>. It specifies a regular expression against which a user-provided parameter value must evaluate at deployment."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:328(para)
msgid "The syntax of the <literal>allowed_pattern</literal> constraint is:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:341(title)
msgid "custom_constraint"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:342(para)
msgid "The <literal>custom_constraint</literal> constraint adds an extra step of validation, generally to check that the specified resource exists in the backend. Custom constraints get implemented by plug-ins and can provide any kind of advanced constraint validation logic."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:346(para)
msgid "The syntax of the <literal>custom_constraint</literal> constraint is:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:348(para)
msgid "The <literal>name</literal> attribute specifies the concrete type of custom constraint. It corresponds to the name under which the respective validation plugin has been registered in the Orchestration engine."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:361(title)
msgid "Pseudo Parameters"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:362(para)
msgid "In addition to parameters defined by a template author, the Orchestration module also creates two parameters for every stack that allow referential access to the stack's name and identifier. These parameters are named <literal>OS::stack_name</literal> for the stack name and <literal>OS::stack_id</literal> for the stack identifier. These values are accessible via the <literal>get_param</literal> intrinsic function, just like user-defined parameters."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:372(title)
msgid "Resources section"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:373(para)
msgid "The <literal>resources</literal> section defines actual resources that make up a stack deployed from the HOT template (for instance compute instances, networks, storage volumes)."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:376(para)
msgid "Each resource is defined as a separate block in the <literal>resources</literal> section with the following syntax:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:390(term) ./doc/user-guide/hot/section_hot_spec.xml:551(term)
msgid "resource ID"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:392(para)
msgid "A resource ID which must be unique within the <literal>resources</literal> section of the template."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:399(para)
msgid "The resource type, such as <literal>OS::Nova::Server</literal> or <literal>OS::Neutron::Port</literal>."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:404(term)
msgid "properties"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:406(para)
msgid "A list of resource-specific properties. The property value can be provided in place, or via a function (see <link linkend=\"hot-spec-intrinsic-functions\"><emphasis>Intrinsic functions</emphasis></link>)."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:412(term)
msgid "metadata"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:414(para)
msgid "Resource-specific metadata."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:419(term)
msgid "depends_on"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:421(para)
msgid "Dependencies of the resource on one or more resources of the template."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:422(para)
msgid "See <link linkend=\"hot-spec-resources-dependencies\"><emphasis>Resource dependencies</emphasis></link> for details."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:427(term)
msgid "update_policy"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:429(para)
msgid "Update policy for the resource, in the form of a nested dictionary. Whether update policies are supported and what the exact semantics are depends on the type of the current resource."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:436(term)
msgid "deletion_policy"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:438(para)
msgid "Deletion policy for the resource. Which type of deletion policy is supported depends on the type of the current resource."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:444(para)
msgid "Depending on the type of resource, the resource block might include more resource specific data."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:446(para)
msgid "All resource types that can be used in CFN templates can also be used in HOT templates, adapted to the YAML structure as outlined above."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:448(para)
msgid "The following example demonstrates the definition of a simple compute resource with some fixed property values:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:457(title)
msgid "Resource dependencies"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:458(para)
msgid "The <literal>depends_on</literal> attribute of a resource defines a dependency between this resource and one or more other resources."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:460(para)
msgid "If a resource depends on just one other resource, the ID of the other resource is specified as string of the <literal>depends_on</literal> attribute, as shown in the following example:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:470(para)
msgid "If a resource depends on more than one other resources, the value of the <literal>depends_on</literal> attribute is specified as a list of resource IDs, as shown in the following example:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:487(title)
msgid "Outputs section"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:488(para)
msgid "The <literal>outputs</literal> section defines output parameters that should be available to the user once a stack has been created. This would be, for example, parameters such as IP addresses of deployed instances, or URLs of web applications deployed as part of a stack."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:492(para)
msgid "Each output parameter is defined as a separate block within the outputs section according to the following syntax:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:500(term) ./doc/user-guide/hot/section_hot_spec.xml:638(term)
msgid "parameter name"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:502(para)
msgid "The output parameter name, which must be unique within the <literal>outputs</literal> section of a template."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:509(para)
msgid "A short description of the output parameter."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:514(term)
msgid "parameter value"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:516(para)
msgid "The value of the output parameter. This value is usually resolved by means of a function. See <link linkend=\"hot-spec-intrinsic-functions\"><emphasis>Intrinsic functions</emphasis></link> for details about the functions."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:523(para)
msgid "The example below shows how the IP address of a compute resource can be defined as an output parameter:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:532(title)
msgid "Intrinsic functions"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:533(para)
msgid "HOT provides a set of intrinsic functions that can be used inside templates to perform specific tasks, such as getting the value of a resource attribute at runtime. The following section describes the role and syntax of the intrinsic functions."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:538(title)
msgid "get_attr"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:539(para)
msgid "The <literal>get_attr</literal> function references an attribute of a resource. The attribute value is resolved at runtime using the resource instance created from the respective resource definition."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:542(para)
msgid "The syntax of the <literal>get_attr</literal> function is:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:553(para)
msgid "The resource ID for which the attribute needs to be resolved."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:554(para)
msgid "The resource ID must exist in the <literal>resources</literal> section of the template."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:558(term)
msgid "attribute name"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:560(para)
msgid "The attribute name to be resolved. If the attribute returns a complex data structure such as a list or a map, then subsequent keys or indexes can be specified. These additional parameters are used to navigate the data structure to return the desired value."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:567(para)
msgid "The following example demonstrates how to use the <literal>get_param</literal> function:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:580(para)
msgid "In this example, if the networks attribute contained the following data:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:583(para)
msgid "then the value of <literal>the get_attr</literal> function would resolve to <literal>10.0.0.1</literal> (first item of the <literal>private</literal> entry in the <literal>networks</literal> map)."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:588(para)
msgid "The <literal>get_file</literal> function returns the content of a file into the template. It is generally used as a file inclusion mechanism for files containing scripts or configuration files."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:591(para)
msgid "The syntax of <literal>the get_file</literal> function is:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:593(para)
msgid "The <literal>content key</literal> is used to look up the <literal>files</literal> dictionary that is provided in the REST API call. The Orchestration client command (<placeholder-1/>) is <literal>get_file</literal> aware and will populate the <literal>files</literal> dictionnary with the actual content of fetched paths and URLs. The Orchestration client command supports relative paths and will transform these to the absolute URLs required by the Orcestration API."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:600(para)
msgid "The <literal>get_file</literal> argument must be a static path or URL and not rely on intrinsic functions like <literal>get_param</literal>. the Orchestration client does not process intrinsic functions (they are only processed by the Orchestration engine)."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:605(para)
msgid "The example below demonstrates the <literal>get_file</literal> function usage with both relative and absolute URLs:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:621(para)
msgid "The <literal>files</literal> dictionary generated by the Orchestration client during instantiation of the stack would contain the following keys: * <literal>file:///path/to/my_instance_user_data.sh</literal> * <literal>http://example.com/my_other_instance_user_data.sh*</literal>"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:628(para)
msgid "The <literal>get_param</literal> function references an input parameter of a template. It resolves to the value provided for this input parameter at runtime."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:630(para)
msgid "The syntax of the <literal>get_param</literal> function is:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:640(para)
msgid "The parameter name to be resolved. If the parameters returns a complex data structure such as a list or a map, then subsequent keys or indexes can be specified. These additional parameters are used to navigate the data structure to return the desired value."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:647(para)
msgid "The following example demonstrates the use of the <literal>get_param</literal> function:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:663(para)
msgid "In this example, if the <literal>instance_type</literal> and <literal>server_data</literal> parameters contained the following data:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:668(para)
msgid "then the value of the property <literal>flavor</literal> would resolve to <literal>m1.tiny</literal>, <literal>metadata</literal> would resolve to <literal>{\"foo\": \"bar\"}</literal> and <literal>key_name</literal> would resolve to <literal>a_key</literal>."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:674(para)
msgid "The <literal>get_resource</literal> function references another resource within the same template. At runtime, it is resolved to reference the ID of the referenced resource, which is resource type specific. For example, a reference to a floating IP resource returns the respective IP address at runtime. The syntax of the <literal>get_resource</literal> function is:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:680(para)
msgid "The resource ID of the referenced resource is given as single parameter to the get_resource function."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:682(para)
msgid "For exemple:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:697(para)
msgid "The <literal>list_join</literal> function joins a list of strings with the given delimiter."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:698(para)
msgid "The syntax of the <literal>list_join</literal> function is:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:704(para)
msgid "This resolve to the string <literal>one, two, and three</literal>."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:707(title)
msgid "resource_facade"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:708(para)
msgid "The <literal>resource_facade</literal> function retrieves data in a parent provider template."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:709(para)
msgid "A provider template provdes a custom definition of a resource, called its facade. For more information about custom templates, see <xref linkend=\"composition\"/>. The syntax of the <literal>resource_facade</literal> function is:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:713(para)
msgid "<literal>data type</literal> can be one of <literal>metadata</literal>, <literal>deletion_policy</literal> or <literal>update_policy</literal>."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:718(para)
msgid "The <literal>str_replace</literal> function dynamically constructs strings by providing a template string with placeholders and a list of mappings to assign values to those placeholders at runtime. The placeholders are replaced with mapping values wherever a mapping key exactly matches a placeholder."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:722(para)
msgid "The syntax of the <literal>str_replace</literal> function is:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:728(term)
msgid "template"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:730(para)
msgid "Defines the template string that contains placeholders which will be substituted at runtime."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:735(term)
msgid "params"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:737(para)
msgid "Provides parameter mappings in the form of dictionary. Each key refers to a placeholder used in the <literal>template</literal> attribute."
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:742(para)
msgid "The following example shows a simple use of the <literal>str_replace</literal> function in the outputs section of a template to build a URL for logging into a deployed application:"
msgstr ""

#: ./doc/user-guide/hot/section_hot_spec.xml:758(para)
msgid "The following examples show the use of the <literal>str_replace</literal> function to build an instance initialization script:"
msgstr ""

#. WARNING: This file is automatically generated. Do not edit it.
#: ./doc/user-guide/hot/section_hello_world.xml:15(title)
msgid "Writing a hello world HOT template"
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:16(para)
msgid "HOT is a new template format meant to replace the CloudFormation-compatible format (CFN) as the native format supported by the Orchestration module over time. This guide is targeted towards template authors and explains how to write HOT templates based on examples. A detailed specification of HOT can be found at <xref linkend=\"hot-spec\"/>."
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:22(para)
msgid "This section gives an introduction on how to write HOT templates, starting from very basic steps and then going into more and more detail by means of examples."
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:26(title)
msgid "A most basic template"
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:27(para)
msgid "The most basic template you can think of contains only a single resource definition using only predefined properties. For example, the template below could be used to deploy a single compute instance:"
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:41(para)
msgid "Each HOT template has to include the <literal>heat_template_version</literal> key with value <literal>2013-05-23</literal>, the current HOT version. While the <literal>description</literal> key is optional, it is good practice to include some useful text that describes what users can do with the template. In case you want to provide a longer description that does not fit on a single line, you can provide multi-line text in YAML, for example:"
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:50(para)
msgid "The <literal>resources</literal> section is required and must contain at least one resource definition. In the above example, a compute instance is defined with fixed values for the <literal>key_name</literal>, <literal>image</literal> and <literal>flavor</literal> properties."
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:54(para)
msgid "All the defined elements (key pair, image, flavor) have to exist in the OpenStack environment where the template is used."
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:60(title)
msgid "Input parameters"
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:61(para)
msgid "Input parameters defined in the <literal>parameters</literal> section of a template allow users to customize a template during deployment. For example, this allows for providing custom key pair names or image IDs to be used for a deployment. From a template author's perspective, this helps to make a template more easily reusable by avoiding hardcoded assumptions."
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:66(para)
msgid "The following example extends the previous template to provide parameters for the key pair, image and flavor properties of the resource:"
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:93(para)
msgid "Values for the three parameters must be defined by the template user during the deployment of a stack. The <literal>get_param</literal> intrinsic function retrieves a user-specified value for a given parameter and uses this value for the associated resource property."
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:97(para)
msgid "For more information about intrinsic functions, see <xref linkend=\"hot-spec-intrinsic-functions\"/>."
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:100(title)
msgid "Providing default values"
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:101(para)
msgid "You can provide default values for parameters. If a user doesn't define a value for a parameter, the default value is used during the stack deployment. The following example defines a default value <literal>m1.small</literal> for the <literal>flavor</literal> property:"
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:112(para)
msgid "If a template doesn't define a default value for a parameter, then the user must define the value, otherwise the stack creation will fail."
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:117(title)
msgid "Hidding parameters values"
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:118(para)
msgid "The values that a user provides when deploying a stack are available in the stack details and can be accessed by any user in the same tenant. To hide the value of a parameter, use the <literal>hidden</literal> boolean attribute of the parameter:"
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:129(title)
msgid "Restricting user input"
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:130(para)
msgid "You can restrict the values of an input parameter to make sure that the user defines valid data for this parameter. The <literal>constraints</literal> property of an input parameter defines a list of constraints to apply for the parameter. The following example restricts the <literal>flavor</literal> parameter to a list of three possible values:"
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:143(para)
msgid "The following example defines multiple contraints for a password definition:"
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:157(para)
msgid "The list of supported constraints is available in the <xref linkend=\"hot-spec-parameters-constraints\"/> section."
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:160(para)
msgid "You can define multiple constraints of the same type. Especially in the case of allowed patterns this not only allows for keeping regular expressions simple and maintainable, but also for keeping error messages to be presented to users precise."
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:169(title)
msgid "Template outputs"
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:170(para)
msgid "In addition to template customization through input parameters, you can provide information about the resources created during the stack deployment to the users in the <literal>outputs</literal> section of a template. In the following example the output section provides the IP address of the <literal>my_instance</literal> resource:"
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:179(para)
msgid "Output values are typically resolved using intrinsic function such as the <literal>get_attr</literal>. See <xref linkend=\"hot-spec-intrinsic-functions\"/> for more information about intrinsic functions.."
msgstr ""

#: ./doc/user-guide/hot/section_hello_world.xml:183(para)
msgid "See <xref linkend=\"hot-spec-outputs\"/> for more information about the <literal>outputs</literal> section."
msgstr ""

#. WARNING: This file is automatically generated. Do not edit it.
#: ./doc/user-guide/hot/section_basic_resources.xml:4(title)
msgid "Instances"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:11(title)
msgid "Manage instances"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:13(title)
msgid "Create an instance"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:14(para)
msgid "Use the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Nova__Server.html\">OS::Nova::Server</link></literal> resource to create a Compute instance. The <literal>flavor</literal> property is the only mandatory one, but you need to define a boot source using one of the <literal>image</literal> or <literal>block_device_mapping</literal> properties."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:17(para)
msgid "You also need to define the <literal>networks</literal> property to indicate to which networks your instance must connect if multiple networks are available in your tenant."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:19(para)
msgid "The following example creates a simple instance, booted from an image, and connecting to the <literal>private</literal> network:"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:31(title)
msgid "Connect an instance to a network"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:32(para)
msgid "Use the <literal>networks</literal> property of an <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Nova__Server.html\">OS::Nova::Server</link></literal> resource to define which networks an instance should connect to. Define each network as a YAML map, containing one of the following keys:"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:38(literal)
msgid "port"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:41(para)
msgid "The ID of an existing Networking port. You usually create this port in the same template using an <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Neutron__Port.html\">OS::Neutron::Port</link></literal> resource. You will be able to associate a floating IP to this port, and the port to your Compute instance."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:49(literal)
msgid "network"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:52(para)
msgid "The name or ID of an existing network. You don't need to create an <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Neutron__Port.html\">OS::Neutron::Port</link></literal> resource if you use this property, but you will not be able to associate a floating IP with the instance interface in the template."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:59(para)
msgid "The following example demonstrates the use of the <literal>port</literal> and <literal>network</literal> properties:"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:86(title)
msgid "Create and associate security groups to an instance"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:87(para)
msgid "Use the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Neutron__SecurityGroup.html\">OS::Neutron::SecurityGroup</link></literal> resource to create security groups."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:89(para)
msgid "Define the <literal>security_groups</literal> property of the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Neutron__Port.html\">OS::Neutron::Port</link></literal> resource to associate security groups to a port, then associate the port to an instance."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:92(para)
msgid "The following example creates a security group allowing inbound connections on ports 80 and 443 (web server) and associates this security group to an instance port:"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:128(title)
msgid "Create and associate a floating IP to an instance"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:129(para)
msgid "You can use two sets of resources to create and associate floating IPs to instances."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:132(title)
msgid "OS::Nova resources"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:133(para)
msgid "Use the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Nova__FloatingIP.html\">OS::Nova::FloatingIP</link></literal> resource to create a floating IP, and the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Nova__FloatingIPAssociation.html\">OS::Nova::FloatingIPAssociation</link></literal> resource to associate the floating IP to an instance."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:136(para)
msgid "The following example creates an instance and a floating IP, and associate the floating IP to the instance:"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:159(title)
msgid "OS::Neutron resources"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:161(para)
msgid "The Networking service (neutron) must be enabled on your OpenStack deployment to use these resources."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:164(para)
msgid "Use the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Neutron__FloatingIP.html\">OS::Neutron::FloatingIP</link></literal> resource to create a floating IP, and the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Neutron__FloatingIPAssociation.html\">OS::Neutron::FloatingIPAssociation</link></literal> resource to associate the floating IP to a port:"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:189(title)
msgid "Enable remote access to an instance"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:190(para)
msgid "The <literal>key_name</literal> attribute of the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Nova__Server.html\">OS::Nova::Server</link></literal> resource defines the key pair to use to enable SSH remote access:"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:200(para)
msgid "For more information about key pairs, see the <link href=\"http://docs.openstack.org/user-guide/content/cli_configure_instances.html\">Configure access and security for instances</link> section of the OpenStack user guide."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:205(title)
msgid "Create a key pair"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:206(para)
msgid "You can create new key pairs with the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Nova__KeyPair.html\">OS::Nova::KeyPair</link></literal> resource. Key pairs can be imported or created during the stack creation."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:208(para)
msgid "If the <literal>public_key</literal> property is not specified, the Orchestration module creates a new key pair. If the <literal>save_private_key</literal> property is set to <literal>true</literal>, the <literal>private_key</literal> attribute of the resource holds the private key."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:211(para)
msgid "The following example creates a new key pair and uses it as authentication key for an instance:"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:234(title)
msgid "Manage networks"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:236(title)
msgid "Create a network and a subnet"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:238(para)
msgid "The Networking service (neutron) must be enabled on your OpenStack deployment to create and manage networks and subnets. Networks and subnets cannot be created if your deployment uses legacy networking (nova-network)."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:242(para)
msgid "Use the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Neutron__Net.html\">OS::Neutron::Net</link></literal> resource to create a network, and the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Neutron__Subnet.html\">OS::Neutron::Subnet</link></literal> resource to provide a subnet for this network:"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:257(title)
msgid "Create and manage a router"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:258(para)
msgid "Use the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Neutron__Router.html\">OS::Neutron::Router</link></literal> resource to create a router. You can define its gateway with the <literal>external_gateway_info</literal> property:"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:265(para)
msgid "You can connect subnets to routers with the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Neutron__RouterInterface.html\">OS::Neutron::RouterInterface</link></literal> resource:"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:275(title)
msgid "Complete network example"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:276(para)
msgid "The following example creates a network stack:"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:279(para)
msgid "A network and an associated subnet."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:282(para)
msgid "A router with an external gateway."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:285(para)
msgid "An interface to the new subnet for the new router."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:288(para)
msgid "In this example, the <literal>public</literal> network is an existing shared network:"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:315(title)
msgid "Manage volumes"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:318(para)
msgid "Use the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Cinder__Volume.html\">OS::Cinder::Volume</link></literal> resource to create a new Block Storage volume."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:326(para)
msgid "The volumes that you create are empty by default. Use the <literal>image</literal> property to create a bootable volume from an existing image:"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:334(para)
msgid "You can also create new volumes from another volume, a volume snapshot, or a volume backup. Use the <literal>source_volid</literal>, <literal>snapshot_id</literal> or <literal>backup_id</literal> properties to create a new volume from an existing source."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:337(para)
msgid "For example, to create a new volume from a backup:"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:343(para)
msgid "In this example the <literal>size</literal> property is not defined because the Block Storage service uses the size of the backup to define the size of the new volume."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:348(para)
msgid "Use the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Cinder__VolumeAttachment.html\">OS::Cinder::VolumeAttachment</link></literal> resource to attach a volume to an instance."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:350(para)
msgid "The following example creates a volume and an instance, and attaches the volume to the instance:"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:371(title)
msgid "Boot an instance from a volume"
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:372(para)
msgid "Use the <literal>block_device_mapping</literal> property of the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Nova__Server.html\">OS::Nova::Server</link></literal> resource to define a volume used to boot the instance. This property is a list of volumes to attach to the instance before its boot."
msgstr ""

#: ./doc/user-guide/hot/section_basic_resources.xml:375(para)
msgid "The following example creates a bootable volume from an image, and uses it to boot an instance:"
msgstr ""

#. WARNING: This file is automatically generated. Do not edit it.
#: ./doc/user-guide/hot/section_composition.xml:4(title)
msgid "Template composition"
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:5(para)
msgid "When writing complex templates you are encouraged to break up your template into separate smaller templates. These can then be brought together using template resources. This is a mechanism to define a resource using a template, thus composing one logical stack with multiple templates."
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:9(para)
msgid "Template resources provide a feature similar to the <literal><link href=\"http://docs.openstack.org/hot-reference/content/AWS__CloudFormation__Stack.html\">AWS::CloudFormation::Stack</link></literal> resource, but also provide a way to:"
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:13(para)
msgid "Define new resource types and build your own resource library."
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:16(para)
msgid "Override the default behaviour of existing resource types."
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:19(para)
msgid "To achieve this:"
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:22(para)
msgid "The Orchestration client gets the associated template files and passes them along in the <literal>files</literal> section of the <literal>POST stacks/</literal> API request."
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:26(para)
msgid "The environment in the Orchestration engine manages the mapping of resource type to template creation."
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:30(para)
msgid "The Orchestration engine translates template parameters into resource properties."
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:34(para)
msgid "The following examples illustrate how you can use a custom template to define new types of resources. These examples use a custom template stored in a <literal>my_nova.yml</literal> file:"
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:53(title)
msgid "Use the template filename as type"
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:54(para)
msgid "The following template defines the <literal>my_nova.yaml</literal> file as value for the <literal>type</literal> property of a resource:"
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:62(para)
msgid "The <literal>key_name</literal> argument of the <literal>my_nova.yaml</literal> template gets its value from the <literal>key_name</literal> property of the new template."
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:65(para)
msgid "The above reference to <literal>my_nova.yaml</literal> assumes it is in the same directory. You can use any of the following forms:"
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:69(para)
msgid "Relative path (<literal>my_nova.yaml</literal>)"
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:72(para)
msgid "Absolute path (<literal>file:///home/user/templates/my_nova.yaml</literal>)"
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:75(para)
msgid "Http URL (<literal>http://example.com/templates/my_nova.yaml</literal>)"
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:78(para)
msgid "Https URL (<literal>https://example.com/templates/my_nova.yaml</literal>)"
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:82(para) ./doc/user-guide/hot/section_composition.xml:105(para)
msgid "To create the stack run:"
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:87(title)
msgid "Define a new resource type"
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:88(para)
msgid "You can associate a name to the <literal>my_noya.yaml</literal> template in an environment file. If the name is already known by the Orchestration module then your new resource will override the default one."
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:91(para)
msgid "In the following example a new <literal>OS::Nova::Server</literal> resource overrides the default resource of the same name."
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:93(para)
msgid "An <literal>env.yaml</literal> environment file holds the definition of the new resource:"
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:97(para)
msgid "See <xref linkend=\"environments\"/> for more detail about environment files."
msgstr ""

#: ./doc/user-guide/hot/section_composition.xml:99(para)
msgid "You can now use the new <literal>OS::Nova::Server</literal> in your new template:"
msgstr ""

#. WARNING: This file is automatically generated. Do not edit it.
#: ./doc/user-guide/hot/section_advanced_topics.xml:4(title)
msgid "Advanced topics"
msgstr ""

#: ./doc/user-guide/hot/section_advanced_topics.xml:9(title)
msgid "Load balancer"
msgstr ""

#: ./doc/user-guide/hot/section_advanced_topics.xml:10(para) ./doc/user-guide/hot/section_advanced_topics.xml:14(para) ./doc/user-guide/hot/section_advanced_topics.xml:18(para) ./doc/user-guide/hot/section_advanced_topics.xml:26(para) ./doc/user-guide/hot/section_advanced_topics.xml:30(para)
msgid "TODO"
msgstr ""

#: ./doc/user-guide/hot/section_advanced_topics.xml:13(title)
msgid "Firewall"
msgstr ""

#: ./doc/user-guide/hot/section_advanced_topics.xml:17(title)
msgid "VPN"
msgstr ""

#: ./doc/user-guide/hot/section_advanced_topics.xml:23(title)
msgid "Auto scaling"
msgstr ""

#: ./doc/user-guide/hot/section_advanced_topics.xml:25(title)
msgid "Alarming"
msgstr ""

#: ./doc/user-guide/hot/section_advanced_topics.xml:29(title)
msgid "Up scaling and down scaling"
msgstr ""

#. WARNING: This file is automatically generated. Do not edit it.
#: ./doc/user-guide/hot/section_environment.xml:4(title)
msgid "Environments"
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:5(para)
msgid "The environment affects the runtime behaviour of a template. It provides a way to override the resource implementations and a mechanism to place parameters that the service needs."
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:8(para)
msgid "To fully understand the runtime behavior you have to consider what plug-ins are installed on the cloud you're using."
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:12(title)
msgid "Environment file format"
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:13(para)
msgid "The environment is a yaml text file that contains two main sections:"
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:20(para)
msgid "A map of key/pair values."
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:25(literal)
msgid "resource_registry"
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:28(para)
msgid "Definition of custom resources."
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:32(para)
msgid "Use the -e option of the <placeholder-1/> command to create a stack using with the environment defined in such a file."
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:34(para)
msgid "You can also provide environment parameters as a list of key/value pairs using the -P option of the <placeholder-1/> command."
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:36(para)
msgid "In the following example the environment is read from the <literal>my_env.yaml</literal> file and an extra parameter is provided using the -P option:"
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:42(title)
msgid "Global and effective environments"
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:43(para)
msgid "The environment used for a stack is the combination of the environment you use with the template for the stack, and a global environment that is determined by your cloud operator. An entry in the user environment takes precedence over the global environment. OpenStack includes a default global environment, but you cloud operator can add additional environment entries."
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:69(title)
msgid "Define values for a template arguments"
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:70(para)
msgid "You can define values for the template arguments in the <literal>parameters</literal> section of an environment file:"
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:79(title)
msgid "Create and override resources"
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:80(para)
msgid "You can create or override resources in the <literal>resource_registry</literal> section of an environment file. The resource you provide in this manner must have an identifier, and references either other resources IDs or the URL of an existing template file."
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:84(para)
msgid "The following example maps the new <literal>OS::Networking::FloatingIP</literal> resource to the existing <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Nova__FloatingIP.html\">OS::Nova::FloatingIP</link></literal> resource:"
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:88(para)
msgid "You can use wilcards to map multiple resources:"
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:91(para)
msgid "To create or override a resource with a custom resource, create a template file to define this resource, and provide the URL to the template file in the environment file:"
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:96(para)
msgid "The supported URL scheme are <literal>file</literal>, <literal>http</literal> and <literal>https</literal>."
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:98(para)
msgid "The template file extension must be <literal>.yaml</literal> or <literal>.template</literal>, or it will not be treated as a custom template resource."
msgstr ""

#: ./doc/user-guide/hot/section_environment.xml:101(para)
msgid "You can limit the usage of a custom resource to a specific resource of the template:"
msgstr ""

#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
#: ./doc/user-guide/hot/section_environment.xml:0(None)
msgid "translator-credits"
msgstr ""