# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-2017, OpenStack contributors
# This file is distributed under the same license as the Administrator Guide package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Administrator Guide 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-07-19 16:20+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: ../appendix.rst:2
msgid "Appendix"
msgstr ""

#: ../cross-project-cors.rst:5
msgid "Cross-origin resource sharing"
msgstr ""

#: ../cross-project-cors.rst:9
msgid "This is a new feature in OpenStack Liberty."
msgstr ""

#: ../cross-project-cors.rst:11
msgid ""
"OpenStack supports :term:`Cross-Origin Resource Sharing (CORS)`, a W3C "
"specification defining a contract by which the single-origin policy of a "
"user agent (usually a browser) may be relaxed. It permits the javascript "
"engine to access an API that does not reside on the same domain, protocol, "
"or port."
msgstr ""

#: ../cross-project-cors.rst:16
msgid ""
"This feature is most useful to organizations which maintain one or more "
"custom user interfaces for OpenStack, as it permits those interfaces to "
"access the services directly, rather than requiring an intermediate proxy "
"server. It can, however, also be misused by malicious actors; please review "
"the security advisory below for more information."
msgstr ""

#: ../cross-project-cors.rst:23
msgid "Enabling CORS with configuration"
msgstr ""

#: ../cross-project-cors.rst:25
msgid ""
"In most cases, CORS support is built directly into the service itself. To "
"enable it, simply follow the configuration options exposed in the default "
"configuration file, or add it yourself according to the pattern below."
msgstr ""

#: ../cross-project-cors.rst:38
msgid ""
"Additional origins can be explicitly added. To express this in your "
"configuration file, first begin with a ``[cors]`` group as above, into which "
"you place your default configuration values. Then, add as many additional "
"configuration groups as necessary, naming them ``[cors.{something}]`` (each "
"name must be unique). The purpose of the suffix to ``cors.`` is legibility, "
"we recommend using a reasonable human-readable string:"
msgstr ""

#: ../cross-project-cors.rst:64
msgid ""
"For more information about CORS configuration, see `cross-origin resource "
"sharing <https://docs.openstack.org/ocata/config-reference/common-"
"configurations/cors.html>`_ in OpenStack Configuration Reference."
msgstr ""

#: ../cross-project-cors.rst:70
msgid "Enabling CORS with PasteDeploy"
msgstr ""

#: ../cross-project-cors.rst:72
msgid ""
"CORS can also be configured using PasteDeploy. First of all, ensure that "
"OpenStack's ``oslo_middleware`` package (version 2.4.0 or later) is "
"available in the Python environment that is running the service. Then, add "
"the following configuration block to your ``paste.ini`` file."
msgstr ""

#: ../cross-project-cors.rst:88
msgid ""
"To add an additional domain in oslo_middleware v2.4.0, add another filter. "
"In v3.0.0 and after, you may add multiple domains in the above "
"``allowed_origin`` field, separated by commas."
msgstr ""

#: ../cross-project-cors.rst:93
msgid "Security concerns"
msgstr ""

#: ../cross-project-cors.rst:95
msgid ""
"CORS specifies a wildcard character ``*``, which permits access to all user "
"agents, regardless of domain, protocol, or host. While there are valid use "
"cases for this approach, it also permits a malicious actor to create a "
"convincing facsimile of a user interface, and trick users into revealing "
"authentication credentials. Please carefully evaluate your use case and the "
"relevant documentation for any risk to your organization."
msgstr ""

#: ../cross-project-cors.rst:104
msgid ""
"The CORS specification does not support using this wildcard as a part of a "
"URI. Setting ``allowed_origin`` to ``*`` would work, while ``*.openstack."
"org`` would not."
msgstr ""

#: ../cross-project-cors.rst:109
msgid "Troubleshooting"
msgstr ""

#: ../cross-project-cors.rst:111
msgid ""
"CORS is very easy to get wrong, as even one incorrect property will violate "
"the prescribed contract. Here are some steps you can take to troubleshoot "
"your configuration."
msgstr ""

#: ../cross-project-cors.rst:116
msgid "Check the service log"
msgstr ""

