Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
tf_mod_aws_efs_backup
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 2
    • Issues 2
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • steamhaus
  • tf_mod_aws_efs_backup
  • Issues
  • #1

Closed
Open
Opened Apr 26, 2018 by Sean Clerkin@sean
  • Report abuse
  • New issue
Report abuse New issue

Intelligently create a scratch EBS of the correct size

Rather than guessing what the the root volume size should be, the EC2 instance could:

  • Check the total size of the EFS volume, CW metric? parse df output?
  • Create an EBS volume slightly larger than that
  • Attach it to itself
  • Format the volume with a filesystem
  • Mount it
  • Run the backup
  • Delete the volume
  • Terminate itself
Edited Apr 26, 2018 by Sean Clerkin
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
0
Labels
None
Assign labels
  • View project labels
Reference: steamhaus/tf_mod_aws_efs_backup#1