Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • MC Job Options MC Job Options
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Jira
    • Jira
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • atlas-physics
  • pmg
  • MC Job OptionsMC Job Options
  • Issues
  • #65
Closed
Open
Issue created Jan 23, 2020 by Spyros Argyropoulos@sargyropMaintainer0 of 4 checklist items completed0/4 checklist items

Running pipelines in custom swarm runner

Instructions from Lukas here: https://clouddocs.web.cern.ch/containers/tutorials/swarmgitlab.html

Idea would be that if we set this up we could run with the full number of events exactly as in production.

The instructions below work. Wo have to understand whether this is what we want:

  • does it have access to cvmfs? If not how would we set it up so that it has?
  • does it buy us anything from using the shared runners?
  • how tough would the maintenance be?
  • is it better to just set up a dedicated machine? Maybe we should ask someone from the CERN IT to do it?
Edited Apr 11, 2020 by Spyros Argyropoulos
Assignee
Assign to
Time tracking