summaryrefslogtreecommitdiffstats
path: root/nova/exception.py
diff options
context:
space:
mode:
authorDan Smith <danms@us.ibm.com>2013-02-06 11:26:59 -0500
committerDan Smith <danms@us.ibm.com>2013-02-06 21:45:17 -0500
commite5cbbcfc6a5fa31565d21e6c0ea260faca3b253d (patch)
tree251e8e9379262dc6cc2322bbe86956763a7a4c38 /nova/exception.py
parent32d6f568aedeee25cb9c0b093ee847459c091f7e (diff)
downloadnova-e5cbbcfc6a5fa31565d21e6c0ea260faca3b253d.tar.gz
nova-e5cbbcfc6a5fa31565d21e6c0ea260faca3b253d.tar.xz
nova-e5cbbcfc6a5fa31565d21e6c0ea260faca3b253d.zip
Ban database access in nova-compute
This adds a wedge between nova-compute and the database implementation to specifically catch, log, and deny accesses. Theoretically, this should not be needed as a production environment would not even have the compute nodes configured to talk to the database. However, testing and upgraded environments may retain database access and thus avoid hitting real issues that can be fixed up prior to release. Putting this into the tree now will help ensure we have a consistent error scenario for test setups prior to release. Note that if nova is configured to use a local conductor, we do not insert the wedge, which provides an easy out for anyone needing to get a production system past a missed database access. Related to bp no-db-compute. Based on Russell's original tracer hack: I328fa92d5bfdadd5022f5c7efe981396d8ae7962 Change-Id: I478230220633e0d2ff94b6a4d756e07eab8517d7
Diffstat (limited to 'nova/exception.py')
0 files changed, 0 insertions, 0 deletions