#: ../cross-project-cors.rst:118
msgid ""
"The CORS middleware used by OpenStack provides verbose debug logging that "
"should reveal most configuration problems. Here are some example log "
"messages, and how to resolve them."
msgstr ""

#: ../cross-project-cors.rst:123 ../cross-project-cors.rst:137
#: ../cross-project-cors.rst:149 ../support-compute.rst:99
#: ../support-compute.rst:129 ../support-compute.rst:176
#: ../support-compute.rst:208 ../support-compute.rst:238
#: ../support-compute.rst:268
msgid "Problem"
msgstr ""

#: ../cross-project-cors.rst:125
msgid "``CORS request from origin 'http://example.com' not permitted.``"
msgstr ""

#: ../cross-project-cors.rst:128 ../cross-project-cors.rst:142
#: ../cross-project-cors.rst:154 ../support-compute.rst:104
#: ../support-compute.rst:138 ../support-compute.rst:189
#: ../support-compute.rst:213 ../support-compute.rst:244
#: ../support-compute.rst:275
msgid "Solution"
msgstr ""

#: ../cross-project-cors.rst:130
msgid ""
"A request was received from the origin ``http://example.com``, however this "
"origin was not found in the permitted list. The cause may be a superfluous "
"port notation (ports 80 and 443 do not need to be specified). To correct, "
"ensure that the configuration property for this host is identical to the "
"host indicated in the log message."
msgstr ""

#: ../cross-project-cors.rst:139
msgid "``Request method 'DELETE' not in permitted list: GET,PUT,POST``"
msgstr ""

#: ../cross-project-cors.rst:144
msgid ""
"A user agent has requested permission to perform a DELETE request, however "
"the CORS configuration for the domain does not permit this. To correct, add "
"this method to the ``allow_methods`` configuration property."
msgstr ""

#: ../cross-project-cors.rst:151
msgid ""
"``Request header 'X-Custom-Header' not in permitted list: X-Other-Header``"
msgstr ""

#: ../cross-project-cors.rst:156
msgid ""
"A request was received with the header ``X-Custom-Header``, which is not "
"permitted. Add this header to the ``allow_headers`` configuration property."
msgstr ""

#: ../cross-project-cors.rst:161
msgid "Open your browser's console log"
msgstr ""

#: ../cross-project-cors.rst:163
msgid ""
"Most browsers provide helpful debug output when a CORS request is rejected. "
"Usually this happens when a request was successful, but the return headers "
"on the response do not permit access to a property which the browser is "
"trying to access."
msgstr ""

#: ../cross-project-cors.rst:169
msgid "Manually construct a CORS request"
msgstr ""

#: ../cross-project-cors.rst:171
msgid ""
"By using ``curl`` or a similar tool, you can trigger a CORS response with a "
"properly constructed HTTP request. An example request and response might "
"look like this."
msgstr ""

#: ../cross-project-cors.rst:175
msgid "Request example:"
msgstr ""

#: ../cross-project-cors.rst:181
msgid "Response example:"
msgstr ""

#: ../cross-project-cors.rst:193
msgid ""
"If the service does not return any access control headers, check the service "
"log, such as ``/var/log/upstart/ironic-api.log`` for an indication on what "
"went wrong."
msgstr ""

#: ../cross-project.rst:3
msgid "Cross-project features"
msgstr ""

#: ../cross-project.rst:5
msgid ""
"Many features are common to all the OpenStack services and are consistent in "
"their configuration and deployment patterns. Unless explicitly noted, you "
"can safely assume that the features in this chapter are supported and "
"configured in a consistent manner."
msgstr ""

#: ../firewalls-default-ports.rst:3
msgid "Firewalls and default ports"
msgstr ""

#: ../firewalls-default-ports.rst:5
msgid ""
"On some deployments, such as ones where restrictive firewalls are in place, "
"you might need to manually configure a firewall to permit OpenStack service "
"traffic."
msgstr ""

#: ../firewalls-default-ports.rst:9
msgid ""
"To manually configure a firewall, you must permit traffic through the ports "
"that each OpenStack service uses. This table lists the default ports that "
"each OpenStack service uses:"
msgstr ""

