Have user declare what pools should be created

[jan--f]

Following an email discussion I'm wondering if we should give admins a way of specifying what pools DS should create and what they should be used for (say CephFS or so).
The pillar might be a good place for this?
Many questions remain open though...how to manage pool life cycles, what if pools are added manually or by other tools, ...

[smithfarm]

I'm with @l-mb that DS should not create any pools. Features should be driven by user demand. Are users demanding this?

[smithfarm]

Also, Ceph itself is moving away from automated pool creation. It used to create an rbd pool, but no longer.

[smithfarm]

Not that we need to copy, but it might be relevant to point out that ceph-ansible does not create pools: ceph/ceph-ansible#946

[swiftgist]

Rados Gateway creates its own pools simply by starting the service. CephFS and iSCSI do not.

We are creating a demo image in the rbd pool for a default iSCSI example. That was requested. The .../ceph/mds/pools does create cephfs_data and cephfs_metadata if role-mds is assigned but no CephFS pools exist. That seems extremely reasonable to give users something that works over something that is broken out of the box.

With no rbd pool by default, we should adapt the image creation for iSCSI.