> On Jul 27, 2017, at 11:51 PM, Sage Weil <sage@xxxxxxxxxx> wrote: > > The basics: > > ceph balancer mode <none,upmap,crush-compat,...> > - which optimiation method to use > ceph balancer on > - run automagically > ceph balancer off > - stop running automagically So this would leave the last CRUSH map installed by the balancer in place? Or would it restore the CRUSH map that was in place before applying running the balancer? If the former (which seems more reasonable, perhaps), is there a command to revert to the last user-applied map? > ceph balancer status > - see curent mode, any plans, whehter it's enabled > > The useful bits: > > ceph balancer eval > - show analysis of current data distribution > ceph balancer optimize <plan> > - create a new plan to optimize named <plan> based on the current > mode > - ceph balancer status will include a list of plans in memory > (these currently go away if ceph-mgr daemon restarts) > ceph balancer eval <plan> > - analyse resulting distribution if plan is executed > ceph balancer show <plan> > - show what the plan would do (basically a dump of cli commands to > adjust weights etc) > ceph balancer execute <plan> > - execute plan (and then discard it) > ceph balancer rm <plan> > - discard plan > > A normal user will be expected to just set the mode and turn it on: > > ceph balancer mode crush-compat > ceph balancer on > > An advanced user can play with different optimizer modes etc and see what > they will actually do before making any changes to their cluster. > > Does this seem like a reasonable direction for an operator interface? I think it makes sense. Possibly unrelated: is there a way to adjust the rate of map changes manually or do we just expect the balancer to handle that automagically? -- 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
