Isn't --allhosts dangerous?

Isn't --allhosts dangerous?

[Nathan Cutler]

Taking actions cluster-wide via a shell script seems like it could have
dangerous unexpected side effects, and indeed while looking through old
tickets, I ran across http://tracker.ceph.com/issues/9407 . . .

This is "fixed" (by getting rid of the --allhosts option to init-ceph)
in https://github.com/ceph/ceph/pull/6089

The same PR also adds getopt to make processing of command-line options
more flexible.

Opinions? Reviews?

-- 
Nathan Cutler
Software Engineer Distributed Storage
SUSE LINUX, s.r.o.
Tel.: +420 284 084 037

Re: Isn't --allhosts dangerous?

[Sage Weil]

On Sun, 27 Sep 2015, Nathan Cutler wrote:
> Taking actions cluster-wide via a shell script seems like it could have
> dangerous unexpected side effects, and indeed while looking through old
> tickets, I ran across http://tracker.ceph.com/issues/9407 . . .
> 
> This is "fixed" (by getting rid of the --allhosts option to init-ceph)
> in https://github.com/ceph/ceph/pull/6089
> 
> The same PR also adds getopt to make processing of command-line options
> more flexible.
> 
> Opinions? Reviews?

I certainly won't miss it, but I suspect a fair number of people use it 
(e.g., service ceph -a start).  The general strategy is to avoid adding 
any such hacks to the newer init system scripts, so as everyone moves to 
systemd this will go away.

sage