#: ../firewalls-default-ports.rst:13
msgid "Default ports that OpenStack components use"
msgstr ""

#: ../firewalls-default-ports.rst:16
msgid "OpenStack service"
msgstr ""

#: ../firewalls-default-ports.rst:17
msgid "Default ports"
msgstr ""

#: ../firewalls-default-ports.rst:18
msgid "Port type"
msgstr ""

#: ../firewalls-default-ports.rst:19
msgid "Application Catalog (``murano``)"
msgstr ""

#: ../firewalls-default-ports.rst:20
msgid "8082"
msgstr ""

#: ../firewalls-default-ports.rst:22
msgid "Block Storage (``cinder``)"
msgstr ""

#: ../firewalls-default-ports.rst:23
msgid "8776"
msgstr ""

#: ../firewalls-default-ports.rst:24 ../firewalls-default-ports.rst:27
#: ../firewalls-default-ports.rst:30 ../firewalls-default-ports.rst:48
#: ../firewalls-default-ports.rst:57 ../firewalls-default-ports.rst:63
#: ../firewalls-default-ports.rst:69 ../firewalls-default-ports.rst:81
msgid "publicurl and adminurl"
msgstr ""

#: ../firewalls-default-ports.rst:25
msgid "Clustering (``senlin``)"
msgstr ""

#: ../firewalls-default-ports.rst:26
msgid "8778"
msgstr ""

#: ../firewalls-default-ports.rst:28
msgid "Compute (``nova``) endpoints"
msgstr ""

#: ../firewalls-default-ports.rst:29
msgid "8774"
msgstr ""

#: ../firewalls-default-ports.rst:31
msgid "Compute API (``nova-api``)"
msgstr ""

#: ../firewalls-default-ports.rst:32
msgid "8773, 8775"
msgstr ""

#: ../firewalls-default-ports.rst:34
msgid "Compute ports for access to virtual machine consoles"
msgstr ""

#: ../firewalls-default-ports.rst:35
msgid "5900-5999"
msgstr ""

#: ../firewalls-default-ports.rst:37
msgid "Compute VNC proxy for browsers ( openstack-nova-novncproxy)"
msgstr ""

#: ../firewalls-default-ports.rst:38
msgid "6080"
msgstr ""

#: ../firewalls-default-ports.rst:40
msgid ""
"Compute VNC proxy for traditional VNC clients (openstack-nova-xvpvncproxy)"
msgstr ""

#: ../firewalls-default-ports.rst:41
msgid "6081"
msgstr ""

#: ../firewalls-default-ports.rst:43
msgid "Proxy port for HTML5 console used by Compute service"
msgstr ""

#: ../firewalls-default-ports.rst:44
msgid "6082"
msgstr ""

#: ../firewalls-default-ports.rst:46
msgid "Data processing service (``sahara``) endpoint"
msgstr ""

#: ../firewalls-default-ports.rst:47
msgid "8386"
msgstr ""

#: ../firewalls-default-ports.rst:49
msgid "Identity service (``keystone``) administrative endpoint"
msgstr ""

#: ../firewalls-default-ports.rst:50
msgid "35357"
msgstr ""

#: ../firewalls-default-ports.rst:51
msgid "adminurl"
msgstr ""

#: ../firewalls-default-ports.rst:52
msgid "Identity service public endpoint"
msgstr ""

#: ../firewalls-default-ports.rst:53
msgid "5000"
msgstr ""

#: ../firewalls-default-ports.rst:54
msgid "publicurl"
msgstr ""

#: ../firewalls-default-ports.rst:55
msgid "Image service (``glance``) API"
msgstr ""

#: ../firewalls-default-ports.rst:56
msgid "9292"
msgstr ""

#: ../firewalls-default-ports.rst:58
msgid "Image service registry"
msgstr ""

#: ../firewalls-default-ports.rst:59
msgid "9191"
msgstr ""

#: ../firewalls-default-ports.rst:61
msgid "Networking (``neutron``)"
msgstr ""

#: ../firewalls-default-ports.rst:62
msgid "9696"
msgstr ""

#: ../firewalls-default-ports.rst:64
msgid "Object Storage (``swift``)"
msgstr ""

