Migrate services to use the new db machine belvedere
ClosedPublic
Actions

Authored by ardumont on May 27 2019, 6:30 PM.

Details

Reviewers

Group Reviewers

Commits

Summary

As soon as the migration is done (in-progress), we should migrate services to
use the new db (new secondary cluster in belvedere:5434).

Related T1744

Test Plan

bin/octocatalog-diff

Repository

rSPSITE puppet-swh-site

Lint

Automatic diff as part of commit; lint not applicable.

Unit

Automatic diff as part of commit; unit tests not applicable.

Looks good to me.
Always using the fqdn belvedere.internal.softwareheritage.org would be more consistent though ;-)

This revision is now accepted and ready to land.May 28 2019, 8:59 AM

ardumont mentioned this in Unknown Object (Maniphest Task).May 28 2019, 9:55 AM

Plug to production branch

This revision was automatically updated to reflect the committed changes.

ardumont mentioned this in Unknown Object (Maniphest Task).May 28 2019, 12:17 PM

Path

Size

data/

32 lines