This can be used to test if mon hosts and
mon initial members are being set properly with
multiple hosts.
Also, to verify that monitor_address and monitor_interface
options both work as described.
Signed-off-by: Andrew Schoen <aschoen@redhat.com>
Resolves: testing#updates
--- /dev/null
+../../../../../Vagrantfile
\ No newline at end of file
--- /dev/null
+---
+
+ceph_stable: True
+public_network: "192.168.42.0/24"
+cluster_network: "192.168.43.0/24"
+journal_size: 100
+devices:
+ - '/dev/sdb'
+ - '/dev/sdc'
+journal_collocation: True
+os_tuning_params:
+ - { name: kernel.pid_max, value: 4194303 }
+ - { name: fs.file-max, value: 26234859 }
--- /dev/null
+---
+os_tuning_params:
+ - { name: kernel.pid_max, value: 4194303 }
+ - { name: fs.file-max, value: 26234859 }
--- /dev/null
+[mons]
+mon0 monitor_address=192.168.42.10
+mon1 monitor_address=192.168.42.11
+mon2 monitor_interface=eth1
--- /dev/null
+# Basic information about ceph and its configuration
+ceph = {
+ 'releases': ['infernalis', 'jewel'],
+ 'cluster_name': 'ceph'
+}
+
+# remote nodes to test, with anything specific to them that might be useful for
+# tests to get. Each one of these can get requested as a py.test fixture to
+# validate information.
+nodes = {
+ 'mon0': {
+ 'username': 'vagrant',
+ 'components': ['conf_tests']
+ },
+ 'mon1': {
+ 'username': 'vagrant',
+ 'components': ['conf_tests']
+ },
+ 'mon2': {
+ 'username': 'vagrant',
+ 'components': ['conf_tests']
+ },
+}