When deploying sites, it would be beneficial to create pool names unique to that site. This will prevent the pool names from colliding when being mirrored to secondary sites and also allow the operator to seperate local/primary pools from secondary/mirrored pools and assign different storage attributes based on priorities.
Without this, every site would have the same "volumes" pool (for instance) and the operater would then have both primary and secondary volumes in the same pool - which limits flexibility. Specifically, we'd like the operator to set pool attributes such that primary volumes could be physically located on SSD drives but mirrored non-primary volumes from another site are stored on a HDD erasure coded pool so as to not impact performance for local users.
To start, it would be helpful to create storage pools with user-defined names. To be specific, create the cinder pool with the name 'foobar' instead of 'volumes' for instance. With this capability, a multisite configuration with rbd-mirror could then be configured to mirror a storage pool to a secondary site without putting all volumes (primary and mirrored) into the same pool.
THT has supported this as far back as OSP-10, so I'm closing this CURRENTRELEASE. These are the parameters, along with their default values: