Dear All,
This email is about
$ ceph-deploy osd create ceph-node4:vdb
and it not behaving identically too:
$ ceph-deploy osd prepare ceph-node2:vdb
$ ceph-deploy osd activate ceph-node2:vdb1
It is my understanding that the following sequence should deploy ceph
correctly and activate an OSD.
(on ceph setup server)
$ ceph-deploy install ceph-node4
$ ceph-deploy new ceph-node2
$ ceph-deploy mon create-initial ceph-node2
(On actual node)
# /etc/init.d/ceph start
(on ceph setup server)
$ ceph-deploy osd prepare ceph-node2:vdb
$ ceph-deploy osd activate ceph-node2:vdb1
and that the last two commands above can be replaced with:
(on ceph setup server)
$ ceph-deploy osd create ceph-node4:vdb
and behind the scenes udev does the second process of activation rather
than use the command:
(On actual node)
# ceph-disk-activate --mark-init ${distro_init} --mount ${disk}
it executes:
(On actual node)
# udevadm trigger --subsystem-match=block --action=add
Is their a logic for the reason why
$ ceph-deploy osd create ceph-node4:vdb
Is described as both "prepare" and "activate" but in fact a different
command? Would you like a patch to make the code really do the same
thing, or am I missing some important deployment logic?
Best regards
Owen
PS:
Goes off to look at why the udev rules are failing and caused me to
notice this discrepancy.
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
