Comment 2 for bug 1037373

OK, so it turns out that this is problematic for two reasons:

1. In the keystone auth case, the configuration required to validate the tenant ID is bound to paste config for the keystone auth_token middleware, as opposed to general nova configuration. This config should be refactored so that its located in the general nova.conf, to avoid the need for users to ever edit paste config, and also to make it available to other nova code (such as the quota project ID validation case at hand). While this change is warranted, its out of scope for Folsom at this late stage.

2. In the noauth case, the project ID can be any value what-so-ever, so the validation doesn't arise and wouldn't add any value. Its currently not easily detectable within an API extension whether noauth is being used, as the context is populated in any case with auth-related headers.

For the reasons set out above, lets punt this issue to Grizzly-1.