Juju Charms Collection
glance package

  1. Bug #1492742
  2. Comment #4

Comment 4 for bug 1492742

Revision history for this message
Nobuto Murata (nobuto) wrote : Re: too many PGs per OSD

I understand that juju charm does not know how many pools to be created at the deployment timing, but knows how many OSDs in the cluster. How about creating pools with assuming 5 to 10 pools to be created (in typical OpenStack deployment) and targeting PGs per OSD as 100 (described in [1]) to be safe at the deployment timing instead of consuming all of recommended ratio with just 1 pool?

Indeed, PGs per OSD ratio won't be optimized just after the deployment. But after the deployment juju charms could know how many pools were created and how many OSDs are there. So we could have an action to optimized PGs per OSD to users' desired value for example:

$ juju action do ceph/0 optimize-pgnum target-pgs-per-osd=200

[1] http://ceph.com/pgcalc/