You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+20-10
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
# Ray VPC allocator / Configuration Generator For IBM VPC
2
2
3
-
`ibm-ray-config` is a CLI tool that seamlessly allocates and registers VPC resources, such as: subnets, gateways, ips, ssh keys and security groups rules to generate Ray configuration files for IBM VPC.
3
+
`ibm-ray-config` is a CLI tool that seamlessly allocates and registers VPC resources (such as: subnets, gateways, ips, ssh keys and security groups rules), to generate Ray configuration files and executables for IBM VPC.
4
4
5
5
## Setup
6
6
7
-
The tool has been mostly tested with Ubuntu 18.04/20.04 and Fedora 35, but should work with most Linux systems.
7
+
The tool has been mostly tested with Ubuntu 20.04/22.04 and Fedora 35/37, but should work on most Linux systems.
8
8
Requirements: `ssh-keygen` utility installed:
9
9
```
10
10
sudo apt install openssh-client
@@ -17,10 +17,11 @@ pip install ibm-ray-config
17
17
```
18
18
19
19
## Usage
20
-
Use the configuration tool as follows:
20
+
21
+
### Set up IBM VPC resources and configure a cluster for Ray:
| iam-api-key | |yes|IBM Cloud API key. To generate a new API Key, adhere to the following [guide](https://www.ibm.com/docs/en/spectrumvirtualizecl/8.1.3?topic=installing-creating-api-key)
36
-
| input-file |<compute_backend>/defaults.py| no | Existing config file to be used as a template in the configuration process |
37
-
| output-path |A randomly generated path to a folder | no |A custom location for the program's outputs |
38
-
| version || no |Returns ibm-ray-config's package version|
39
-
|endpoint|| no|Geographical location for deployment and scope for available resources by the IBM-VPC service. Endpoint urls are listed <ahref="https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-in-a-different-region&interface=cli"> here</a>. |
37
+
|output-path |current working directory ($PWD) | no |A custom location for the program's outputs |
38
+
|version || no |Returns ibm-ray-config's package version|
39
+
|region|| no|Geographical location for deployment and scope for available resources by the IBM-VPC service. Region are listed <ahref="https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-in-a-different-region&interface=cli"> here</a>. |
40
40
compute_iam_endpoint|https://iam.cloud.ibm.com|no|Alternative IAM endpoint url for the cloud provider, e.g. https://iam.test.cloud.ibm.com|
41
41
42
+
### Operate the cluster
43
+
To interact with the cluster, execute the scripts in `<cluster_folder>/scripts/`:
44
+
-`up.sh`, `down.sh`, `stop.sh` and `submit.sh` correspond to Ray's counterpart [commands](https://docs.ray.io/en/latest/cluster/cli.html?highlight=cli#ray-monitor).
45
+
-`down-vpc.sh` will delete all resources created by Ray and `ibm-ray-config`
46
+
-`connect.sh` will open a secure connection to your cluster, while `disconnect.sh` will terminate it.
47
+
-`ray.sh` can be used to run all other of Ray's [commands](https://docs.ray.io/en/latest/cluster/cli.html?highlight=cli#ray-monitor).
48
+
-`tunnel.sh` establish forward additional ports over secure ssh tunnel using, e.g. ray serve ports: `tunnel.sh 8000`.
42
49
50
+
Notice - To use Ray commands without the aforementioned scripts, either run them from the cluster's folder, or edit the `ssh_private_key` field to contain the absolute path to the associated ssh private key.
43
51
44
52
### Using ibm-ray-config Config Tool Programmatically
45
-
Attention: though not all fields are mandatory, unspecified resources will be created automatically on the backend.
53
+
#### Disclaimer:
54
+
This feature is currently dysfunctional, as it wasn't maintained throughout the previous releases.
55
+
We hope to support it in the near future.
46
56
47
-
#### IBM VPC
57
+
Attention: though not all fields are mandatory, unspecified resources will be created automatically on the backend.
0 commit comments