13%
30.11.2025
"
05
06 signing_ca_path "/var/chef/ca"
07 couchdb_database 'chef'
08
09 cookbook_path [ "/var/chef/cookbooks", "/var/chef/site-cookbooks" ]
10
11 file_cache_path "/var/chef/cache"
12 node
13%
30.11.2025
/ceph/$name.keyring
04 [mon]
05 mon data = /srv/mon.$id
06 [mds]
07 [osd]
08 osd data = /srv/osd.$id
09 osd journal = /srv/osd.$id.journal
10 osd journal size = 1000
11 [mon.a]
12 host = alice
13 mon
13%
30.11.2025
Scenarios:
21 cucumber /usr/lib/nagios/plugins/cucumber-nagios/checks/features/www.xing.com/startpage.feature:4 # Scenario: Visiting home page
22
23 1 scenario (1 failed)
24 4 steps (1 failed, 3 skipped)
25 0
13%
30.11.2025
were delivered as part of the RHCS scope. Thus, up to RHCS 3.0, everything was fine if you wanted Pacemaker and GFS to cooperate.
But Red Hat changed its policy in Red Hat Cluster Suite 3.1, deciding
13%
31.10.2025
of options, including dual four-core Xeon, dual six-core Xeon, or quad 12-core AMD processors ranging in speed from 2.2 to 2.9GHz with 24 to 128GB of RAM per server and up to 1TB of scratch local storage per
