hiro/ray
1
0
Fork 0
mirror of https://github.com/vale981/ray synced 2025-03-06 10:31:39 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
ray/doc/source/cluster/config.rst
Chen Shen 1d981e0cf1
[doc] fix /cluster/config.html #23720 
closes #23560
2022-04-22 10:13:12 -07:00

1219 lines
36 KiB
ReStructuredText
Raw Blame History

.. include:: we_are_hiring.rst
.. _cluster-config:
Cluster YAML Configuration Options
==================================
The cluster configuration is defined within a YAML file that will be used by the Cluster Launcher to launch the head node, and by the Autoscaler to launch worker nodes. Once the cluster configuration is defined, you will need to use the :ref:`Ray CLI <ray-cli>` to perform any operations such as starting and stopping the cluster.
Syntax
------
.. parsed-literal::
:ref:`cluster_name <cluster-configuration-cluster-name>`: str
:ref:`max_workers <cluster-configuration-max-workers>`: int
:ref:`upscaling_speed <cluster-configuration-upscaling-speed>`: float
:ref:`idle_timeout_minutes <cluster-configuration-idle-timeout-minutes>`: int
:ref:`docker <cluster-configuration-docker>`:
:ref:`docker <cluster-configuration-docker-type>`
:ref:`provider <cluster-configuration-provider>`:
:ref:`provider <cluster-configuration-provider-type>`
:ref:`auth <cluster-configuration-auth>`:
:ref:`auth <cluster-configuration-auth-type>`
:ref:`available_node_types <cluster-configuration-available-node-types>`:
:ref:`node_types <cluster-configuration-node-types-type>`
:ref:`head_node_type <cluster-configuration-head-node-type>`: str
:ref:`file_mounts <cluster-configuration-file-mounts>`:
:ref:`file_mounts <cluster-configuration-file-mounts-type>`
:ref:`cluster_synced_files <cluster-configuration-cluster-synced-files>`:
- str
:ref:`rsync_exclude <cluster-configuration-rsync-exclude>`:
- str
:ref:`rsync_filter <cluster-configuration-rsync-filter>`:
- str
:ref:`initialization_commands <cluster-configuration-initialization-commands>`:
- str
:ref:`setup_commands <cluster-configuration-setup-commands>`:
- str
:ref:`head_setup_commands <cluster-configuration-head-setup-commands>`:
- str
:ref:`worker_setup_commands <cluster-configuration-worker-setup-commands>`:
- str
:ref:`head_start_ray_commands <cluster-configuration-head-start-ray-commands>`:
- str
:ref:`worker_start_ray_commands <cluster-configuration-worker-start-ray-commands>`:
- str
Custom types
------------
.. _cluster-configuration-docker-type:
Docker
~~~~~~
.. parsed-literal::
:ref:`image <cluster-configuration-image>`: str
:ref:`head_image <cluster-configuration-head-image>`: str
:ref:`worker_image <cluster-configuration-worker-image>`: str
:ref:`container_name <cluster-configuration-container-name>`: str
:ref:`pull_before_run <cluster-configuration-pull-before-run>`: bool
:ref:`run_options <cluster-configuration-run-options>`:
- str
:ref:`head_run_options <cluster-configuration-head-run-options>`:
- str
:ref:`worker_run_options <cluster-configuration-worker-run-options>`:
- str
:ref:`disable_automatic_runtime_detection <cluster-configuration-disable-automatic-runtime-detection>`: bool
:ref:`disable_shm_size_detection <cluster-configuration-disable-shm-size-detection>`: bool
.. _cluster-configuration-auth-type:
Auth
~~~~
.. tabbed:: AWS
.. parsed-literal::
:ref:`ssh_user <cluster-configuration-ssh-user>`: str
:ref:`ssh_private_key <cluster-configuration-ssh-private-key>`: str
.. tabbed:: Azure
.. parsed-literal::
:ref:`ssh_user <cluster-configuration-ssh-user>`: str
:ref:`ssh_private_key <cluster-configuration-ssh-private-key>`: str
:ref:`ssh_public_key <cluster-configuration-ssh-public-key>`: str
.. tabbed:: GCP
.. parsed-literal::
:ref:`ssh_user <cluster-configuration-ssh-user>`: str
:ref:`ssh_private_key <cluster-configuration-ssh-private-key>`: str
.. _cluster-configuration-provider-type:
Provider
~~~~~~~~
.. tabbed:: AWS
.. parsed-literal::
:ref:`type <cluster-configuration-type>`: str
:ref:`region <cluster-configuration-region>`: str
:ref:`availability_zone <cluster-configuration-availability-zone>`: str
:ref:`cache_stopped_nodes <cluster-configuration-cache-stopped-nodes>`: bool
:ref:`security_group <cluster-configuration-security-group>`:
:ref:`Security Group <cluster-configuration-security-group-type>`
.. tabbed:: Azure
.. parsed-literal::
:ref:`type <cluster-configuration-type>`: str
:ref:`location <cluster-configuration-location>`: str
:ref:`resource_group <cluster-configuration-resource-group>`: str
:ref:`subscription_id <cluster-configuration-subscription-id>`: str
:ref:`cache_stopped_nodes <cluster-configuration-cache-stopped-nodes>`: bool
.. tabbed:: GCP
.. parsed-literal::
:ref:`type <cluster-configuration-type>`: str
:ref:`region <cluster-configuration-region>`: str
:ref:`availability_zone <cluster-configuration-availability-zone>`: str
:ref:`project_id <cluster-configuration-project-id>`: str
:ref:`cache_stopped_nodes <cluster-configuration-cache-stopped-nodes>`: bool
.. _cluster-configuration-security-group-type:
Security Group
~~~~~~~~~~~~~~
.. tabbed:: AWS
.. parsed-literal::
:ref:`GroupName <cluster-configuration-group-name>`: str
:ref:`IpPermissions <cluster-configuration-ip-permissions>`:
- `IpPermission <https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_IpPermission.html>`_
.. _cluster-configuration-node-types-type:
Node types
~~~~~~~~~~
The ``available_nodes_types`` object's keys represent the names of the different node types.
Deleting a node type from ``available_node_types`` and updating with :ref:`ray up<ray-up-doc>` will cause the autoscaler to scale down all nodes of that type.
In particular, changing the key of a node type object will
result in removal of nodes corresponding to the old key; nodes with the new key name will then be
created according to cluster configuration and Ray resource demands.
.. parsed-literal::
<node_type_1_name>:
:ref:`node_config <cluster-configuration-node-config>`:
:ref:`Node config <cluster-configuration-node-config-type>`
:ref:`resources <cluster-configuration-resources>`:
:ref:`Resources <cluster-configuration-resources-type>`
:ref:`min_workers <cluster-configuration-node-min-workers>`: int
:ref:`max_workers <cluster-configuration-node-max-workers>`: int
:ref:`worker_setup_commands <cluster-configuration-node-type-worker-setup-commands>`:
- str
:ref:`docker <cluster-configuration-node-docker>`:
:ref:`Node Docker <cluster-configuration-node-docker-type>`
<node_type_2_name>:
...
...
.. _cluster-configuration-node-config-type:
Node config
~~~~~~~~~~~
Cloud-specific configuration for nodes of a given node type.
Modifying the ``node_config`` and updating with :ref:`ray up<ray-up-doc>` will cause the autoscaler to scale down all existing nodes of the node type;
nodes with the newly applied ``node_config`` will then be created according to cluster configuration and Ray resource demands.
.. tabbed:: AWS
A YAML object which conforms to the EC2 ``create_instances`` API in `the AWS docs <https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2.html#EC2.ServiceResource.create_instances>`_.
.. tabbed:: Azure
A YAML object as defined in `the deployment template <https://docs.microsoft.com/en-us/azure/templates/microsoft.compute/virtualmachines>`_ whose resources are defined in `the Azure docs <https://docs.microsoft.com/en-us/azure/templates/>`_.
.. tabbed:: GCP
A YAML object as defined in `the GCP docs <https://cloud.google.com/compute/docs/reference/rest/v1/instances>`_.
.. _cluster-configuration-node-docker-type:
Node Docker
~~~~~~~~~~~
.. parsed-literal::
:ref:`worker_image <cluster-configuration-image>`: str
:ref:`pull_before_run <cluster-configuration-pull-before-run>`: bool
:ref:`worker_run_options <cluster-configuration-worker-run-options>`:
- str
:ref:`disable_automatic_runtime_detection <cluster-configuration-disable-automatic-runtime-detection>`: bool
:ref:`disable_shm_size_detection <cluster-configuration-disable-shm-size-detection>`: bool
.. _cluster-configuration-resources-type:
Resources
~~~~~~~~~
.. parsed-literal::
:ref:`CPU <cluster-configuration-CPU>`: int
:ref:`GPU <cluster-configuration-GPU>`: int
:ref:`object_store_memory <cluster-configuration-object-store-memory>`: int
:ref:`memory <cluster-configuration-memory>`: int
<custom_resource1>: int
<custom_resource2>: int
...
.. _cluster-configuration-file-mounts-type:
File mounts
~~~~~~~~~~~
.. parsed-literal::
<path1_on_remote_machine>: str # Path 1 on local machine
<path2_on_remote_machine>: str # Path 2 on local machine
...
Properties and Definitions
--------------------------
.. _cluster-configuration-cluster-name:
``cluster_name``
~~~~~~~~~~~~~~~~
The name of the cluster. This is the namespace of the cluster.
* **Required:** Yes
* **Importance:** High
* **Type:** String
* **Default:** "default"
* **Pattern:** ``[a-zA-Z0-9_]+``
.. _cluster-configuration-max-workers:
``max_workers``
~~~~~~~~~~~~~~~
The maximum number of workers the cluster will have at any given time.
* **Required:** No
* **Importance:** High
* **Type:** Integer
* **Default:** ``2``
* **Minimum:** ``0``
* **Maximum:** Unbounded
.. _cluster-configuration-upscaling-speed:
``upscaling_speed``
~~~~~~~~~~~~~~~~~~~
The number of nodes allowed to be pending as a multiple of the current number of nodes. For example, if set to 1.0, the cluster can grow in size by at most 100% at any time, so if the cluster currently has 20 nodes, at most 20 pending launches are allowed. Note that although the autoscaler will scale down to `min_workers` (which could be 0), it will always scale up to 5 nodes at a minimum when scaling up.
* **Required:** No
* **Importance:** Medium
* **Type:** Float
* **Default:** ``1.0``
* **Minimum:** ``0.0``
* **Maximum:** Unbounded
.. _cluster-configuration-idle-timeout-minutes:
``idle_timeout_minutes``
~~~~~~~~~~~~~~~~~~~~~~~~
The number of minutes that need to pass before an idle worker node is removed by the Autoscaler.
* **Required:** No
* **Importance:** Medium
* **Type:** Integer
* **Default:** ``5``
* **Minimum:** ``0``
* **Maximum:** Unbounded
.. _cluster-configuration-docker:
``docker``
~~~~~~~~~~
Configure Ray to run in Docker containers.
* **Required:** No
* **Importance:** High
* **Type:** :ref:`Docker <cluster-configuration-docker-type>`
* **Default:** ``{}``
In rare cases when Docker is not available on the system by default (e.g., bad AMI), add the following commands to :ref:`initialization_commands <cluster-configuration-initialization-commands>` to install it.
.. code-block:: yaml
initialization_commands:
- curl -fsSL https://get.docker.com -o get-docker.sh
- sudo sh get-docker.sh
- sudo usermod -aG docker $USER
- sudo systemctl restart docker -f
.. _cluster-configuration-provider:
``provider``
~~~~~~~~~~~~
The cloud provider-specific configuration properties.
* **Required:** Yes
* **Importance:** High
* **Type:** :ref:`Provider <cluster-configuration-provider-type>`
.. _cluster-configuration-auth:
``auth``
~~~~~~~~
Authentication credentials that Ray will use to launch nodes.
* **Required:** Yes
* **Importance:** High
* **Type:** :ref:`Auth <cluster-configuration-auth-type>`
.. _cluster-configuration-available-node-types:
``available_node_types``
~~~~~~~~~~~~~~~~~~~~~~~~
Tells the autoscaler the allowed node types and the resources they provide.
Each node type is identified by a user-specified key.
* **Required:** No
* **Importance:** High
* **Type:** :ref:`Node types <cluster-configuration-node-types-type>`
* **Default:**
.. tabbed:: AWS
.. code-block:: yaml
available_node_types:
ray.head.default:
node_config:
InstanceType: m5.large
BlockDeviceMappings:
- DeviceName: /dev/sda1
Ebs:
VolumeSize: 100
resources: {"CPU": 2}
ray.worker.default:
node_config:
InstanceType: m5.large
InstanceMarketOptions:
MarketType: spot
resources: {"CPU": 2}
min_workers: 0
.. _cluster-configuration-head-node-type:
``head_node_type``
~~~~~~~~~~~~~~~~~~
The key for one of the node types in :ref:`available_node_types <cluster-configuration-available-node-types>`. This node type will be used to launch the head node.
If the field ``head_node_type`` is changed and an update is executed with :ref:`ray up<ray-up-doc>`, the currently running head node will
be considered outdated. The user will receive a prompt asking to confirm scale-down of the outdated head node, and the cluster will restart with a new
head node. Changing the :ref:`node_config<cluster-configuration-node-config>` of the :ref:`node_type<cluster-configuration-node-types-type>` with key ``head_node_type`` will also result in cluster restart after a user prompt.
* **Required:** Yes
* **Importance:** High
* **Type:** String
* **Pattern:** ``[a-zA-Z0-9_]+``
.. _cluster-configuration-file-mounts:
``file_mounts``
~~~~~~~~~~~~~~~
The files or directories to copy to the head and worker nodes.
* **Required:** No
* **Importance:** High
* **Type:** :ref:`File mounts <cluster-configuration-file-mounts-type>`
* **Default:** ``[]``
.. _cluster-configuration-cluster-synced-files:
``cluster_synced_files``
~~~~~~~~~~~~~~~~~~~~~~~~
A list of paths to the files or directories to copy from the head node to the worker nodes. The same path on the head node will be copied to the worker node. This behavior is a subset of the file_mounts behavior, so in the vast majority of cases one should just use :ref:`file_mounts <cluster-configuration-file-mounts>`.
* **Required:** No
* **Importance:** Low
* **Type:** List of String
* **Default:** ``[]``
.. _cluster-configuration-rsync-exclude:
``rsync_exclude``
~~~~~~~~~~~~~~~~~
A list of patterns for files to exclude when running ``rsync up`` or ``rsync down``. The filter is applied on the source directory only.
Example for a pattern in the list: ``**/.git/**``.
* **Required:** No
* **Importance:** Low
* **Type:** List of String
* **Default:** ``[]``
.. _cluster-configuration-rsync-filter:
``rsync_filter``
~~~~~~~~~~~~~~~~
A list of patterns for files to exclude when running ``rsync up`` or ``rsync down``. The filter is applied on the source directory and recursively through all subdirectories.
Example for a pattern in the list: ``.gitignore``.
* **Required:** No
* **Importance:** Low
* **Type:** List of String
* **Default:** ``[]``
.. _cluster-configuration-initialization-commands:
``initialization_commands``
~~~~~~~~~~~~~~~~~~~~~~~~~~~
A list of commands that will be run before the :ref:`setup commands <cluster-configuration-setup-commands>`. If Docker is enabled, these commands will run outside the container and before Docker is setup.
* **Required:** No
* **Importance:** Medium
* **Type:** List of String
* **Default:** ``[]``
.. _cluster-configuration-setup-commands:
``setup_commands``
~~~~~~~~~~~~~~~~~~
A list of commands to run to set up nodes. These commands will always run on the head and worker nodes and will be merged with :ref:`head setup commands <cluster-configuration-head-setup-commands>` for head and with :ref:`worker setup commands <cluster-configuration-worker-setup-commands>` for workers.
* **Required:** No
* **Importance:** Medium
* **Type:** List of String
* **Default:**
.. tabbed:: AWS
.. code-block:: yaml
# Default setup_commands:
setup_commands:
- echo 'export PATH="$HOME/anaconda3/envs/tensorflow_p36/bin:$PATH"' >> ~/.bashrc
- pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-2.0.0.dev0-cp36-cp36m-manylinux2014_x86_64.whl
- Setup commands should ideally be *idempotent* (i.e., can be run multiple times without changing the result); this allows Ray to safely update nodes after they have been created. You can usually make commands idempotent with small modifications, e.g. ``git clone foo`` can be rewritten as ``test -e foo || git clone foo`` which checks if the repo is already cloned first.
- Setup commands are run sequentially but separately. For example, if you are using anaconda, you need to run ``conda activate env && pip install -U ray`` because splitting the command into two setup commands will not work.
- Ideally, you should avoid using setup_commands by creating a docker image with all the dependencies preinstalled to minimize startup time.
- **Tip**: if you also want to run apt-get commands during setup add the following list of commands:
.. code-block:: yaml
setup_commands:
- sudo pkill -9 apt-get || true
- sudo pkill -9 dpkg || true
- sudo dpkg --configure -a
.. _cluster-configuration-head-setup-commands:
``head_setup_commands``
~~~~~~~~~~~~~~~~~~~~~~~
A list of commands to run to set up the head node. These commands will be merged with the general :ref:`setup commands <cluster-configuration-setup-commands>`.
* **Required:** No
* **Importance:** Low
* **Type:** List of String
* **Default:** ``[]``
.. _cluster-configuration-worker-setup-commands:
``worker_setup_commands``
~~~~~~~~~~~~~~~~~~~~~~~~~
A list of commands to run to set up the worker nodes. These commands will be merged with the general :ref:`setup commands <cluster-configuration-setup-commands>`.
* **Required:** No
* **Importance:** Low
* **Type:** List of String
* **Default:** ``[]``
.. _cluster-configuration-head-start-ray-commands:
``head_start_ray_commands``
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Commands to start ray on the head node. You don't need to change this.
* **Required:** No
* **Importance:** Low
* **Type:** List of String
* **Default:**
.. tabbed:: AWS
.. code-block:: yaml
head_start_ray_commands:
- ray stop
- ulimit -n 65536; ray start --head --port=6379 --object-manager-port=8076 --autoscaling-config=~/ray_bootstrap_config.yaml
.. _cluster-configuration-worker-start-ray-commands:
``worker_start_ray_commands``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Command to start ray on worker nodes. You don't need to change this.
* **Required:** No
* **Importance:** Low
* **Type:** List of String
* **Default:**
.. tabbed:: AWS
.. code-block:: yaml
worker_start_ray_commands:
- ray stop
- ulimit -n 65536; ray start --address=$RAY_HEAD_IP:6379 --object-manager-port=8076
.. _cluster-configuration-image:
``docker.image``
~~~~~~~~~~~~~~~~
The default Docker image to pull in the head and worker nodes. This can be overridden by the :ref:`head_image <cluster-configuration-head-image>` and :ref:`worker_image <cluster-configuration-worker-image>` fields. If neither `image` nor (:ref:`head_image <cluster-configuration-head-image>` and :ref:`worker_image <cluster-configuration-worker-image>`) are specified, Ray will not use Docker.
* **Required:** Yes (If Docker is in use.)
* **Importance:** High
* **Type:** String
The Ray project provides Docker images on `DockerHub <https://hub.docker.com/u/rayproject>`_. The repository includes following images:
* ``rayproject/ray-ml:latest-gpu``: CUDA support, includes ML dependencies.
* ``rayproject/ray:latest-gpu``: CUDA support, no ML dependencies.
* ``rayproject/ray-ml:latest``: No CUDA support, includes ML dependencies.
* ``rayproject/ray:latest``: No CUDA support, no ML dependencies.
.. _cluster-configuration-head-image:
``docker.head_image``
~~~~~~~~~~~~~~~~~~~~~
Docker image for the head node to override the default :ref:`docker image <cluster-configuration-image>`.
* **Required:** No
* **Importance:** Low
* **Type:** String
.. _cluster-configuration-worker-image:
``docker.worker_image``
~~~~~~~~~~~~~~~~~~~~~~~
Docker image for the worker nodes to override the default :ref:`docker image <cluster-configuration-image>`.
* **Required:** No
* **Importance:** Low
* **Type:** String
.. _cluster-configuration-container-name:
``docker.container_name``
~~~~~~~~~~~~~~~~~~~~~~~~~
The name to use when starting the Docker container.
* **Required:** Yes (If Docker is in use.)
* **Importance:** Low
* **Type:** String
* **Default:** ray_container
.. _cluster-configuration-pull-before-run:
``docker.pull_before_run``
~~~~~~~~~~~~~~~~~~~~~~~~~~
If enabled, the latest version of image will be pulled when starting Docker. If disabled, ``docker run`` will only pull the image if no cached version is present.
* **Required:** No
* **Importance:** Medium
* **Type:** Boolean
* **Default:** ``True``
.. _cluster-configuration-run-options:
``docker.run_options``
~~~~~~~~~~~~~~~~~~~~~~
The extra options to pass to ``docker run``.
* **Required:** No
* **Importance:** Medium
* **Type:** List of String
* **Default:** ``[]``
.. _cluster-configuration-head-run-options:
``docker.head_run_options``
~~~~~~~~~~~~~~~~~~~~~~~~~~~
The extra options to pass to ``docker run`` for head node only.
* **Required:** No
* **Importance:** Low
* **Type:** List of String
* **Default:** ``[]``
.. _cluster-configuration-worker-run-options:
``docker.worker_run_options``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The extra options to pass to ``docker run`` for worker nodes only.
* **Required:** No
* **Importance:** Low
* **Type:** List of String
* **Default:** ``[]``
.. _cluster-configuration-disable-automatic-runtime-detection:
``docker.disable_automatic_runtime_detection``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If enabled, Ray will not try to use the NVIDIA Container Runtime if GPUs are present.
* **Required:** No
* **Importance:** Low
* **Type:** Boolean
* **Default:** ``False``
.. _cluster-configuration-disable-shm-size-detection:
``docker.disable_shm_size_detection``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If enabled, Ray will not automatically specify the size ``/dev/shm`` for the started container and the runtime's default value (64MiB for Docker) will be used.
If ``--shm-size=<>`` is manually added to ``run_options``, this is *automatically* set to ``True``, meaning that Ray will defer to the user-provided value.
* **Required:** No
* **Importance:** Low
* **Type:** Boolean
* **Default:** ``False``
.. _cluster-configuration-ssh-user:
``auth.ssh_user``
~~~~~~~~~~~~~~~~~
The user that Ray will authenticate with when launching new nodes.
* **Required:** Yes
* **Importance:** High
* **Type:** String
.. _cluster-configuration-ssh-private-key:
``auth.ssh_private_key``
~~~~~~~~~~~~~~~~~~~~~~~~
.. tabbed:: AWS
The path to an existing private key for Ray to use. If not configured, Ray will create a new private keypair (default behavior). If configured, the key must be added to the project-wide metadata and ``KeyName`` has to be defined in the :ref:`node configuration <cluster-configuration-node-config>`.
* **Required:** No
* **Importance:** Low
* **Type:** String
.. tabbed:: Azure
The path to an existing private key for Ray to use.
* **Required:** Yes
* **Importance:** High
* **Type:** String
You may use ``ssh-keygen -t rsa -b 4096`` to generate a new ssh keypair.
.. tabbed:: GCP
The path to an existing private key for Ray to use. If not configured, Ray will create a new private keypair (default behavior). If configured, the key must be added to the project-wide metadata and ``KeyName`` has to be defined in the :ref:`node configuration <cluster-configuration-node-config>`.
* **Required:** No
* **Importance:** Low
* **Type:** String
.. _cluster-configuration-ssh-public-key:
``auth.ssh_public_key``
~~~~~~~~~~~~~~~~~~~~~~~
.. tabbed:: AWS
Not available.
.. tabbed:: Azure
The path to an existing public key for Ray to use.
* **Required:** Yes
* **Importance:** High
* **Type:** String
.. tabbed:: GCP
Not available.
.. _cluster-configuration-type:
``provider.type``
~~~~~~~~~~~~~~~~~
.. tabbed:: AWS
The cloud service provider. For AWS, this must be set to ``aws``.
* **Required:** Yes
* **Importance:** High
* **Type:** String
.. tabbed:: Azure
The cloud service provider. For Azure, this must be set to ``azure``.
* **Required:** Yes
* **Importance:** High
* **Type:** String
.. tabbed:: GCP
The cloud service provider. For GCP, this must be set to ``gcp``.
* **Required:** Yes
* **Importance:** High
* **Type:** String
.. _cluster-configuration-region:
``provider.region``
~~~~~~~~~~~~~~~~~~~
.. tabbed:: AWS
The region to use for deployment of the Ray cluster.
* **Required:** Yes
* **Importance:** High
* **Type:** String
* **Default:** us-west-2
.. tabbed:: Azure
Not available.
.. tabbed:: GCP
The region to use for deployment of the Ray cluster.
* **Required:** Yes
* **Importance:** High
* **Type:** String
* **Default:** us-west1
.. _cluster-configuration-availability-zone:
``provider.availability_zone``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. tabbed:: AWS
A string specifying a comma-separated list of availability zone(s) that nodes may be launched in.
Nodes will be launched in the first listed availability zone and will be tried in the following availability
zones if launching fails.
* **Required:** No
* **Importance:** Low
* **Type:** String
* **Default:** us-west-2a,us-west-2b
.. tabbed:: Azure
Not available.
.. tabbed:: GCP
A string specifying a comma-separated list of availability zone(s) that nodes may be launched in.
* **Required:** No
* **Importance:** Low
* **Type:** String
* **Default:** us-west1-a
.. _cluster-configuration-location:
``provider.location``
~~~~~~~~~~~~~~~~~~~~~
.. tabbed:: AWS
Not available.
.. tabbed:: Azure
The location to use for deployment of the Ray cluster.
* **Required:** Yes
* **Importance:** High
* **Type:** String
* **Default:** westus2
.. tabbed:: GCP
Not available.
.. _cluster-configuration-resource-group:
``provider.resource_group``
~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. tabbed:: AWS
Not available.
.. tabbed:: Azure
The resource group to use for deployment of the Ray cluster.
* **Required:** Yes
* **Importance:** High
* **Type:** String
* **Default:** ray-cluster
.. tabbed:: GCP
Not available.
.. _cluster-configuration-subscription-id:
``provider.subscription_id``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. tabbed:: AWS
Not available.
.. tabbed:: Azure
The subscription ID to use for deployment of the Ray cluster. If not specified, Ray will use the default from the Azure CLI.
* **Required:** No
* **Importance:** High
* **Type:** String
* **Default:** ``""``
.. tabbed:: GCP
Not available.
.. _cluster-configuration-project-id:
``provider.project_id``
~~~~~~~~~~~~~~~~~~~~~~~
.. tabbed:: AWS
Not available.
.. tabbed:: Azure
Not available.
.. tabbed:: GCP
The globally unique project ID to use for deployment of the Ray cluster.
* **Required:** Yes
* **Importance:** Low
* **Type:** String
* **Default:** ``null``
.. _cluster-configuration-cache-stopped-nodes:
``provider.cache_stopped_nodes``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If enabled, nodes will be *stopped* when the cluster scales down. If disabled, nodes will be *terminated* instead. Stopped nodes launch faster than terminated nodes.
* **Required:** No
* **Importance:** Low
* **Type:** Boolean
* **Default:** ``True``
.. _cluster-configuration-security-group:
``provider.security_group``
~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. tabbed:: AWS
A security group that can be used to specify custom inbound rules.
* **Required:** No
* **Importance:** Medium
* **Type:** :ref:`Security Group <cluster-configuration-security-group-type>`
.. tabbed:: Azure
Not available.
.. tabbed:: GCP
Not available.
.. _cluster-configuration-group-name:
``security_group.GroupName``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The name of the security group. This name must be unique within the VPC.
* **Required:** No
* **Importance:** Low
* **Type:** String
* **Default:** ``"ray-autoscaler-{cluster-name}"``
.. _cluster-configuration-ip-permissions:
``security_group.IpPermissions``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The inbound rules associated with the security group.
* **Required:** No
* **Importance:** Medium
* **Type:** `IpPermission <https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_IpPermission.html>`_
.. _cluster-configuration-node-config:
``available_node_types.<node_type_name>.node_type.node_config``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The configuration to be used to launch the nodes on the cloud service provider. Among other things, this will specify the instance type to be launched.
* **Required:** Yes
* **Importance:** High
* **Type:** :ref:`Node config <cluster-configuration-node-config-type>`
.. _cluster-configuration-resources:
``available_node_types.<node_type_name>.node_type.resources``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The resources that a node type provides, which enables the autoscaler to automatically select the right type of nodes to launch given the resource demands of the application. The resources specified will be automatically passed to the ``ray start`` command for the node via an environment variable. If not provided, Autoscaler can automatically detect them only for AWS/Kubernetes cloud providers. For more information, see also the `resource demand scheduler <https://github.com/ray-project/ray/blob/master/python/ray/autoscaler/_private/resource_demand_scheduler.py>`_
* **Required:** Yes (except for AWS/K8s)
* **Importance:** High
* **Type:** :ref:`Resources <cluster-configuration-resources-type>`
* **Default:** ``{}``
In some cases, adding special nodes without any resources may be desirable. Such nodes can be used as a driver which connects to the cluster to launch jobs. In order to manually add a node to an autoscaled cluster, the *ray-cluster-name* tag should be set and *ray-node-type* tag should be set to unmanaged. Unmanaged nodes can be created by setting the resources to ``{}`` and the :ref:`maximum workers <cluster-configuration-node-min-workers>` to 0. The Autoscaler will not attempt to start, stop, or update unmanaged nodes. The user is responsible for properly setting up and cleaning up unmanaged nodes.
.. _cluster-configuration-node-min-workers:
``available_node_types.<node_type_name>.node_type.min_workers``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The minimum number of workers to maintain for this node type regardless of utilization.
* **Required:** No
* **Importance:** High
* **Type:** Integer
* **Default:** ``0``
* **Minimum:** ``0``
* **Maximum:** Unbounded
.. _cluster-configuration-node-max-workers:
``available_node_types.<node_type_name>.node_type.max_workers``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The maximum number of workers to have in the cluster for this node type regardless of utilization. This takes precedence over :ref:`minimum workers <cluster-configuration-node-min-workers>`. By default, the number of workers of a node type is unbounded, constrained only by the cluster-wide :ref:`max_workers <cluster-configuration-max-workers>`. (Prior to Ray 1.3.0, the default value for this field was 0.)
Note, for the nodes of type ``head_node_type`` the default number of max workers is 0.
* **Required:** No
* **Importance:** High
* **Type:** Integer
* **Default:** cluster-wide :ref:`max_workers <cluster-configuration-max-workers>`
* **Minimum:** ``0``
* **Maximum:** cluster-wide :ref:`max_workers <cluster-configuration-max-workers>`
.. _cluster-configuration-node-type-worker-setup-commands:
``available_node_types.<node_type_name>.node_type.worker_setup_commands``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A list of commands to run to set up worker nodes of this type. These commands will replace the general :ref:`worker setup commands <cluster-configuration-worker-setup-commands>` for the node.
* **Required:** No
* **Importance:** low
* **Type:** List of String
* **Default:** ``[]``
.. _cluster-configuration-cpu:
``available_node_types.<node_type_name>.node_type.resources.CPU``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. tabbed:: AWS
The number of CPUs made available by this node. If not configured, Autoscaler can automatically detect them only for AWS/Kubernetes cloud providers.
* **Required:** Yes (except for AWS/K8s)
* **Importance:** High
* **Type:** Integer
.. tabbed:: Azure
The number of CPUs made available by this node.
* **Required:** Yes
* **Importance:** High
* **Type:** Integer
.. tabbed:: GCP
The number of CPUs made available by this node.
* **Required:** No
* **Importance:** High
* **Type:** Integer
.. _cluster-configuration-gpu:
``available_node_types.<node_type_name>.node_type.resources.GPU``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. tabbed:: AWS
The number of GPUs made available by this node. If not configured, Autoscaler can automatically detect them only for AWS/Kubernetes cloud providers.
* **Required:** No
* **Importance:** Low
* **Type:** Integer
.. tabbed:: Azure
The number of GPUs made available by this node.
* **Required:** No
* **Importance:** High
* **Type:** Integer
.. tabbed:: GCP
The number of GPUs made available by this node.
* **Required:** No
* **Importance:** High
* **Type:** Integer
.. _cluster-configuration-memory:
``available_node_types.<node_type_name>.node_type.resources.memory``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. tabbed:: AWS
The memory in bytes allocated for python worker heap memory on the node. If not configured, Autoscaler will automatically detect the amount of RAM on the node for AWS/Kubernetes and allocate 70% of it for the heap.
* **Required:** No
* **Importance:** Low
* **Type:** Integer
.. tabbed:: Azure
The memory in bytes allocated for python worker heap memory on the node.
* **Required:** No
* **Importance:** High
* **Type:** Integer
.. tabbed:: GCP
The memory in bytes allocated for python worker heap memory on the node.
* **Required:** No
* **Importance:** High
* **Type:** Integer
.. _cluster-configuration-object-store-memory:
``available_node_types.<node_type_name>.node_type.resources.object-store-memory``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. tabbed:: AWS
The memory in bytes allocated for the object store on the node. If not configured, Autoscaler will automatically detect the amount of RAM on the node for AWS/Kubernetes and allocate 30% of it for the object store.
* **Required:** No
* **Importance:** Low
* **Type:** Integer
.. tabbed:: Azure
The memory in bytes allocated for the object store on the node.
* **Required:** No
* **Importance:** High
* **Type:** Integer
.. tabbed:: GCP
The memory in bytes allocated for the object store on the node.
* **Required:** No
* **Importance:** High
* **Type:** Integer
.. _cluster-configuration-node-docker:
``available_node_types.<node_type_name>.docker``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A set of overrides to the top-level :ref:`Docker <cluster-configuration-docker>` configuration.
* **Required:** No
* **Importance:** Low
* **Type:** :ref:`docker <cluster-configuration-node-docker-type>`
* **Default:** ``{}``
Examples
--------
Minimal configuration
~~~~~~~~~~~~~~~~~~~~~
.. tabbed:: AWS
.. literalinclude:: ../../../python/ray/autoscaler/aws/example-minimal.yaml
:language: yaml
.. tabbed:: Azure
.. literalinclude:: ../../../python/ray/autoscaler/azure/example-minimal.yaml
:language: yaml
.. tabbed:: GCP
.. literalinclude:: ../../../python/ray/autoscaler/gcp/example-minimal.yaml
:language: yaml
Full configuration
~~~~~~~~~~~~~~~~~~
.. tabbed:: AWS
.. literalinclude:: ../../../python/ray/autoscaler/aws/example-full.yaml
:language: yaml
.. tabbed:: Azure
.. literalinclude:: ../../../python/ray/autoscaler/azure/example-full.yaml
:language: yaml
.. tabbed:: GCP
.. literalinclude:: ../../../python/ray/autoscaler/gcp/example-full.yaml
:language: yaml
TPU Configuration
~~~~~~~~~~~~~~~~~
It is possible to use `TPU VMs <https://cloud.google.com/tpu/docs/users-guide-tpu-vm>`_ on GCP. Currently, `TPU pods <https://cloud.google.com/tpu/docs/system-architecture-tpu-vm#pods>`_ (TPUs other than v2-8 and v3-8) are not supported.
Before using a config with TPUs, ensure that the `TPU API is enabled for your GCP project <https://cloud.google.com/tpu/docs/users-guide-tpu-vm#enable_the_cloud_tpu_api>`_.
.. tabbed:: GCP
.. literalinclude:: ../../../python/ray/autoscaler/gcp/tpu.yaml
:language: yaml
Reference in a new issue View git blame Copy permalink