#: ../firewalls-default-ports.rst:65
msgid "6000, 6001, 6002"
msgstr ""

#: ../firewalls-default-ports.rst:67
msgid "Orchestration (``heat``) endpoint"
msgstr ""

#: ../firewalls-default-ports.rst:68
msgid "8004"
msgstr ""

#: ../firewalls-default-ports.rst:70
msgid ""
"Orchestration AWS CloudFormation-compatible API (``openstack-heat-api-cfn``)"
msgstr ""

#: ../firewalls-default-ports.rst:71
msgid "8000"
msgstr ""

#: ../firewalls-default-ports.rst:73
msgid ""
"Orchestration AWS CloudWatch-compatible API (``openstack-heat-api-"
"cloudwatch``)"
msgstr ""

#: ../firewalls-default-ports.rst:74
msgid "8003"
msgstr ""

#: ../firewalls-default-ports.rst:76
msgid "Root Cause Analysis service (``Vitrage``)"
msgstr ""

#: ../firewalls-default-ports.rst:77
msgid "8999"
msgstr ""

#: ../firewalls-default-ports.rst:79
msgid "Telemetry (``ceilometer``)"
msgstr ""

#: ../firewalls-default-ports.rst:80
msgid "8777"
msgstr ""

#: ../firewalls-default-ports.rst:82
msgid "Workflow service (``Mistral``)"
msgstr ""

#: ../firewalls-default-ports.rst:83
msgid "8989"
msgstr ""

#: ../firewalls-default-ports.rst:86
msgid ""
"To function properly, some OpenStack components depend on other, non-"
"OpenStack services. For example, the OpenStack dashboard uses HTTP for non-"
"secure communication. In this case, you must configure the firewall to allow "
"traffic to and from HTTP."
msgstr ""

#: ../firewalls-default-ports.rst:91
msgid "This table lists the ports that other OpenStack components use:"
msgstr ""

#: ../firewalls-default-ports.rst:93
msgid ""
"Default ports that secondary services related to OpenStack components use"
msgstr ""

#: ../firewalls-default-ports.rst:96
msgid "Service"
msgstr ""

#: ../firewalls-default-ports.rst:97
msgid "Default port"
msgstr ""

#: ../firewalls-default-ports.rst:98
msgid "Used by"
msgstr ""

#: ../firewalls-default-ports.rst:99
msgid "HTTP"
msgstr ""

#: ../firewalls-default-ports.rst:100
msgid "80"
msgstr ""

#: ../firewalls-default-ports.rst:101
msgid ""
"OpenStack dashboard (``Horizon``) when it is not configured to use secure "
"access."
msgstr ""

#: ../firewalls-default-ports.rst:102
msgid "HTTP alternate"
msgstr ""

#: ../firewalls-default-ports.rst:103
msgid "8080"
msgstr ""

#: ../firewalls-default-ports.rst:104
msgid "OpenStack Object Storage (``swift``) service."
msgstr ""

#: ../firewalls-default-ports.rst:105
msgid "HTTPS"
msgstr ""

#: ../firewalls-default-ports.rst:106
msgid "443"
msgstr ""

#: ../firewalls-default-ports.rst:107
msgid ""
"Any OpenStack service that is enabled for SSL, especially secure-access "
"dashboard."
msgstr ""

#: ../firewalls-default-ports.rst:108
msgid "rsync"
msgstr ""

#: ../firewalls-default-ports.rst:109
msgid "873"
msgstr ""

#: ../firewalls-default-ports.rst:110
msgid "OpenStack Object Storage. Required."
msgstr ""

#: ../firewalls-default-ports.rst:111
msgid "iSCSI target"
msgstr ""

#: ../firewalls-default-ports.rst:112
msgid "3260"
msgstr ""

#: ../firewalls-default-ports.rst:113
msgid "OpenStack Block Storage. Required."
msgstr ""

#: ../firewalls-default-ports.rst:114
msgid "MySQL database service"
msgstr ""

#: ../firewalls-default-ports.rst:115
msgid "3306"
msgstr ""

#: ../firewalls-default-ports.rst:116
msgid "Most OpenStack components."
msgstr ""

