Thanks for the great response! I tested out your suggestion and yes, you can restrict a tenant from creating volumes on defined volume types.

The thing to keep in mind is you must know the tenant ID in order to apply the specific volume type quota and apply the quota for each tenant created (now and going forward). Another thing I discovered is I could not find one good example to reference anywhere on the internet :). So here is one:

This lists out all the quotas defined for the tenant:

$ cinder quota-show <tenant_ID>
$ cinder quota-show 0ece405bde4b412fb689a6b072f2744a

Now set your volume type quota for that tenant:

$ cinder quota-update --volumes <volume_count> --volume-type <volume_type_name> <tenant_ID>
$ cinder quota-update --volumes 100 --volume-type lvm-SSD 0ece405bde4b412fb689a6b072f2744a

Before doing the above you need to create the volume types ahead of time of course. I used this blog to help with that and focused on Case 3 - http://www.rushiagr.com/blog/2014/01/16/playing-around-with-cinder-multi-backend/ (http://www.rushiagr.com/blog/2014/01/...) .

The default value for the volume type is '-1'. If you do not reset it with the command above, it will not change. Also, you must pass the '--volumes' parameter with the 'volume-type' parameter. Doing one without the other gives you the appearance that it worked but, when you run the quota-show command again you will see it did not change.