PMIx Tools and Dynamic Workflows WG - Meeting April 2nd. 2025

12 views
Skip to first unread message

Isaías Alberto Comprés Ureña

unread,
Apr 2, 2025, 9:09:05 AMApr 2
to PMIx Standard Tools Working Group
Greetings everyone,

As planned, we will meet today at 17:00 German time.

Isaías Alberto Comprés Ureña

unread,
Apr 2, 2025, 12:09:08 PMApr 2
to PMIx Standard Tools Working Group
Thanks to everyone for your participation.  Please find the minutes below:

Participants:
Ralph Castain
Norbert Eicker
Dominik Huber
Simon Preibisch
Felix Jung
Isaias Compres

Topics:
- We continue to work on a scheduler with a PMIx server
  - Addivice from Ralph: scheduler as a PMIx tool, with server callbacks
  - Handlers
    - pmix_server_notify_event_fn_t
    - pmix_server_alloc_fn_t
  - Dominik has also made use of the spawn API
  - We can use this opportunity to improve the standard
    - Mostly add clarification (not expected to change at the moment)
  - Document this as a use case
    - HPE and Slurm are incresing support of PMIx
    - Documenting the scheduler use case, and confirm which features are sufficient, can help increase PMIx addoption 

Next meeting (unmodified):
- May 7th 2025 at 17:00 German time.

Dominik Huber

unread,
Apr 3, 2025, 7:46:05 AMApr 3
to Isaías Alberto Comprés Ureña, PMIx Standard Tools Working Group

Hi,


thank you Isaias for the minutes.

Just adding a few comments:

- I think the pmix_server_notify_event_fn_t handler is not necessary to be implemented in the scheduler. At least it was not in my case. The PMIx_register_event_handler API can be used to receive notification from PRRTE e.g. for events related to job termination.

- The Flux team also seems to welcome contributions to their PMIx module. I will probably have a look at this in the context of some upcoming project.

- Until next meeting I hope to finish a more detailed use case documentation of my prototype to share my experiences with the group.


Best regards,


Dominik


Von: pmix-foru...@googlegroups.com <pmix-foru...@googlegroups.com> im Auftrag von Isaías Alberto Comprés Ureña <com...@gmail.com>
Gesendet: Mittwoch, 2. April 2025 18:09:08
An: PMIx Standard Tools Working Group
Betreff: [pmix-forum-wg-tools] Re: PMIx Tools and Dynamic Workflows WG - Meeting April 2nd. 2025
 
--
You received this message because you are subscribed to the Google Groups "PMIx Standard Tools Working Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pmix-forum-wg-t...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pmix-forum-wg-tools/7b38056f-47e0-48d7-a7cb-8daba4e666d4n%40googlegroups.com.

Isaías Alberto Comprés Ureña

unread,
Apr 4, 2025, 5:55:40 AMApr 4
to Ralph Castain, Dominik Huber, PMIx Standard Tools Working Group
Hi Ralph, 

I will be using C for the scheduler project (at least at the beginning).

Thank you for your advice, as always.

Isaías A. Comprés Ureña


On Thu, Apr 3, 2025 at 1:16 PM Ralph Castain <r...@pmix.org> wrote:


On Apr 3, 2025, at 5:46 AM, Dominik Huber <domi....@tum.de> wrote:

Hi,

thank you Isaias for the minutes.
Just adding a few comments:
- I think the pmix_server_notify_event_fn_t handler is not necessary to be implemented in the scheduler. At least it was not in my case. The PMIx_register_event_handler API can be used to receive notification from PRRTE e.g. for events related to job termination.

Correct - the notify_event_fn_t handler is for a client to pass an event up to the host for circulation. The scheduler does not act in that role.

- The Flux team also seems to welcome contributions to their PMIx module. I will probably have a look at this in the context of some upcoming project.

Oh, kewl - that would be most appreciated!

- Until next meeting I hope to finish a more detailed use case documentation of my prototype to share my experiences with the group.


Me too. Isaias - can you confirm the language (Python or C) you are using for your proto-scheduler? I can then point you to some example code.

Ralph

Ralph Castain

unread,
Apr 4, 2025, 6:59:45 AMApr 4
to Dominik Huber, Isaías Alberto Comprés Ureña, PMIx Standard Tools Working Group
On Apr 3, 2025, at 5:46 AM, Dominik Huber <domi....@tum.de> wrote:

Hi,

thank you Isaias for the minutes.
Just adding a few comments:
- I think the pmix_server_notify_event_fn_t handler is not necessary to be implemented in the scheduler. At least it was not in my case. The PMIx_register_event_handler API can be used to receive notification from PRRTE e.g. for events related to job termination.
Correct - the notify_event_fn_t handler is for a client to pass an event up to the host for circulation. The scheduler does not act in that role.
- The Flux team also seems to welcome contributions to their PMIx module. I will probably have a look at this in the context of some upcoming project.

Oh, kewl - that would be most appreciated!
- Until next meeting I hope to finish a more detailed use case documentation of my prototype to share my experiences with the group.


Me too. Isaias - can you confirm the language (Python or C) you are using for your proto-scheduler? I can then point you to some example code.

Ralph


Best regards,

Dominik

Reply all
Reply to author
Forward
0 new messages