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

a few more small changes in conf docs #990

Open
wants to merge 4 commits into
base: master
from

Conversation

Projects
None yet
3 participants
@danielskatz
Copy link
Collaborator

commented May 29, 2019

No description provided.

@danielskatz danielskatz requested a review from yadudoc May 29, 2019

danielskatz and others added some commits May 29, 2019

@@ -1,17 +1,17 @@
.. _configuration-section:

Configuration
Environment Configuration

This comment has been minimized.

Copy link
@yadudoc

yadudoc May 30, 2019

Member

Environment is so overloaded that I'd rather not use it here.

This comment has been minimized.

Copy link
@danielskatz

danielskatz May 30, 2019

Author Collaborator

But configuration by itself is not enough. Would execution be better?

configuration somewhat complex, and also makes determining how to set up Parsl's configuration
for a particular set of choices fairly complex, though we think the actual configuration
itself is reasonable simple.

Parsl offers an extensible configuration model through which the execution environment and
communication with that environment is configured. Parsl is configured
communication within that environment is configured. Parsl is configured

This comment has been minimized.

Copy link
@yadudoc

yadudoc May 30, 2019

Member

There are two types of communication that you might be configuring: the channels that determine how you connect to the resource (where communication with makes sense), and the executor itself over which the user doesn't really configure/control the communication. So this with is more correct that within.

This comment has been minimized.

Copy link
@danielskatz

danielskatz May 30, 2019

Author Collaborator

If the main parsl process is part of the environment we are configuring (which I think it is), then within seems more appropriate to me, since nothing is outside the environment.

@yadudoc yadudoc added this to the Parsl-0.8.0 milestone May 30, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.