Page MenuHomeSoftware Heritage

Migrate services to use the new db machine belvedere
ClosedPublic

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

Details

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

Diff Detail

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.

Event Timeline

ardumont created this revision.Mon, May 27, 6:30 PM
ftigeot accepted this revision.Tue, May 28, 8:59 AM

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.Tue, May 28, 8:59 AM
ardumont mentioned this in Unknown Object (Maniphest Task).Tue, May 28, 9:55 AM
ardumont edited the summary of this revision. (Show Details)Tue, May 28, 9:58 AM
ardumont updated this revision to Diff 4991.Tue, May 28, 9:58 AM
  • db::host: Use consistently fqdn
ardumont updated this revision to Diff 4992.Tue, May 28, 10:01 AM

Plug to production branch

This revision was automatically updated to reflect the committed changes.
ardumont mentioned this in Unknown Object (Maniphest Task).Tue, May 28, 12:17 PM