Hi, I've proposed a patch which adds the ability to whitelist which extensions are loaded for the V3 API (anything which is not in the whitelist is not loaded) and to blacklist extensions (anything in the blacklist is not loaded). https://review.openstack.org/#/c/29487<https://review.openstack.org/#/c/29487/6> There is also a check to see if something is in both the blacklist and the whitelist as this may be an indication of a misconfiguration and currently the code just does a LOG warn. The question is whether it should instead raise an exception which will effectively abort the nova-api process. Do people think there are any circumstances where someone would intentionally want to both blacklist and whitelist an extension? Presumably if it happened it would only be a temporary thing anyway as they could otherwise just remove it from the whitelist. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130531/daeb27fb/attachment.html>