Moving task scheduling outside of king arthur about grimoirelab-kingarthur

[alpgarcia]

@acs in that scenario, why do you need Arthur? I guess airflow is able to execute the jobs and there will be options to track them so that each job can inform about its status.

[acs]

You need arthur to execute the jobs. The idea is that airflow asks arthur to execute jobs using its REST API. Airflow can not execute jobs in a distributed fashion by itself.

[sduenas]

This is out of the scope of Arthur. Arthur is the scheduler of Perceval tasks and that's not going to change. If at some point we decide we need a different engine for scheduling all GrimoireLab tasks, we will deprecate this tool and we'll create those tool needed for that purpose. I don't see a good reason to mutate tools from one thing to another.

Thanks for the pointer, though.

[acs]

Thanks for the explanation @sduenas. Yes, I was thinking in scheduling for all GrimoireLab tasks, not just perceval ones. For example, all the scheduling done in mordred. IMHO, if you decide to use a scheduling tool for GrimoireLab, you will need arthur for task registering and execution, which I envision must be the core features of arthur.

Just my 2 cents!