Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
R
rwm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Radoslav Bodó
rwm
Commits
46bd8a35
Commit
46bd8a35
authored
1 year ago
by
Radoslav Bodó
Browse files
Options
Downloads
Patches
Plain Diff
general: readme updates
parent
12380498
No related branches found
No related tags found
No related merge requests found
Pipeline
#7726
passed
1 year ago
Stage: code_quality
Changes
1
Pipelines
2
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+29
-2
29 additions, 2 deletions
README.md
with
29 additions
and
2 deletions
README.md
+
29
−
2
View file @
46bd8a35
...
@@ -143,11 +143,38 @@ rwm restic mount /mnt/restore
...
@@ -143,11 +143,38 @@ rwm restic mount /mnt/restore
## Notes
## Notes
*
Executed tools stdout is buffered, eg.
`restic mount`
does not print immediate output as normal
*
Executed tools stdout is buffered, eg.
`restic mount`
does not print immediate output as normal
.
*
Passthrough full arguments to underlying tool with "--" (eg.
`rwm aws -- s3api --help`
).
*
Passthrough full arguments to underlying tool with "--" (eg.
`rwm aws -- s3api --help`
).
*
TODO: elaborate and hardcode default retention (?restic keeps are tricky)
*
TODO: elaborate and hardcode default retention (?restic keeps are tricky).
*
TODO: microceph in CI runner break sometimes, reinstall microceph and reboot to salvage it.
## DU S3 Account provisioning via e-infra.cz
1.
Ensure the existence of the Perun Virtual Organization (VO) whose members
will utilize CESNET Data Storage (DS) services.
2.
Create a VO group named
`project_backup`
to organize storage service accounts.
This group will be associated with the Ceph S3 tenant.
3.
Establish the following Perun VO service identities:
*
`project_admin`
*
`project_backedresource1`
*
`project_backedresource2`
*
...
Add these identities as members of the project_backup group.
4.
Generate S3 access credentials for each identity through the DS web portal.
5.
Utilize the
`project_admin`
identity to create policed storage buckets. Note
that bucket names cannot be changed once created.
6.
Perform backups using the designated resource identities
(
`project_backedresource1`
and
`project_backedresource2`
).
7.
Employ the project_admin identity to execute maintenance tasks as necessary.
## Development
## Development
```
```
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment