req: allow archive to send to directory vs drives #322
Conversation
|
Note: I'll update the WIKI once this is merged. |
| @@ -8,6 +8,7 @@ def test_compute_priority(): | |||
| def test_rsync_dest(): | |||
| arch_dir = '/plotdir/012' | |||
| arch_cfg = configuration.Archive( | |||
| rsyncd_type='drives' | |||
There was a problem hiding this comment.
Might appease tests:
| rsyncd_type='drives' | |
| rsyncd_type='drives', |
|
Archiving is being significantly reworked in terms of the identification of target directories and the transfer commands. This will allow users to enter their own scripts for those activities as well as set us up to generically provide multiple presets. There is already a local and remote rsync option in |
|
I believe you could implement this now by way of a custom archive target definition (released in v0.4). The transfer script wouldn't need to change. The disk space script could loop over the configured directories and check and report the space for each. I do appreciate the effort to contribute this to the project and apologize for my very slow handling of yours and other contributions. |
|
I think that adding this now would take a sufficiently different form that it probably ought to be submitted as a new PR. |
Handles #321
The archiver currently requires separate drives to be mounted for archiving. For instance:
df)However, if you have a RAID or ZRAID where you are storing elements, there is no "mounted drive" to use. For instance:
This PR adds a new configuration option of
rsyncd_typewhich defaults todrivesif it does not exist in the configuration (the original method).If it is set to
directoryin the configuration YAML, then:dfchecks free space on the destination directory without requiring it to be a separate mounted diskchia) would be the rsync destination, which in turn is the single directory destinationI've run this across 3 plots in testing, and all functions smoothly.