I only tried to use the Ceph CLI once out of curiosity, simply because
it is there, but I don't really benefit from it.
Usually when I'm working with clusters it requires a combination of
different commands (rbd, rados, ceph etc.), so this would mean either
exiting and entering the CLI back
Den ons 10 okt. 2018 kl 16:20 skrev John Spray :
> So the question is: does anyone actually use this feature? It's not
> particularly expensive to maintain, but it might be nice to have one
> less path through the code if this is entirely unused.
It can go as far as I am concerned too.
Better
I run 2 clusters and have never purposely executed the interactive cli. I
save remove the code bloat.
On Wed, Oct 10, 2018 at 9:20 AM John Spray wrote:
> Hi all,
>
> Since time immemorial, the Ceph CLI has had a mode where when run with
> no arguments, you just get an interactive prompt that
All uncommon tasks can easily be done using basic shell scripting so I don't
see any practical use for such interface.
> On 10.10.2018, at 17:19, John Spray wrote:
>
> Hi all,
>
> Since time immemorial, the Ceph CLI has had a mode where when run with
> no arguments, you just get an
On Wed, 2018-10-10 at 15:19 +0100, John Spray wrote:
> Since time immemorial, the Ceph CLI has had a mode where when run with
> no arguments, you just get an interactive prompt that lets you run
> commands without "ceph" at the start.
>
> I recently discovered that we actually broke this in
I know that it existed, but I've never bothered using it. In applications
like Python where you can get a different reaction by interacting with it
line by line and setting up an environment it is very helpful. Ceph,
however, doesn't have any such environment variables that would make this
more
Hi all,
Since time immemorial, the Ceph CLI has had a mode where when run with
no arguments, you just get an interactive prompt that lets you run
commands without "ceph" at the start.
I recently discovered that we actually broke this in Mimic[1], and it
seems that nobody noticed!
So the