#: ../firewalls-default-ports.rst:117
msgid "Message Broker (AMQP traffic)"
msgstr ""

#: ../firewalls-default-ports.rst:118
msgid "5672"
msgstr ""

#: ../firewalls-default-ports.rst:119
msgid "OpenStack Block Storage, Networking, Orchestration, and Compute."
msgstr ""

#: ../firewalls-default-ports.rst:121
msgid ""
"On some deployments, the default port used by a service may fall within the "
"defined local port range of a host. To check a host's local port range:"
msgstr ""

#: ../firewalls-default-ports.rst:129
msgid ""
"If a service's default port falls within this range, run the following "
"program to check if the port has already been assigned to another "
"application:"
msgstr ""

#: ../firewalls-default-ports.rst:137
msgid ""
"Configure the service to use a different port if the default port is already "
"being used by another application."
msgstr ""

#: ../index.rst:3
msgid "OpenStack Administrator Guide"
msgstr ""

#: ../index.rst:7
msgid "Major rework in progress!"
msgstr ""

#: ../index.rst:9
msgid ""
"Note that on July 3rd of 2017, all projects have been moved to a new "
"location on this server. Keep in mind that bookmarks saved before the "
"changes may no longer function."
msgstr ""

#: ../index.rst:14
msgid ""
"Project-specific content have been moved to the project repos. For example, "
"if you are looking for Identity service administration information, please "
"visit the `keystone <https://docs.openstack.org/keystone/latest/>`_ page."
msgstr ""

#: ../index.rst:20
msgid ""
"See `the specification <http://specs.openstack.org/openstack/docs-specs/"
"specs/pike/os-manuals-migration.html>`_ for more information."
msgstr ""

#: ../index.rst:25
msgid "Abstract"
msgstr ""

#: ../index.rst:27
msgid ""
"OpenStack offers open source software for OpenStack administrators to manage "
"and troubleshoot an OpenStack cloud."
msgstr ""

#: ../index.rst:31
msgid ""
"This guide documents OpenStack Ocata, Newton, and Mitaka releases and may "
"not apply to EOL releases Kilo and Liberty."
msgstr ""

#: ../index.rst:35
msgid "Contents"
msgstr ""

#: ../support-compute.rst:8
msgid "Troubleshoot Compute"
msgstr ""

#: ../support-compute.rst:10
msgid ""
"Common problems for Compute typically involve misconfigured networking or "
"credentials that are not sourced properly in the environment. Also, most "
"flat networking configurations do not enable :command:`ping` or :command:"
"`ssh` from a compute node to the instances that run on that node. Another "
"common problem is trying to run 32-bit images on a 64-bit compute node. This "
"section shows you how to troubleshoot Compute."
msgstr ""

#: ../support-compute.rst:22
msgid "Compute service logging"
msgstr ""

#: ../support-compute.rst:24
msgid ""
"Compute stores a log file for each service in ``/var/log/nova``. For "
"example, ``nova-compute.log`` is the log for the ``nova-compute`` service. "
"You can set the following options to format log strings for the ``nova.log`` "
"module in the ``nova.conf`` file:"
msgstr ""

#: ../support-compute.rst:30
msgid "``logging_context_format_string``"
msgstr ""

#: ../support-compute.rst:32
msgid "``logging_default_format_string``"
msgstr ""

#: ../support-compute.rst:34
msgid ""
"If the log level is set to ``debug``, you can also specify "
"``logging_debug_format_suffix`` to append extra formatting. For information "
"about what variables are available for the formatter, see `Formatter Objects "
"<https://docs.python.org/library/logging.html#formatter-objects>`_."
msgstr ""

#: ../support-compute.rst:40
msgid ""
"You have two logging options for OpenStack Compute based on configuration "
"settings. In ``nova.conf``, include the ``logfile`` option to enable "
"logging. Alternatively you can set ``use_syslog = 1`` so that the nova "
"daemon logs to syslog."
msgstr ""

#: ../support-compute.rst:49
msgid "Guru Meditation reports"
msgstr ""

