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

Move MPI behavior from HTEX to MPIExecutor #3582

Merged
merged 2 commits into from
Aug 16, 2024
Merged

Conversation

yadudoc
Copy link
Member

@yadudoc yadudoc commented Aug 14, 2024

Description

This PR moves the following MPI related functionality and options from HTEX to MPIExecutor:

  • Kwarg options enable_mpi_mode and mpi_launcher is now removed from HTEX
  • Checks for launcher being set to SimpleLauncher
  • Checks for a valid mpi_launcher in now in MPIExecutor
  • A new validate_resource_specification method is added to HTEX that currently asserts that no resource_specification is passed to it, since HTEX does not support any such options
  • MPIExecutor overrides validate_resource_specification to check for a valid MPI resource specification

These changes should make it easier to have executor specific resource validation.

Changed Behaviour

  • HTEX kwarg enable_mpi_mode and mpi_launcher are no longer supported.
  • Expect to use MPI functionality only through the MPIExecutor

Type of change

I'm marking this as maintenance since the docs have moved on to only advertize MPI functionality through MPIExecutor.

  • Code maintenance/cleanup

parsl/executors/high_throughput/executor.py Show resolved Hide resolved
parsl/executors/high_throughput/mpi_executor.py Outdated Show resolved Hide resolved
parsl/executors/high_throughput/mpi_executor.py Outdated Show resolved Hide resolved
parsl/executors/high_throughput/executor.py Outdated Show resolved Hide resolved
parsl/executors/high_throughput/mpi_executor.py Outdated Show resolved Hide resolved
provider=SlurmProvider(launcher=launcher),
)
])


@pytest.mark.local
def test_correct_launcher_with_mpi_mode():
def test_bad_mpi_launcher():
"""ValueError if an unsupported mpi_launcher is specified"""
Copy link
Collaborator

Choose a reason for hiding this comment

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

this test looks for a type error not a value error?

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed.

Copy link
Collaborator

Choose a reason for hiding this comment

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

it's meant to be a test for a value error though, right?

test-requirements.txt Outdated Show resolved Hide resolved
@@ -25,4 +25,3 @@ Sphinx==4.5.0
twine
wheel
isort

Copy link
Collaborator

Choose a reason for hiding this comment

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

are you trolling me

* Adding `validate_resource_specification` method to HTEX and overriding that with MPI specific validation in MPIEX
* HTEX will no longer accept mpi_resource_specification even with `enable_mpi_mode=True`
* `enable_mpi_mode` and `mpi_launcher` are no longer supported in HTEX. `mpi_launcher` is now set only via MPIEX
* MPI specific checks are now in MPIEX instead of HTEX
@benclifford benclifford merged commit 123df51 into master Aug 16, 2024
7 checks passed
@benclifford benclifford deleted the reorg_mpiexecutor branch August 16, 2024 19:04
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