1. Proposed title of this feature request
Enable volumeSnapshot quota depending on the volumeSnapshotClasses

2. Who is the customer behind the request?

Account: name and acct : Industria de Diseño Textil SA and 785804
TAM customer: Romero, Antonio Mari
CSM customer: no
Strategic: Yes

3. What is the nature and description of the request?
The customer wants to define the number of snapshot depending on the volumeSnapshotClasses

4. Why does the customer need this? (List the business requirements here)

Currently is possible to create a custom resource quota regarding snapshots in OCP as we can see in the following KCS [1]. But it is not possible to define the number of snapshot depending on the volumeSnapshotClasses.

We would like to create a new RFE in order to define this kind of flexibility when creating resource limits. So, the main idea instead of computing the number of snapshots would be:

• To be able to allow X number of snapshots for RBD volumes.
• To be able to allow Y number of snapshots for CephFS volumes.

Something similar as it is possible to do using storage quotas where we can specify different quotas depending on the storage class used:

apiVersion: v1
kind: ResourceQuota
metadata:
name: testing-quota
namespace: testing-quota
spec:
hard:
ocs-storagecluster-ceph-rbd.storageclass.storage.k8s.io/persistentvolumeclaims: "2"
ocs-storagecluster-cephfs.storageclass.storage.k8s.io/persistentvolumeclaims: "5"

[1] https://access.redhat.com/solutions/5973781

5. How would the customer like to achieve this? (List the functional requirements here)

They would like to be able to allow a number of snapshots for RBD and CephFS volumes to have more control over them.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
NO

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
NO

9. Is the sales team involved in this request and do they have any additional input?
NO

10. List any affected packages or components.
CSI-Driver

11. Would the customer be able to assist in testing this functionality if implemented?
Have not check this yet