antoniocali opened a new pull request #10578: URL: https://github.com/apache/airflow/pull/10578
**Jira** My PR addresses the following Airflow Jira issues and references them in the PR title. https://issues.apache.org/jira/browse/AAR-487 **Description** _Why this is important?_ At the moment when you spin up a training, you cannot specify an accelerator, so when you end up with a CUSTOM tier and a standard machine, you cannot add GPUs that would speed up the training process. _Documentation_ It refers to the follow [REST API Documentation](https://cloud.google.com/ai-platform/training/docs/reference/rest/v1/projects.jobs#traininginput). > Optional. The configuration for your master worker. > > You should only set masterConfig.acceleratorConfig if masterType is set to a Compute Engine machine type. Learn about restrictions on accelerator configurations for training. <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md). ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
