[
https://issues.apache.org/jira/browse/AIRFLOW-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17377437#comment-17377437
]
ASF GitHub Bot commented on AIRFLOW-1746:
-----------------------------------------
sblanton commented on pull request #2708:
URL: https://github.com/apache/airflow/pull/2708#issuecomment-876504246
What are the next steps to get this "official"...I'll see what I can do. I
know nothing about the process and procedures. What I do know is that Airflow
crashed not 15 minutes ago due to exceeding available resources with that
Docker Compose garbage. This would not have happened with Nomad managing
resources. This makes AIRFLOW LOOK BAD and management are never going to look
at the details. "Airflow crashed again" is what management hears and they think
"Let's use something that doesn't crash"
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> Add a Nomad operator to trigger job from Airflow
> ------------------------------------------------
>
> Key: AIRFLOW-1746
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1746
> Project: Apache Airflow
> Issue Type: New Feature
> Components: contrib
> Reporter: Eyal Trabelsi
> Assignee: Eyal Trabelsi
> Priority: Major
>
> We recently face the need to trigger nomad jobs from Airflow and no operator
> are available for that.
> The way the operator works is to register a nomad job and dispatch the job ,
> than check the status of the job using similar method like boto-core
> (https://github.com/boto/botocore/blob/5a07b477114b11e6dc5f676f5db810972565b113/botocore/docs/waiter.py)
> The operator uses https://github.com/jrxFive/python-nomad which is a wrap
> over nomad rest api of nomad written in python.
> Link to the PR : https://github.com/apache/incubator-airflow/pull/2708
--
This message was sent by Atlassian Jira
(v8.3.4#803005)