Re: Luminous: osd_crush_location_hook renamed to crush_location_hook

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

 



On Thu, 19 Oct 2017, Wido den Hollander wrote:
> > Op 19 oktober 2017 om 14:22 schreef John Spray <jspray@xxxxxxxxxx>:
> > I would vote that we treat this as a bug and change the setting name
> > back to osd_crush_location_hook, even if the name isn't quite
> > descriptive any more -- Sage?
> > 
> 
> Can't we alias it somehow? I ran into this with a pre-production cluster 
> before we started the upgrade of two production systems.
> 
> Problem is that this setting is usually only touched by large 
> deployments so not very much tested nor used.

Yeah, it is probably easiest and the least painful to make both option 
names work (with crush_location_hook taking precedence).  Ideally we'd 
also issue a health warning after upgrade so they know to update it after 
so we can remove the osd_ option name later...  although until we 
centralize config there isn't a great way to do that.

sage



--
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