#: ../support-compute.rst:51
msgid ""
"A Guru Meditation report is sent by the Compute service upon receipt of the "
"``SIGUSR2`` signal (``SIGUSR1`` before Mitaka). This report is a general-"
"purpose error report that includes details about the current state of the "
"service. The error report is sent to ``stderr``."
msgstr ""

#: ../support-compute.rst:56
msgid ""
"For example, if you redirect error output to ``nova-api-err.log`` using :"
"command:`nova-api 2>/var/log/nova/nova-api-err.log`, resulting in the "
"process ID 8675, you can then run:"
msgstr ""

#: ../support-compute.rst:64
msgid ""
"This command triggers the Guru Meditation report to be printed to ``/var/log/"
"nova/nova-api-err.log``."
msgstr ""

#: ../support-compute.rst:67
msgid "The report has the following sections:"
msgstr ""

#: ../support-compute.rst:69
msgid ""
"Package: Displays information about the package to which the process "
"belongs, including version information."
msgstr ""

#: ../support-compute.rst:72
msgid ""
"Threads: Displays stack traces and thread IDs for each of the threads within "
"the process."
msgstr ""

#: ../support-compute.rst:75
msgid ""
"Green Threads: Displays stack traces for each of the green threads within "
"the process (green threads do not have thread IDs)."
msgstr ""

#: ../support-compute.rst:78
msgid ""
"Configuration: Lists all configuration options currently accessible through "
"the CONF object for the current process."
msgstr ""

#: ../support-compute.rst:81
msgid ""
"For more information, see `Guru Meditation Reports <https://docs.openstack."
"org/developer/nova/devref/gmr.html>`_."
msgstr ""

#: ../support-compute.rst:87
msgid "Common errors and fixes for Compute"
msgstr ""

#: ../support-compute.rst:89
msgid ""
"The `ask.openstack.org <http://ask.openstack.org>`_ site offers a place to "
"ask and answer questions, and you can also mark questions as frequently "
"asked questions. This section describes some errors people have posted "
"previously. Bugs are constantly being fixed, so online resources are a great "
"way to get the most up-to-date errors and fixes."
msgstr ""

#: ../support-compute.rst:96
msgid "Credential errors, 401, and 403 forbidden errors"
msgstr ""

#: ../support-compute.rst:101
msgid "Missing credentials cause a ``403 forbidden`` error."
msgstr ""

#: ../support-compute.rst:106
msgid "To resolve this issue, use one of these methods:"
msgstr ""

#: ../support-compute.rst:109
msgid ""
"Gets the ``novarc`` file from the project ZIP file, saves existing "
"credentials in case of override, and manually sources the ``novarc`` file."
msgstr ""

#: ../support-compute.rst:111
msgid "Manual method"
msgstr ""

#: ../support-compute.rst:114
msgid "Generates ``novarc`` from the project ZIP file and sources it for you."
msgstr ""

#: ../support-compute.rst:114
msgid "Script method"
msgstr ""

#: ../support-compute.rst:116
msgid ""
"When you run ``nova-api`` the first time, it generates the certificate "
"authority information, including ``openssl.cnf``. If you start the CA "
"services before this, you might not be able to create your ZIP file. Restart "
"the services. When your CA information is available, create your ZIP file."
msgstr ""

#: ../support-compute.rst:122
msgid ""
"Also, check your HTTP proxy settings to see whether they cause problems with "
"``novarc`` creation."
msgstr ""

#: ../support-compute.rst:126
msgid "Instance errors"
msgstr ""

#: ../support-compute.rst:131
msgid ""
"Sometimes a particular instance shows ``pending`` or you cannot SSH to it. "
"Sometimes the image itself is the problem. For example, when you use flat "
"manager networking, you do not have a DHCP server and certain images do not "
"support interface injection; you cannot connect to them."
msgstr ""

#: ../support-compute.rst:140
msgid ""
"To fix instance errors use an image that does support this method, such as "
"Ubuntu, which obtains an IP address correctly with FlatManager network "
"settings."
msgstr ""

#: ../support-compute.rst:144
msgid ""
"To troubleshoot other possible problems with an instance, such as an "
"instance that stays in a spawning state, check the directory for the "
"particular instance under ``/var/lib/nova/instances`` on the ``nova-"
"compute`` host and make sure that these files are present:"
msgstr ""

