Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
A
ansible
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 36
    • Issues 36
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • las-it-organisation
  • 32-0-IT instructions and rules
  • ansible
  • Issues
  • #87

Closed
Open
Opened Feb 29, 2020 by julian.gethmann@gethmannOwner

Add backup daemon to LASMagLab computer

Like done on the CN TGU terminal, it would make sense to have a backup daemon for the measurement data of the LASMagLab (on ueberdrus), too.

See also: las-software/15-1-Controls/Jena_UndulatorDocumentation#5 and las-it-organisation/issues#8 and https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/systemdocu/-/blob/master/experiment_backup.md

It's not trivial and requires some more advanced knowledge of (Fedora/RHEL) Linux like SELinux and systemd. @ue5734 hopefully understands my documentation and can do it or assist you (@vn4918 @updzh).

Edited Jun 09, 2020 by julian.gethmann
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: las-it-organisation/32-0-IT-InstructionsAndRules/ansible#87