Re: subpackages for mgr modules

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, May 20, 2017 at 2:25 AM, Ken Dreyer <kdreyer@xxxxxxxxxx> wrote:
> On Fri, May 19, 2017 at 12:19 AM, Tim Serong <tserong@xxxxxxxx> wrote:
>> We can't have mgr just load everything that exists (someone might want
>> to disable some modules, without necessarily uninstalling them).

it does not. user can always enable/disable a plugin using "mgr_modules", right?

>
> I'm curious why not?
>
> Ceph is already hard to configure, and "install to enable / uninstall
> to disable" would make it simpler to use.


i agree, if he/she wants to disable it, he/she could just uninstall
the plugin. actually, i am planning to split the dashboard into a
separated package. so for example, mgr does not need to depend on
cherrypy.

>
> - Ken
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
Regards
Kefu Chai
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux