mirror of
https://github.com/vale981/ray
synced 2025-03-06 10:31:39 -05:00
76bb5396c7
- Adds links to Job Submission from existing library tutorials where `ray submit` is used. When Jobs becomes GA, we should fully replace the uses of `ray submit` with Ray job submission and ensure this is tested. - Adds docstrings for the Jobs SDK, which automatically show up in the API reference - Improve the Job Submission main page - Add a "Deployment Guide" landing page explaining when to use Ray Client vs Ray Jobs Co-authored-by: Edward Oakes <ed.nmi.oakes@gmail.com>
22 lines
844 B
ReStructuredText
22 lines
844 B
ReStructuredText
.. include:: we_are_hiring.rst
|
|
|
|
.. _ref-deployment-guide:
|
|
|
|
Deployment Guide
|
|
================
|
|
|
|
This section explains how to set up a distributed Ray cluster and run your workloads on it.
|
|
|
|
To set up your cluster, check out the :ref:`Ray Cluster Overview <cluster-index>`, or jump to the :ref:`Ray Cluster Quick Start <ref-cluster-quick-start>`.
|
|
|
|
To trigger a Ray workload from your local machine, a CI system, or a third-party job scheduler/orchestrator via a command line interface or API call, try :ref:`Ray Job Submission <jobs-overview>`.
|
|
|
|
To run an interactive Ray workload and see the output in real time in a client of your choice (e.g. your local machine, SageMaker Studio, or Google Colab), you can use :ref:`Ray Client <ray-client>`.
|
|
|
|
.. toctree::
|
|
:maxdepth: 2
|
|
|
|
index.rst
|
|
guide.rst
|
|
job-submission.rst
|
|
ray-client.rst
|