Preliminary support for seperate reporting database

This commit implements a Django database router which routes each
Django application to a database whose name matches a key in the database
dict, falling back to the default database if no matching key is found.

This support is plumbed through to the config file via
database.reporting_* database connection config options.  These options
mirror ones available for the default database config. If
database.reporting_engine is not specified in the config, then the
configuration falls back to the traditional single-database way of doing
things with the database router becoming a no-op.

1 files changed, 3 insertions, 3 deletions

diff --git a/src/lib/Bcfg2/Reporting/Storage/DjangoORM.py b/src/lib/Bcfg2/Reporting/Storage/DjangoORM.py
index c223c3c73..992687a85 100644
--- a/src/lib/Bcfg2/Reporting/Storage/DjangoORM.py
+++ b/src/lib/Bcfg2/Reporting/Storage/DjangoORM.py
@@ -380,9 +380,9 @@ class DjangoORM(StorageBase):
                 vrb = 1
             else:
                 vrb = 0
-            management.call_command("syncdb", verbosity=vrb, interactive=False)
-            management.call_command("migrate", verbosity=vrb,
-                                    interactive=False)
+            Bcfg2.DBSettings.sync_databases(verbosity=vrb, interactive=False)
+            Bcfg2.DBSettings.migrate_databases(verbosity=vrb,
+                                               interactive=False)
         except:
             msg = "Failed to update database schema: %s" % sys.exc_info()[1]
             self.logger.error(msg)