#: ../support-compute.rst:149
msgid "``libvirt.xml``"
msgstr ""

#: ../support-compute.rst:150
msgid "``disk``"
msgstr ""

#: ../support-compute.rst:151
msgid "``disk-raw``"
msgstr ""

#: ../support-compute.rst:152
msgid "``kernel``"
msgstr ""

#: ../support-compute.rst:153
msgid "``ramdisk``"
msgstr ""

#: ../support-compute.rst:154
msgid "``console.log``, after the instance starts."
msgstr ""

#: ../support-compute.rst:156
msgid ""
"If any files are missing, empty, or very small, the ``nova-compute`` service "
"did not successfully download the images from the Image service."
msgstr ""

#: ../support-compute.rst:159
msgid ""
"Also check ``nova-compute.log`` for exceptions. Sometimes they do not appear "
"in the console output."
msgstr ""

#: ../support-compute.rst:162
msgid ""
"Next, check the log file for the instance in the ``/var/log/libvirt/qemu`` "
"directory to see if it exists and has any useful error messages in it."
msgstr ""

#: ../support-compute.rst:165
msgid ""
"Finally, from the ``/var/lib/nova/instances`` directory for the instance, "
"see if this command returns an error:"
msgstr ""

#: ../support-compute.rst:173
msgid "Empty log output for Linux instances"
msgstr ""

#: ../support-compute.rst:178
msgid ""
"You can view the log output of running instances from either the :guilabel:"
"`Log` tab of the dashboard or the output of :command:`nova console-log`. In "
"some cases, the log output of a running Linux instance will be empty or only "
"display a single character (for example, the `?` character)."
msgstr ""

#: ../support-compute.rst:184
msgid ""
"This occurs when the Compute service attempts to retrieve the log output of "
"the instance via a serial console while the instance itself is not "
"configured to send output to the console."
msgstr ""

#: ../support-compute.rst:191
msgid ""
"To rectify this, append the following parameters to kernel arguments "
"specified in the instance's boot loader:"
msgstr ""

#: ../support-compute.rst:198
msgid ""
"Upon rebooting, the instance will be configured to send output to the "
"Compute service."
msgstr ""

#: ../support-compute.rst:205
msgid "Reset the state of an instance"
msgstr ""

#: ../support-compute.rst:210
msgid "Instances can remain in an intermediate state, such as ``deleting``."
msgstr ""

#: ../support-compute.rst:215
msgid ""
"You can use the :command:`nova reset-state` command to manually reset the "
"state of an instance to an error state. You can then delete the instance. "
"For example:"
msgstr ""

#: ../support-compute.rst:224
msgid ""
"You can also use the ``--active`` parameter to force the instance back to an "
"active state instead of an error state. For example:"
msgstr ""

#: ../support-compute.rst:235
msgid "Injection problems"
msgstr ""

#: ../support-compute.rst:240
msgid ""
"Instances may boot slowly, or do not boot. File injection can cause this "
"problem."
msgstr ""

#: ../support-compute.rst:246
msgid "To disable injection in libvirt, set the following in ``nova.conf``:"
msgstr ""

#: ../support-compute.rst:255
msgid ""
"If you have not enabled the configuration drive and you want to make user-"
"specified files available from the metadata server for to improve "
"performance and avoid boot failure if injection fails, you must disable "
"injection."
msgstr ""

#: ../support-compute.rst:265
msgid "Disable live snapshotting"
msgstr ""

#: ../support-compute.rst:270
msgid ""
"Administrators using libvirt version ``1.2.2`` may experience problems with "
"live snapshot creation. Occasionally, libvirt version ``1.2.2`` fails to "
"create live snapshots under the load of creating concurrent snapshot."
msgstr ""

#: ../support-compute.rst:277
msgid ""
"To effectively disable the libvirt live snapshotting, until the problem is "
"resolved, configure the ``disable_libvirt_livesnapshot`` option. You can "
"turn off the live snapshotting mechanism by setting up its value to ``True`` "
"in the ``[workarounds]`` section of the ``nova.conf`` file:"
msgstr ""