Feature #10767
opensimplify the ceph-deploy suite
0%
Description
The current ceph-deploy suite requires 9 nodes to complete it's tests. Because of this it typically eats up a ton of lab resources waiting on those nodes. At the time of this ticket there is a ceph-deploy run that's using 18 workers, all of which that have been waiting for over 9 hours. http://pulpito.ceph.redhat.com/teuthology-2015-02-03_01:10:01-ceph-deploy-firefly-distro-basic-magna/
Alfredo thinks this can be simplified quite a bit and only test specific things that ceph-deploy does.
- set up a cluster and install monitor
- set up a cluster and install monitors + OSDs
- set up a cluster, install monitors and then add another monitor
Updated by Alfredo Deza over 9 years ago
All of these subcommands should get tested. Minimal cluster needed for all of these (whatever minimal means, I think 3 a the moment?):
new Start deploying a new cluster, and write a
CLUSTER.conf and keyring for it.
install Install Ceph packages on remote hosts.
mds Deploy ceph MDS on remote hosts.
mon Deploy ceph monitor on remote hosts.
gatherkeys Gather authentication keys for provisioning new nodes.
disk Manage disks on a remote host.
osd Prepare a data disk on remote host.
admin Push configuration and client.admin key to a remote
host.
config Push configuration file to a remote host.
uninstall Remove Ceph packages from remote hosts.
purgedata Purge (delete, destroy, discard, shred) any Ceph data
from /var/lib/ceph
purge Remove Ceph packages from remote hosts and purge all
data.
forgetkeys Remove authentication keys from the local directory.
pkg Manage packages on remote hosts.
calamari Install and configure Calamari nodes
Each of those subcommands means at least one test.
There are other things the we currently don't have tests for like the `ssh` magic where we create keys and copy them, but that may be tricky to test since we need user input.