mirror of
https://github.com/wassname/ray.git
synced 2026-08-16 11:27:09 +08:00
[docs] Add example showing how to use Ray on Kubernetes. (#3126)
Closes #1353.
This commit is contained in:
@@ -0,0 +1,143 @@
|
||||
Deploying on Kubernetes
|
||||
=======================
|
||||
|
||||
.. warning::
|
||||
|
||||
These instructions have not been tested extensively. If you have a suggestion
|
||||
for how to improve them, please open a pull request or email
|
||||
ray-dev@googlegroups.com.
|
||||
|
||||
You can run Ray on top of Kubernetes. This document assumes that you have access
|
||||
to a Kubernetes cluster and have ``kubectl`` installed locally.
|
||||
|
||||
Start by cloning the Ray repository.
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
git clone https://github.com/ray-project/ray.git
|
||||
|
||||
Work Interactively on the Cluster
|
||||
---------------------------------
|
||||
|
||||
To work interactively, first start Ray on Kubernetes.
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
kubectl create -f ray/kubernetes/head.yaml
|
||||
kubectl create -f ray/kubernetes/worker.yaml
|
||||
|
||||
This will start one head pod and 3 worker pods. You can check that the pods are
|
||||
running by running ``kubectl get pods``.
|
||||
|
||||
You should see something like the following (you will have to wait a couple
|
||||
minutes for the pods to enter the "Running" state).
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
$ kubectl get pods
|
||||
NAME READY STATUS RESTARTS AGE
|
||||
ray-head-controller-2kkfq 1/1 Running 0 47s
|
||||
ray-worker-controller-d6jml 1/1 Running 0 45s
|
||||
ray-worker-controller-m7jxs 1/1 Running 0 45s
|
||||
ray-worker-controller-rg2sl 1/1 Running 0 45s
|
||||
|
||||
To run tasks interactively on the cluster, connect to one of the pods, e.g.,
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
kubectl exec -it ray-head-controller-2kkfq -- bash
|
||||
|
||||
Start an IPython interpreter, e.g., ``ipython``
|
||||
|
||||
.. code-block:: python
|
||||
|
||||
from collections import Counter
|
||||
import socket
|
||||
import time
|
||||
import ray
|
||||
|
||||
ray.init(redis_address="{}:6379".format(socket.gethostbyname("ray-head")))
|
||||
|
||||
@ray.remote
|
||||
def f(x):
|
||||
time.sleep(0.01)
|
||||
return x + (ray.services.get_node_ip_address(), )
|
||||
|
||||
# Check that objects can be transferred from each node to each other node.
|
||||
%time Counter(ray.get([f.remote(f.remote(())) for _ in range(1000)]))
|
||||
|
||||
Submitting a Script to the Cluster
|
||||
----------------------------------
|
||||
|
||||
To submit a self-contained Ray application to your Kubernetes cluster, do the
|
||||
following.
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
kubectl create -f ray/kubernetes/submit.yaml
|
||||
|
||||
One of the pods will download and run `this example script`_.
|
||||
|
||||
.. _`this example script`: https://github.com/ray-project/ray/tree/master/kubernetes/example.py
|
||||
|
||||
The script prints its output. To view the output, first find the pod name by
|
||||
running ``kubectl get all``. You'll see output like the following.
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
$ kubectl get all
|
||||
NAME READY STATUS RESTARTS AGE
|
||||
pod/ray-head-controller-q6lck 1/1 Running 0 1m
|
||||
pod/ray-worker-controller-kchfh 1/1 Running 0 1m
|
||||
pod/ray-worker-controller-nmq5c 1/1 Running 0 1m
|
||||
pod/ray-worker-controller-tfl2q 1/1 Running 0 1m
|
||||
|
||||
NAME DESIRED CURRENT READY AGE
|
||||
replicationcontroller/ray-head-controller 1 1 1 1m
|
||||
replicationcontroller/ray-worker-controller 3 3 3 1m
|
||||
|
||||
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
|
||||
service/ray-head ClusterIP 10.64.5.153 <none> 6379/TCP,6380/TCP,6381/TCP,12345/TCP,12346/TCP 1m
|
||||
|
||||
Find the name of the ``ray-head-controller`` pod and run the equivalent of
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
kubectl logs ray-head-controller-q6lck
|
||||
|
||||
Cleaning Up
|
||||
-----------
|
||||
|
||||
To remove the services you have created, run the following.
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
kubectl delete service/ray-head \
|
||||
replicationcontroller/ray-head-controller \
|
||||
replicationcontroller/ray-worker-controller
|
||||
|
||||
|
||||
Customization
|
||||
-------------
|
||||
|
||||
You will probably need to do some amount of customization.
|
||||
|
||||
1. The example above uses the Docker image ``rayproject/examples``, which is
|
||||
built using `these Dockerfiles`_. You will most likely need to use your own
|
||||
Docker image.
|
||||
2. You will need to modify the ``command`` and ``args`` fields to potentially
|
||||
install and run the script of your choice.
|
||||
3. You will need to customize the resource requests.
|
||||
|
||||
TODO
|
||||
----
|
||||
|
||||
The following are also important but haven't been documented yet. Contributions
|
||||
are welcome!
|
||||
|
||||
1. Request CPU/GPU/memory resources.
|
||||
2. Increase shared memory.
|
||||
3. How to make Kubernetes clean itself up once the script finishes.
|
||||
4. Follow Kubernetes best practices.
|
||||
|
||||
.. _`these Dockerfiles`: https://github.com/ray-project/ray/tree/master/docker
|
||||
@@ -53,6 +53,7 @@ Ray comes with libraries that accelerate deep learning and reinforcement learnin
|
||||
:caption: Installation
|
||||
|
||||
installation.rst
|
||||
deploy-on-kubernetes.rst
|
||||
install-on-docker.rst
|
||||
installation-troubleshooting.rst
|
||||
|
||||
|
||||
Reference in New Issue
Block a user