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

Proposal for Homogenizing Computing Element Interfaces in DIRAC #7398

Open
aldbr opened this issue Jan 17, 2024 · 0 comments
Open

Proposal for Homogenizing Computing Element Interfaces in DIRAC #7398

aldbr opened this issue Jan 17, 2024 · 0 comments
Assignees
Milestone

Comments

@aldbr
Copy link
Contributor

aldbr commented Jan 17, 2024

The diversity and complexity of Computing Elements (CEs) in DIRAC have significantly increased, leading to a somewhat disorganized system. We have observed that the current structure, which broadly categorizes CEs into Remote (e.g. ARC, HTCondor, SSH, ...), Inner (e.g. InProcess, Singularity), and Inner Pool (e.g. Pool) types, is becoming increasingly unwieldy. This situation necessitates a more streamlined and unified approach to enhance maintainability and usability.

I propose a unified interface approach for all types of CEs. The core idea is to make these interfaces homogeneous, thus simplifying the interaction and management of various CE types.

Key aspects of the proposal include:

  • Submission status returns: For Inner CEs (InProcess, Singularity, Pool), the submission method should return the status of the submission but not the payload's exit code directly.
  • Introduction of getJobStatus() method: Implement a getJobStatus() method for Inner CEs. This method would retrieve the job's status from taskResults similarly to how it's currently handled by Remote CEs. This approach ensures consistency across different CE types and simplifies status retrieval mechanisms.
  • Enhanced Maintainability: By streamlining the interface, the maintenance and development of CEs within DIRAC would become more manageable, allowing for easier updates and potential expansions in the future.

The proposal was introduced in #6970 but not followed up.

@aldbr aldbr added this to the v9.0 milestone Jan 17, 2024
@aldbr aldbr self-assigned this Jan 17, 2024
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

No branches or pull requests

1 participant