openstack-manuals/doc/common/tables/swift-object-server-app-object-server.xml
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

76 lines
4.0 KiB
XML

<?xml version="1.0" encoding="UTF-8"?>
<!-- The tool that generated this table lives in the
tools directory of this repository. As it was a one-time
generation, you can edit this file. -->
<para xmlns="http://docbook.org/ns/docbook" version="5.0">
<table rules="all">
<caption>Description of configuration options for <literal>[app:object-server]</literal> in <literal>object-server.conf-sample</literal></caption>
<col width="50%"/>
<col width="50%"/>
<thead>
<tr>
<td>Configuration option=Default value</td>
<td>Description</td>
</tr>
</thead>
<tbody>
<tr>
<td>use=egg:swift#object</td><td>Entry point of paste.deploy in the server</td>
</tr>
<tr>
<td>set log_name=object-server</td><td>Label to use when logging</td>
</tr>
<tr>
<td>set log_facility=LOG_LOCAL0</td><td>Syslog log facility</td>
</tr>
<tr>
<td>set log_level=INFO</td><td>Log level</td>
</tr>
<tr>
<td>set log_requests=true</td><td>Whether or not to log requests</td>
</tr>
<tr>
<td>set log_address=/dev/log</td><td>No help text available for this option</td>
</tr>
<tr>
<td>node_timeout=3</td><td>Request timeout to external services</td>
</tr>
<tr>
<td>conn_timeout=0.5</td><td>Connection timeout to external services</td>
</tr>
<tr>
<td>network_chunk_size=65536</td><td>Size of chunks to read/write over the network</td>
</tr>
<tr>
<td>disk_chunk_size=65536</td><td>Size of chunks to read/write to disk</td>
</tr>
<tr>
<td>max_upload_time=86400</td><td>Maximum time allowed to upload an object</td>
</tr>
<tr>
<td>slow=0</td><td>If > 0, Minimum time in seconds for a PUT or DELETE request to complete</td>
</tr>
<tr>
<td>keep_cache_size=5424880</td><td>Largest object size to keep in buffer cache</td>
</tr>
<tr>
<td>keep_cache_private=false</td><td>Allow non-public objects to stay in kernel's buffer cache</td>
</tr>
<tr>
<td>mb_per_sync=512</td><td>On PUT requests, sync file every n MB</td>
</tr>
<tr>
<td>allowed_headers=Content-Disposition, Content-Encoding, X-Delete-At, X-Object-Manifest, X-Static-Large-Object</td><td>Comma-separated list of headers that can be set in metadata of an object</td>
</tr>
<tr>
<td>auto_create_account_prefix=.</td><td>Prefix to use when automatically creating accounts</td>
</tr>
<tr>
<td>replication_server=false</td><td>If defined, tells server how to handle replication verbs in requests. When set to True (or 1), only replication verbs will be accepted. When set to False, replication verbs will be rejected. When undefined, server will accept any verb in the request.</td>
</tr>
<tr>
<td>threads_per_disk=0</td><td>Size of the per-disk thread pool used for performing disk I/O. The default of 0 means to not use a per-disk thread pool. It is recommended to keep this value small, as large values can result in high read latencies due to large queue depths. A good starting point is 4 threads per disk.</td>
</tr>
</tbody>
</table>
</para>