Description of problem:

Currently the following meters are enabled by default when ManagePolling: true.

However disk.* meters were already removed from ceilometer[1], and
we don't have any valid disk performance meters enabled.

[1] https://review.opendev.org/c/openstack/ceilometer/+/580710

/var/lib/config-data/puppet-generated/ceilometer/etc/ceilometer/polling.yaml
~~~
---
sources:
    - name: some_pollsters
      interval: 600
      meters:
        - cpu
        - cpu_l3_cache
        - memory.usage
        - network.incoming.bytes
        - network.incoming.packets
        - network.outgoing.bytes
        - network.outgoing.packets
        - disk.read.bytes
        - disk.read.requests
        - disk.write.bytes
        - disk.write.requests
        - volume.size
        - volume.snapshot.size
        - volume.backup.size
        - hardware.cpu.util
        - hardware.memory.used
        - hardware.memory.total
        - hardware.memory.buffer
        - hardware.memory.cached
        - hardware.memory.swap.avail
        - hardware.memory.swap.total
        - hardware.system_stats.io.outgoing.blocks
        - hardware.system_stats.io.incoming.blocks
        - hardware.network.ip.incoming.datagrams
        - hardware.network.ip.outgoing.datagrams
~~~

Because of this we don't get any disk performance captured by ceilometer,
unless we customize pollong.yaml


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Deploy overcloud with ceilometer enabled and ManagePolling: true
2. Create an instance

Actual results:
Any disk performance meters are not captured

Expected results:
Disk performance meters are captured


Additional info: