We wanted to provide at least 2 different ways for deploying Ray. One that is dependent on JupyterHub and one that is not (which can be compatible with other interfaces like Kubeflow Notebooks).
This PR is primarily organization:
1) Renamed "odh-ray-cluster" to "odh-ray-jh" and left unchanged. This directory contains everything needed for the JH integration of Ray.
2) Created "odh-ray-nbc" which contains files needed to deploy the Ray Operator and a Ray cluster independent of Jupyterhub, Future PR will also include kuebflow notebook resource that works with Ray.
We wanted to provide at least 2 different ways for deploying Ray. One that is dependent on JupyterHub and one that is not (which can be compatible with other interfaces like Kubeflow Notebooks).
This PR is primarily organization: 1) Renamed "odh-ray-cluster" to "odh-ray-jh" and left unchanged. This directory contains everything needed for the JH integration of Ray.
2) Created "odh-ray-nbc" which contains files needed to deploy the Ray Operator and a Ray cluster independent of Jupyterhub, Future PR will also include kuebflow notebook resource that works with Ray.