Change Details

Another step forward to having eqiad1 in production is to have the `nova` and `nova-api` databases in a production db server (m5-master). Since the `nova` names are already in use by the old `main` deployment, we should pick another name, like `nova-eqiad1`/`nova-api-eqiad1` or something like that. Steps: [] review connectivity (should simply work after previous database migrations) [] m5-master DB GRANTS (cc @jcrespo) [] puppet patch to refresh nova DB references for eqiad1 (server + db name) [] db backup-copy-import This task is for tracking such work.

Another step forward to having eqiad1 in production is to have the `nova` and `nova-api` databases in a production db server (m5-master). Since the `nova` names are already in use by the old `main` deployment, we should pick another name, like `nova-eqiad1`/`nova-api-eqiad1` or something like that. Steps: [] leave room for more nova connections [] review connectivity (should simply work after previous database migrations) [] m5-master DB GRANTS (cc @jcrespo) [] puppet patch to refresh nova DB references for eqiad1 (server + db name) [] db backup-copy-import This task is for tracking such work.

Another step forward to having eqiad1 in production is to have the `nova` and `nova-api` databases in a production db server (m5-master). Since the `nova` names are already in use by the old `main` deployment, we should pick another name, like `nova-eqiad1`/`nova-api-eqiad1` or something like that. Steps: [] leave room for more nova connections [] review connectivity (should simply work after previous database migrations) [] m5-master DB GRANTS (cc @jcrespo) [] puppet patch to refresh nova DB references for eqiad1 (server + db name) [] db backup-copy-import This task is for tracking such work.