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

bug: #1220407

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

3722 lines
215 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters

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

msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2013-03-12 15:09+0800\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:6(title)
msgid "Installing OpenStack Object Storage on Ubuntu"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:7(para)
msgid "Though you can install OpenStack Object Storage for development or testing purposes on a single server, a multiple-server installation enables the high availability and redundancy you want in a production distributed object storage system."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:8(para)
msgid "If you would like to perform a single node installation on Ubuntu for development purposes from source code, use the Swift All In One instructions or DevStack. See <link href=\"http://swift.openstack.org/development_saio.html\">http://swift.openstack.org/development_saio.html</link> for manual instructions or <link href=\"http://devstack.org\">http://devstack.org</link> for all-in-one including authentication and a dashboard."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:16(title)
msgid "Before You Begin"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:17(para)
msgid "Have a copy of the Ubuntu Server installation media on hand if you are installing on a new server."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:19(para)
msgid "This document demonstrates installing a cluster using the following types of nodes:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:23(para)
msgid "One Proxy node which runs the swift-proxy-server processes and may also run the optional swauth or tempauth services, this walkthrough uses the Identity service code-named Keystone. The proxy server serves proxy requests to the appropriate Storage nodes."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:31(para)
msgid "Five Storage nodes that run the swift-account-server, swift-container-server, and swift-object-server processes which control storage of the account databases, the container databases, as well as the actual stored objects."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:39(para) ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:62(para)
msgid "Fewer Storage nodes can be used initially, but a minimum of 5 is recommended for a production cluster."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:44(title)
msgid "General Installation Steps"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:47(para)
msgid "Install the baseline operating system, such as Ubuntu Server (10.04 through 12.04) or RHEL, CentOS, or Fedora, on all nodes."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:51(para)
msgid "Install the swift service and openSSH."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:56(para)
msgid "Create and populate configuration directories on all nodes:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:64(para)
msgid "Create /etc/swift/swift.conf:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:70(para)
msgid "The suffix value in <filename>/etc/swift/swift.conf</filename> should be set to some random string of text to be used as a salt when hashing to determine mappings in the ring. This file should be the same on every node in the cluster!"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml:77(para)
msgid "Next, set up your storage nodes, proxy node, and an auth node, in this walkthrough we'll use the OpenStack Identity Service, Keystone, for the common auth piece."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:7(title)
msgid "OpenStack Folsom upgrade"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:8(para)
msgid "This chapter will lead you through the Essex to Folsom upgrade process. If you are running an earlier version, you should upgrade to Essex before continuing."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:12(para)
msgid "As a preliminary step, you should check the release notes:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:16(para)
msgid "<link href=\"http://wiki.openstack.org/ReleaseNotes/Folsom\">Folsom release notes, 2012.2</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:20(para)
msgid "<link href=\"http://wiki.openstack.org/ReleaseNotes/2012.2.1\">2012.2.1</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:24(para)
msgid "<link href=\"http://wiki.openstack.org/ReleaseNotes/2012.2.2\">2012.2.2</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:27(para)
msgid "<link href=\"http://wiki.openstack.org/ReleaseNotes/2012.2.3\">2012.2.3</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:31(para)
msgid "The upgrade process will be done in the following steps:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:34(para)
msgid "Upgrade the OpenStack Identity service (Keystone)."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:37(para)
msgid "Upgrade the OpenStack Image service (Glance)."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:40(para)
msgid "Upgrade all OpenStack Compute (Nova) services."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:43(para)
msgid "Optional: Upgrade nova-volume to OpenStack Block Storage (Cinder). Please note that nova-volume will be deprecated in the following release."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:47(para)
msgid "Optional: Upgrade nova-network to OpenStack Networking (Neutron). Please note that nova-network will be deprecated in the following release."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:53(title)
msgid "Identity service (Keystone) upgrade"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:56(para) ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:109(para)
msgid "Stop the services: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:64(para) ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:118(para) ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:208(para)
msgid "Create a backup of your configuration files and of your database contents: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:72(para) ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:126(para)
msgid "Upgrade the packages to the latest 2012.2 version, using your distribution package manager."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:78(para) ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:165(para)
msgid "Apply the database upgrade. <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:85(para)
msgid "Start the keystone service: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:92(para) ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:180(para)
msgid "Check that everything is running fine: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:106(title)
msgid "Image service (Glance) upgrade"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:132(para)
msgid "Change the configuration files according to the <link href=\"http://wiki.openstack.org/ReleaseNotes/Folsom#OpenStack_Image_Service_.28Glance.29gt\">Release Notes</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:137(para)
msgid "You have to add the sql connection parameters to your API configuration file, or disable the new v2 API setting the <literal>enable_v2_api</literal> to <literal>false</literal>: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:145(para)
msgid "Also, the <literal>auth_token</literal> middleware configuration has been moved from the paste configuration to the server configuration. Unless you have made modifications to your paste config it is recommended to accept the distributed <filename>glance-api-paste.ini</filename> and <filename>glance-registry-paste.ini</filename> files and then add the <literal>auth_token</literal> configuration at the bottom of your <filename>glance-api.conf</filename> and <filename>glance-registry.conf</filename>, adapting it to your actual configuration: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:172(para)
msgid "Start the glance services: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:194(title)
msgid "Compute service (Nova) upgrade"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:195(para)
msgid "We will perform an upgrade of all the nova packages to the Folsom version. However, in this section we do not cover the upgrade to OpenStack Networking (Neutron) and OpenStack Block Storage (Cinder) of the respective and deprecated nova-network and nova-volume packages, as this will be covered in another section."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:202(para)
msgid "Stop all the nova services."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:216(para)
msgid "Upgrade the configuration files according to the <link href=\"http://wiki.openstack.org/ReleaseNotes/Folsom#OpenStack_Compute_.28Nova.29\">Release Notes</link>. You have to take into account the following:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:223(para)
msgid "IMPORTANT: If you are backing your instances with shared storage, make sure to disable image cache BEFORE upgrading to Folsom: <placeholder-1/> There is a serious issue when using cache manager and shared storage, for more details please check this <link href=\"https://bugs.launchpad.net/nova/+bug/1078594\">this bug report</link>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:233(para)
msgid "Change the <filename>nova.conf</filename> file to the new configuration format. In Essex the configuration was based on the old <literal>--option-name</literal> format, but in Folsom it has been changed to the INI config format, with options specified as <literal>key=value</literal> pairs. Because of this change, boolean options have to be explicitly set to true/false (such as <literal>verbose=true</literal>). The following code: <placeholder-1/> Will transform into this. <placeholder-2/> Check the <link href=\"..openstack-compute/admin/content/list-of-compute-config-options.html\">compute options reference card</link> to check if all your flags are recognized."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:255(para)
msgid "Check new the rootwrap configuration <link href=\"http://wiki.openstack.org/Packager/Rootwrap\">changes</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:263(para)
msgid "The <literal>connection_type</literal> flag has been deprecated in favor of the <literal>compute_driver</literal> flag, so <literal>connection_type=libvirt</literal> should be replaced with <literal>compute_driver=libvirt.LibvirtDriver</literal> and <literal>connection_type=xenapi</literal> should be replaced with <literal>compute_driver=xenapi.XenAPIDriver</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:272(para)
msgid "The libvirt.xml and cpuinfo.xml templates have been removed in favor of a <link href=\"http://wiki.openstack.org/LibvirtXMLConfigAPIs\">new config API</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:260(para)
msgid "If you are using Libvirt: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:284(para)
msgid "Upgrade all the packages to the latest 2012.2 version, using your distribution package manager. Note that we are not migrating nova-network and nova-volume to OpenStack Networking (Neutron) and OpenStack Block Storage (Cinder) in this step, but just upgrade those packages to Folsom."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:291(para)
msgid "Upgrade the nova api paste. It is recommended to accept the new <filename>nova/api-paste.ini</filename> file from the package, and then check it against a backed file for any local modifications."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:297(para)
msgid "Upgrade the <filename>nova/policy.json</filename> file. Unless you have made local changes you should accept the new file provided with the package."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:303(para)
msgid "Apply the DB upgrade. <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:311(para)
msgid "Restart all the services."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:316(para)
msgid "Check that everything is working fine: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:333(title)
msgid "Upgrade nova-volume to OpenStack Block Storage (Cinder)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:337(para)
msgid "Install Folsom version of OpenStack Block Storage (Cinder)."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:343(para)
msgid "Create a cinder user in Keystone as an admin in service tenant."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:348(para)
msgid "Edit <filename>/etc/cinder/api-paste.ini</filename> to reflect the <literal>admin_user</literal>, <literal>admin_tenant_name</literal>, and <literal>admin_password</literal> that you created in the previous step."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:355(para)
msgid "Create Cinder database and database user."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:360(para)
msgid "Check the SQL connection in <filename>/etc/cinder/cinder.conf</filename>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:365(para)
msgid "Create initial Cinder database: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:371(para)
msgid "Copy volume tables using the following command: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:375(para)
msgid "Do not include the database names in <literal>--src</literal> or <literal>--dest</literal>; <placeholder-1/> assumes your source database is named \"<literal>nova</literal>\" and that your destination database is named \"<literal>cinder</literal>\", and appends these to the strings you supply."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:385(para)
msgid "Copy iSCSI target configuration <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:391(para)
msgid "Set the correct volume api class in your <filename>nova.conf</filename> configuration file. <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:397(para)
msgid "Remove the <literal>osapi_volume</literal> from the <literal>enabled_apis</literal> in your <filename>/etc/nova/nova.conf</filename>. If you do not have such a configuration option, set it explicitly to the following (as it is included by default): <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:404(para)
msgid "Disable and stop the <placeholder-1/> service. <placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:411(para)
msgid "Restart the <literal>nova-api</literal> service <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:417(para)
msgid "Start cinder service: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:423(para)
msgid "Ensure that <filename>/etc/tgt/conf.d/cinder.conf</filename> exists and has an include line that matches <literal>volumes_dir</literal> option in <filename>cinder.conf</filename>. In the default case this is include <literal>/var/lib/cinder/volumes/*</literal>, if you edit this file restart the <literal>tgtd</literal> service."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:334(para)
msgid "We assume that all the services (including nova-volume) are migrated to Folsom. <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:434(title)
msgid "Upgrade nova-network to OpenStack Networking (Neutron)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_upgrading_from_essex.xml:435(para)
msgid "This process has not yet been documented."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-troubleshooting.xml:6(title)
msgid "Troubleshooting the Identity Service (Keystone)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-troubleshooting.xml:7(para)
msgid "To begin troubleshooting, look at the logs in the <filename>/var/log/keystone.log</filename> file (the location of log files is configured in the <filename>/etc/keystone/logging.conf</filename> file). It shows all the components that have come in to the WSGI request, and will ideally have an error in that log that explains why an authorization request failed. If you're not seeing the request at all in those logs, then run keystone with \"--debug\" where --debug is passed in directly after the CLI command prior to parameters."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:6(title)
msgid "OpenStack Terminology"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:9(title)
msgid "Version Names"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:12(para)
msgid "Each OpenStack release has a name, in increasing alphabetical order (e.g., Grizzly follows Folsom). There are also version numbers corresponding to these releases, but the numbering schemes are different for OpenStack Compute and OpenStack Object Storage, as shown in the table below: <table rules=\"all\"><caption> OpenStack version names </caption><thead><tr><td>Release name</td><td>Release date</td><td>OpenStack Compute version number</td><td>OpenStack Object Storage version number</td></tr></thead><tbody><tr><td><link href=\"http://wiki.openstack.org/ReleaseNotes/Grizzly\">Grizzly</link></td><td>April 2013</td><td>2013.1</td><td>1.7.6</td></tr><tr><td><link href=\"http://wiki.openstack.org/ReleaseNotes/Folsom\">Folsom</link></td><td>October 2012</td><td>2012.2</td><td>1.7.2</td></tr><tr><td><link href=\"http://wiki.openstack.org/ReleaseNotes/Essex\">Essex</link></td><td>April 2012</td><td>2012.1</td><td>1.4.8</td></tr><tr><td><link href=\"http://wiki.openstack.org/ReleaseNotes/Diablo\">Diablo</link></td><td>October 2011</td><td>2011.3</td><td>1.4.3</td></tr><tr><td><link href=\"http://wiki.openstack.org/ReleaseNotes/Cactus\">Cactus</link></td><td>April 2011</td><td>2011.2</td><td>1.3.0</td></tr><tr><td><link href=\"http://wiki.openstack.org/ReleaseNotes/Bexar\">Bexar</link></td><td>March 2011</td><td>2011.1</td><td>1.2.0</td></tr><tr><td><link href=\"http://wiki.openstack.org/ReleaseNotes/Austin\">Austin</link></td><td>October 2010</td><td>0.9.0</td><td>1.0.0</td></tr></tbody></table> Beginning with the Cactus release, OpenStack adopted a six month release schedule. The Havana release is scheduled for October 2013."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:84(title)
msgid "Code Names"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:100(para)
msgid "Identity"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:103(para)
msgid "Keystone"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:108(para)
msgid "Compute"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:111(para)
msgid "Nova"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:116(para)
msgid "Image"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:119(para)
msgid "Glance"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:124(para)
msgid "Dashboard"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:127(para)
msgid "Horizon"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:132(para)
msgid "Object Storage"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:135(para)
msgid "Swift"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:140(para)
msgid "Volumes"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:143(para) ./doc/src/docbkx/openstack-install/ch_externals.xml:107(title)
msgid "Cinder"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:148(para)
msgid "Networking"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:151(para)
msgid "Neutron"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:85(para)
msgid "Each OpenStack service has a code name. For example, the Image Service is code-named Glance. The full list is shown in the table below: <table rules=\"all\" width=\"100%\"><caption>Code names</caption><col width=\"50%\"/><col width=\"50%\"/><thead><tr><td>Service name</td><td>Code name</td></tr></thead><placeholder-1/></table>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:157(para)
msgid "These code names are reflected in the names of configuration files and command-line utility programs. For example, the Identity service has a configuration file called <filename>keystone.conf</filename>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:164(title)
msgid "OpenStack Services and Linux Services"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:165(para)
msgid "In the Linux world, a service (also known as a daemon) refers to a single program that runs in the background and typically listens on a port to respond to service requests. An OpenStack service, on the other hand, refers to a collection of Linux services working in concert."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:170(para)
msgid "OpenStack services are implemented by multiple Linux services. For example, <placeholder-1/> and <placeholder-2/> are two of the Linux services that implement the Compute service. OpenStack also depends on several third-party services, such as a database (typically MySQL) and a message broker (typically RabbitMQ or Qpid)."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:177(para)
msgid "In this document, we generally use the term \"service\" to refer both to lower-level Linux services and higher-level OpenStack services. It should be clear from the context whether we are referring to a high-level OpenStack service (e.g., Image), or a low-level Linux service (e.g., <placeholder-1/>)."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:185(title)
msgid "Storage: objects, blocks, and files"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:186(para)
msgid "Many cloud computing use cases require persistent remote storage. Storage solutions are often divided into three categories: object storage, block storage, and file storage."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:189(para)
msgid "Note that some storage solutions support multiple categories. For example, <link href=\"http://nexenta.com\">NexentaStor</link> supports both block storage and file storage (with announcements for future support for object storage), <link href=\"http://www.gluster.org\">GlusterFS</link> supports file storage and object storage, and <link href=\"http://ceph.com\">Ceph Storage</link> supports object storage, block storage, and file storage."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:196(title)
msgid "Object storage"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:197(para)
msgid "In OpenStack: Object Storage service (Swift)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:198(para)
msgid "Related concepts: Amazon S3, Rackspace Cloud Files, Ceph Storage"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:199(para)
msgid "With <emphasis role=\"italic\">object storage</emphasis>, files are exposed through an HTTP interface, typically with a REST API. All client data access is done at the user level: the operating system is unaware of the presence of the remote storage system. In OpenStack, the Object Storage service provides this type of functionality. Users access and modify files by making HTTP requests. Because the data access interface provided by an object storage system is at a low level of abstraction, people often build on top of object storage to build file-based applications that provide a higher level of abstraction. For example, the OpenStack Image service can be configured to use the Object Storage service as a backend. Another use for object storage solutions is as a content delivery network (CDN) for hosting static web content (e.g., images, and media files), since object storage already provides an HTTP interface."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:220(title)
msgid "Block storage (SAN)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:221(para)
msgid "In OpenStack: Volumes (<systemitem class=\"service\">nova-volume</systemitem> service) in OpenStack Compute or cinder as a separate Volume service"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:224(para)
msgid "Related concepts: Amazon Elastic Block Store (EBS), Ceph RADOS Block Device (RBD), iSCSI"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:226(para)
msgid "With <emphasis role=\"italic\">block storage</emphasis>, files are exposed through a low-level computer bus interface such as SCSI or ATA, that is accessible over the network. Block storage is synonymous with SAN (storage area network). Clients access data through the operating system at the device level: users access the data by mounting the remote device in a similar manner to how they would mount a local, physical disk (e.g., using the \"mount\" command in Linux). In OpenStack, the <systemitem class=\"service\">nova-volume</systemitem> service that forms part of the Compute service provides this type of functionality, and uses iSCSI to expose remote data as a SCSI disk that is attached to the network."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:235(para)
msgid "Because the data is exposed as a physical device, the end-user is responsible for creating partitions and formatting the exposed disk device. In addition, in OpenStack Compute a device can only be attached to one server at a time, so block storage cannot be used to share data across virtual machine instances concurrently."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:242(title)
msgid "File storage (NAS)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:243(para)
msgid "In OpenStack: none"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:244(para)
msgid "Related concepts: NFS, Samba/CIFS, GlusterFS, Dropbox, Google Drive"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:245(para)
msgid "With <emphasis role=\"italic\">file storage</emphasis>, files are exposed through a distributed file system protocol. Filesystem storage is synonymous with NAS (network attached storage). Clients access data through the operating system at the file system level: users access the data by mounting a remote file system. Examples of file storage include NFS and GlusterFS. The operating system needs to have the appropriate client software installed to be able to access the remote file system."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_terminology.xml:251(para)
msgid "Currently, OpenStack Compute does not have any native support for this type of file storage inside of an instance. However, there is a <link href=\"http://gluster.org/community/documentation//index.php/OSConnect\">Gluster storage connector for OpenStack</link> that enables the use of the GlusterFS file system as a back-end for the Image service."
msgstr ""
#: ./doc/src/docbkx/openstack-install/image-troubleshooting.xml:6(title)
msgid "Troubleshooting the Image Service (Glance)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/image-troubleshooting.xml:7(para)
msgid "To begin troubleshooting, look at the logs in the <filename>/var/log/glance/registry.log</filename> or <filename>/var/log/glance/api.log</filename>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installobjectstorage.xml:6(title)
msgid "Installing OpenStack Object Storage"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installobjectstorage.xml:7(para)
msgid "The OpenStack Object Storage services work together to provide object storage and retrieval through a REST API."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:6(title)
msgid "Configuring OpenStack Compute"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:7(para)
msgid "This section describes the relevant <filename>nova.conf</filename> settings for getting a minimal install running. Refer to the OpenStack Compute Administration Manual for guidance on more configuration options."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:13(literal) ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:36(literal)
msgid "my_ip"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:16(literal) ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:39(literal)
msgid "vncserver_listen"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:19(literal) ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:42(literal)
msgid "vncserver_proxyclient_address"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:10(para)
msgid "In general, you can use the same <filename>nova.conf</filename> file across the controller and compute nodes. However, the following configuration options need to be changed on each compute host: <placeholder-1/>For the above configuration options, you must use the IP address of the specific compute host, not the cloud controller."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:24(para)
msgid "The packages automatically do these steps for a user named nova, but if you are installing as another user you should ensure that the <filename>nova.conf</filename> file should have its owner set to <literal>root:nova</literal>, and mode set to <literal>0640</literal>, since the file contains your MySQL server’s username and password."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:30(para)
msgid "If you are installing as another user, you should set permissions correctly. This packaged install ensures that the nova user belongs to the nova group and that the .conf file permissions are set, but here are the manual commands, which should be run as root:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:41(para)
msgid "The hypervisor is set by editing <filename>/etc/nova/nova.conf</filename>. The hypervisor defaults to <literal>kvm</literal>, but if you are working within a VM already, switch to <literal>qemu</literal> on the <literal>libvirt_type=</literal> line. To use Xen, refer to the overview in this book for where to install nova components."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:45(para)
msgid "You can also configure the nova-compute service (and, for example configure a hypervisor-per-compute-node) with a separate <filename>nova-compute.conf</filename> file and then referring to <filename>nova-compute.conf</filename> in the <filename>nova.conf</filename> file."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:51(para)
msgid "Ensure the database connection defines your backend data store by adding a <literal>sql_connection</literal> line to <filename>nova.conf</filename>: <literal>sql_connection=mysql://<replaceable>[user]</replaceable>:<replaceable>[pass]</replaceable>@<replaceable>[primary IP]</replaceable>/<replaceable>[db name]</replaceable></literal>, such as <literal>sql_connection=mysql://nova:yourpassword@192.168.206.130/nova</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:56(para)
msgid "Add these settings to <filename>/etc/nova/nova.conf</filename> for the network configuration assumptions made for this installation scenario. You can place comments in the <filename>nova.conf</filename> file by entering a new line with a <literal>#</literal> sign at the beginning of the line. To see a listing of all possible configuration option settings, see <link href=\"http://docs.openstack.org/trunk/openstack-compute/admin/content/compute-options-reference.html\">the reference in the OpenStack Compute Administration Manual</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:73(para)
msgid "Here is an example <filename>nova.conf</filename> with commented sections:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:79(para)
msgid "The <literal>my_ip</literal> configuration option will be different for each host, edit it accordingly."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-minimum-configuration.xml:83(para)
msgid "Stop the nova- services prior to running db sync, by running stop commands as root. Otherwise your logs show errors because the database has not yet been populated:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-mysql.xml:6(title)
msgid "Installing MySQL"
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-mysql.xml:7(para)
msgid "Install MySQL as root:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-mysql.xml:12(para)
msgid "During the install, you'll be prompted for the mysql root password. Enter a password of your choice and verify it."
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-mysql.xml:14(para)
msgid "Use <placeholder-1/> to edit <filename>/etc/mysql/my.cnf</filename> to change <literal>bind-address</literal> from localhost (127.0.0.1) to any (0.0.0.0) and restart the mysql service, as root."
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-mysql.xml:22(para)
msgid "Set MySQL to start the daemon every time you start and then start the server. <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-configure.xml:6(title)
msgid "Configuring the Dashboard"
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-configure.xml:7(para)
msgid "A full example <filename>local_settings.py</filename> file is included in the Appendix of the OpenStack Install and Deploy manual. Here are some common options:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-configure.xml:11(para)
msgid "<literal>SWIFT_ENABLED</literal>: If an Object Storage (Swift) endpoint is available and configured in the Identity service catalog, set <literal>SWIFT_ENABLED = True</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-configure.xml:16(para)
msgid "<literal>NEUTRON_ENABLED</literal>: If a Network Connection (Neutron) service is available and configured in the Identity service catalog, set <literal>NEUTRON_ENABLED = True</literal>. Else keep it FALSE if you are not using Neutron."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installidentity.xml:6(title)
msgid "Installing OpenStack Identity Service"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installidentity.xml:7(para)
msgid "The OpenStack Identity service manages users, tenants (accounts or projects) and offers a common identity system for all the OpenStack components."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:3(title)
msgid "Instructions for a Multiple Server Swift Installation (Ubuntu)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:6(title) ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:14(title)
msgid "Prerequisites"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:10(para)
msgid "Ubuntu Server 10.04 LTS installation media"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:15(para)
msgid "Swift can run with other distros, but for this document we will focus on installing on Ubuntu Server, ypmv (your packaging may vary)."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:18(para)
msgid "Basic architecture and terms"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:28(para)
msgid "This document shows a cluster using the following types of nodes:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:33(para)
msgid "one Proxy node"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:38(para)
msgid "Runs the swift-proxy-server processes which proxy requests to the appropriate Storage nodes. The proxy server will also contain the TempAuth service as WSGI middleware."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:47(para)
msgid "five Storage nodes"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:52(para)
msgid "Runs the swift-account-server, swift-container-server, and swift-object-server processes which control storage of the account databases, the container databases, as well as the actual stored objects."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:63(para)
msgid "This document describes each Storage node as a separate zone in the ring. It is recommended to have a minimum of 5 zones. A zone is a group of nodes that is as isolated as possible from other nodes (separate servers, network, power, even geography). The ring guarantees that every replica is stored in a separate zone. For more information about the ring and zones, see: <link linkend=\"the-ring\">The Ring</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:71(para)
msgid "To increase reliability, you may want to add additional Proxy servers for performance which is described in <link linkend=\"adding-a-proxy-server\">Adding a Proxy Server</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:77(title)
msgid "Network Setup Notes"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:79(para)
msgid "This document refers to two networks. An external network for connecting to the Proxy server, and a storage network that is not accessible from outside the cluster, to which all of the nodes are connected. All of the Swift services, as well as the rsync daemon on the Storage nodes are configured to listen on their STORAGE_LOCAL_NET IP addresses."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:87(para)
msgid "Run all commands as the root user"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:89(title)
msgid "General OS configuration and partitioning for each node"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:94(para)
msgid "Install the baseline Ubuntu Server 10.04 LTS on all nodes."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:99(para)
msgid "Install common Swift software prereqs:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:110(para)
msgid "Create and populate configuration directories:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:119(para)
msgid "On the first node only, create /etc/swift/swift.conf:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:131(para)
msgid "On the second and subsequent nodes: Copy that file over. It must be the same on every node in the cluster!:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:140(para)
msgid "Publish the local network IP address for use by scripts found later in this documentation:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:150(para)
msgid "The random string of text in /etc/swift/swift.conf is used as a salt when hashing to determine mappings in the ring."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:152(title)
msgid "Configure the Proxy node"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:154(para)
msgid "It is assumed that all commands are run as the root user"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:157(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:17(para)
msgid "Install swift-proxy service:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:165(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:22(para)
msgid "Create self-signed cert for SSL:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:174(para)
msgid "If you don't create the cert files, Swift silently uses http internally rather than https. This document assumes that you have created these certs, so if you're following along step-by-step, create them."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:177(para)
msgid "Modify memcached to listen on the default interfaces. Preferably this should be on a local, non-public network. Edit the IP address in /etc/memcached.conf, for example:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:187(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:40(para)
msgid "Restart the memcached server:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:195(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:52(para)
msgid "Create /etc/swift/proxy-server.conf:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:229(title) ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:234(title) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:127(title) ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:61(title) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:42(title) ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:67(title) ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:8(title) ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:71(title)
msgid "Note"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:229(para)
msgid "If you run multiple memcache servers, put the multiple IP:port listings in the [filter:cache] section of the <filename>proxy-server.conf</filename> file like: `10.1.2.3:11211,10.1.2.4:11211`. Only the proxy server uses memcache."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:234(para)
msgid "The memcache_servers variable can also be set in a separate file: <filename>/etc/swift/memcache.conf</filename>. If it is set in both places, the value in <filename>proxy-server.conf</filename> will override the one in <filename>memcache.conf</filename>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:241(para)
msgid "Create the account, container and object rings. The builder command is basically creating a builder file with a few parameters. The parameter with the value of 18 represents 2 ^ 18th, the value that the partition will be sized to. Set this \"partition power\" value based on the total amount of storage you expect your entire ring to use. The value of 3 represents the number of replicas of each object, with the last value being the number of hours to restrict moving a partition more than once."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:262(para)
msgid "For every storage device in /srv/node on each node add entries to each ring:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:277(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:102(para)
msgid "Assuming there are 5 zones with 1 node per zone, ZONE should start at 1 and increment by one for each additional node."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:280(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:108(para)
msgid "Verify the ring contents for each ring:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:290(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:118(para)
msgid "Rebalance the rings:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:300(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:128(para)
msgid "Rebalancing rings can take some time."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:303(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:132(para)
msgid "Copy the account.ring.gz, container.ring.gz, and object.ring.gz files to each of the Proxy and Storage nodes in /etc/swift."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:310(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:137(para)
msgid "Make sure all the config files are owned by the swift user:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:318(para) ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:142(para)
msgid "Start Proxy services:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:327(title)
msgid "Configure the Storage nodes"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:329(para)
msgid "Swift should work on any modern filesystem that supports Extended Attributes (XATTRS). We currently recommend XFS as it demonstrated the best overall performance for the swift use case after considerable testing and benchmarking at Rackspace. It is also the only filesystem that has been thoroughly tested. These instructions assume that you are going to devote /dev/sdb1 to an XFS filesystem."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:332(para) ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:17(para)
msgid "Install Storage node packages:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:340(para)
msgid "For every device on the node, setup the XFS volume (/dev/sdb is used as an example):"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:354(para)
msgid "Create /etc/rsyncd.conf:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:386(para)
msgid "Edit the RSYNC_ENABLE= line in /etc/default/rsync:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:394(para) ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:69(para)
msgid "Start rsync daemon:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:402(para) ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:72(para)
msgid "The rsync daemon requires no authentication, so it should be run on a local, private network."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:405(para)
msgid "Create /etc/swift/account-server.conf:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:429(para)
msgid "Create /etc/swift/container-server.conf:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:453(para)
msgid "Create /etc/swift/object-server.conf:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:477(para)
msgid "Start the storage services. If you use this command, it will try to start every service for which a configuration file exists, and throw a warning for any configuration files which don't exist:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:486(para)
msgid "Or, if you want to start them one at a time, run them as below. Note that if the server program in question generates any output on its stdout or stderr, swift-init has already redirected the command's output to /dev/null. If you encounter any difficulty, stop the server and run it by hand from the command line. Any server may be started using \"swift-$SERVER-$SERVICE /etc/swift/$SERVER-config\", where $SERVER might be object, continer, or account, and $SERVICE might be server, replicator, updater, or auditor."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:513(title)
msgid "Create Swift admin account and test"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:515(para)
msgid "You run these commands from the Proxy node."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:520(para) ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:31(para)
msgid "Get an X-Storage-Url and X-Auth-Token:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:528(para) ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:37(para)
msgid "Check that you can HEAD the account:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:536(para)
msgid "Check that <literal>swift</literal> works (at this point, expect zero containers, zero objects, and zero bytes):"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:545(para)
msgid "Use <literal>swift</literal> to upload a few files named 'bigfile[1-2].tgz' to a container named 'myfiles':"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:555(para)
msgid "Use <literal>swift</literal> to download all files from the 'myfiles' container:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:564(para)
msgid "Use <literal>swift</literal> to save a backup of your builder files to a container named 'builders'. Very important not to lose your builders!:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:574(para)
msgid "Use <literal>swift</literal> to list your containers:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:582(para)
msgid "Use <literal>swift</literal> to list the contents of your 'builders' container:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:591(para)
msgid "Use <literal>swift</literal> to download all files from the 'builders' container:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:601(title)
msgid "Adding a Proxy Server"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:603(para)
msgid "For reliability's sake you may want to have more than one proxy server. You can set up the additional proxy node in the same manner that you set up the first proxy node but with additional configuration steps."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:609(para)
msgid "Once you have more than two proxies, you also want to load balance between the two, which means your storage endpoint also changes. You can select from different strategies for load balancing. For example, you could use round robin dns, or an actual load balancer (like pound) in front of the two proxies, and point your storage url to the load balancer."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:617(para)
msgid "See <link linkend=\"configure-the-proxy-node\">config-proxy</link> for the initial setup, and then follow these additional steps."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:623(para)
msgid "Update the list of memcache servers in /etc/swift/proxy-server.conf for all the added proxy servers. If you run multiple memcache servers, use this pattern for the multiple IP:port listings: `10.1.2.3:11211,10.1.2.4:11211` in each proxy server's conf file.:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:637(para)
msgid "Change the storage url for any users to point to the load balanced url, rather than the first proxy server you created in /etc/swift/proxy-server.conf:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:649(para) ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:53(para)
msgid "Next, copy all the ring information to all the nodes, including your new proxy nodes, and ensure the ring info gets to all the storage nodes as well."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:656(para)
msgid "After you sync all the nodes, make sure the admin has the keys in /etc/swift and the ownership for the ring file is correct."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:663(title)
msgid "Troubleshooting Notes"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:665(para)
msgid "If you see problems, look in var/log/syslog (or messages on some distros)."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:669(para)
msgid "Also, at Rackspace we have seen hints at drive failures by looking at error messages in /var/log/kern.log."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-howto-install-multinode.xml:673(para)
msgid "There are more debugging hints and tips in the <link linkend=\"troubleshooting-openstack-object-storage\">Troubleshooting</link> section."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:6(title)
msgid "Verifying the Identity Service Installation"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:7(para)
msgid "Verify that authentication is behaving as expected by using your established username and password to generate an authentication token:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:23(para)
msgid "You should receive a token in response, paired with your user ID."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:26(para)
msgid "This verifies that keystone is running on the expected endpoint, and that your user account is established with the expected credentials."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:30(para)
msgid "Next, verify that authorization is behaving as expected by requesting authorization on a tenant:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:47(para)
msgid "You should receive a new token in response, this time including the ID of the tenant you specified."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:51(para)
msgid "This verifies that your user account has an explicitly defined role on the specified tenant, and that the tenant exists as expected."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:55(para)
msgid "You can also set your <literal>--os-*</literal> variables in your environment to simplify CLI usage. First, set up a <literal>keystonerc</literal> file with the admin credentials and admin endpoint:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:67(para)
msgid "Save and source the file."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:71(para)
msgid "Verify that your <literal>keystonerc</literal> is configured correctly by performing the same command as above, but without any <literal>--os-*</literal> arguments."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:89(para)
msgid "You should receive a new token in response, reflecting the same tenant and user ID values as above."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:93(para)
msgid "This verifies that you have configured your environment variables correctly."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:97(para)
msgid "Finally, verify that your admin account has authorization to perform administrative commands."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:102(title) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:76(title)
msgid "Reminder"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:103(para)
msgid "Unlike basic authentication/authorization, which can be performed against either port 5000 or 35357, administrative commands MUST be performed against the admin API port: 35357). This means that you MUST use port 35357 in your <literal>OS_AUTH_URL</literal> or <literal>--os-auth-url</literal> setting."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-verify-install.xml:127(para)
msgid "This verifies that your user account has the <literal>admin</literal> role, as defined in keystone's <literal>policy.json</literal> file."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-cloud-controller.xml:6(title)
msgid "Installing the Cloud Controller"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-cloud-controller.xml:7(para)
msgid "Install the required nova- packages, and dependencies are automatically installed."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-cloud-controller.xml:10(para)
msgid "If you see the error: <placeholder-1/>ensure that you have installed the Ubuntu Cloud Archive packages by adding the following to <filename>/etc/apt/sources.list.d/folsom.list</filename>: <placeholder-2/>Prior to running apt-get update and apt-get upgrade, install the keyring: <placeholder-3/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-rabbitmq.xml:6(title)
msgid "Installing RabbitMQ"
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-rabbitmq.xml:7(para)
msgid "Install the messaging queue server, RabbitMQ."
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-rabbitmq.xml:8(para)
msgid "You have the option of installing Apache Qpid, refer to the Compute Administration Manual for configuration instructions, including adding rpc_backend=nova.rpc.impl_qpid to your <filename>nova.conf</filename>."
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:23(None)
msgid "@@image: 'figures/nova-external-1.svg'; md5=f9c2bec7596726c484472ddef91a0da7"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:26(None)
msgid "@@image: 'figures/nova-external-1.png'; md5=fbdd2189f1ea2caf0c7f1c0d0c89c867"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:33(None)
msgid "@@image: 'figures/nova-external-2.svg'; md5=3d002addd52a75b22ff44c2e353ec54c"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:36(None)
msgid "@@image: 'figures/nova-external-2.png'; md5=dd9285024dc9167294d3bec75929643a"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:6(title)
msgid "Underlying Technologies"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:7(para)
msgid "You can think of OpenStack Compute as a toolkit for building a cloud computing environment by stitching together existing Linux technologies."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:10(para)
msgid "The figures below shows two examples of how these underlying technologies can be assembled to construct an OpenStack Compute cloud. The circles are Linux services that are part of OpenStack Compute, and the rectangles are external (not maintained by the OpenStack project) components. Solid lines show interactions between OpenStack components and external components, and dashed lines show interactions between external components. All services that are part of OpenStack Compute interact with a queueing backend (e.g., RabbitMQ, Qpid) and a database backend (e.g., MySQL, PostgreSQL); these connections are not shown. Also not shown are services that do not explicitly rely on external technologies. For example, the <systemitem class=\"service\">nova-api</systemitem> service, the Identity service, and the Image service are not shown."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:20(title)
msgid "Underlying technologies (Scenario 1)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:30(title)
msgid "Underlying technologies (Scenario 2)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:41(para)
msgid "Many of the external technologies can be substituted with other components, as shown in the table below.<table frame=\"void\"><caption>Technologies and supported implementations</caption><col width=\"25%\"/><col width=\"75%\"/><thead><tr><th>Technology</th><th>Supported implementations</th></tr></thead><tbody><tr><td>Message queue</td><td>RabbitMQ, Qpid, ZeroMQ</td></tr><tr><td>Virtualization</td><td>xapi+XCP, xapi+XenServer, libvirt+KVM, libvirt+QEMU, libvirt+LXC, libvirt+VMWare</td></tr><tr><td>iSCSI back-end</td><td>LVM+IET, LVM+tgt, Xen Storage Manager, SAN (Solaris, HP, SolidFire), NexentaStor, NetApp, Ceph, Sheepdog</td></tr><tr><td>Database</td><td>MySQL, PostgreSQL, sqlite</td></tr><tr><td>Web server</td><td>Apache, Nginx</td></tr><tr><td>Session cache</td><td>memcache, any Django-supported database backend (e.g., MySQL, PostgreSQL, sqlite)</td></tr></tbody></table>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:82(title) ./doc/src/docbkx/openstack-install/ch_instances-running.xml:84(systemitem)
msgid "nova-compute"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:82(para)
msgid "The <systemitem class=\"service\">nova-compute</systemitem> service depends on a virtualization driver to manage virtual machines. By default, this driver is <emphasis role=\"italic\">libvirt</emphasis>, which is used to drive <emphasis role=\"italic\">KVM</emphasis>. However, the libvirt driver can also drive other hypervisor technologies, and there is a separate Xen virtualization driver for driving Xen-based virtual machines if configured to use Xen Cloud Platform (XCP) or XenServer. <emphasis role=\"italic\">Open-iscsi</emphasis> is used to mount remote block devices, also known as volumes. Open-iscsi exposes these remote devices as local device files which can be attached to instances."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:91(title) ./doc/src/docbkx/openstack-install/ch_instances-running.xml:92(systemitem)
msgid "nova-network"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:92(para)
msgid "The <systemitem class=\"service\">nova-network</systemitem> service depends on a number of Linux networking technologies. It uses <emphasis role=\"italic\">Linux bridging</emphasis> to create network bridges to connect virtual machines to the physical networks. These bridges may be associated with VLANs using <emphasis role=\"italic\">Linux networking VLAN support</emphasis>, if running in the VLAN networking mode. <emphasis role=\"italic\">Iptables</emphasis> is used to implement security rules and implement NAT functionality, which is used for providing instances with access to the metadata service and for supporting floating IP addresses. <emphasis role=\"italic\">Dnsmasq</emphasis> is used as a DHCP server to hand out IP addresses to virtual machine instances, as well as a DNS server."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:102(para)
msgid "In a future OpenStack release, functionality that is currently implemented by <systemitem class=\"service\">nova-network</systemitem> will be available through a separate OpenStack project, codenamed Neutron."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:108(para)
msgid "By default, <systemitem class=\"service\">Cinder</systemitem> service uses <emphasis role=\"italic\">LVM</emphasis> to create and manage local volumes, and exports them via iSCSI using <emphasis role=\"italic\">IET</emphasis> or <emphasis role=\"italic\">tgt</emphasis>. It can also be configured to use other iSCSI-based storage technologies."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:112(para)
msgid "In the Folsom OpenStack release, functionality available through <systemitem class=\"service\">nova-volume</systemitem> is also available through a separate OpenStack Volumes project, code-named Cinder."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:118(title)
msgid "openstack-dashboard"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_externals.xml:119(para)
msgid "The <systemitem class=\"service\">openstack-dashboard</systemitem> is a Django-based application that runs behind an <emphasis role=\"italic\">Apache</emphasis> web server by default. It uses <emphasis role=\"italic\">memcache</emphasis> for the session cache by default. A web-based VNC client called <emphasis role=\"italic\">novnc</emphasis> is used to provide access to the VNC consoles associated with the running KVM instances."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:6(title)
msgid "Compute and Image System Requirements"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:7(para)
msgid "<emphasis role=\"bold\">Hardware</emphasis>: OpenStack components are intended to run on standard hardware. Recommended hardware configurations for a minimum production deployment are as follows for the cloud controller nodes and compute nodes for Compute and the Image Service, and object, account, container, and proxy servers for Object Storage."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:15(caption) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:10(caption)
msgid "Hardware Recommendations"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:22(td) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:17(td)
msgid "Server"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:23(td) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:18(td)
msgid "Recommended Hardware"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:24(td) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:19(td)
msgid "Notes"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:29(td)
msgid "Cloud Controller node (runs network, volume, API, scheduler and image services)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:32(para) ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:47(para)
msgid "Processor: 64-bit x86"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:33(para)
msgid "Memory: 12 GB RAM"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:34(para)
msgid "Disk space: 30 GB (SATA, SAS or SSD)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:35(para)
msgid "Volume storage: two disks with 2 TB (SATA) for volumes attached to the compute nodes"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:37(para)
msgid "Network: one 1 Gbps Network Interface Card (NIC)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:40(para)
msgid "Two NICS are recommended but not required. A quad core server with 12 GB RAM would be more than sufficient for a cloud controller node."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:45(td)
msgid "Compute nodes (runs virtual instances)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:48(para)
msgid "Memory: 32 GB RAM"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:49(para)
msgid "Disk space: 30 GB (SATA)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:50(para)
msgid "Network: two 1 Gbps NICs"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:53(para)
msgid "With 2 GB RAM you can run one m1.small instance on a node or three m1.tiny instances without memory swapping, so 2 GB RAM would be a minimum for a test-environment compute node. As an example, Rackspace Cloud Builders use 96 GB RAM for compute nodes in OpenStack deployments."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:58(para)
msgid "Specifically for virtualization on certain hypervisors on the node or nodes running nova-compute, you need a x86 machine with an AMD processor with SVM extensions (also called AMD-V) or an Intel processor with VT (virtualization technology) extensions."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:62(para)
msgid "For XenServer and XCP refer to the <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#sys_requirements\"> XenServer installation guide</link> and the <link href=\"http://hcl.vmd.citrix.com/\"> XenServer harware compatibility list</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:67(para)
msgid "For LXC, the VT extensions are not required."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:74(para)
msgid "While certain parts of OpenStack are known to work on various operating systems, currently the only feature-complete, production-supported host environment is 64-bit Linux."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:85(para)
msgid "The Folsom release of OpenStack Compute requires Ubuntu 12.04 or later, as the version of libvirt that ships with Ubuntu 11.10 does not function properly with OpenStack due to <link href=\"https://bugs.launchpad.net/nova/+bug/1011863\">bug #1011863</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:91(para)
msgid "The Folsom release of OpenStack Compute requires Fedora 16 or later, as the version of libvirt that ships with Fedora 15 does not function properly with OpenStack due to <link href=\"https://bugs.launchpad.net/nova/+bug/1011863\">bug #1011863</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:78(para)
msgid "<emphasis role=\"bold\">Operating System</emphasis>: OpenStack currently has packages for the following distributions: CentOS, Debian, Fedora, RHEL, and Ubuntu. These packages are maintained by community members, refer to <link href=\"http://wiki.openstack.org/Packaging\">http://wiki.openstack.org/Packaging</link> for additional links. <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:98(para)
msgid "<emphasis role=\"bold\">Database</emphasis>: For OpenStack Compute, you need access to either a PostgreSQL or MySQL database, or you can install it as part of the OpenStack Compute installation process."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:102(para)
msgid "<emphasis role=\"bold\">Permissions</emphasis>: You can install OpenStack services either as root or as a user with sudo permissions if you configure the sudoers file to enable all the permissions."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-sys-requirements.xml:106(para)
msgid "<emphasis role=\"bold\">Network Time Protocol</emphasis>: You must install a time synchronization program such as NTP. For Compute, time synchronization avoids problems when scheduling VM launches on compute nodes. For Object Storage, time synchronization ensure the object replications are accurately updating objects when needed so that the freshest content is served."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-db-sync.xml:5(title)
msgid "Configuring the Database for Compute"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-db-sync.xml:6(para)
msgid "Create the tables in your backend data store by running the following command:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-db-sync.xml:9(para)
msgid "If you see any response, you can look in /var/log/nova/nova-manage.log to see the problem. No response means the command completed correctly and your nova database is now populated."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-db-sync.xml:13(title)
msgid "Deprecation warnings"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-db-sync.xml:14(para)
msgid "Note that if while running this command you see warnings such as <literal> SADeprecationWarning: The 'listeners' argument to Pool (and create_engine()) is deprecated. Use event.listen().</literal>, these will be fixed in future version of the libraries and can be safely ignored."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-db-sync.xml:16(para)
msgid "Restart all services in total, just to cover the entire spectrum:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-db-sync.xml:31(para)
msgid "All nova services are now installed and started. If the \"start\" command doesn't work, your services may not be running correctly (or not at all). Review the logs in /var/log/nova to look for clues."
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/src/docbkx/openstack-install/dashboard-verify.xml:18(None) ./doc/src/docbkx/openstack-install/dashboard-verify.xml:22(None) ./doc/src/docbkx/openstack-install/vnc-console.xml:18(None) ./doc/src/docbkx/openstack-install/vnc-console.xml:22(None)
msgid "@@image: 'figures/dashboard-overview.png'; md5=e8da604fd0de70c96f6becbef3cba0fa"
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-verify.xml:6(title) ./doc/src/docbkx/openstack-install/vnc-console.xml:6(title)
msgid "Validating the Dashboard Install"
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-verify.xml:7(para)
msgid "To validate the Dashboard installation, point your browser at http://192.168.206.130/horizon. Note that you cannot use VNC Console from a Chrome browser. You need both Flash installed and a Firefox browser. Once you connect to the Dashboard with the URL, you should see a login window. Enter the credentials for users you created with the Identity Service, Keystone. For example, enter \"admin\" for the username and \"secrete\" as the password."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:6(title)
msgid "Appendix: Configuration File Examples"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:8(para)
msgid "Included for your reference are all configuration files."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:9(title)
msgid "keystone.conf"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:9(para)
msgid "The Identity service's configuration file is found in /etc/keystone/keystone.conf. This file needs to be modified after installing to use SQL for endpoint data and to replace the ADMIN key with the one created during the installation."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:15(title)
msgid "glance-registry.conf"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:15(para)
msgid "The Image service's registry, which stores the metadata about images, is found in /etc/glance/glance-registry.conf. This file needs to be modified after installing."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:21(title)
msgid "glance-registry-paste.ini"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:22(para)
msgid "The Image service's API middleware pipeline is found in /etc/glance/glance-registry-paste.ini. This file needs to be modified after installing."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:28(title)
msgid "glance-api.conf"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:28(para)
msgid "The configuration file for the Image API is found in /etc/glance/glance-api.conf. You need to change this file to look like this example after installing from packages."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:34(title)
msgid "glance-api-paste.ini"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:35(para)
msgid "The Image service's API middleware pipeline is found in /etc/glance/glance-api-paste.ini. You should not need to modify this file."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:41(title)
msgid "glance-scrubber.conf"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:41(para)
msgid "An additional configuration file for the Image service is found in /etc/glance/glance-scrubber.conf. The scrubber is a utility that cleans up images that have been deleted."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:46(title)
msgid "nova.conf"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:46(para)
msgid "The configuration file for Compute (nova) settings is stored in /etc/nova/nova.conf. To see a list of all possible configuration options for this file, see the List of Tables at the beginning of the <link href=\"http://docs.openstack.org/trunk/openstack-compute/admin/content/\">OpenStack Compute Admin guide</link> ."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:55(literal)
msgid "service_host"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:58(literal)
msgid "auth_host"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:61(literal)
msgid "auth_uri"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:51(para)
msgid "This guide assumes that the IP address of the machine that runs the Identity service is <literal>192.168.206.130</literal>. If the IP address of the machine on your setup is different, change the following configuration options:<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:66(title)
msgid "api-paste.ini"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:66(para)
msgid "The /etc/nova/api-paste.ini file is a middleware configuration file used by the EC2 API and OpenStack Compute API. You should not need to edit it."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:69(title)
msgid "Credentials (openrc)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:69(para)
msgid "This file contains the credentials used by Compute, Image, and Identity services, you can optionally store in /home/openrc. The important concept to avoid errors is to ensure that it is sourced in the environment from which you issue commands. Run \"env | grep OS_\" or \"env | grep NOVA_\" to view what is being used in your environment."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:78(title)
msgid "Dashboard configuration"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:78(para)
msgid "This file contains the database and configuration settings for the OpenStack Dashboard."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:81(title)
msgid "etc/swift/swift.conf"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:82(para)
msgid "This file contains the settings to randomize the hash for the ring for Object Storage, code-named swift."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:86(title)
msgid "etc/network/interfaces.conf"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:87(para)
msgid "These instructions are for using the FlatDHCP networking mode with a single network interface."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:90(title)
msgid "etc/swift/proxy-server.conf"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:91(para)
msgid "This file contains the settings for the Object Storage proxy server, which contains the Identity service settings."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:94(title)
msgid "etc/swift/account-server.conf"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:98(title)
msgid "etc/swift/account-server/1.conf"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:102(title)
msgid "etc/swift/container-server.conf"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:106(title)
msgid "etc/swift/container-server/1.conf"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:110(title)
msgid "etc/swift/object-server.conf"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_configuration_files.xml:114(title)
msgid "etc/swift/object-server/1.conf"
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:6(title)
msgid "System Requirements for the Dashboard"
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:7(para)
msgid "Because Apache does not serve content from a root user, you must use another user with sudo privileges and run as that user."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:8(para)
msgid "You should have a running OpenStack Compute installation with the Identity Service, Keystone, enabled for identity management."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:10(para)
msgid "The dashboard needs to be installed on the node that can contact the Identity Service."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:11(para)
msgid "You should know the URL of your Identity endpoint and the Compute endpoint."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:12(para)
msgid "You must know the credentials of a valid Identity service user."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:13(para)
msgid "You must have git installed. It's straightforward to install it with sudo apt-get install git-core."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:15(para)
msgid "Python 2.6 is required, and these instructions have been tested with Ubuntu 10.10. It should run on any system with Python 2.6 or 2.7 that is capable of running Django including Mac OS X (installing prerequisites may differ depending on platform)."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:18(para)
msgid "Optional components:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:21(para)
msgid "An Image Store (<emphasis role=\"italic\">Glance</emphasis>) endpoint."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:22(para)
msgid "An Object Store (<emphasis role=\"italic\">Swift</emphasis>) endpoint."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-system-reqs.xml:23(para)
msgid "A <link href=\"http://wiki.openstack.org/Neutron\">Neutron</link> (networking) endpoint."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:6(title)
msgid "Pre-configuring the network"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:7(para)
msgid "These instructions are for using the FlatDHCP networking mode with a single network interface. More complex configurations are described in the networking section, but this configuration is known to work. These configuration options should be set on all compute nodes."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:11(para)
msgid "Set your network interface in promiscuous mode so that it can receive packets that are intended for virtual machines. As root:<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:14(para)
msgid "Set up your /etc/network/interfaces file with these settings:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:15(para)
msgid "eth0: public IP, gateway"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:16(para)
msgid "br100: no ports, stp off, fd 0, first address from fixed_range set in nova.conf files."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:17(para)
msgid "Here's an Ubuntu/Debian example:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:33(para)
msgid "Here's an example network setup for RHEL, Fedora, or CentOS. Create <filename>/etc/sysconfig/network-scripts/ifcfg-br100</filename>:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:45(para)
msgid "Also install bridge-utils:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:48(para)
msgid "Ensure that you set up the bridge, although if you use flat_network_bridge=br100 in your <filename>nova.conf</filename> file, nova will set up the bridge for you when you run the nova-manage network command."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:53(para)
msgid "Lastly, restart networking to have these changes take effect. (This method is deprecated but \"<code>restart networking</code>\" doesn't always work.)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:58(title)
msgid "Configuration requirements with RHEL"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:60(para)
msgid "Ensure auth=no is set in <filename>/etc/qpidd.conf</filename>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:62(para)
msgid "Set selinux in permissive mode:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:64(para)
msgid "Otherwise you will get issues like <link href=\"https://bugzilla.redhat.com/show_bug.cgi?id=734346\">https://bugzilla.redhat.com/show_bug.cgi?id=734346</link> /usr/bin/nova-dhcpbridge: No such file or directory."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:68(para)
msgid "If RHEL 6.2 based, use the openstack-config package to turn off force DHCP releases."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:71(para)
msgid "If RHEL 6.3 based, install dnsmasq utilities."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-config-guest-network.xml:73(para)
msgid "If you intend to use guest images that don't have a single partition, then allow libguestfs to inspect the image so that files can be injected, by setting:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:6(title)
msgid "Installing and Configuring the Proxy Node"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:7(para)
msgid "The proxy server takes each request and looks up locations for the account, container, or object and routes the requests correctly. The proxy server also handles API requests. You enable account management by configuring it in the <filename>proxy-server.conf</filename> file."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:13(para)
msgid "It is assumed that all commands are run as the root user."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:29(para)
msgid "Modify memcached to listen on the default interfaces. Preferably this should be on a local, non-public network. Edit the following line in /etc/memcached.conf, changing:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:45(para)
msgid "RHEL/CentOS/Fedora Only: To set up Object Storage to authenticate tokens we need to set the keystone Admin token in the swift proxy file with the openstack-config command. <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:57(para)
msgid "If you run multiple memcache servers, put the multiple IP:port listings in the [filter:cache] section of the proxy-server.conf file like: <placeholder-1/>Only the proxy server uses memcache."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:65(para)
msgid "Create the account, container and object rings. The builder command is basically creating a builder file with a few parameters. The parameter with the value of 18 represents 2 ^ 18th, the value that the partition will be sized to. Set this “partition power” value based on the total amount of storage you expect your entire ring to use. The value of 3 represents the number of replicas of each object, with the last value being the number of hours to restrict moving a partition more than once."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:84(para)
msgid "For every storage device on each node add entries to each ring:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-proxy-node.xml:92(para)
msgid "For example, if you were setting up a storage node with a partition in Zone 1 on IP 10.0.0.1. The mount point of this partition is /srv/node/sdb1, and the path in rsyncd.conf is /srv/node/, the DEVICE would be sdb1 and the commands would look like: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-verifying-install.xml:6(title)
msgid "Verifying the Compute Installation"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-verifying-install.xml:7(para)
msgid "You can ensure all the Compute services are running by using the <placeholder-1/> command, as root:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-verifying-install.xml:10(para)
msgid "In return you should see \"smiley faces\" rather than three X symbols. Here's an example."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-verifying-install.xml:19(para)
msgid "If you see three X symbols and are running services on separate hosts, ensure that ntp is synchronizing time correctly and that all servers match their time. Out-of-sync time stamps are the most common cause of the XXX state."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-verifying-install.xml:18(para)
msgid "<placeholder-1/>You can find the version of the installation by using the <placeholder-2/> command, as root:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-verifying-install.xml:28(para)
msgid "The version number 2012.2 corresponds with the Folsom release of Compute."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:6(title)
msgid "Configuring the SQL Database (MySQL) on the Cloud Controller"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:8(para)
msgid "Start the mysql command line client by running:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:11(para) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:35(para)
msgid "Enter the mysql root user's password when prompted."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:12(para)
msgid "To configure the MySQL database, create the nova database."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:15(para)
msgid "Create a MySQL user and password for the newly-created nova database that has full control of the database."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:17(replaceable) ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:18(replaceable) ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:16(replaceable) ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:28(replaceable)
msgid "[YOUR_NOVADB_PASSWORD]"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:20(para)
msgid "In the above commands, even though the <literal>'nova'@'%'</literal> also matches <literal>'nova'@'localhost'</literal>, you must explicitly specify the <literal>'nova'@'localhost'</literal> entry."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:23(para)
msgid "By default, MySQL will create entries in the user table with <literal>User=''</literal> and <literal>Host='localhost'</literal>. The <literal>User=''</literal> acts as a wildcard, matching all users. If you do not have the <literal>'nova'@'localhost'</literal> account, and you try to log in as the nova user, the precedence rules of MySQL will match against the <literal>User='' Host='localhost'</literal> account before it matches against the <literal>User='nova' Host='%'</literal> account. This will result in an error message that looks like:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:34(para)
msgid "Thus, we create a separate <literal>User='nova' Host='localhost'</literal> entry that will match with higher precedence."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:36(para) ./doc/src/docbkx/openstack-install/install-config-glance.xml:47(para) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:67(para)
msgid "See the <link href=\"http://dev.mysql.com/doc/refman/5.5/en/connection-access.html\">MySQL documentation on connection verification</link> for more details on how MySQL determines which row in the user table it uses when authenticating connections."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:41(para)
msgid "Enter quit at the mysql&gt; prompt to exit MySQL."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:46(para)
msgid "The command to populate the database is described later in the documentation, in the Section entitled <link linkend=\"compute-db-sync\">Configuring the Database for Compute</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:50(title)
msgid "Securing MySQL"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-mysql.xml:51(para)
msgid "Additional steps are required to configure MySQL for production mode. In particular, anonymous accounts should be removed. On several distributions, these accounts can be removed by running the following script after installing mysql: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-hypervisor-selection.xml:5(title)
msgid "Configuring the Hypervisor"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-hypervisor-selection.xml:6(para)
msgid "For production environments the most tested hypervisors are KVM and Xen-based hypervisors. KVM runs through libvirt, Xen runs best through XenAPI calls. KVM is selected by default and requires the least additional configuration. This guide offers information on both but the specific walkthrough configuration options set up KVM."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:6(title)
msgid "Configuring the SQL Database (PostgreSQL) on the Cloud Controller"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:7(para)
msgid "Optionally, if you choose not to use MySQL, you can install and configure PostgreSQL for all your databases. Here's a walkthrough for the Nova database:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:10(para)
msgid "Start the PostgreSQL command line client by running:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:12(para)
msgid "Enter the postgresql root user's password if prompted."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:13(para)
msgid "To configure the database, create the nova database."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:21(para)
msgid "The database is created and we have a privileged user that controls the database. Now we have to install the packages that will help Nova access the database."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:26(para)
msgid "Configure the <filename>/etc/nova/nova.conf</filename> file, to ensure it knows to use the PostgreSQL database:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-database-postgresql.xml:29(para)
msgid "The command to populate the database is described later in the documentation, in the section entitled <link linkend=\"compute-db-sync\">Configuring the Database for Compute</link>."
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:57(None)
msgid "@@image: 'figures/NOVA_install_arch.png'; md5=0f72da9079e5e0516ac664d2e4a15910"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:70(None)
msgid "@@image: 'figures/NOVA_compute_nodes.png'; md5=bc6a5eb2b9358d000d96f274800752aa"
msgstr ""
#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:6(title)
msgid "Example Compute Installation Architectures"
msgstr ""
#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:7(para)
msgid "OpenStack architecture consists of these major components: Compute, Object Storage, Identity, and Images. A common Identity component provides authentication for users to have access to these components. The Image service stores and serves images to run virtual machines. Compute uses a shared-nothing, messaging-based architecture. While very flexible, the fact that you can install each nova- service on an independent server means there are many possible methods for installing OpenStack Compute. The only co-dependency between possible multi-node installations is that the Dashboard must be installed on a server running the nova-api service. Here are the types of installation architectures for OpenStack Compute with the Image and Identity Services:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:25(para)
msgid "Single node, Compute-only: Only one server runs all nova- services and also drives all the virtual instances. Use this configuration only for trying out OpenStack Compute, or for development purposes."
msgstr ""
#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:30(para)
msgid "Two nodes, Compute-only: A cloud controller node runs the nova- services except for nova-compute, and a compute node runs nova-compute. A client computer is likely needed to bundle images and interfacing to the servers, but a client is not required. Use this configuration for proof of concepts or development environments."
msgstr ""
#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:38(para)
msgid "Multiple nodes, Compute-only: You can add more compute nodes to the two node installation by simply installing nova-compute on an additional server and copying a nova.conf file to the added node. This would result in a multiple node installation. You can also add a volume controller and a network controller as additional nodes in a more complex multiple node installation. A minimum of 4 nodes is best for running multiple virtual instances that require a lot of processing power."
msgstr ""
#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:52(para)
msgid "This is an illustration of one possible multiple server installation of OpenStack Compute; virtual server networking in the cluster may vary."
msgstr ""
#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:60(para)
msgid "An alternative architecture would be to add more messaging servers if you notice a lot of back up in the messaging queue causing performance problems. In that case you would add an additional RabbitMQ server in addition to or instead of scaling up the database server. Your installation can run any nova- service on any server as long as the nova.conf is configured to point to the RabbitMQ server and the server can send messages to the server."
msgstr ""
#: ./doc/src/docbkx/openstack-install/example-compute-install-arch.xml:66(para)
msgid "Multiple installation architectures are possible, here is another example illustration."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-configure-volumes.xml:5(title)
msgid "Installing and Configuring Volumes for Compute"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-configure-volumes.xml:6(para)
msgid "For additional information about managing volumes including troubleshooting, refer to the OpenStack Compute Administration Guide."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:6(title)
msgid "Installing OpenStack Walk-through"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:7(para)
msgid "The OpenStack Compute and Image services work together to provide access to virtual servers and images through REST APIs. The Identity Service provides a common authorization layer for all OpenStack services. You must use the Identity Service to install the OpenStack Dashboard, which offers a web-based user interface for OpenStack components. The OpenStack Object Storage service provides not only a storage method for virtual images but also a cloud-based object storage system with a REST API to store and retrieve objects such as images or videos. This walk-through starts with Identity, then goes through Image and Compute and also provides deployment information about an Object Storage installation."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:20(para)
msgid "Here are the overall steps:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:22(para)
msgid "Review the most supported platforms. Red Hat Enterprise Linux, Scientific Linux, CentOS, Fedora, Debian, and Ubuntu are the most tested platforms currently."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:26(para)
msgid "Install the Identity Service (Keystone)."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:29(para)
msgid "Configure the Identity Service."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:32(para)
msgid "Install the Image Service (Glance)."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:35(para)
msgid "Configure the Image Service."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:38(para)
msgid "Install Compute (Nova)."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:41(para)
msgid "Review the assumptions made in this installation for Compute."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:45(para)
msgid "Configure Compute with FlatDHCP networking using <literal>192.168.100.0/24</literal> as the fixed range for our guest VMs on a bridge named <literal>br100</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:50(para)
msgid "Create and initialize the Compute database with MySQL. PostgreSQL is also documented but all examples follow MySQL as an assumed default."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:55(para)
msgid "Add images."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:58(para)
msgid "(optional) Install OpenStack Object Storage (Swift)."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:62(para)
msgid "Install the OpenStack Dashboard."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:65(para)
msgid "Launch the Dashboard."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:68(para)
msgid "Add a keypair through the Dashboard."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installing-openstack-overview.xml:71(para)
msgid "Launch an image through the Dashboard to verify the entire installation."
msgstr ""
#: ./doc/src/docbkx/openstack-install/determining-version-of-compute.xml:6(title)
msgid "Determining the Version of Compute"
msgstr ""
#: ./doc/src/docbkx/openstack-install/determining-version-of-compute.xml:7(para)
msgid "You can find the version of the installation by using the nova-manage command:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:9(title)
msgid "Installing and Configuring the Image Service"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:11(para)
msgid "Install the Image service, as root:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:14(para)
msgid "10/10/12: When using the Ubuntu Cloud Archive, you need to re-install the <literal>python-keystoneclient</literal> after installing the glance packages listed above, otherwise you see an error."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:18(para)
msgid "If you are using Ubuntu, delete the <filename>glance.sqlite</filename> file created in the <filename>/var/lib/glance/</filename> directory:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:22(title)
msgid "Configuring the Image Service database backend"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:23(para)
msgid "Configure the backend data store. For MySQL, create a glance MySQL database and a glance MySQL user. Grant the \"glance\" user full access to the glance MySQL database."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:24(para)
msgid "Start the MySQL command line client by running:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:25(para)
msgid "Enter the MySQL root user's password when prompted."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:26(para)
msgid "To configure the MySQL database, create the glance database."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:27(para)
msgid "Create a MySQL user for the newly-created glance database that has full control of the database."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:28(replaceable) ./doc/src/docbkx/openstack-install/install-config-glance.xml:29(replaceable) ./doc/src/docbkx/openstack-install/install-config-glance.xml:135(replaceable) ./doc/src/docbkx/openstack-install/install-config-glance.xml:170(replaceable)
msgid "[YOUR_GLANCEDB_PASSWORD]"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:31(para)
msgid "In the above commands, even though the <literal>'glance'@'%'</literal> also matches <literal>'glance'@'localhost'</literal>, you must explicitly specify the <literal>'glance'@'localhost'</literal> entry."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:34(para)
msgid "By default, MySQL will create entries in the user table with <literal>User=''</literal> and <literal>Host='localhost'</literal>. The <literal>User=''</literal> acts as a wildcard, matching all users. If you do not have the <literal>'glance'@'localhost'</literal> account, and you try to log in as the glance user, the precedence rules of MySQL will match against the <literal>User='' Host='localhost'</literal> account before it matches against the <literal>User='glance' Host='%'</literal> account. This will result in an error message that looks like:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:45(para)
msgid "Thus, we create a separate <literal>User='glance' Host='localhost'</literal> entry that will match with higher precedence."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:52(para)
msgid "Enter <literal>quit </literal>at the <literal>mysql&gt;</literal> prompt to exit MySQL."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:59(title)
msgid "Edit the Glance configuration files and paste ini middleware files"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:61(para)
msgid "The Image service has a number of options that you can use to configure the Glance API server, optionally the Glance Registry server, and the various storage backends that Glance can use to store images. By default, the storage backend is in file, specified in the <filename>glance-api.conf</filename> config file in the section <literal>[DEFAULT]</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:68(para)
msgid "The <literal>glance-api</literal> service implements versions 1 and 2 of the OpenStack Images API. By default, both are enabled by setting these configuration options to <literal>True</literal> in the <filename>glance-api.conf</filename> file."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:76(para)
msgid "Disable either version of the Images API by setting the option to False in the <filename>glance-api.conf</filename> file."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:80(para)
msgid "In order to use the v2 API, you must copy the necessary SQL configuration from your <literal>glance-registry</literal> service to your <literal>glance-api</literal> configuration file. The following instructions assume that you want to use the v2 Image API for your installation. The v1 API is implemented on top of the glance-registry service while the v2 API is not."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:88(para)
msgid "Most configuration is done via configuration files, with the Glance API server (and possibly the Glance Registry server) using separate configuration files. When installing through an operating system package management system, sample configuration files are installed in <literal>/etc/glance</literal>. You configure the PasteDeploy configuration, which controls the deployment of the WSGI application for each component, in files named <replaceable>component</replaceable>-paste.ini, such as <filename>glance-api-paste.ini</filename>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:98(para)
msgid "This walkthrough installs the image service using a file backend and the Identity service (Keystone) for authentication."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:101(para)
msgid "Update <filename>/etc/glance/glance-api-paste.ini</filename> and configure the <literal>admin_<replaceable>*</replaceable></literal> values under <literal>[filter:authtoken]</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:110(para)
msgid "Add the admin and service identifiers and <literal>flavor=keystone</literal> to the end of <filename>/etc/glance/glance-api.conf</filename> as shown below."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:132(para)
msgid "Ensure that <filename>/etc/glance/glance-api.conf</filename> points to the MySQL database rather than sqlite.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:136(para)
msgid "Restart glance-api to pick up these changed settings."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:139(para)
msgid "Update the last sections of <filename>/etc/glance/glance-registry.conf</filename> to reflect the values you set earlier for admin user and the service tenant, plus enable the Identity service with <literal>flavor=keystone</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:161(para)
msgid "Update <filename>/etc/glance/glance-registry-paste.ini</filename> by enabling the Identity service, keystone:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:167(para)
msgid "Ensure that <filename>/etc/glance/glance-registry.conf</filename> points to the MySQL database rather than sqlite.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:171(para)
msgid "Restart glance-registry to pick up these changed settings."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:175(para)
msgid "Any time you change the .conf files, restart the corresponding service."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:178(para)
msgid "On Ubuntu 12.04, the database tables are under version control and you must do these steps on a new install to prevent the Image service from breaking possible upgrades, as root: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:183(para)
msgid "Now you can populate or migrate the database. <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:185(para)
msgid "Restart glance-registry and glance-api services, as root:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-glance.xml:190(para)
msgid "This guide does not configure image caching, refer to <link href=\"http://glance.openstack.org\">http://docs.openstack.org/developer/glance/</link> for more information."
msgstr ""
#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:6(title)
msgid "Verifying the Image Service Installation"
msgstr ""
#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:7(para)
msgid "To validate the Image service client is installed, enter <placeholder-1/> at the command line."
msgstr ""
#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:10(para)
msgid "Obtain a test image."
msgstr ""
#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:15(para)
msgid "Upload the kernel."
msgstr ""
#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:16(para)
msgid "This example shows inputting --os-username, --os-password, --os-tenant-name, --os-auth-url on the command line for reference. You could also use the OS_* environment variables by setting them in an openrc file:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:21(para)
msgid "Then you would source these environment variables by running <placeholder-1/>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:48(para)
msgid "Upload the initrd."
msgstr ""
#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:75(para)
msgid "Upload the image."
msgstr ""
#: ./doc/src/docbkx/openstack-install/images-verifying-install.xml:108(para)
msgid "Now a glance image-list should show three images."
msgstr ""
#: ./doc/src/docbkx/openstack-install/vnc-console.xml:7(para)
msgid "To validate the Dashboard installation, point your browser at http://192.168.206.130. Note that you cannot use VNC Console from a Chrome browser. You need both Flash installed and a Firefox browser. Once you connect to the Dashboard with the URL, you should see a login window. Enter the credentials for users you created with the Identity Service, Keystone. For example, enter \"admin\" for the username and \"secrete\" as the password."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:10(title)
msgid "OpenStack Install and Deploy Manual - <phrase os=\"rhel;centos;fedora\">Red Hat</phrase><phrase os=\"ubuntu\">Ubuntu</phrase>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:20(orgname) ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:30(productname)
msgid "OpenStack"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:24(year)
msgid "2012"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:25(year)
msgid "2013"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:26(holder)
msgid "OpenStack Foundation"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:28(releaseinfo)
msgid "Grizzly, Compute 2013.1, Network 2013.1, Object Storage 1.7.6"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:31(pubdate) ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:57(date)
msgid "2013-02-12"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:34(remark)
msgid "Copyright details are filled in by the template."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:38(para)
msgid "The OpenStack™ system has several key projects that are separate installations but can work together depending on your cloud needs: OpenStack Compute, OpenStack Object Storage, OpenStack Identity Service, and OpenStack Image Service. You can install any of these projects separately and then configure them either as standalone or connected entities. <phrase os=\"ubuntu\">This guide walks through an installation using packages available through Ubuntu 12.04.</phrase><phrase os=\"rhel;centos;fedora\">This guide walks through an installation using packages available through Fedora 17 as well as on RHEL and derivatives through the EPEL repository.</phrase> It offers explanations for the configuration choices as well as sample configuration files."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:61(para)
msgid "Adds chapter about Essex to Folsom upgrade for Compute and related services (excludes OpenStack Object Storage (Swift) and OpenStack Networking (Neutron)."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:71(date)
msgid "2013-01-16"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:75(para)
msgid "Fix file copy issue for figures in the /common/ directory."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:81(date)
msgid "2012-11-09"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:85(para)
msgid "Folsom release of this document."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:91(date)
msgid "2012-10-10"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:95(para)
msgid "Doc bug fixes: <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1054459\">1054459</link><link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1064745\">1064745</link>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:105(date)
msgid "2012-09-26"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:109(para)
msgid "Adds an all-in-one install section."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:115(date)
msgid "2012-07-23"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:119(para)
msgid "Adds additional detail about installing and configuring nova-volumes."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:124(para)
msgid "Doc bug fixes: <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/978510\">978510</link><link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1027230\">1027230</link>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:135(date)
msgid "2012-07-17"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:139(para)
msgid "Update build process so two uniquely-named PDF files are output."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:145(date)
msgid "2012-07-13"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:149(para)
msgid "Doc bug fixes: <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1025840\">1025840</link><link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1025847\">1025847</link>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:162(date)
msgid "2012-06-19"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:166(para)
msgid "Fix PDF links."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:169(para)
msgid "Doc bug fixes: <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/967778\">967778</link><link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/984959\">984959</link>, <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1002294\">1002294</link>, <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1010163\">1010163</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:187(date)
msgid "2012-05-31"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:191(para)
msgid "Revise install guide to encompass more Linux distros."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:195(para)
msgid "Doc bug fixes: <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/996988\">996988</link>, <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/998116\">998116</link>, <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/999005\">999005</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:207(date)
msgid "2012-05-03"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:211(para)
msgid "Fixes problems with <filename>glance-api-paste.ini</filename> and <filename>glance-registry-paste.ini</filename> samples and instructions."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:218(para)
msgid "Removes \"DRAFT\" designation."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:224(date)
msgid "2012-05-02"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:228(para)
msgid "Essex release."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:234(date)
msgid "2012-05-01"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:238(para)
msgid "Updates the Object Storage and Identity (Keystone) configuration."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:244(date)
msgid "2012-04-25"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:248(para)
msgid "Changes service_id copy/paste error for the EC2 service-create command."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:249(para)
msgid "Adds verification steps for Object Storage installation."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:250(para)
msgid "Fixes <filename>proxy-server.conf</filename> file so it points to keystone not tempauth."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:256(date)
msgid "2012-04-23"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:260(para)
msgid "Adds installation and configuration for mulit-node Object Storage service."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:266(date)
msgid "2012-04-17"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:270(para)
msgid "Doc bug fixes: <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/983417\">983417</link>, <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/984106\">984106</link>, <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/984034\">984034</link>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:282(date)
msgid "2012-04-13"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:286(para)
msgid "Doc bug fixes: <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/977905\">977905</link>, <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/980882\">980882</link>, <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/977823\">977823</link>, adds additional Glance database preparation steps"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:300(date)
msgid "2012-04-10"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:304(para)
msgid "Doc bug fixes: <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/977831\">977831</link>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:310(date)
msgid "2012-03-23"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:314(para)
msgid "Updates for Xen hypervisor."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:320(date)
msgid "2012-03-09"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:324(para)
msgid "Updates for Essex release, includes new Glance config files, new Keystone configuration."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:332(date)
msgid "2012-01-24"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:336(para)
msgid "Initial draft for Essex."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:338(para)
msgid "Assumes use of Ubuntu 12.04 repository."
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:345(date)
msgid "2011-01-24"
msgstr ""
#: ./doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml:349(para)
msgid "Initial draft for Diablo."
msgstr ""
#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:6(title)
msgid "Configuring Multiple Compute Nodes"
msgstr ""
#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:7(para)
msgid "If your goal is to split your VM load across more than one server, you can connect an additional nova-compute node to a cloud controller node. This configuring can be reproduced on multiple compute servers to start building a true multi-node OpenStack Compute cluster."
msgstr ""
#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:12(para)
msgid "To build out and scale the Compute platform, you spread out services amongst many servers. While there are additional ways to accomplish the build-out, this section describes adding compute nodes, and the service we are scaling out is called 'nova-compute.'"
msgstr ""
#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:17(para)
msgid "For a multi-node install you only make changes to <filename>nova.conf</filename> and copy it to additional compute nodes. Ensure each <filename>nova.conf</filename> file points to the correct IP addresses for the respective services. Customize the <filename>nova.conf</filename> example below to match your environment. The <literal>CC_ADDR</literal> is the Cloud Controller IP Address."
msgstr ""
#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:40(para)
msgid "By default, Nova sets the bridge device based on the setting in <literal>--flat_network_bridge</literal>. Now you can edit <filename>/etc/network/interfaces</filename> with the following template, updated with your IP information."
msgstr ""
#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:65(para)
msgid "Restart networking:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:67(para)
msgid "With <filename>nova.conf</filename> updated and networking set, configuration is nearly complete. First, bounce the relevant services to take the latest updates:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:71(para)
msgid "To avoid issues with KVM and permissions with Nova, run the following commands to ensure we have VM's that are running optimally:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:78(para)
msgid "If you want to use the 12.04 Ubuntu Enterprise Cloud images that are readily available at http://uec-images.ubuntu.com/releases/12.04/release/, you may run into delays with booting. Any server that does not have nova-api running on it needs this iptables entry so that UEC images can get metadata info. On compute nodes, configure the iptables with this next step:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:86(para)
msgid "Lastly, confirm that your compute node is talking to your cloud controller. From the cloud controller, run this database query:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:90(para)
msgid "In return, you should see something similar to this:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/configuring-multiple-compute-nodes.xml:104(para)
msgid "You can see that <literal>osdemo0{1,2,4,5}</literal> are all running <literal>nova-compute</literal>. When you start spinning up instances, they will allocate on any node that is running <literal>nova-compute</literal> from this list."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:6(title)
msgid "Defining Roles and Users in the Identity Service (Keystone)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:7(para)
msgid "Before you begin, ensure that the OpenStack Compute and Image services are installed and connect all databases prior to configuring the Identity Service endpoints."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:10(para)
msgid "Create tenants first. Here is an example set."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:15(para)
msgid "Next, create users."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:22(para)
msgid "Here are some roles to create."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:28(para)
msgid "Add Roles to Users in Tenants"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:36(para)
msgid "Also, the Member role is used by Horizon and Swift so we need to continue creating it:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:42(title)
msgid "Define Services and Endpoints"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:43(para)
msgid "Now that all your starter tenants, users, and roles have been created, let's move on to endpoints."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:45(para)
msgid "First add all the services you want to have the Identity service connected with. Here's an example using all the available services in this example."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-config-keystone.xml:78(para)
msgid "The Identity Service, Keystone, is now configured and ready to accept requests."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:7(title)
msgid "Verify the Installation"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:8(para)
msgid "You can run these commands from the proxy server or any server with access to the Identity Service."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:11(para)
msgid "First, export the swift admin password (setup previously) in a variable so it can be re-used."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:15(para)
msgid "If you do not wish to have the swift admin password stored in your shell's history, you may perform the following:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:22(para)
msgid "Run the swift CLI, swift, with the correct Identity service URL. Export the information for ADMINPASS using <code>$ export ADMINPASS=secrete</code>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:43(para)
msgid "Use swift to upload a few files named ‘bigfile[1-2].tgz’ to a container named ‘myfiles’:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:53(para)
msgid "Use swift to download all files from the ‘myfiles’ container:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-verifying-install.xml:62(para)
msgid "If you are using swauth in preference to the OpenStack Identity service, you should use the <literal>default_swift_cluster</literal> variable to connect to your swift cluster. Please follow the <link href=\"http://gholt.github.com/swauth/stable/\">swauth documentation</link> to verify your installation."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:6(title)
msgid "Installing and Configuring the Identity Service"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:7(para)
msgid "Install the Identity service on any server that is accessible to the other servers you intend to use for OpenStack services, as root:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:12(para)
msgid "After installing, you need to delete the sqlite database it creates, then change the configuration to point to a MySQL database. This configuration enables easier scaling scenarios since you can bring up multiple Keystone front ends when needed, and configure them all to point back to the same database. Plus a database backend has built-in data replication features and documentation surrounding high availability and data redundancy configurations."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:20(para)
msgid "Delete the <filename>keystone.db</filename> file created in the <filename>/var/lib/keystone</filename> directory.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:23(para)
msgid "Configure the production-ready backend data store rather than using the catalog supplied by default for the ability to backup the service and endpoint data. This example shows MySQL."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:26(para)
msgid "The following sequence of commands will create a MySQL database named \"keystone\" and a MySQL user named \"keystone\" with full access to the \"keystone\" MySQL database."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:29(para)
msgid "On Fedora, RHEL, and CentOS, you can configure the Keystone database with the <placeholder-1/> command.<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:32(para)
msgid "To manually create the database, start the <placeholder-1/> command line client by running:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:36(para)
msgid "To configure the MySQL database, create the keystone database."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:39(para)
msgid "Create a MySQL user for the newly-created keystone database that has full control of the keystone database."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:43(para)
msgid "Choose a secure password for the keystone user and replace all references to <replaceable>[YOUR_KEYSTONEDB_PASSWORD]</replaceable> with this password."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:48(replaceable) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:49(replaceable) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:87(replaceable)
msgid "[YOUR_KEYSTONEDB_PASSWORD]"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:52(para)
msgid "In the above commands, even though the <literal>'keystone'@'%'</literal> also matches <literal>'keystone'@'localhost'</literal>, you must explicitly specify the <literal>'keystone'@'localhost'</literal> entry."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:55(para)
msgid "By default, MySQL will create entries in the user table with <literal>User=''</literal> and <literal>Host='localhost'</literal>. The <literal>User=''</literal> acts as a wildcard, matching all users. If you do not have the <literal>'keystone'@'localhost'</literal> account, and you try to log in as the keystone user, the precedence rules of MySQL will match against the <literal>User='' Host='localhost</literal> account before it matches against the <literal>User='keystone' Host='%'</literal> account. This will result in an error message that looks like:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:65(para)
msgid "Thus, we create a separate <literal>User='keystone' Host='localhost'</literal> entry that will match with higher precedence."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:72(para)
msgid "Enter quit at the <literal>mysql&gt;</literal> prompt to exit MySQL."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:77(para)
msgid "Recall that this document assumes the Cloud Controller node has an IP address of <literal>192.168.206.130</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:80(para)
msgid "Once Keystone is installed, it is configured via a primary configuration file (<filename>/etc/keystone/keystone.conf</filename>), and by initializing data into keystone using the command line client. By default, Keystone's data store is sqlite. To change the data store to mysql, change the line defining <literal>connection</literal> in <filename>/etc/keystone/keystone.conf</filename> like so:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:88(para)
msgid "Also, ensure that the proper service token is used in the <filename>keystone.conf</filename> file. An example is provided in the Appendix or you can generate a random string. The sample token is:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:93(para)
msgid "Next, restart the keystone service so that it picks up the new database configuration."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:97(para)
msgid "Lastly, initialize the new keystone database, as root:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:100(title)
msgid "Configuring Services to work with Keystone"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:101(para)
msgid "Once Keystone is installed and running, you set up users and tenants and services to be configured to work with it. You can either follow the <link linkend=\"setting-up-tenants-users-and-roles-manually\">manual steps</link> or <link linkend=\"scripted-keystone-setup\">use a script</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:108(para)
msgid "The parameters <literal>--token</literal> and <literal>--endpoint</literal> are valid for the keystoneclient available after October 2012. Use <literal>--token</literal> and <literal>--endpoint</literal> with the keystoneclient released with the Folsom packaging. This install guide documents installing the client from packages, but you can use the client from another computer with the <link href=\"http://docs.openstack.org/cli/quick-start/content/install_openstack_keystone_cli.html\">CLI Guide instructions for <placeholder-1/></link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:120(title)
msgid "Setting up tenants, users, and roles - manually"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:121(para)
msgid "You need to minimally define a tenant, user, and role to link the tenant and user as the most basic set of details to get other services authenticating and authorizing with the Identity service."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:126(title)
msgid "Scripted method available"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:127(para)
msgid "These are the manual, unscripted steps using the keystone client. A scripted method is available at <link linkend=\"scripted-keystone-setup\">Setting up tenants, users, and roles - scripted</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:132(para)
msgid "First, create a default tenant, we'll name it <literal>demo</literal> in this example."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:143(para)
msgid "Create a default user named <literal>admin</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:154(para)
msgid "Create an administrative role based on keystone's default <literal>policy.json</literal> file, <literal>admin</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:164(para)
msgid "Grant the <literal>admin</literal> role to the <literal>admin</literal> user in the <literal>demo</literal> tenant with \"user-role-add\"."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:169(para) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:198(para) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:214(para) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:230(para) ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:247(para)
msgid "There is no output to this command."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:170(para)
msgid "Create a Service Tenant. This tenant contains all the services that we make known to the service catalog."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:181(para)
msgid "Create a Glance Service User in the Service Tenant. You'll do this for any service you add to be in the Keystone service catalog."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:194(para)
msgid "Grant the <literal>admin</literal> role to the <literal>glance</literal> user in the <literal>service</literal> tenant."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:199(para)
msgid "Create a Nova Service User in the Service Tenant."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:210(para)
msgid "Grant the <literal>admin</literal> role to the <literal>nova</literal> user in the <literal>service</literal> tenant."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:215(para)
msgid "Create an EC2 Service User in the Service Tenant."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:226(para)
msgid "Grant the <literal>admin</literal> role to the <literal>ec2</literal> user in the <literal>service</literal> tenant."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:231(para)
msgid "Create an Object Storage Service User in the Service Tenant."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:243(para)
msgid "Grant the <literal>admin</literal> role to the <literal>swift</literal> user in the <literal>service</literal> tenant."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:248(para)
msgid "Next you create definitions for the services."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:253(title) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:7(title)
msgid "Defining Services"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:254(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:8(para)
msgid "Keystone also acts as a service catalog to let other OpenStack systems know where relevant API endpoints exist for OpenStack Services. The OpenStack Dashboard, in particular, uses the service catalog heavily - and this <emphasis role=\"strong\"> must</emphasis> be configured for the OpenStack Dashboard to properly function."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:263(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:17(para)
msgid "Using a template file"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:266(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:20(para)
msgid "Using a database backend"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:260(para)
msgid "There are two alternative ways of defining services with keystone: <placeholder-1/> While using a template file is simpler, it is not recommended except for development environments such as <link href=\"http://www.devstack.org\">DevStack</link>. The template file does not enable CRUD operations on the service catalog through keystone commands, but you can use the service-list command when using the template catalog. A database backend can provide better reliability, availability, and data redundancy. This section describes how to populate the Keystone service catalog using the database backend. Your <filename>/etc/keystone/keystone.conf</filename> file should contain the following lines if it is properly configured to use the database backend."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:285(title) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:45(title)
msgid "Elements of a Keystone service catalog entry"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:293(literal) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:55(literal)
msgid "--name"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:295(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:56(para)
msgid "Name of the service (e.g., <literal>nova</literal>, <literal>ec2</literal>, <literal>glance</literal>, <literal>keystone</literal>)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:303(literal) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:59(literal)
msgid "--type"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:305(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:60(para)
msgid "Type of service (e.g., <literal>compute</literal>, <literal>ec2</literal>, <literal>image</literal>, <literal>identity</literal>)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:313(literal) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:63(literal)
msgid "--description"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:315(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:64(para)
msgid "A description of the service, (e.g., <literal>\"Nova Compute Service\"</literal>)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:289(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:50(para)
msgid "Use the <placeholder-1/> command to create a database entry for the service, with the following attributes: <placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:324(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:70(para)
msgid "Use the <placeholder-1/> command to create a database entry that describes how different types of clients can connect to the service, with the following attributes:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:330(literal) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:75(literal)
msgid "--region"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:332(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:76(para)
msgid "the region name you've given to the OpenStack cloud you are deploying (e.g., RegionOne)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:337(literal)
msgid "--service-id"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:339(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:81(para)
msgid "The ID field returned by the <placeholder-1/> (e.g., <literal>935fd37b6fa74b2f9fba6d907fa95825</literal>)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:345(literal) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:85(literal)
msgid "--publicurl"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:347(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:86(para)
msgid "The URL of the public-facing endpoint for the service (e.g., <literal>http://192.168.206.130:9292</literal> or <literal>http://192.168.206.130:8774/v2/%(tenant_id)s</literal>)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:356(literal) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:89(literal)
msgid "--internalurl"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:358(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:90(para)
msgid "The URL of an internal-facing endpoint for the service."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:360(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:91(para)
msgid "This typically has the same value as <literal>publicurl</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:365(literal) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:94(literal)
msgid "--adminurl"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:367(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:95(para)
msgid "The URL for the admin endpoint for the service. The Keystone and EC2 services use different endpoints for <literal>adminurl</literal> and <literal>publicurl</literal>, but for other services these endpoints will be the same."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:286(para) ./doc/src/docbkx/openstack-install/identity-defining-services.xml:46(para)
msgid "For each service in the catalog, you must perform two keystone operations: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:379(para)
msgid "Keystone allows some URLs to contain special variables, which are automatically substituted with the correct value at runtime. Some examples in this document employ the <literal>tenant_id</literal> variable, which we use when specifying the Volume and Compute service endpoints. Variables can be specified using either <literal>%(<replaceable>varname</replaceable>)s</literal> or <literal>$(<replaceable>varname</replaceable>)s</literal> notation. In this document, we always use the <literal>%(<replaceable>varname</replaceable>)s</literal> notation (e.g., <literal>%(tenant_id)s</literal>) since <literal>$</literal> is interpreted as a special character by Unix shells."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:394(title)
msgid "Creating keystone services and service endpoints"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:395(para)
msgid "Here we define the services and their endpoints."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:396(para)
msgid "Define the Identity service:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:436(para)
msgid "The <literal>%(tenant_id)s</literal> and single quotes around the <literal>publicurl</literal>, <literal>internalurl</literal>, and <literal>adminurl</literal> must be typed exactly as shown for both the Compute endpoint and the Volume endpoint."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:433(para)
msgid "Define the Compute service, which requires a separate endpoint for each tenant. Here we use the <literal>service</literal> tenant from the previous section. <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:479(para)
msgid "Define the Volume service, which also requires a separate endpoint for each tenant."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:521(para)
msgid "Define the Image service:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:562(para)
msgid "Define the EC2 compatibility service:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:601(para)
msgid "Define the Object Storage service:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:642(title)
msgid "Setting up Tenants, Users, Roles, and Services - Scripted"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-install-keystone.xml:644(para)
msgid "The Keystone project offers a bash script for populating tenants, users, roles and services at <link href=\"https://github.com/openstack/keystone/blob/master/tools/sample_data.sh\">https://github.com/openstack/keystone/blob/master/tools/sample_data.sh</link> with sample data. This script uses 127.0.0.1 for all endpoint IP addresses. This script also defines services for you."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:7(title)
msgid "System Requirements"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:7(para)
msgid "<emphasis role=\"bold\">Hardware</emphasis>: OpenStack Object Storage specifically is designed to run on commodity hardware."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:22(para)
msgid "Object Storage object servers"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:24(para) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:49(para) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:56(para)
msgid "Processor: dual quad core"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:24(para) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:50(para)
msgid "Memory: 8 or 12 GB RAM"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:25(para)
msgid "Disk space: optimized for cost per GB"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:27(para) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:51(para) ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:56(para)
msgid "Network: one 1 GB Network Interface Card (NIC)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:29(para)
msgid "The amount of disk space depends on how much you can fit into the rack efficiently. You want to optimize these for best cost per GB while still getting industry-standard failure rates. At Rackspace, our storage servers are currently running fairly generic 4U servers with 24 2T SATA drives and 8 cores of processing power. RAID on the storage drives is not required and not recommended. Swift's disk usage pattern is the worst case possible for RAID, and performance degrades very quickly using RAID 5 or 6."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:41(para)
msgid "As an example, Rackspace runs Cloud Files storage servers with 24 2T SATA drives and 8 cores of processing power. Most services support either a worker or concurrency value in the settings. This allows the services to make effective use of the cores available."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:48(para)
msgid "Object Storage container/account servers"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:53(para)
msgid "Optimized for IOPS due to tracking with SQLite databases."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:54(para)
msgid "Object Storage proxy server"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:57(para)
msgid "Higher network throughput offers better performance for supporting many API requests."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:59(para)
msgid "Optimize your proxy servers for best CPU performance. The Proxy Services are more CPU and network I/O intensive. If you are using 10g networking to the proxy, or are terminating SSL traffic at the proxy, greater CPU power will be required."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:65(para)
msgid "<emphasis role=\"bold\">Operating System</emphasis>: OpenStack Object Storage currently runs on Ubuntu, RHEL, CentOS, or Fedora and the large scale deployment at Rackspace runs on Ubuntu 10.04 LTS."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:69(para)
msgid "<emphasis role=\"bold\">Networking</emphasis>: 1000 Mbps are suggested. For OpenStack Object Storage, an external network should connect the outside world to the proxy servers, and the storage network is intended to be isolated on a private network or multiple private networks."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:73(para)
msgid "<emphasis role=\"bold\">Database</emphasis>: For OpenStack Object Storage, a SQLite database is part of the OpenStack Object Storage container and account management process."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-sys-requirements.xml:76(para)
msgid "<emphasis role=\"bold\">Permissions</emphasis>: You can install OpenStack Object Storage either as root or as a user with sudo permissions if you configure the sudoers file to enable all the permissions."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:6(title)
msgid "OpenStack Object Storage Post Installation"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:7(para)
msgid "Now that the proxy server and storage servers are configured, you want to restart the services."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:12(title)
msgid "Adding an Additional Proxy Server"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:13(para)
msgid "For reliability’s sake you may want to have more than one proxy server. You can set up the additional proxy node in the same manner that you set up the first proxy node but with additional configuration steps."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:19(para)
msgid "Once you have more than two proxies, you also want to load balance between the two, which means your storage endpoint (what clients use to connect to your storage) also changes. You can select from different strategies for load balancing. For example, you could use round robin dns, or a software or hardware load balancer (like pound) in front of the two proxies, and point your storage url to the load balancer."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:29(para)
msgid "Configure an initial proxy node for the initial setup, and then follow these additional steps for more proxy servers."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:34(para)
msgid "Update the list of memcache servers in <filename>/etc/swift/proxy-server.conf</filename> for all the added proxy servers. If you run multiple memcache servers, use this pattern for the multiple IP:port listings: <placeholder-1/> in each proxy server’s conf file.:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:60(para)
msgid "After you sync all the nodes, make sure the admin has the keys in <filename>/etc/swift</filename> and the ownership for the ring file is correct."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-post-install.xml:68(para)
msgid "If you are using swauth in preference to the OpenStack Identity service, there are additional steps to follow for the addition of a second proxy server. Please follow the <link href=\"http://gholt.github.com/swauth/stable/\">swauth documentation</link> Installation section, paying close attention to the <literal>default_swift_cluster</literal> variable."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installdashboard.xml:7(title) ./doc/src/docbkx/openstack-install/dashboard-install.xml:3(title)
msgid "Installing the OpenStack Dashboard"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installdashboard.xml:8(para)
msgid "OpenStack has components that provide a view of the OpenStack installation such as a Django-built website that serves as a dashboard."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installdashboard.xml:12(title) ./doc/src/docbkx/openstack-install/about-dashboard.xml:8(title)
msgid "About the Dashboard"
msgstr ""
#. <?dbhtml stop-chunking?>
#: ./doc/src/docbkx/openstack-install/ch_installdashboard.xml:13(para) ./doc/src/docbkx/openstack-install/about-dashboard.xml:10(para)
msgid "You can use a dashboard interface with an OpenStack Compute installation with a web-based console provided by the Openstack-Dashboard project. It provides web-based interactions with the OpenStack Compute cloud controller through the OpenStack APIs. For more information about the Openstack-Dashboard project, please visit: <link href=\"https://github.com/openstack/horizon/\">https://github.com/openstack/horizon/</link>. These instructions are for an example deployment configured with an Apache web server."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:4(para)
msgid "Here are the overall steps for creating the OpenStack dashboard."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:7(para)
msgid "Install the OpenStack Dashboard framework including Apache and related modules."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:11(para)
msgid "Configure the Dashboard."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:14(para)
msgid "Restart and run the Apache server."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:17(para)
msgid "Install the OpenStack Dashboard, as root:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:20(para)
msgid "Next, modify the variable <literal>CACHE_BACKEND</literal> in <filename>/etc/openstack-dashboard/local_settings.py</filename> to match the ones set in <filename os=\"ubuntu\">/etc/memcached.conf</filename><filename os=\"centos;fedora;rhel\">/etc/sysconfig/memcached.conf</filename>. Open <filename>/etc/openstack-dashboard/local_settings.py</filename> and look for this line:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:26(para)
msgid "The address and port in the new value need to be equal to the ones set in <filename os=\"ubuntu\">/etc/memcached.conf</filename><filename os=\"centos;fedora;rhel\">/etc/sysconfig/memcached.conf</filename>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:28(para)
msgid "If you change the memcached settings, restart the Apache web server for the changes to take effect."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:30(para)
msgid "This guide has selected memcache as a session store for OpenStack Dashboard. There are other options available, each with benefits and drawbacks. Refer to the OpenStack Dashboard Session Storage section for more information."
msgstr ""
#: ./doc/src/docbkx/openstack-install/dashboard-install.xml:35(para)
msgid "In order to change the timezone you can use either dashboard or inside <filename>/etc/openstack-dashboard/local_settings.py</filename> you can change below mentioned parameter.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-network-planning.xml:5(title)
msgid "Compute Network Planning"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-network-planning.xml:6(para)
msgid "For both conserving network resources and ensuring that network administrators understand the needs for networks and public IP addresses for accessing the APIs and VMs as necessary, this section offers recommendations and required minimum sizes. Throughput of at least 1000 Mbps is suggested. This walkthrough shows network configurations for a single server."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-network-planning.xml:13(para)
msgid "For OpenStack Compute, networking is configured on multi-node installations between the physical machines on a single subnet. For networking between virtual machine instances, three network options are available: flat, DHCP, and VLAN. Two NICs (Network Interface Cards) are recommended on the server running nova-network."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-network-planning.xml:19(para)
msgid "Management Network (RFC1918 IP Range, not publicly routable): This network is utilized for all inter-server communications within the cloud infrastructure. Recommended size: 255 IPs (CIDR /24)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-network-planning.xml:23(para)
msgid "Public Network (Publicly routable IP range): This network is utilized for providing Public IP accessibility to the API endpoints within the cloud infrastructure. Minimum size: 8 IPs (CIDR /29)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-network-planning.xml:27(para)
msgid "VM Network (RFC1918 IP Range, not publicly routable): This network is utilized for providing primary IP addresses to the cloud instances. Recommended size: 1024 IPs (CIDR /22)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-network-planning.xml:30(para)
msgid "Floating IP network (Publicly routable IP Range): This network is utilized for providing Public IP accessibility to selected cloud instances. Minimum size: 16 IPs (CIDR /28)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:6(title)
msgid "Installation Assumptions"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:7(para)
msgid "OpenStack Compute has a large number of configuration options. To simplify this installation guide, we make a number of assumptions about the target installation."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:12(para)
msgid "You have a collection of compute nodes, each installed with Fedora 17, RHEL 6.2, Scientific Linux 6.1 or CentOS 6 + CR distributions (continuous release ( CR ) repository)."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:18(para)
msgid "You have a collection of compute nodes, each installed with Ubuntu Server 12.04."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:20(para)
msgid "<phrase os=\"rhel;centos;fedora\">There is also an <link href=\"http://docs.openstack.org/trunk/openstack-compute/install/apt/content/\">OpenStack Install and Deploy Manual for Ubuntu</link></phrase><phrase os=\"ubuntu\">There is also an <link href=\"http://docs.openstack.org/trunk/openstack-compute/install/yum/content/\">OpenStack Install and Deploy Manual for RHEL, CentOS and Fedora</link></phrase> Debian, openSUSE, and SLES also have OpenStack support, but are not documented here."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:23(para)
msgid "You have designated one of the nodes as the Cloud Controller, which will run all of the services (RabbitMQ or Qpid, MySQL, Identity, Image, nova-api, nova-network, nova-scheduler, nova-volume) except for nova-compute."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:28(para)
msgid "The disk partitions on your cloud controller are being managed by the <link href=\"http://docs.openstack.org/trunk/openstack-compute/admin/content/managing-volumes.html\">Logical Volume Manager</link> (LVM)."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:33(para)
msgid "Your Cloud Controller has an LVM volume group named \"nova-volumes\" to provide persistent storage to guest VMs. Either create this during the installation or leave some free space to create it prior to installing nova services."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:41(para)
msgid "Ensure that the server can resolve its own hostname, otherwise you may have problems if you are using RabbitMQ as the messaging backend. <phrase os=\"ubuntu\">RabbitMQ is the default messaging back-end on Ubuntu</phrase><phrase os=\"rhel;centos;fedora\">Qpid is the default messaging back-end on Fedora</phrase>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:50(para)
msgid "<literal>192.168.206.130</literal> is the primary IP for our host on <literal>eth0</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:54(para)
msgid "<literal>192.168.100.0/24</literal> as the fixed range for our guest VMs, connected to the host via <literal>br100</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:58(para)
msgid "FlatDHCP with a single network interface."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:61(para)
msgid "KVM or Xen (XenServer or XCP) as the hypervisor."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:65(para)
msgid "On Ubuntu, enable the <link href=\"https://wiki.ubuntu.com/ServerTeam/CloudArchive\">Cloud Archive</link> repository by adding the following to /etc/apt/sources.list.d/folsom.list:<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:69(para)
msgid "Prior to running apt-get update and apt-get upgrade, install the keyring :"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:73(para)
msgid "Ensure the operating system is up-to-date by running <placeholder-1/> prior to the installation."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:76(para)
msgid "Ensure the operating system is up-to-date by running <placeholder-1/> and <placeholder-2/> prior to the installation."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:81(para)
msgid "On RHEL (and derivatives) enable the EPEL repository by running:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_assumptions.xml:84(para)
msgid "This installation process walks through installing a cloud controller node and a compute node using a set of packages that are known to work with each other. The cloud controller node contains all the nova- services including the API server and the database server. The compute node needs to run only the nova-compute service. You only need one nova-network service running in a multi-node install, though if high availability for networks is required, there are additional options."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installcomputeimage.xml:6(title)
msgid "Installing OpenStack Compute and Image Service"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_installcomputeimage.xml:7(para)
msgid "The OpenStack Compute and Image services work together to provide access to virtual servers and images through REST APIs."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-create-network.xml:6(title)
msgid "Creating the Network for Compute VMs"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-create-network.xml:7(para)
msgid "You must run the command that creates the network and the bridge using the br100 specified in the nova.conf file to create the network that the virtual machines use. This example shows the network range using <literal>192.168.100.0/24</literal> as the fixed range for our guest VMs, but you can substitute the range for the network you have available. We're labeling it with <literal>private</literal> in this case."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:6(title)
msgid "Running Virtual Machine Instances"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:8(title)
msgid "Security groups: Enabling SSH and ICMP (ping)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:9(para)
msgid "The Compute service uses the concept of security groups to control what network protocols (TCP, UDP, ICMP), ports, and IP addresses are permitted to access instances. Each tenant manages its own list of security groups and starts off with a security group called <literal>default</literal>. If no security group is specified upon boot, the virtual machine will be associated with the <literal>default</literal> security group."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:14(para)
msgid "Security groups can be listed by the <placeholder-1/> command.<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:21(para)
msgid "In this example, we will use the nova <placeholder-1/> command to enable access to TCP port 22 (so we can SSH to instances) Allow access to port 22 from all IP addresses (specified in CIDR notation as <literal>0.0.0.0/0</literal>) with the following command:<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:25(para)
msgid "When specifying rules for TCP and UDP protocols, you may specify a range of port consecutive addresses in a single rule (e.g., from port <literal>5901</literal> to port <literal>5999</literal>). In this case, only a single port is being enabled, so we specify the start port as <literal>22</literal> and the end port as <literal>22</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:30(para)
msgid "To be able to ping virtual machine instances, you must specify a rule to allow ICMP traffic. When specifying ICMP rules, instead of specifying a begin and end port, you specify a pemitted ICMP code and ICMP type. You can also specify <literal>-1</literal> for the code to enable all codes and <literal>-1</literal> for the type to enable all ICMP types. Allow access to all codes and types of ICMP traffic from all IP addresses with the following command:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:41(title)
msgid "Adding a keypair"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:42(para)
msgid "The Compute service can inject an SSH public key into an account on the instance, assuming the virtual machine image being used supports this. To add a keypair to the Compute service, use the <placeholder-1/> command. This command can be used to either generate a new keypair, or to upload an existing public key. The following example uploads an existing public key, located at <filename>~/.ssh/id_rsa.pub</filename>, and gives the keypair the name <literal>mykey</literal>.<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:49(para)
msgid "List the keypairs by doing:<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:55(para)
msgid "Confirm that the uploaded keypair matches your local key by checking your key's fingerprint with the <placeholder-1/> command:<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:61(title)
msgid "Confirm all services running"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:65(systemitem)
msgid "nova-api"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:67(para)
msgid "The <systemitem class=\"service\">nova-api</systemitem> service must be running to respond to the request to boot an instance, as well as to serve as the metadata server so that the instance can retrieve the public key uploaded i a previous section. If the <placeholder-1/> commands in the previous section succeeded, then the service is running."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:76(systemitem)
msgid "nova-scheduler"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:78(para)
msgid "The <systemitem class=\"service\">nova-scheduler</systemitem> service must be running in order to dispatch requests for a new virtual machine instance to a host running the <systemitem class=\"service\">nova-compute</systemitem> service that has sufficient resources."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:86(para)
msgid "The <systemitem class=\"service\">nova-compute</systemitem> service must be running in order to interact with the hypervisor to bring up a virtual machine instance."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:94(para)
msgid "The <systemitem class=\"service\">nova-network</systemitem> service must be running in order to perform networking tasks such as assigning an IP address to the virtual machine instance and implementing the security group rules."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:62(para)
msgid "Before trying to start an instance, confirm that all of the necessary services are running, in particular:<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:103(para)
msgid "The <placeholder-1/> command does not indicate whether the <systemitem class=\"service\">nova-api</systemitem> service is running."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:101(para)
msgid "The <placeholder-1/> command can be used to confirm that these services are running properly.<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:107(para)
msgid "As root:<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:113(para)
msgid "If any of the services are missing in your configuration, or the <literal>State</literal> column does not show a smiley face, then your Compute service will not be able to launch an instance."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:118(title)
msgid "Starting an instance"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:119(para)
msgid "To start an instance, we need to specify a <emphasis role=\"italic\">flavor</emphasis>, also known as an <emphasis role=\"italic\">instance type</emphasis>, which indicates the size of an instance. Use the <placeholder-1/> command to view the list of available flavors:<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:133(para)
msgid "We also need to specify the image. Use the <placeholder-1/> to retrieve the ID of the CirrOS image.<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:148(replaceable)
msgid "f4addd24-4e8a-46bb-b15d-fae2591f1a35"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:141(para)
msgid "Use the <literal>nova boot</literal> command to launch a new virtual machine instance. We'll use an <literal>m1.small</literal> instance in this example, using the CirrOS image, and the <literal>mykey</literal> keypair we added. We also need to give this virtual machine instance a name, we'll call it <literal>cirros</literal>. We will explicitly specify the <literal>default</literal> security group in this example, although this isn't strictly necessary since the <literal>default</literal> group will be used if no security group is specified.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:177(para)
msgid "Check the progress of the instance with the <placeholder-1/> command. When the instance has booted, the command output will look something like:<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:185(para)
msgid "You can view the boot messages of the instances using the <placeholder-1/> command:<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:214(para)
msgid "You should be able to ping your instance:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:228(para)
msgid "You should be able to ssh to your instance as the <literal>cirros</literal> user, using either the ssh keypair you uploaded or using the password <literal>cubswin:)</literal><placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:239(title)
msgid "Bringing down an instance"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_instances-running.xml:240(para)
msgid "Bring down your instance using the <placeholder-1/> command:<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:6(title)
msgid "Installing and Configuring the Storage Nodes"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:9(para)
msgid "OpenStack Object Storage should work on any modern filesystem that supports Extended Attributes (XATTRS). We currently recommend XFS as it demonstrated the best overall performance for the swift use case after considerable testing and benchmarking at Rackspace. It is also the only filesystem that has been thoroughly tested."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:23(para)
msgid "For every device on the node you wish to use for storage, setup the XFS volume (<literal>/dev/sdb</literal> is used as an example). Use a single partition per drive. For example, in a server with 12 disks you may use one or two disks for the operating system which should not be touched in this step. The other 10 or 11 disks should be partitioned with a single partition, then formatted in XFS."
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:37(para)
msgid "Create <filename>/etc/rsyncd.conf</filename>:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:65(para)
msgid "Edit the following line in <filename>/etc/default/rsync</filename>:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:76(para)
msgid "Create <filename>/etc/swift/account-server.conf</filename>:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:96(para)
msgid "Create <filename>/etc/swift/container-server.conf</filename>:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:116(para)
msgid "Create <filename>/etc/swift/object-server.conf</filename>:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:138(para)
msgid "Start the storage services:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:152(title)
msgid "Don't Panic"
msgstr ""
#: ./doc/src/docbkx/openstack-install/install-config-storage-nodes.xml:152(para)
msgid "If you are following these instructions in a linear manner, at this point the ring files may not be present on the storage nodes. This may cause some of the services such as the <literal>*-replicator</literal> to fail to start. After you have created the ring files and distributed them to the storage nodes, a service restart should allow these to start."
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-ntp.xml:6(title)
msgid "Installing Network Time Protocol (NTP)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-ntp.xml:7(para)
msgid "To keep all the services in sync across multiple machines, you need to install NTP, and if you do a multi-node configuration you will configure one server to be the reference server."
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-ntp.xml:13(para)
msgid "Set up the NTP server on your controller node so that it receives data by modifying the <filename>ntp.conf</filename> file and restarting the service. As root:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-ntp.xml:20(para)
msgid "Set up the NTP client on your compute node so that the time between controller node and compute node is synchronized. Install the NTP package on the compute nodes in addition to the API nodes, to allow more gradual time updates."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:8(title)
msgid "OpenStack Grizzly deployment guide for Ubuntu Precise, Single node installation."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:10(para)
msgid "ASSUMPTION: Currently guide uses Nova-Network will be updated for Neutron soon, although we have created database and endpoint for the Neutron service."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:15(para)
msgid "One server with two NICs"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:17(para)
msgid "IF1 : Public traffic"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:18(para)
msgid "IF2 : Private traffic"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:49(para)
msgid "Download and install the Ubuntu Precise 12.04 LTS x86_64."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:51(para)
msgid "Add the following Ubuntu repository read about it <link href=\"http://blog.canonical.com/2012/09/14/now-you-can-have-your-openstack-cake-and-eat-it/\">on the Canonical blog.</link> (as root):"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:60(para)
msgid "Install the required packages."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:64(para)
msgid "Enable the ip_forwarding."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:71(para)
msgid "Update the configuration."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:74(para)
msgid "Edit /etc/ntp.conf"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:147(para)
msgid "Edit /etc/mysql/my.cnf and uncomment this line:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:149(para)
msgid "Restart mysql server."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:151(para)
msgid "Creating and adding the databases for all the services.<placeholder-1/>Add mysql permissions for the created databases.<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:172(title)
msgid "Installing and Configuring Identity service"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:173(para)
msgid "Install the packages.<placeholder-1/>Edit /etc/keystone/keystone.conf and modify Admin token, SQLAlchemy, Catalog accordingly.<placeholder-2/><placeholder-3/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:177(para)
msgid "Restart Keystone.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:179(para)
msgid "Populate the database.<placeholder-1/>Update the /home/$user/.bashrc by adding then credentials below.<placeholder-2/>Source the environment setting.<placeholder-3/>Add keystone users.<placeholder-4/>Create roles.<placeholder-5/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:201(para)
msgid "Create tenants.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:204(para)
msgid "Create services.<placeholder-1/>Create endpoints.<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:241(para)
msgid "Retrieve all the ids.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:282(para)
msgid "Adding roles."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:305(para)
msgid "NOTE: All These ID will differ in your configuration - use the appropriate command and retrieve all the IDs."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:310(title)
msgid "Installing and configuring Image Service"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:311(para)
msgid "Install the packages."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:313(para)
msgid "Edit /etc/glance/glance-api-paste.ini (filter authoken).<placeholder-1/>Edit /etc/glance/glance-registry-paste.ini (filter authtoken).<placeholder-2/> Edit /etc/glance/glance-api.conf."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:332(para) ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:338(para)
msgid "SQLAlchemy part of config.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:334(para) ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:340(para)
msgid "Append the following lines.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:337(para)
msgid "Edit /etc/glance/glance-registry.conf."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:343(para) ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:532(para)
msgid "Populate the database.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:345(para)
msgid "Restart all services.<placeholder-1/>Testing Glance configuration.<placeholder-2/>If nothing is returned, then it is working."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:354(title)
msgid "Installing and configuring Compute"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:356(para)
msgid "Install the packages.<placeholder-1/>Update /etc/nova/nova.conf.<placeholder-2/>Update the file ownership rights.<placeholder-3/>Edit /etc/nova/api-paste.ini (filter authtoken).<placeholder-4/>Populate the database.<placeholder-5/>Create the private network.<placeholder-6/> Restart everything."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:429(para)
msgid "The use of <literal>--vlan=100</literal> in the above command is to work around <link href=\"https://bugs.launchpad.net/devstack/+bug/1049869\">a bug in OpenStack Folsom</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:434(para)
msgid "Check the smiling services.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:445(title)
msgid "Installing and configuring Dashboard"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:446(para)
msgid "Install the packages.<placeholder-1/>Disable the neutron endpoint, as of now in our setup we are not using Neutron to do so Edit /etc/openstack-dashboard/local_settings.py - under TEMPLATE_DEBUG.<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:453(para)
msgid "In order to change the timezone you can use either dashboard or inside /etc/openstack-dashboard/local_settings.py you can change the parameter below.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:461(para)
msgid "Also be aware that the <filename>local_settings.py</filename> config file has comments that instruct you to configure Apache to redirect according to the location where the Horizon login screen is installed, otherwise you just see the \"It works!\" text on the root landing page for the web server. Here is the meaningful section in <filename>local_settings.py</filename>:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:474(para)
msgid "Restart the services.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:476(para)
msgid "Logging into the dashboard with browser"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:480(title)
msgid "Installing and configuring Cinder"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:481(para)
msgid "Install the packages.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:484(para)
msgid "Edit /etc/cinder/api-paste.init (filter authtoken).<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:496(para)
msgid "Edit /etc/cinder/cinder.conf."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:508(para)
msgid "Configuring Rabbit /etc/cinder/cinder.conf."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:516(para)
msgid "Verify entries in nova.conf."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:521(para)
msgid "Add a filter entry to the devices section /etc/lvm/lvm.conf to keep LVM from scanning devices used by virtual machines. NOTE: You must add every physical volume that is needed for LVM on the Cinder host. You can get a list by running pvdisplay. Each item in the filter array starts with either an \"a\" for accept, or an \"r\" for reject. Physical volumes that are needed on the Cinder host begin with \"a\". The array must end with \"r/.*/\""
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:527(para)
msgid "Setup the tgts file <emphasis role=\"italic\">NOTE: $state_path=/var/lib/cinder/ and $volumes_dir = $state_path/volumes by default and path MUST exist!</emphasis>.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:530(para)
msgid "Restart the tgt service.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:534(para)
msgid "Create a 2GB test loopfile."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:536(para)
msgid "Mount it."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:538(para)
msgid "Initialise it as an lvm 'physical volume', then create the lvm 'volume group' <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:541(para)
msgid "Lets check if our volume is created. <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:545(para)
msgid "Restart the services.<placeholder-1/>Create a 1 GB test volume.<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:560(title)
msgid "Installing and configuring Swift"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:561(para)
msgid "Install the packages.<placeholder-1/>Create a loopback device.<placeholder-2/> Create a mountpoint.<placeholder-3/>Add an fstab entry inside /etc/fstab. ($user, replace it with your logged in Linux username)<placeholder-4/>Mount it.<placeholder-5/>Create the backend.<placeholder-6/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:580(para)
msgid "Configure rsync, by modifying /etc/default/rsync.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:582(para)
msgid "Create, /etc/rsyncd.conf and populate it with contents below.<placeholder-1/>Restart the service.<placeholder-2/>Create /etc/rsyslog.d/10-swift.conf.<placeholder-3/>Append/add to /etc/rsyslog.conf.<placeholder-4/>Configure the file permissions.<placeholder-5/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:698(para)
msgid "Configure the components."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:699(para)
msgid "Edit /etc/swift/swift.conf.<placeholder-1/>Edit /etc/swift/proxy-server.conf.<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:759(para)
msgid "Create the account file /etc/swift/account-server/1.conf.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:784(para)
msgid "Duplicate it.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:791(para)
msgid "Configure the container file (/etc/swift/container-server/1.conf).<placeholder-1/>Duplicate it.<placeholder-2/>Create the object server file (/etc/swift/object-server/1.conf).<placeholder-3/>Duplicate it.<placeholder-4/>Configure the rings.<placeholder-5/>Create the zones and balance them. <placeholder-6/>Restart the services. It will take sometime.<placeholder-7/> Check the status<placeholder-8/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_installingfolsom.xml:883(para)
msgid "Create a container name \"test\" and with the list option we can see it created."
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:40(None)
msgid "@@image: 'figures/swift_install_arch.png'; md5=c6519fb969c1184afa22e024de9bd2a6"
msgstr ""
#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:6(title)
msgid "Example Object Storage Installation Architecture"
msgstr ""
#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:9(para)
msgid "node - a host machine running one or more OpenStack Object Storage services"
msgstr ""
#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:13(para)
msgid "Proxy node - node that runs Proxy services"
msgstr ""
#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:16(para)
msgid "Auth node - an optionally separate node that runs the Auth service separately from the Proxy services"
msgstr ""
#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:20(para)
msgid "Storage node - node that runs Account, Container, and Object services"
msgstr ""
#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:24(para)
msgid "Ring - a set of mappings of OpenStack Object Storage data to physical devices"
msgstr ""
#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:28(para)
msgid "To increase reliability, you may want to add additional Proxy servers for performance."
msgstr ""
#: ./doc/src/docbkx/openstack-install/example-object-storage-install-arch.xml:30(para)
msgid "This document describes each Storage node as a separate zone in the ring. It is recommended to have a minimum of 5 zones. A zone is a group of nodes that is as isolated as possible from other nodes (separate servers, network, power, even geography). The ring guarantees that every replica is stored in a separate zone. This diagram shows one possible configuration for a minimal installation."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:5(title)
msgid "Registering Virtual Machine Images"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:16(para)
msgid "Username: <literal>cirros</literal>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:19(para)
msgid "Password: <literal>cubswin:)</literal>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:6(para)
msgid "To test your deployment, download some virtual machine images that are known to work with OpenStack. CirrOS is a small test image that is often used for testing OpenStack deployments. You can find the most recent CirrOS image on the <link href=\"https://launchpad.net/cirros\">CirrOS Launchpad home page</link> under \"Downloads\". As of this writing the most recent image is version 0.3.0. A 64-bit version in QCOW2 format (compatible with KVM or QEMU hypervisors) can be downloaded at <link href=\"https://launchpad.net/cirros/trunk/0.3.0/+download/cirros-0.3.0-x86_64-disk.img\">https://launchpad.net/cirros/trunk/0.3.0/+download/cirros-0.3.0-x86_64-disk.img</link>. Once you launch the image, log in with the following credentials:<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:22(para)
msgid "The 64-bit CirrOS QCOW2 image is the image we'll use for this walkthrough. More detailed information about how to obtain and create images can be found in the <link href=\"http://docs.openstack.org\">OpenStack Compute Administration Guide</link> in the \"Image Management\" chapter."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:26(para)
msgid "Create a directory called <filename>stackimages</filename> to house your image files:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:31(para)
msgid "Download the CirrOS image into your <filename>stackimages</filename> directory."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:35(para)
msgid "Verify that your <placeholder-1/> client can access the Image service by requesting a list of installed images:<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:41(para)
msgid "If you get the following error, make sure that the environment variables set in <filename>~/openrc</filename><placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:50(para)
msgid "Add the CirrOS image to the Image service using the <placeholder-1/> command, passing the image file through standard input:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:58(para)
msgid "The returned image ID is generated dynamically, and therefore will be different on your deployment than in this example."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:64(literal)
msgid "name=cirros-0.3.0-x86_64"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:66(para)
msgid "The <literal>name</literal> field is an arbitrary label. In this example the name encodes the distribution, version, and architecture: <literal>cirros-0.3.0-x864_64</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:72(literal)
msgid "disk-format=qcow2"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:74(para)
msgid "The <literal>disk-format</literal> field specifies the format of the image file. In this case, the image file format is QCOW2, which can be verified using the <placeholder-1/> command:<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:79(para)
msgid "Other valid formats are <literal>raw</literal>, <literal>vhd</literal>, <literal>vmdk</literal>, <literal>vdi</literal>, <literal>iso</literal>, <literal>aki</literal>, <literal>ari</literal> and <literal>ami</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:86(literal)
msgid "container-format=bare"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:88(para)
msgid "The <literal>container-format</literal> field is required by the <placeholder-1/> command but isn't actually used by any of the OpenStack services, so the value specified here has no effect on system behavior. We specify <literal>bare</literal> to indicate that the image file is not in a file format that contains metadata about the virtual machine."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:94(para)
msgid "Because the value is not used anywhere, it safe to always specify <literal>bare</literal> as the container format, although the command will accept other formats: <literal>ovf</literal>, <literal>aki</literal>, <literal>ari</literal>, <literal>ami</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:62(para)
msgid "The rationale for the arguments is:<placeholder-1/>Confirm it was uploaded by listing the images in the Image service:<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ch_images-uploading.xml:105(para)
msgid "The <placeholder-1/> command will also list the images in the Image service:<placeholder-2/>"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_dependencies.xml:6(title)
msgid "Appendix: Dependencies"
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_dependencies.xml:8(para)
msgid "Included for your reference is a list of dependencies."
msgstr ""
#: ./doc/src/docbkx/openstack-install/ap_dependencies.xml:9(title)
msgid "Ubuntu 12.04 dependencies"
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:6(title)
msgid "Installing Additional Compute Nodes"
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:7(para)
msgid "There are many different ways to perform a multinode install of Compute in order to scale out your deployment and run more compute nodes, enabling more virtual machines to run simultaneously."
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:11(para)
msgid "Ensure that the networking on each node is configured as documented in the <link linkend=\"compute-configuring-guest-network\">Pre-configuring the network</link> section."
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:14(para)
msgid "In this case, you can install all the nova- packages and dependencies as you did for the Cloud Controller node, or just install nova-compute. Your installation can run any nova- services anywhere, so long as the service can access <filename>nova.conf</filename> so it knows where the Rabbitmq or Qpid messaging server is installed."
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:20(para)
msgid "When running in a high-availability mode for networking, the compute node is where you configure the compute network, the networking between your instances. Learn more about high-availability for networking in the Compute Administration manual."
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:25(para)
msgid "Because you may need to query the database from the compute node and learn more information about instances, the nova client and MySQL client or PostgresSQL client packages should be installed on any additional compute nodes."
msgstr ""
#: ./doc/src/docbkx/openstack-install/installing-additional-compute-nodes.xml:29(para)
msgid "Copy the <filename>nova.conf</filename> from your controller node to all additional compute nodes. As mentioned in the section entitled <link linkend=\"compute-minimum-configuration-settings\">Configuring OpenStack Compute</link>, modify the following configuration options so that they match the IP address of the compute host:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:6(title)
msgid "Compute Scripted Installations"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:7(para)
msgid "You can download a script for a standalone install for proof-of-concept, learning, or for development purposes for Ubuntu 11.04 at <link href=\"http://devstack.org\">https://devstack.org</link>. This is not a permanent installation."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:15(para)
msgid "Install Ubuntu 11.04 (Natty):"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:15(para)
msgid "In order to correctly install all the dependencies, we assume a specific version of Ubuntu to make it as easy as possible. OpenStack works on other flavors of Linux (and some folks even run it on Windows!) We recommend using a minimal install of Ubuntu server in a VM if this is your first time."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:22(para)
msgid "Download DevStack:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:24(para)
msgid "The devstack repo contains a script that installs OpenStack Compute with the Image Service and the Identity Service and OpenStack Object Storage. It offers templates for configuration files plus data scripts."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:32(para)
msgid "Start the install:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:32(para)
msgid "It takes a few minutes, we recommend <link href=\"http://devstack.org/stack.sh.html\">reading the well-documented script</link> while it is building to learn more about what is going on."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:38(para)
msgid "You can also install a more permanent deployment using an upstart script after running the devstack script."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:39(para)
msgid "Once you have tested stack.sh and tailored it to your system, you can convert the installation into upstart services. The additions with this script are the ability to run services like daemons instead of in screens, to store logs in files and offer an automatic start up after a reboot."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:46(para)
msgid "It works with glance- services, nova- services, novnc, and keystone, but not with neutron or swift as of November 22 2011. Here are the basic steps."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:50(para)
msgid "Ensure you've run ./stack.sh with all the configuration you need for your systems."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:52(para)
msgid "Download the upstart scripts:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:54(para)
msgid "The devstack repo contains a script that installs OpenStack Compute, the Image Service and the Identity Service and offers templates for configuration files plus data scripts."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:57(para)
msgid "Run the upstart install script."
msgstr ""
#: ./doc/src/docbkx/openstack-install/compute-scripted-ubuntu-install.xml:60(para)
msgid "Now the services are installed. To use them, either reboot to get rid of the services started by stack.sh, and automatically start those services, or do killall screen, then:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-network-planning.xml:5(title)
msgid "Object Storage Network Planning"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-network-planning.xml:6(para)
msgid "For both conserving network resources and ensuring that network administrators understand the needs for networks and public IP addresses for providing access to the APIs and storage network as necessary, this section offers recommendations and required minimum sizes. Throughput of at least 1000 Mbps is suggested."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-network-planning.xml:12(para)
msgid "This document refers to two networks. One is a Public Network for connecting to the Proxy server, and the second is a Storage Network that is not accessible from outside the cluster, to which all of the nodes are connected. All of the OpenStack Object Storage services, as well as the rsync daemon on the Storage nodes are configured to listen on their STORAGE_LOCAL_NET IP addresses."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-network-planning.xml:18(para)
msgid "Public Network (Publicly routable IP range): This network is utilized for providing Public IP accessibility to the API endpoints within the cloud infrastructure."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-network-planning.xml:20(para)
msgid "Minimum size: 8 IPs (CIDR /29)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-network-planning.xml:21(para)
msgid "Storage Network (RFC1918 IP Range, not publicly routable): This network is utilized for all inter-server communications within the Object Storage infrastructure."
msgstr ""
#: ./doc/src/docbkx/openstack-install/object-storage-network-planning.xml:24(para)
msgid "Recommended size: 255 IPs (CIDR /24)"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-defining-services.xml:14(para)
msgid "There are two alternative ways of defining services with keystone: <placeholder-1/> While using a template file is simpler, it is not recommended except for development environments such as <link href=\"http://www.devstack.org\">DevStack</link>. The template file does not enable Create, Read, Update, or Delete (CRUD) operations on the service catalog through keystone commands, but you can use the service-list command when using the template catalog. When keystone uses a template file backend, then changes made to the endpoints are kept in memory and don't persist if you restart the service or reboot the machine. Use the SQL backend when deploying a system for production."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-defining-services.xml:33(para)
msgid "A database backend can provide better reliability, availability, and data redundancy. This section describes how to populate the Keystone service catalog using the database backend. Your <filename>/etc/keystone/keystone.conf</filename> file should contain the following lines if it is properly configured to use the database backend."
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-defining-services.xml:80(literal)
msgid "--service_id"
msgstr ""
#: ./doc/src/docbkx/openstack-install/identity-defining-services.xml:104(para)
msgid "Keystone allows some URLs to contain special variables, which are automatically substituted with the correct value at runtime. Some examples in this document employ the <literal>tenant_id</literal> variable, which we use when specifying the Volume and Compute service endpoints. Variables can be specified using either <literal>%(<replaceable>varname</replaceable>)s</literal> or <literal>$(<replaceable>varname</replaceable>)s</literal> notation. In this document, we always use the <literal>%(<replaceable>varname</replaceable>)s</literal> notation (e.g., <literal>%(tenant_id)s</literal>) since <literal>$</literal> is interpeted as a special character by Unix shells."
msgstr ""
#: ./doc/src/docbkx/openstack-install/configure-creds.xml:6(title)
msgid "Defining Compute and Image Service Credentials"
msgstr ""
#: ./doc/src/docbkx/openstack-install/configure-creds.xml:7(para)
msgid "The commands in this section can be run on any machine that can access the cloud controller node over the network. You can run commands directly on the cloud controller, if you like, but it isn't required."
msgstr ""
#: ./doc/src/docbkx/openstack-install/configure-creds.xml:10(para)
msgid "Create an <filename>openrc</filename> file that can contain these variables that are used by the <placeholder-1/> (Compute) and <placeholder-2/> (Image) command-line interface clients. These commands can be run by any user, and the <filename>openrc</filename> file can be stored anywhere. In this document, we store the <filename>openrc</filename> file in the <filename>~/creds</filename> directory:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/configure-creds.xml:20(para)
msgid "In this example, we are going to create an <filename>openrc</filename> file with credentials associated with a user who is not an administrator. Because the user is not an administrator, the credential file will use the URL associated with the keystone service API, which runs on port <literal>5000</literal>. If we wanted to use the <placeholder-1/> command-line tool to perform administrative commands, we would use the URL associated with the keystone admin API, which runs on port <literal>35357</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-install/configure-creds.xml:28(para)
msgid "In the <filename>openrc</filename> file you create, paste these values:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/configure-creds.xml:30(para)
msgid "Next, ensure these are used in your environment. If you see 401 Not Authorized errors on commands using tokens, ensure that you have properly sourced your credentials and that all the pipelines are accurate in the configuration files."
msgstr ""
#: ./doc/src/docbkx/openstack-install/configure-creds.xml:39(para)
msgid "Verify your credentials are working by using the <placeholder-1/> client to list the available images:"
msgstr ""
#: ./doc/src/docbkx/openstack-install/configure-creds.xml:53(para)
msgid "Note that the ID values on your installation will be different."
msgstr ""
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
#: ./doc/src/docbkx/openstack-install/configure-creds.xml:0(None)
msgid "translator-credits"
msgstr ""
View Git Blame Copy Permalink