On Thu, Nov 17, 10:01, Tommi Virtanen wrote: > On Thu, Nov 17, 2011 at 02:35, Andre Noll <maan@xxxxxxxxxxxxxxx> wrote: > > I was under the impression that equal weights on all osds means to > > fill up all file systems by the same percentage, i.e. that file system > > sizes are already taken care of. > > > > But apparently this is not the case. So one has to set the weights > > manually according to the available disk space. > > The weight is actually a combination of all the factors that would go > in: storage size, disk IO speed, network link bandwidth, heat in that > part of the data center, future expansion plans, .. True. But as we all know, perfect is the enemy of good ;) > We could automate more of it, but it really is a fundamentally holistic > number, and setting it based on just one aspect of reality will lead to > someone else being unhappy. So it goes something like this: > > Step 1: improve documentation For starters, it would be nice to include the ceph osd subcommands in the man pages. To my knowledge they are only documented on the (old) wiki http://ceph.newdream.net/wiki/Monitor_commands at the moment. Would a patch that adds the subcommands and descriptions to the man pages be accepted? If so, I'd be willing to do this work. However, the files in man/ of the ceph git repo seem to be generated by docutils, so I suspect they are not meant to be edited directly. What's the preferred way to patch the man pages? > Step 2: have a monitoring system be able to feed back information to > use as osd weights, with admin customazability How could such a monitoring system be implemented? In particular if abstract criteria like "future extension plans" have to be considered. Andre -- The only person who always got his work done by Friday was Robinson Crusoe
Attachment:
signature.asc
Description: Digital signature
