Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • S swh-provenance
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Platform
  • Development
  • swh-provenance
  • Issues
  • #4408
Closed
Open
Issue created Jul 22, 2022 by Nicolas Dandrimont@olasdMaintainer4 of 4 checklist items completed4/4 checklist items

Resume provenance content-revision layer processing through the revision journal client

We want to resume processing of revisions in the provenance database using the new journal client.

To do so, we will:

  • give mmca access to the main archive through a SSH reverse tunnel
  • give mmca access to the journal through read-only, non-privileged journal credentials
  • upgrade swh.provenance on mmca
  • restart mmca's content-revision layer using the journal client

Migrated from T4408 (view on Phabricator)

Edited Jan 07, 2023 by Phabricator Migration user
Assignee
Assign to
Time tracking