/
objectstorageadmin.xml
2210 lines (2104 loc) · 124 KB
/
objectstorageadmin.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="UTF-8"?>
<chapter xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:id="ch_running-openstack-object-storage">
<title>System Administration for OpenStack Object Storage</title>
<para>By understanding the concepts inherent to the Object Storage system you can better monitor and administer your storage solution. </para>
<section xml:id="understanding-how-object-storage-works">
<title>Understanding How Object Storage Works</title>
<para>This section offers a brief overview of each concept in administering Object Storage. </para>
<simplesect xml:id="the-ring"><title>The Ring</title>
<para>A ring represents a mapping between the names of entities stored on disk and their physical location. There are separate rings for accounts, containers, and objects. When other components need to perform any operation on an object, container, or account, they need to interact with the appropriate ring to determine its location in the cluster.
</para>
<para>The Ring maintains this mapping using zones, devices, partitions, and replicas. Each partition in the ring is replicated, by default, 3 times across the cluster, and the locations for a partition are stored in the mapping maintained by the ring. The ring is also responsible for determining which devices are used for handoff in failure scenarios.</para>
<para>Data can be isolated with the concept of zones in the ring. Each replica of a partition is guaranteed to reside in a different zone. A zone could represent a drive, a server, a cabinet, a switch, or even a datacenter.</para>
<para>The partitions of the ring are equally divided among all the devices in the OpenStack Object Storage installation. When partitions need to be moved around (for example if a device is added to the cluster), the ring ensures that a minimum number of partitions are moved at a time, and only one replica of a partition is moved at a time.</para>
<para>Weights can be used to balance the distribution of partitions on drives across the cluster. This can be useful, for example, when different sized drives are used in a cluster.</para>
<para>The ring is used by the Proxy server and several background processes (like replication).</para></simplesect>
<simplesect><title>Proxy Server</title>
<para>The Proxy Server is responsible for tying together the rest of the OpenStack Object Storage architecture. For each request, it will look up the location of the account, container, or object in the ring (see below) and route the request accordingly. The public API is also exposed through the Proxy Server.
</para>
<para>A large number of failures are also handled in the Proxy Server. For example, if a
server is unavailable for an object PUT, it will ask the ring for a hand-off server
and route there instead. </para>
<para>When objects are streamed to or from an object server, they are streamed directly through the proxy server to or from the user – the proxy server does not spool them.</para>
<para>You can use a proxy server with account management enabled by configuring it in
the proxy server configuration file.</para></simplesect>
<simplesect xml:id="object-server"><title>Object Server</title>
<para>The Object Server is a very simple blob storage server that can store, retrieve and delete objects stored on local devices. Objects are stored as binary files on the filesystem with metadata stored in the file’s extended attributes (xattrs). This requires that the underlying filesystem choice for object servers support xattrs on files. Some filesystems, like ext3, have xattrs turned off by default.</para>
<para>Each object is stored using a path derived from the object name’s hash and the operation’s timestamp. Last write always wins, and ensures that the latest object version will be served. A deletion is also treated as a version of the file (a 0 byte file ending with “.ts”, which stands for tombstone). This ensures that deleted files are replicated correctly and older versions don’t magically reappear due to failure scenarios.</para>
</simplesect>
<simplesect xml:id="container-server"><title>Container Server</title>
<para>The Container Server’s primary job is to handle listings of objects. It doesn’t know where those object’s are, just what objects are in a specific container. The listings are stored as sqlite database files, and replicated across the cluster similar to how objects are. Statistics are also tracked that include the total number of objects, and total storage usage for that container.</para>
</simplesect>
<simplesect><title>Account Server</title>
<para>The Account Server is very similar to the Container Server, excepting that it is
responsible for listings of containers rather than objects.</para>
</simplesect>
<simplesect xml:id="swift-replication"> <title>Replication</title>
<para>Replication is designed to keep the system in a consistent state in the face of temporary error conditions like network outages or drive failures.
</para>
<para>The replication processes compare local data with each remote copy to ensure they all contain the latest version. Object replication uses a hash list to quickly compare subsections of each partition, and container and account replication use a combination of hashes and shared high water marks.
</para>
<para>Replication updates are push based. For object replication, updating is just a matter of rsyncing files to the peer. Account and container replication push missing records over HTTP or rsync whole database files.
</para>
<para>The replicator also ensures that data is removed from the system. When an item (object, container, or account) is deleted, a tombstone is set as the latest version of the item. The replicator will see the tombstone and ensure that the item is removed from the entire system.
</para></simplesect>
<simplesect xml:id="updaters"><title>Updaters</title>
<para>There are times when container or account data can not be immediately updated.
This usually occurs during failure scenarios or periods of high load. If an update
fails, the update is queued locally on the file system, and the updater will process
the failed updates. This is where an eventual consistency window will most likely
come in to play. For example, suppose a container server is under load and a new
object is put in to the system. The object will be immediately available for reads
as soon as the proxy server responds to the client with success. However, the
container server did not update the object listing, and so the update would be
queued for a later update. Container listings, therefore, may not immediately
contain the object. </para>
<para>In practice, the consistency window is only as large as the frequency at which the updater runs and may not even be noticed as the proxy server will route listing requests to the first container server which responds. The server under load may not be the one that serves subsequent listing requests – one of the other two replicas may handle the listing.</para>
</simplesect>
<simplesect xml:id="auditors"><title>Auditors</title>
<para>Auditors crawl the local server checking the integrity of the objects, containers, and accounts. If corruption is found (in the case of bit rot, for example), the file is quarantined, and replication will replace the bad file from another replica. If other errors are found they are logged (for example, an object’s listing can’t be found on any container server it should be).
</para></simplesect>
</section>
<section xml:id="configuring-and-tuning-openstack-object-storage">
<title>Configuring and Tuning OpenStack Object Storage</title>
<para>This section walks through deployment options and considerations.</para>
<para>You have multiple deployment options to choose from. The swift services run completely autonomously, which provides for a lot of flexibility when
designing the hardware deployment for swift. The 4 main services are:</para>
<itemizedlist>
<listitem><para>Proxy Services</para></listitem>
<listitem><para>Object Services</para></listitem>
<listitem><para>Container Services</para></listitem>
<listitem><para>Account Services</para></listitem>
</itemizedlist>
<para>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.</para>
<para>The Object, Container, and Account Services (Storage Services) are more disk
and network I/O intensive.</para>
<para>The easiest deployment is to install all services on each server. There is
nothing wrong with doing this, as it scales each service out horizontally.</para>
<para>At Rackspace, we put the Proxy Services on their own servers and all of the
Storage Services on the same server. This allows us to send 10g networking to
the proxy and 1g to the storage servers, and keep load balancing to the
proxies more manageable. Storage Services scale out horizontally as storage
servers are added, and we can scale overall API throughput by adding more
Proxies.</para>
<para>If you need more throughput to either Account or Container Services, they may
each be deployed to their own servers. For example you might use faster (but
more expensive) SAS or even SSD drives to get faster disk I/O to the databases.</para>
<para>Load balancing and network design is left as an exercise to the reader,
but this is a very important part of the cluster, so time should be spent
designing the network for a Swift cluster.</para>
</section>
<section xml:id="preparing-the-ring">
<title>Preparing the Ring</title>
<note><title>Note</title><para>"Partition" in this section refers to the logical
partitions of the swift ring - not physical partitions on Storage node drives.
You should setup your Storage Node disk partitions with one physical partition
per disk, as per the
<link linkend="installing-and-configuring-storage-nodes">installation instructions</link>
.</para></note>
<para>The first step is to determine the number of partitions that will be in the
ring. We recommend that there be a minimum of 100 partitions per drive to
insure even distribution across the drives. A good starting point might be
to figure out the maximum number of drives the cluster will contain, and then
multiply by 100, and then round up to the nearest power of two.</para>
<para>For example, imagine we are building a cluster that will have no more than
5,000 drives. That would mean that we would have a total number of 500,000
partitions, which is pretty close to 2^19, rounded up.</para>
<para>It is also a good idea to keep the number of partitions small (relatively).
The more partitions there are, the more work that has to be done by the
replicators and other backend jobs and the more memory the rings consume in
process. The goal is to find a good balance between small rings and maximum
cluster size.</para>
<para>The next step is to determine the number of replicas to store of the data.
Currently it is recommended to use 3 (as this is the only value that has
been tested). The higher the number, the more storage that is used but the
less likely you are to lose data.</para>
<para>It is also important to determine how many zones the cluster should have. It is
recommended to start with a minimum of 5 zones. You can start with fewer, but
our testing has shown that having at least five zones is optimal when failures
occur. We also recommend trying to configure the zones at as high a level as
possible to create as much isolation as possible. Some example things to take
into consideration can include physical location, power availability, and
network connectivity. For example, in a small cluster you might decide to
split the zones up by cabinet, with each cabinet having its own power and
network connectivity. The zone concept is very abstract, so feel free to use
it in whatever way best isolates your data from failure. Zones are referenced
by number, beginning with 1.</para>
<para>You can now start building the ring with:</para>
<literallayout>swift-ring-builder <builder_file> create <part_power> <replicas> <min_part_hours></literallayout>
<para>This will start the ring build process creating the <builder_file> with
2^<part_power> partitions. <min_part_hours> is the time in hours before a
specific partition can be moved in succession (24 is a good value for this).</para>
<para>Devices can be added to the ring with:</para>
<literallayout>swift-ring-builder <builder_file> add z<zone>-<ip>:<port>/<device_name>_<meta> <weight></literallayout>
<para>This will add a device to the ring where <builder_file> is the name of the
builder file that was created previously, <zone> is the number of the zone
this device is in, <ip> is the ip address of the server the device is in,
<port> is the port number that the server is running on, <device_name> is
the name of the device on the server (for example: sdb1), <meta> is a string
of metadata for the device (optional), and <weight> is a float weight that
determines how many partitions are put on the device relative to the rest of
the devices in the cluster (a good starting point is 100.0 x TB on the drive).
Add each device that will be initially in the cluster.</para>
<para>Once all of the devices are added to the ring, run:</para>
<literallayout>swift-ring-builder <builder_file> rebalance</literallayout>
<para>This will distribute the partitions across the drives in the ring. It is
important whenever making changes to the ring to make all the changes
required before running rebalance. This will ensure that the ring stays as
balanced as possible, and as few partitions are moved as possible.</para>
<para>The above process should be done to make a ring for each storage service
(Account, Container and Object). The builder files will be needed in future
changes to the ring, so it is very important that these be kept and backed up.
The resulting .tar.gz ring file should be pushed to all of the servers in the
cluster. For more information about building rings, running
swift-ring-builder with no options will display help text with available
commands and options. </para>
</section>
<section xml:id="server-configuration-reference">
<title>Server Configuration Reference</title>
<para>Swift uses paste.deploy to manage server configurations. Default configuration
options are set in the <code>[DEFAULT]</code> section, and any options specified there
can be overridden in any of the other sections.</para>
<section xml:id="object-server-configuration">
<title>Object Server Configuration</title>
<para>An Example Object Server configuration can be found at
etc/object-server.conf-sample in the source code repository.</para>
<para>The following configuration options are available:</para>
<table rules="all">
<caption>object-server.conf Default Options in the [DEFAULT] section</caption>
<tbody>
<tr>
<td>Option</td>
<td>Default</td>
<td>Description</td>
</tr>
<tr>
<td>swift_dir</td>
<td>/etc/swift</td>
<td>Swift configuration directory</td>
</tr>
<tr>
<td>devices</td>
<td>/srv/node</td>
<td>Parent directory of where devices are mounted</td>
</tr>
<tr>
<td>mount_check</td>
<td>true</td>
<td>Whether or not check if the devices are mounted to prevent accidentally
writing to the root device</td>
</tr>
<tr>
<td>bind_ip</td>
<td>0.0.0.0</td>
<td>IP Address for server to bind to</td>
</tr>
<tr>
<td>bind_port</td>
<td>6000</td>
<td>Port for server to bind to</td>
</tr>
<tr>
<td>workers</td>
<td>1</td>
<td>Number of workers to fork</td>
</tr>
<tr>
<td>backlog</td>
<td>4096</td>
<td>Maximum number of allowed pending TCP connections.</td>
</tr>
<tr>
<td>expiring_objects_container_divisor</td>
<td>86400</td>
<td></td>
</tr>
<tr>
<td>log_name</td>
<td>swift</td>
<td>Label used when logging</td>
</tr>
<tr>
<td>log_facility</td>
<td>LOG_LOCAL0</td>
<td>Syslog log facility</td>
</tr>
<tr>
<td>log_level</td>
<td>INFO</td>
<td>Logging level</td>
</tr>
<tr>
<td>user</td>
<td>swift</td>
<td>User to run as</td>
</tr>
</tbody>
</table>
<table rules="all">
<caption>object-server.conf Server Options in the [object-server] section</caption>
<tbody>
<tr>
<td>Option</td>
<td>Default</td>
<td>Description</td>
</tr>
<tr>
<td>use</td>
<td> </td>
<td>paste.deploy entry point for the object server. For most cases, this
should be <code>egg:swift#object</code>.</td>
</tr>
<tr>
<td>log_name</td>
<td>object-server</td>
<td>Label used when logging</td>
</tr>
<tr>
<td>log_facility</td>
<td>LOG_LOCAL0</td>
<td>Syslog log facility</td>
</tr>
<tr>
<td>log_level</td>
<td>INFO</td>
<td>Logging level</td>
</tr>
<tr>
<td>log_requests</td>
<td>True</td>
<td>Whether or not to log each request</td>
</tr>
<tr>
<td>user</td>
<td>swift</td>
<td>User to run as</td>
</tr>
<tr>
<td>node_timeout</td>
<td>3</td>
<td>Request timeout to external services</td>
</tr>
<tr>
<td>conn_timeout</td>
<td>0.5</td>
<td>Connection timeout to external services</td>
</tr>
<tr>
<td>network_chunk_size</td>
<td>65536</td>
<td>Size of chunks to read/write over the network</td>
</tr>
<tr>
<td>disk_chunk_size</td>
<td>65536</td>
<td>Size of chunks to read/write to disk</td>
</tr>
<tr>
<td>max_upload_time</td>
<td>86400</td>
<td>Maximum time allowed to upload an object</td>
</tr>
<tr>
<td>slow</td>
<td>0</td>
<td>If > 0, Minimum time in seconds for a PUT or DELETE request to
complete</td>
</tr>
<tr>
<td>auto_create_account_prefix</td>
<td>.</td>
<td>prefix used when automatically creating accounts</td>
</tr>
<tr>
<td>allowed_headers</td>
<td>content-disposition, content-encoding, x-delete-at, x-object-manifest,</td>
<td>comma separated list of headers that can be set in metadata of an object</td>
</tr>
<tr>
<td>mb_per_sync</td>
<td>512</td>
<td>on PUTs, sync data every n MB</td>
</tr>
</tbody>
</table>
<table rules="all">
<caption>object-server.conf Replicator Options in the [object-replicator] section</caption>
<tbody>
<tr>
<td>Option</td>
<td>Default</td>
<td>Description</td>
</tr>
<tr>
<td>log_name</td>
<td>object-replicator</td>
<td>Label used when logging</td>
</tr>
<tr>
<td>log_facility</td>
<td>LOG_LOCAL0</td>
<td>Syslog log facility</td>
</tr>
<tr>
<td>log_level</td>
<td>INFO</td>
<td>Logging level</td>
</tr>
<tr>
<td>daemonize</td>
<td>yes</td>
<td>Whether or not to run replication as a daemon</td>
</tr>
<tr>
<td>run_pause</td>
<td>30</td>
<td>Time in seconds to wait between replication passes</td>
</tr>
<tr>
<td>concurrency</td>
<td>1</td>
<td>Number of replication workers to spawn</td>
</tr>
<tr>
<td>timeout</td>
<td>5</td>
<td>Timeout value sent to rsync –timeout and –contimeout
options</td>
</tr>
<tr>
<td>http_timeout</td>
<td>60</td>
<td>Maximum duration for an HTTP request</td>
</tr>
<tr>
<td>lockup_timeout</td>
<td>1800</td>
<td>Attempts to kill all workers if nothing replicates for lockup_timeout seconds.</td>
</tr>
<tr>
<td>stats_interval</td>
<td>300</td>
<td>Interval in seconds between logging replication statistics</td>
</tr>
<tr>
<td>reclaim_age</td>
<td>604800</td>
<td>Time elapsed in seconds before an object can be reclaimed</td>
</tr>
<tr>
<td>recon_cache_path</td>
<td>/var/cache/swift</td>
<td>Directory where stats for a few items will be stored</td>
</tr>
<tr>
<td>recon_enable</td>
<td>no</td>
<td>Enable logging of replication stats for recon</td>
</tr>
<tr>
<td>ring_check_interval</td>
<td>15</td>
<td>How often (in seconds) to check the ring</td>
</tr>
<tr>
<td>rsync_io_timeout</td>
<td>30</td>
<td>Passed to rsync for max duration (seconds) of an I/O op</td>
</tr>
<tr>
<td>rsync_timeout</td>
<td>900</td>
<td>Max duration (seconds) of a partition rsync</td>
</tr>
<tr>
<td>vm_test_mode</td>
<td>no</td>
<td>Indicates that you are using a VM environment</td>
</tr>
</tbody>
</table>
<table rules="all">
<caption>object-server.conf Updater Options in the [object-updater] section</caption>
<tbody>
<tr>
<td>Option</td>
<td>Default</td>
<td>Description</td>
</tr>
<tr>
<td>log_name</td>
<td>object-updater</td>
<td>Label used when logging</td>
</tr>
<tr>
<td>log_facility</td>
<td>LOG_LOCAL0</td>
<td>Syslog log facility</td>
</tr>
<tr>
<td>log_level</td>
<td>INFO</td>
<td>Logging level</td>
</tr>
<tr>
<td>interval</td>
<td>300</td>
<td>Minimum time for a pass to take</td>
</tr>
<tr>
<td>concurrency</td>
<td>1</td>
<td>Number of updater workers to spawn</td>
</tr>
<tr>
<td>node_timeout</td>
<td>10</td>
<td>Request timeout to external services</td>
</tr>
<tr>
<td>conn_timeout</td>
<td>0.5</td>
<td>Connection timeout to external services</td>
</tr>
<tr>
<td>slowdown</td>
<td>0.01</td>
<td>Time in seconds to wait between objects</td>
</tr>
</tbody>
</table>
<table rules="all">
<caption>object-server.conf Auditor Options in the [object-auditor] section</caption>
<tbody>
<tr>
<td>Option</td>
<td>Default</td>
<td>Description</td>
</tr>
<tr>
<td>log_name</td>
<td>object-auditor</td>
<td>Label used when logging</td>
</tr>
<tr>
<td>log_facility</td>
<td>LOG_LOCAL0</td>
<td>Syslog log facility</td>
</tr>
<tr>
<td>log_level</td>
<td>INFO</td>
<td>Logging level</td>
</tr>
<tr>
<td>log_time</td>
<td>3600</td>
<td>Frequency of status logs in seconds.</td>
</tr>
<tr>
<td>files_per_second</td>
<td>20</td>
<td>Maximum files audited per second. Should be tuned according to
individual system specs. 0 is unlimited.</td>
</tr>
<tr>
<td>bytes_per_second</td>
<td>10000000</td>
<td>Maximum bytes audited per second. Should be tuned according to
individual system specs. 0 is unlimited.</td>
</tr>
<tr>
<td>zero_byte_files_per_second</td>
<td>50</td>
<td>Maximum zero byte files audited per second.</td>
</tr>
</tbody>
</table>
</section>
<section xml:id="container-server-configuration">
<title>Container Server Configuration</title>
<para>An example Container Server configuration can be found at
etc/container-server.conf-sample in the source code repository.</para>
<para>The following configuration options are available:</para>
<table rules="all">
<caption>container-server.conf Default Options in the [DEFAULT] section</caption>
<tbody>
<tr>
<td>Option</td>
<td>Default</td>
<td>Description</td>
</tr>
<tr>
<td>swift_dir</td>
<td>/etc/swift</td>
<td>Swift configuration directory</td>
</tr>
<tr>
<td>devices</td>
<td>/srv/node</td>
<td>Parent directory of where devices are mounted</td>
</tr>
<tr>
<td>mount_check</td>
<td>true</td>
<td>Whether or not check if the devices are mounted to prevent accidentally
writing to the root device</td>
</tr>
<tr>
<td>bind_ip</td>
<td>0.0.0.0</td>
<td>IP Address for server to bind to</td>
</tr>
<tr>
<td>bind_port</td>
<td>6001</td>
<td>Port for server to bind to</td>
</tr>
<tr>
<td>workers</td>
<td>1</td>
<td>Number of workers to fork</td>
</tr>
<tr>
<td>user</td>
<td>swift</td>
<td>User to run as</td>
</tr>
</tbody>
</table>
<table rules="all">
<caption>container-server.conf Server Options in the [container-server] section</caption>
<tbody>
<tr>
<td>Option</td>
<td>Default</td>
<td>Description</td>
</tr>
<tr>
<td>use</td>
<td> </td>
<td>paste.deploy entry point for the container server. For most cases, this
should be <code>egg:swift#container</code>.</td>
</tr>
<tr>
<td>log_name</td>
<td>container-server</td>
<td>Label used when logging</td>
</tr>
<tr>
<td>log_facility</td>
<td>LOG_LOCAL0</td>
<td>Syslog log facility</td>
</tr>
<tr>
<td>log_level</td>
<td>INFO</td>
<td>Logging level</td>
</tr>
<tr>
<td>node_timeout</td>
<td>3</td>
<td>Request timeout to external services</td>
</tr>
<tr>
<td>conn_timeout</td>
<td>0.5</td>
<td>Connection timeout to external services</td>
</tr>
</tbody>
</table>
<table rules="all">
<caption>container-server.conf Replicator Options in the [container-replicator] section</caption>
<tbody>
<tr>
<td>Option</td>
<td>Default</td>
<td>Description</td>
</tr>
<tr>
<td>log_name</td>
<td>container-replicator</td>
<td>Label used when logging</td>
</tr>
<tr>
<td>log_facility</td>
<td>LOG_LOCAL0</td>
<td>Syslog log facility</td>
</tr>
<tr>
<td>log_level</td>
<td>INFO</td>
<td>Logging level</td>
</tr>
<tr>
<td>per_diff</td>
<td>1000</td>
<td>Limit number of items to get per diff</td>
</tr>
<tr>
<td>concurrency</td>
<td>8</td>
<td>Number of replication workers to spawn</td>
</tr>
<tr>
<td>run_pause</td>
<td>30</td>
<td>Time in seconds to wait between replication passes</td>
</tr>
<tr>
<td>node_timeout</td>
<td>10</td>
<td>Request timeout to external services</td>
</tr>
<tr>
<td>conn_timeout</td>
<td>0.5</td>
<td>Connection timeout to external services</td>
</tr>
<tr>
<td>reclaim_age</td>
<td>604800</td>
<td>Time elapsed in seconds before a container can be reclaimed</td>
</tr>
</tbody>
</table>
<table rules="all">
<caption>container-server.conf Updater Options in the [container-updater] section</caption>
<tbody>
<tr>
<td>Option</td>
<td>Default</td>
<td>Description</td>
</tr>
<tr>
<td>log_name</td>
<td>container-updater</td>
<td>Label used when logging</td>
</tr>
<tr>
<td>log_facility</td>
<td>LOG_LOCAL0</td>
<td>Syslog log facility</td>
</tr>
<tr>
<td>log_level</td>
<td>INFO</td>
<td>Logging level</td>
</tr>
<tr>
<td>interval</td>
<td>300</td>
<td>Minimum time for a pass to take</td>
</tr>
<tr>
<td>concurrency</td>
<td>4</td>
<td>Number of updater workers to spawn</td>
</tr>
<tr>
<td>node_timeout</td>
<td>3</td>
<td>Request timeout to external services</td>
</tr>
<tr>
<td>conn_timeout</td>
<td>0.5</td>
<td>Connection timeout to external services</td>
</tr>
<tr>
<td>slowdown</td>
<td>0.01</td>
<td>Time in seconds to wait between containers</td>
</tr>
</tbody>
</table>
<table rules="all">
<caption>container-server.conf Auditor Options in the [container-auditor] section</caption>
<tbody>
<tr>
<td>Option</td>
<td>Default</td>
<td>Description</td>
</tr>
<tr>
<td>log_name</td>
<td>container-auditor</td>
<td>Label used when logging</td>
</tr>
<tr>
<td>log_facility</td>
<td>LOG_LOCAL0</td>
<td>Syslog log facility</td>
</tr>
<tr>
<td>log_level</td>
<td>INFO</td>
<td>Logging level</td>
</tr>
<tr>
<td>interval</td>
<td>1800</td>
<td>Minimum time for a pass to take</td>
</tr>
</tbody>
</table>
</section>
<section xml:id="account-server-configuration">
<title>Account Server Configuration</title>
<para>An example Account Server configuration can be found at
etc/account-server.conf-sample in the source code repository.</para>
<para>The following configuration options are available:</para>
<table rules="all">
<caption>account-server.conf Default Options in the [DEFAULT] section</caption>
<tbody>
<tr>
<td>Option</td>
<td>Default</td>
<td>Description</td>
</tr>
<tr>
<td>swift_dir</td>
<td>/etc/swift</td>
<td>Swift configuration directory</td>
</tr>
<tr>
<td>devices</td>
<td>/srv/node</td>
<td>Parent directory or where devices are mounted</td>
</tr>
<tr>
<td>mount_check</td>
<td>true</td>
<td>Whether or not check if the devices are mounted to prevent accidentally
writing to the root device</td>
</tr>
<tr>
<td>bind_ip</td>
<td>0.0.0.0</td>
<td>IP Address for server to bind to</td>
</tr>
<tr>
<td>bind_port</td>
<td>6002</td>
<td>Port for server to bind to</td>
</tr>
<tr>
<td>workers</td>
<td>1</td>
<td>Number of workers to fork</td>
</tr>
<tr>
<td>user</td>
<td>swift</td>
<td>User to run as</td>
</tr>
<tr>
<td>backlog</td>
<td>4096</td>
<td>Maximum number of allowed pending TCP connections.</td>
</tr>
<tr>
<td>db_preallocation</td>
<td>true</td>
<td>preallocate disk space for new SQLite databases to decrease fragmentation</td>
</tr>
</tbody>
</table>
<table rules="all">
<caption>account-server.conf Server Options in the [account-server] section</caption>
<tbody >
<tr>
<td>Option</td>
<td>Default</td>
<td>Description</td>
</tr>
<tr>
<td>use</td>
<td> </td>
<td>Entry point for paste.deploy for the account server. For most cases,
this should be <code>egg:swift#account</code>.</td>
</tr>
<tr>
<td>log_name</td>
<td>account-server</td>
<td>Label used when logging</td>
</tr>
<tr>
<td>log_facility</td>
<td>LOG_LOCAL0</td>
<td>Syslog log facility</td>
</tr>
<tr>
<td>log_level</td>
<td>INFO</td>
<td>Logging level</td>
</tr>
<tr>
<td>log_requests</td>
<td>true</td>
<td>Whether or not to log each request</td>
</tr>
<tr>
<td>auto_create_account_prefix</td>
<td>.</td>
<td>prefix used when automatically creating accounts</td>
</tr>
</tbody>
</table>
<table rules="all">
<caption>account-server.conf Replicator Options in the [account-replicator] section</caption>
<tbody>
<tr>
<td>Option</td>
<td>Default</td>
<td>Description</td>
</tr>
<tr>
<td>log_name</td>
<td>account-replicator</td>
<td>Label used when logging</td>
</tr>
<tr>
<td>log_facility</td>
<td>LOG_LOCAL0</td>
<td>Syslog log facility</td>
</tr>
<tr>
<td>log_level</td>
<td>INFO</td>
<td>Logging level</td>
</tr>
<tr>
<td>per_diff</td>
<td>1000</td>
<td>Limit number of items to get per diff</td>
</tr>
<tr>
<td>max_diffs</td>
<td>100</td>
<td>Caps how long the replicator spends trying to sync a database per pass</td>
</tr>
<tr>
<td>concurrency</td>
<td>8</td>
<td>Number of replication workers to spawn</td>
</tr>
<tr>
<td>run_pause</td>
<td>30</td>
<td>Time in seconds to wait between replication passes</td>
</tr>
<tr>
<td>node_timeout</td>
<td>10</td>
<td>Request timeout to external services</td>
</tr>
<tr>
<td>conn_timeout</td>
<td>0.5</td>
<td>Connection timeout to external services</td>
</tr>
<tr>
<td>reclaim_age</td>
<td>604800</td>
<td>Time elapsed in seconds before an account can be reclaimed</td>
</tr>
<tr>
<td>vm_test_mode</td>
<td>no</td>
<td>Indicates that you are using a VM environment</td>
</tr>
<tr>
<td>interval</td>
<td>30</td>
<td>Minimum time for a pass to take</td>
</tr>
<tr>
<td>error_suppression_interval</td>
<td>60</td>
<td>Time in seconds that must elapse since the last error for a node to be
considered no longer error limited</td>
</tr>
<tr>
<td>error_suppression_limit</td>
<td>10</td>
<td>Error count to consider a node error limited</td>
</tr>
</tbody>
</table>
<table rules="all">
<caption>account-server.conf Auditor Options in the [account-auditor] section</caption>
<tbody>
<tr>
<td>Option</td>
<td>Default</td>
<td>Description</td>
</tr>
<tr>
<td>log_name</td>
<td>account-auditor</td>
<td>Label used when logging</td>
</tr>
<tr>
<td>log_facility</td>
<td>LOG_LOCAL0</td>
<td>Syslog log facility</td>
</tr>
<tr>
<td>log_level</td>
<td>INFO</td>
<td>Logging level</td>
</tr>
<tr>
<td>interval</td>
<td>1800</td>
<td>Minimum time for a pass to take</td>
</tr>
</tbody>