Comment 11 for bug 1492742

So my current thinking on this is that we could have each client optionally provide a max_pg_num that will override whatever the charm would have used by inference. That way each client can specify a different value (e.g. for Nova, Cinder or Glance pools). We could accompany this with an action to optimise pg_num on pools that can be called once the deployment has finished.