airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-3284) Support for Azure Batch AI Deployment
Date Fri, 07 Dec 2018 17:11:00 GMT

    [ https://issues.apache.org/jira/browse/AIRFLOW-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16713097#comment-16713097
] 

ASF GitHub Bot commented on AIRFLOW-3284:
-----------------------------------------

elizabethhalper opened a new pull request #4293: [AIRFLOW-3284] Add Azure Batch AI Operator
URL: https://github.com/apache/incubator-airflow/pull/4293
 
 
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [ ] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/)
issues and references them in the PR title:
     -https://issues.apache.org/jira/browse/AIRFLOW-3284
     - In case you are fixing a typo in the documentation you can prepend your commit with
[AIRFLOW-3284], code changes always need a Jira issue.
   
   ### Description
   
   - [ ] Here are some details about my PR, including screenshots of any UI changes:
   Adds an operator to create an Azure Batch AI cluster. There is a hook, example DAG, and
tests to support this operator. Azure Batch AI allows users to experiment and train deep learning
and AI models in parallel at scale.
   Operator supports creating a batch AI cluster by using any Marketplace image when given
the publisher, offer, sku, and version.
   
   ### Tests
   
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely
good reason:
   There are unit tests that test a successful execution of the operator and an execution
that raises an Airflow exception.
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines, and I have squashed
multiple commits if they address the same issue. In addition, my commits follow the guidelines
from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes how to use
it.
     - When adding new operators/hooks/sensors, the autoclass documentation generation needs
to be added.
     - All the public functions and the classes in the PR contain docstrings that explain
what it does
   
   ### Code Quality
   
   - [ ] Passes `flake8`
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Support for Azure Batch AI Deployment
> -------------------------------------
>
>                 Key: AIRFLOW-3284
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3284
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: hooks, operators
>            Reporter: Elizabeth
>            Assignee: Elizabeth
>            Priority: Major
>
> An Azure Batch AI Operator allows the user to run and monitor a Batch AI Cluster on Azure



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message