The symbolic constant for microversion 3.39 isn't used anywhere in
the code (only in some tests). Instead, the constant for mv 3.38
is used, which is OK but confusing. Use mv.get_prior_version() with
mv.LIMITS_ADMIN_FILTER to keep things clear.
Credit: a comment by Gorka on change I5108fd51effa
Change-Id: Icbf29b5eba9eb9161be8976c4d2f571e21e5bab4
We very often end up with merge conflicts for any patches that increment
microversions due to conflicting numbers. We can't really solve that,
but we can avoid the need to update version numbers throughout the code
by defining a constant value in one place and using that variable instead.
Change-Id: Ib3a80fee6caaabb49af097aa197f550c65d94985
"cinder absolute-limits" command supports <tenant_id> filter,
But server side doesn't, this patch added the support for server
side.
APIImpact
Closes-bug: #1668416
Change-Id: Ib31ab87d0954c2bedf55c6d71623b2c7d07b5fa7
Brian Rosmaita