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

Provide a mechanism to configure airflow task configurations like pool, queue. #263

Closed
sravankorumilli opened this issue Apr 5, 2022 · 1 comment · Fixed by #290 or raystack/proton#130
Assignees

Comments

@sravankorumilli
Copy link
Contributor

sravankorumilli commented Apr 5, 2022

Description

There's a requirement from the user, where they need to put some additional requirements in the job spec. As the current Optimus version uses Airflow as the scheduler, then the focus for this issue is to address it in Airflow specific only. Others will follow if implemented.

Expectation

  • the user is allowed to put additional configuration specific to the Airflow pool and queue
@irainia
Copy link
Member

irainia commented Apr 13, 2022

Chosen Approach

The approach taken is to minimise changes in the job spec, but still accommodate the requirements. As it is specific to Airflow, then the focus is only for this.

The following is the approach taken for this issue, which will be implemented in the job spec. Example of the job spec:

...
behavior:
  ...
task:
  ...
metadata:
  resource:
    ...
  airflow: [struct]
    queue: queueA
    pool: poolA

Using struct for the Airflow is to make it easier to process.

References:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants