Page MenuHomeSoftware Heritage

Migrate services to use the new db machine belvedere
ClosedPublic

Authored by ardumont on May 27 2019, 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
Branch
update_configuration
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 5941
Build 8143: arc lint + arc unit

Event Timeline

ardumont created this revision.May 27 2019, 6:30 PM
ftigeot accepted this revision.May 28 2019, 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.May 28 2019, 8:59 AM
ardumont mentioned this in Unknown Object (Maniphest Task).May 28 2019, 9:55 AM
ardumont edited the summary of this revision. (Show Details)May 28 2019, 9:58 AM
ardumont updated this revision to Diff 4991.May 28 2019, 9:58 AM
  • db::host: Use consistently fqdn
ardumont updated this revision to Diff 4992.May 28 2019, 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).May 28 2019, 12:17 PM