forked from salt-formulas/salt-formula-ceph
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.rst
879 lines (673 loc) · 26.5 KB
/
README.rst
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
============
Ceph formula
============
Ceph provides extraordinary data storage scalability. Thousands of client
hosts or KVMs accessing petabytes to exabytes of data. Each one of your
applications can use the object, block or file system interfaces to the same
RADOS cluster simultaneously, which means your Ceph storage system serves as a
flexible foundation for all of your data storage needs.
Use salt-formula-linux for initial disk partitioning.
Daemons
--------
Ceph uses several daemons to handle data and cluster state. Each daemon type requires different computing capacity and hardware optimization.
These daemons are currently supported by formula:
* MON (`ceph.mon`)
* OSD (`ceph.osd`)
* RGW (`ceph.radosgw`)
Architecture decisions
-----------------------
Please refer to upstream achritecture documents before designing your cluster. Solid understanding of Ceph principles is essential for making architecture decisions described bellow.
http://docs.ceph.com/docs/master/architecture/
* Ceph version
There is 3 or 4 stable releases every year and many of nighty/dev release. You should decide which version will be used since the only stable releases are recommended for production. Some of the releases are marked LTS (Long Term Stable) and these releases receive bugfixed for longer period - usually until next LTS version is released.
* Number of MON daemons
Use 1 MON daemon for testing, 3 MONs for smaller production clusters and 5 MONs for very large production cluster. There is no need to have more than 5 MONs in normal environment because there isn't any significant benefit in running more than 5 MONs. Ceph require MONS to form quorum so you need to heve more than 50% of the MONs up and running to have fully operational cluster. Every I/O operation will stop once less than 50% MONs is availabe because they can't form quorum.
* Number of PGs
Placement groups are providing mappping between stored data and OSDs. It is necessary to calculate number of PGs because there should be stored decent amount of PGs on each OSD. Please keep in mind *decreasing number of PGs* isn't possible and *increading* can affect cluster performance.
http://docs.ceph.com/docs/master/rados/operations/placement-groups/
http://ceph.com/pgcalc/
* Daemon colocation
It is recommended to dedicate nodes for MONs and RWG since colocation can have and influence on cluster operations. Howerver, small clusters can be running MONs on OSD node but it is critical to have enough of resources for MON daemons because they are the most important part of the cluster.
Installing RGW on node with other daemons isn't recommended because RGW daemon usually require a lot of bandwith and it harm cluster health.
* Store type (Bluestore/Filestore)
Recent version of Ceph support Bluestore as storage backend and backend should be used if available.
http://docs.ceph.com/docs/master/rados/configuration/bluestore-config-ref/
* Block.db location for Bluestore
There are two ways to setup block.db:
* **Colocated** block.db partition is created on the same disk as partition for the data. This setup is easier for installation and it doesn't require any other disk to be used. However, colocated setup is significantly slower than dedicated)
* **Dedicate** block.db is placed on different disk than data (or into partition). This setup can deliver much higher performance than colocated but it require to have more disks in servers. Block.db drives should be carefully selected because high I/O and durability is required.
* Block.wal location for Bluestore
There are two ways to setup block.wal - stores just the internal journal (write-ahead log):
* **Colocated** block.wal uses free space of the block.db device.
* **Dedicate** block.wal is placed on different disk than data (better put into partition as the size can be small) and possibly block.db device. This setup can deliver much higher performance than colocated but it require to have more disks in servers. Block.wal drives should be carefully selected because high I/O and durability is required.
* Journal location for Filestore
There are two ways to setup journal:
* **Colocated** journal is created on the same disk as partition for the data. This setup is easier for installation and it doesn't require any other disk to be used. However, colocated setup is significantly slower than dedicated)
* **Dedicate** journal is placed on different disk than data (or into partition). This setup can deliver much higher performance than colocated but it require to have more disks in servers. Journal drives should be carefully selected because high I/O and durability is required.
* Cluster and public network
Ceph cluster is accessed using network and thus you need to have decend capacity to handle all the client. There are two networks required for cluster: **public** network and cluster network. Public network is used for client connections and MONs and OSDs are listening on this network. Second network ic called **cluster** networks and this network is used for communication between OSDs.
Both networks should have dedicated interfaces, bonding interfaces and dedicating vlans on bonded interfaces isn't allowed. Good practise is dedicate more throughput for the cluster network because cluster traffic is more important than client traffic.
* Pool parameters (size, min_size, type)
You should setup each pool according to it's expected usage, at least `min_size` and `size` and pool type should be considered.
* Cluster monitoring
* Hardware
Please refer to upstream hardware recommendation guide for general information about hardware.
Ceph servers are required to fulfil special requirements becauce load generated by Ceph can be diametrically opposed to common load.
http://docs.ceph.com/docs/master/start/hardware-recommendations/
Basic management commands
------------------------------
Cluster
********
- :code:`ceph health` - check if cluster is healthy (:code:`ceph health detail` can provide more information)
.. code-block:: bash
root@c-01:~# ceph health
HEALTH_OK
- :code:`ceph status` - shows basic information about cluster
.. code-block:: bash
root@c-01:~# ceph status
cluster e2dc51ae-c5e4-48f0-afc1-9e9e97dfd650
health HEALTH_OK
monmap e1: 3 mons at {1=192.168.31.201:6789/0,2=192.168.31.202:6789/0,3=192.168.31.203:6789/0}
election epoch 38, quorum 0,1,2 1,2,3
osdmap e226: 6 osds: 6 up, 6 in
pgmap v27916: 400 pgs, 2 pools, 21233 MB data, 5315 objects
121 GB used, 10924 GB / 11058 GB avail
400 active+clean
client io 481 kB/s rd, 132 kB/s wr, 185 op/
MON
****
http://ceph.com/docs/master/rados/troubleshooting/troubleshooting-mon/
OSD
****
http://ceph.com/docs/master/rados/troubleshooting/troubleshooting-osd/
- :code:`ceph osd tree` - show all OSDs and it's state
.. code-block:: bash
root@c-01:~# ceph osd tree
ID WEIGHT TYPE NAME UP/DOWN REWEIGHT PRIMARY-AFFINITY
-4 0 host c-04
-1 10.79993 root default
-2 3.59998 host c-01
0 1.79999 osd.0 up 1.00000 1.00000
1 1.79999 osd.1 up 1.00000 1.00000
-3 3.59998 host c-02
2 1.79999 osd.2 up 1.00000 1.00000
3 1.79999 osd.3 up 1.00000 1.00000
-5 3.59998 host c-03
4 1.79999 osd.4 up 1.00000 1.00000
5 1.79999 osd.5 up 1.00000 1.00000
- :code:`ceph osd pools ls` - list of pool
.. code-block:: bash
root@c-01:~# ceph osd lspools
0 rbd,1 test
PG
***
http://ceph.com/docs/master/rados/troubleshooting/troubleshooting-pg
- :code:`ceph pg ls` - list placement groups
.. code-block:: bash
root@c-01:~# ceph pg ls | head -n 4
pg_stat objects mip degr misp unf bytes log disklog state state_stamp v reported up up_primary acting acting_primary last_scrub scrub_stamp last_deep_scrub deep_scrub_stamp
0.0 11 0 0 0 0 46137344 3044 3044 active+clean 2015-07-02 10:12:40.603692 226'10652 226:1798 [4,2,0] 4 [4,2,0] 4 0'0 2015-07-01 18:38:33.126953 0'0 2015-07-01 18:17:01.904194
0.1 7 0 0 0 0 25165936 3026 3026 active+clean 2015-07-02 10:12:40.585833 226'5808 226:1070 [2,4,1] 2 [2,4,1] 2 0'0 2015-07-01 18:38:32.352721 0'0 2015-07-01 18:17:01.904198
0.2 18 0 0 0 0 75497472 3039 3039 active+clean 2015-07-02 10:12:39.569630 226'17447 226:3213 [3,1,5] 3 [3,1,5] 3 0'0 2015-07-01 18:38:34.308228 0'0 2015-07-01 18:17:01.904199
- :code:`ceph pg map 1.1` - show mapping between PG and OSD
.. code-block:: bash
root@c-01:~# ceph pg map 1.1
osdmap e226 pg 1.1 (1.1) -> up [5,1,2] acting [5,1,2]
Sample pillars
==============
Common metadata for all nodes/roles
.. code-block:: yaml
ceph:
common:
version: luminous
cluster_name: ceph
config:
global:
param1: value1
param2: value1
param3: value1
pool_section:
param1: value2
param2: value2
param3: value2
fsid: a619c5fc-c4ed-4f22-9ed2-66cf2feca23d
members:
- name: cmn01
host: 10.0.0.1
- name: cmn02
host: 10.0.0.2
- name: cmn03
host: 10.0.0.3
keyring:
admin:
caps:
mds: "allow *"
mgr: "allow *"
mon: "allow *"
osd: "allow *"
bootstrap-osd:
caps:
mon: "allow profile bootstrap-osd"
Optional definition for cluster and public networks. Cluster network is used
for replication. Public network for front-end communication.
.. code-block:: yaml
ceph:
common:
version: luminous
fsid: a619c5fc-c4ed-4f22-9ed2-66cf2feca23d
....
public_network: 10.0.0.0/24, 10.1.0.0/24
cluster_network: 10.10.0.0/24, 10.11.0.0/24
Ceph mon (control) roles
------------------------
Monitors: A Ceph Monitor maintains maps of the cluster state, including the
monitor map, the OSD map, the Placement Group (PG) map, and the CRUSH map.
Ceph maintains a history (called an “epoch”) of each state change in the Ceph
Monitors, Ceph OSD Daemons, and PGs.
.. code-block:: yaml
ceph:
common:
config:
mon:
key: value
mon:
enabled: true
keyring:
mon:
caps:
mon: "allow *"
admin:
caps:
mds: "allow *"
mgr: "allow *"
mon: "allow *"
osd: "allow *"
Ceph mgr roles
------------------------
The Ceph Manager daemon (ceph-mgr) runs alongside monitor daemons, to provide additional monitoring and interfaces to external monitoring and management systems. Since the 12.x (luminous) Ceph release, the ceph-mgr daemon is required for normal operations. The ceph-mgr daemon is an optional component in the 11.x (kraken) Ceph release.
By default, the manager daemon requires no additional configuration, beyond ensuring it is running. If there is no mgr daemon running, you will see a health warning to that effect, and some of the other information in the output of ceph status will be missing or stale until a mgr is started.
.. code-block:: yaml
ceph:
mgr:
enabled: true
dashboard:
enabled: true
host: 10.103.255.252
port: 7000
Ceph OSD (storage) roles
------------------------
.. code-block:: yaml
ceph:
common:
version: luminous
fsid: a619c5fc-c4ed-4f22-9ed2-66cf2feca23d
public_network: 10.0.0.0/24, 10.1.0.0/24
cluster_network: 10.10.0.0/24, 10.11.0.0/24
keyring:
bootstrap-osd:
caps:
mon: "allow profile bootstrap-osd"
....
osd:
enabled: true
crush_parent: rack01
journal_size: 20480 (20G)
bluestore_block_db_size: 10073741824 (10G)
bluestore_block_wal_size: 10073741824 (10G)
bluestore_block_size: 807374182400 (800G)
backend:
filestore:
disks:
- dev: /dev/sdm
enabled: false
journal: /dev/ssd
journal_partition: 5
data_partition: 6
lockbox_partition: 7
data_partition_size: 12000 (MB)
class: bestssd
weight: 1.666
dmcrypt: true
journal_dmcrypt: false
- dev: /dev/sdf
journal: /dev/ssd
journal_dmcrypt: true
class: bestssd
weight: 1.666
- dev: /dev/sdl
journal: /dev/ssd
class: bestssd
weight: 1.666
bluestore:
disks:
- dev: /dev/sdb
- dev: /dev/sdf
block_db: /dev/ssd
block_wal: /dev/ssd
block_db_dmcrypt: true
block_wal_dmcrypt: true
- dev: /dev/sdc
block_db: /dev/ssd
block_wal: /dev/ssd
data_partition: 1
block_partition: 2
lockbox_partition: 5
block_db_partition: 3
block_wal_partition: 4
class: ssd
weight: 1.666
dmcrypt: true
block_db_dmcrypt: false
block_wal_dmcrypt: false
- dev: /dev/sdd
enabled: false
Ceph client roles - ...Deprecated - use ceph:common instead
--------------------------------------------------------
Simple ceph client service
.. code-block:: yaml
ceph:
client:
config:
global:
mon initial members: ceph1,ceph2,ceph3
mon host: 10.103.255.252:6789,10.103.255.253:6789,10.103.255.254:6789
keyring:
monitoring:
key: 00000000000000000000000000000000000000==
At OpenStack control settings are usually located at cinder-volume or glance-
registry services.
.. code-block:: yaml
ceph:
client:
config:
global:
fsid: 00000000-0000-0000-0000-000000000000
mon initial members: ceph1,ceph2,ceph3
mon host: 10.103.255.252:6789,10.103.255.253:6789,10.103.255.254:6789
osd_fs_mkfs_arguments_xfs:
osd_fs_mount_options_xfs: rw,noatime
network public: 10.0.0.0/24
network cluster: 10.0.0.0/24
osd_fs_type: xfs
osd:
osd journal size: 7500
filestore xattr use omap: true
mon:
mon debug dump transactions: false
keyring:
cinder:
key: 00000000000000000000000000000000000000==
glance:
key: 00000000000000000000000000000000000000==
Ceph gateway
------------
Rados gateway with keystone v2 auth backend
.. code-block:: yaml
ceph:
radosgw:
enabled: true
hostname: gw.ceph.lab
bind:
address: 10.10.10.1
port: 8080
identity:
engine: keystone
api_version: 2
host: 10.10.10.100
port: 5000
user: admin
password: password
tenant: admin
Rados gateway with keystone v3 auth backend
.. code-block:: yaml
ceph:
common:
config:
rgw:
key: value
radosgw:
enabled: true
hostname: gw.ceph.lab
bind:
address: 10.10.10.1
port: 8080
identity:
engine: keystone
api_version: 3
host: 10.10.10.100
port: 5000
user: admin
password: password
project: admin
domain: default
swift:
versioning:
enabled: true
Ceph setup role
---------------
Replicated ceph storage pool
.. code-block:: yaml
ceph:
setup:
pool:
replicated_pool:
pg_num: 256
pgp_num: 256
type: replicated
crush_rule: sata
application: rbd
.. note:: For Kraken and earlier releases please specify crush_rule as a ruleset number.
For Kraken and earlier releases application param is not needed.
Erasure ceph storage pool
.. code-block:: yaml
ceph:
setup:
pool:
erasure_pool:
pg_num: 256
pgp_num: 256
type: erasure
crush_rule: ssd
application: rbd
Inline compression for Bluestore backend
.. code-block:: yaml
ceph:
setup:
pool:
volumes:
pg_num: 256
pgp_num: 256
type: replicated
crush_rule: hdd
application: rbd
compression_algorithm: snappy
compression_mode: aggressive
compression_required_ratio: .875
...
Ceph manage keyring keys
------------------------
Keyrings are dynamically generated unless specified by the following pillar.
.. code-block:: yaml
ceph:
common:
manage_keyring: true
keyring:
glance:
name: images
key: AACf3ulZFFPNDxAAd2DWds3aEkHh4IklZVgIaQ==
caps:
mon: "allow r"
osd: "allow class-read object_prefix rdb_children, allow rwx pool=images"
Generate CRUSH map - Recommended way
-----------------------------------
It is required to define the `type` for crush buckets and these types must start with `root` (top) and end with `host`. OSD daemons will be assigned to hosts according to it's hostname. Weight of the buckets will be calculated according to weight of it's children.
If the pools that are in use have size of 3 it is best to have 3 children of a specific type in the root CRUSH tree to replicate objects across (Specified in rule steps by 'type region').
.. code-block:: yaml
ceph:
setup:
crush:
enabled: True
tunables:
choose_total_tries: 50
choose_local_tries: 0
choose_local_fallback_tries: 0
chooseleaf_descend_once: 1
chooseleaf_vary_r: 1
chooseleaf_stable: 1
straw_calc_version: 1
allowed_bucket_algs: 54
type:
- root
- region
- rack
- host
- osd
root:
- name: root-ssd
- name: root-sata
region:
- name: eu-1
parent: root-sata
- name: eu-2
parent: root-sata
- name: eu-3
parent: root-ssd
- name: us-1
parent: root-sata
rack:
- name: rack01
parent: eu-1
- name: rack02
parent: eu-2
- name: rack03
parent: us-1
rule:
sata:
ruleset: 0
type: replicated
min_size: 1
max_size: 10
steps:
- take take root-ssd
- chooseleaf firstn 0 type region
- emit
ssd:
ruleset: 1
type: replicated
min_size: 1
max_size: 10
steps:
- take take root-sata
- chooseleaf firstn 0 type region
- emit
Generate CRUSH map - Alternative way
------------------------------------
It's necessary to create per OSD pillar.
.. code-block:: yaml
ceph:
osd:
crush:
- type: root
name: root1
- type: region
name: eu-1
- type: rack
name: rack01
- type: host
name: osd001
Add OSDs with specific weight
-----------------------------
Add OSD device(s) with initial weight set specifically to certain value.
.. code-block:: yaml
ceph:
osd:
crush_initial_weight: 0
Apply CRUSH map
---------------
Before you apply CRUSH map please make sure that settings in generated file in /etc/ceph/crushmap are correct.
.. code-block:: yaml
ceph:
setup:
crush:
enforce: true
pool:
images:
crush_rule: sata
application: rbd
volumes:
crush_rule: sata
application: rbd
vms:
crush_rule: ssd
application: rbd
.. note:: For Kraken and earlier releases please specify crush_rule as a ruleset number.
For Kraken and earlier releases application param is not needed.
Persist CRUSH map
--------------------
After the CRUSH map is applied to Ceph it's recommended to persist the same settings even after OSD reboots.
.. code-block:: yaml
ceph:
osd:
crush_update: false
Ceph monitoring
---------------
By default monitoring is setup to collect information from MON and OSD nodes. To change the default values add the following pillar to MON nodes.
.. code-block:: yaml
ceph:
monitoring:
space_used_warning_threshold: 0.75
space_used_critical_threshold: 0.85
apply_latency_threshold: 0.007
commit_latency_threshold: 0.7
pool:
vms:
pool_space_used_utilization_warning_threshold: 0.75
pool_space_used_critical_threshold: 0.85
pool_write_ops_threshold: 200
pool_write_bytes_threshold: 70000000
pool_read_bytes_threshold: 70000000
pool_read_ops_threshold: 1000
images:
pool_space_used_utilization_warning_threshold: 0.50
pool_space_used_critical_threshold: 0.95
pool_write_ops_threshold: 100
pool_write_bytes_threshold: 50000000
pool_read_bytes_threshold: 50000000
pool_read_ops_threshold: 500
Ceph monitor backups
--------------------
Backup client with ssh/rsync remote host
.. code-block:: yaml
ceph:
backup:
client:
enabled: true
full_backups_to_keep: 3
hours_before_full: 24
target:
host: cfg01
backup_dir: server-backup-dir
Backup client with local backup only
.. code-block:: yaml
ceph:
backup:
client:
enabled: true
full_backups_to_keep: 3
hours_before_full: 24
Backup client at exact times:
..code-block:: yaml
ceph:
backup:
client:
enabled: true
full_backups_to_keep: 3
incr_before_full: 3
backup_times:
day_of_week: 0
hour: 4
minute: 52
compression: true
compression_threads: 2
database:
user: user
password: password
target:
host: host01
.. note:: Parameters in ``backup_times`` section can be used to set up exact
time the cron job should be executed. In this example, the backup job
would be executed every Sunday at 4:52 AM. If any of the individual
``backup_times`` parameters is not defined, the defalut ``*`` value will be
used. For example, if minute parameter is ``*``, it will run the backup every minute,
which is ususally not desired.
Available parameters are ``day_of_week``, ``day_of_month``, ``month``, ``hour`` and ``minute``.
Please see the crontab reference for further info on how to set these parameters.
.. note:: Please be aware that only ``backup_times`` section OR
``hours_before_full(incr)`` can be defined. If both are defined,
the ``backup_times`` section will be peferred.
.. note:: New parameter ``incr_before_full`` needs to be defined. This
number sets number of incremental backups to be run, before a full backup
is performed.
Backup server rsync
.. code-block:: yaml
ceph:
backup:
server:
enabled: true
hours_before_full: 24
full_backups_to_keep: 5
key:
ceph_pub_key:
enabled: true
key: ssh_rsa
Backup server without strict client restriction
.. code-block:: yaml
ceph:
backup:
restrict_clients: false
Backup server at exact times:
..code-block:: yaml
ceph:
backup:
server:
enabled: true
full_backups_to_keep: 3
incr_before_full: 3
backup_dir: /srv/backup
backup_times:
day_of_week: 0
hour: 4
minute: 52
key:
ceph_pub_key:
enabled: true
key: key
.. note:: Parameters in ``backup_times`` section can be used to set up exact
time the cron job should be executed. In this example, the backup job
would be executed every Sunday at 4:52 AM. If any of the individual
``backup_times`` parameters is not defined, the defalut ``*`` value will be
used. For example, if minute parameter is ``*``, it will run the backup every minute,
which is ususally not desired.
Available parameters are ``day_of_week``, ``day_of_month``, ``month``, ``hour`` and ``minute``.
Please see the crontab reference for further info on how to set these parameters.
.. note:: Please be aware that only ``backup_times`` section OR
``hours_before_full(incr)`` can be defined. If both are defined, The
``backup_times`` section will be peferred.
.. note:: New parameter ``incr_before_full`` needs to be defined. This
number sets number of incremental backups to be run, before a full backup
is performed.
Migration from Decapod to salt-formula-ceph
--------------------------------------------
The following configuration will run a python script which will generate ceph config and osd disk mappings to be put in cluster model.
.. code-block:: yaml
ceph:
decapod:
ip: 192.168.1.10
user: user
password: psswd
deploy_config_name: ceph
More information
================
* https://github.com/cloud-ee/ceph-salt-formula
* http://ceph.com/ceph-storage/
* http://ceph.com/docs/master/start/intro/
Documentation and bugs
======================
To learn how to install and update salt-formulas, consult the documentation
available online at:
http://salt-formulas.readthedocs.io/
In the unfortunate event that bugs are discovered, they should be reported to
the appropriate issue tracker. Use Github issue tracker for specific salt
formula:
https://github.com/salt-formulas/salt-formula-ceph/issues
For feature requests, bug reports or blueprints affecting entire ecosystem,
use Launchpad salt-formulas project:
https://launchpad.net/salt-formulas
You can also join salt-formulas-users team and subscribe to mailing list:
https://launchpad.net/~salt-formulas-users
Developers wishing to work on the salt-formulas projects should always base
their work on master branch and submit pull request against specific formula.
https://github.com/salt-formulas/salt-formula-ceph
Any questions or feedback is always welcome so feel free to join our IRC
channel:
#salt-formulas @ irc.freenode.net