Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support multiple mount points #34

Merged
merged 9 commits into from
Feb 20, 2024
Merged

Support multiple mount points #34

merged 9 commits into from
Feb 20, 2024

Conversation

rernst
Copy link
Member

@rernst rernst commented Dec 15, 2023

Add support for multiple mount points.

rsync_to_rdisc.py Show resolved Hide resolved
rsync_to_rdisc.py Show resolved Hide resolved
rsync_to_rdisc.py Outdated Show resolved Hide resolved
rsync_to_rdisc.py Show resolved Hide resolved
rsync_to_rdisc.py Outdated Show resolved Hide resolved
Comment on lines 349 to 364
for mount_name in settings.transfer_settings:
mount_path = settings.transfer_settings[mount_name]['mount_path']
# Check if mount is available and continue
if is_mount_available(mount_name, mount_path, run_file):
# Get folders to be transferred
to_be_transferred = get_folders_remote_server(
client,
settings.transfer_settings[mount_name],
run_file,
transferred_set
)

# Rsync folders from HPC to mount
rsync_succes = rsync_server_remote(hpc_server, client, to_be_transferred, mount_path, run_file)
if not rsync_succes:
remove_run_file = False
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Originally, a new rsync_to_rdisc process would be blocked when a mount was unavailable. Someone has to take a look and fix the mount, and I think to avoid many emails as well.
I think the new code changes this scenario; the sys.exit() is removed in is_mount_available.
Can be resolved with:

else:
    remove_run_file = False

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have implemented this but have to think about it. The problem is that we will now block bgarray transfers if for example the glims mount is not available. I am not sure if that is something we would like to do....

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see. Let's think about a solution that continues bgarray transfer if glims is unavailable, and avoid multiple emails if a mount is lost. :)

@rernst rernst marked this pull request as ready for review January 31, 2024 11:56
@rernst rernst merged commit 2bd8ac6 into development Feb 20, 2024
1 check passed
@rernst rernst deleted the feature/glims branch February 20, 2024 13:28
@ellendejong ellendejong mentioned this pull request Dec 30, 2024
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants