Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • nomad-FAIR nomad-FAIR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 217
    • Issues 217
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 28
    • Merge requests 28
  • 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
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nomad-labnomad-lab
  • nomad-FAIRnomad-FAIR
  • Issues
  • #288
Closed
Open
Issue created Feb 21, 2020 by Markus Scheidgen@mscheidgOwner2 of 2 checklist items completed2/2 checklist items

Implement mirror functions that are fit to be used with external NOMAD deployments

This includes

  • Add a new endpoint to serve files. This is necessary to copy the raw and archive files to an OASIS. Ideally all files are served with a single call. Only the non restricted files must be served.
  • Add a new endpoint to serve a list of all users. OASIS deployments should use this instead of accessing the user management.

The cli.client.mirror command should use the new file endpoint by default, and use options to allow the current local copy, move, link operations.

The endpoints should be implemented in nomad/app/api/mirror.py. Both endpoints will require a new resource, e.g. Files and Users.

Edited Mar 19, 2020 by Alvin Noe Ladines
Assignee
Assign to
Time tracking