Demo of hacking in custom registration behaviour into interchange registrations #3359
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
no need for this to remain open |
|
Thanks for this @benclifford. Could you keep this branch around for a little bit? |
|
@cms21 yeah no problem - I just closed it to get it off the open PRs list |
benclifford
added a commit
that referenced
this pull request
Jun 24, 2024
…ssages This is intended to clarify that what an interchange is sending is nothing special, beyond a normal monitoring message. This is intended to loosen up future opportunities in two ways: this is hard-coded / not configurable in the interchange - it might be later desirable to make the interchange configurable if wanting to do other stuff with this status information - eg christines prototype use case (see PR #3359) of wanting to run specific commands when a worker connects (where a radio message is treated as a more general event hook), or sending monitoring info to other places not the monitoring db it might be desirable to deliver monitoring information from a worker node using ZMQ, for example when using work queue co-processes or the task vine equivalent - where the cost of starting a ZMQ connection might be amortised across many tasks.
benclifford
added a commit
that referenced
this pull request
Jul 11, 2024
…ssages This is intended to clarify that what an interchange is sending is nothing special, beyond a normal monitoring message. This is intended to loosen up future opportunities in two ways: this is hard-coded / not configurable in the interchange - it might be later desirable to make the interchange configurable if wanting to do other stuff with this status information - eg christines prototype use case (see PR #3359) of wanting to run specific commands when a worker connects (where a radio message is treated as a more general event hook), or sending monitoring info to other places not the monitoring db it might be desirable to deliver monitoring information from a worker node using ZMQ, for example when using work queue co-processes or the task vine equivalent - where the cost of starting a ZMQ connection might be amortised across many tasks.
benclifford
added a commit
that referenced
this pull request
Jul 18, 2024
…ssages This is intended to clarify that what an interchange is sending is nothing special, beyond a normal monitoring message. This is intended to loosen up future opportunities in two ways: this is hard-coded / not configurable in the interchange - it might be later desirable to make the interchange configurable if wanting to do other stuff with this status information - eg christines prototype use case (see PR #3359) of wanting to run specific commands when a worker connects (where a radio message is treated as a more general event hook), or sending monitoring info to other places not the monitoring db it might be desirable to deliver monitoring information from a worker node using ZMQ, for example when using work queue co-processes or the task vine equivalent - where the cost of starting a ZMQ connection might be amortised across many tasks.
benclifford
added a commit
that referenced
this pull request
Jul 26, 2024
…ssages This is intended to clarify that what an interchange is sending is nothing special, beyond a normal monitoring message. This is intended to loosen up future opportunities in two ways: this is hard-coded / not configurable in the interchange - it might be later desirable to make the interchange configurable if wanting to do other stuff with this status information - eg christines prototype use case (see PR #3359) of wanting to run specific commands when a worker connects (where a radio message is treated as a more general event hook), or sending monitoring info to other places not the monitoring db it might be desirable to deliver monitoring information from a worker node using ZMQ, for example when using work queue co-processes or the task vine equivalent - where the cost of starting a ZMQ connection might be amortised across many tasks.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This is a demo for @cms21 of hacking in custom registration behaviour when a manager registers to an interchange.
(Longer term, I'd like this sort of thing to be possible through configurable monitoring radios, something like PR #3315, allowing people to plug in whatever behaviour they want, throughout parsl, when "interesting things happen")
Changed Behaviour
you should see a file benc.demo appear in the working directory of the interchange, with a new line appended every time a manager registers
Type of change