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

Remove ability to set monitoring log directory separate from rundir #3699

Merged
merged 2 commits into from
Nov 14, 2024

Conversation

benclifford
Copy link
Collaborator

Prior to this PR, MonitoringHub had a logdir parameter which let the log directory be set separately from the DFK-level run directory.

Other Parsl components generally don't let the user set this unless there is a specific reason.

So this PR removes that feature, reducing the amount of state to be threaded around.

When reading this patch, note that what the DFK calls the rundir is a different directory vs what a Config object calls the rundir.

Changed Behaviour

This removes a parameter from user facing MonitoringHub configuration.

Type of change

  • Code maintenance/cleanup

Prior to this PR, MonitoringHub had a logdir parameter which let the log
directory be set separately from the DFK-level run directory.

Other Parsl components generally don't let the user set this unless there is
a specific reason.

So this PR removes that feature, reducing the amount of state to be threaded
around.

When reading this patch, note that what the DFK calls the rundir is a different
directory vs what a Config object calls the rundir.
parsl/monitoring/db_manager.py Outdated Show resolved Hide resolved
@benclifford benclifford added this pull request to the merge queue Nov 14, 2024
Merged via the queue into master with commit 9fb5269 Nov 14, 2024
7 checks passed
@benclifford benclifford deleted the benc-no-monitoring-logdir branch November 14, 2024 16:08
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