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
Get a short description of the available flags via ```lithopscloud --help```
25
+
Get a short description of the available flags via ```ibm-ray-config --help```
26
26
27
27
<br/>
28
28
@@ -34,135 +34,40 @@ Get a short description of the available flags via ```lithopscloud --help```
34
34
| 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)
35
35
| input-file |<compute_backend>/defaults.py| no | Existing config file to be used as a template in the configuration process |
36
36
| output-path |A randomly generated path to a randomly named yaml file | no |A custom location the config file will be written to |
37
-
| verify-config <imgwidth=125/>| | no |Verifies the integrity of an existing config file and outputs a usable config file based on it. Currently doesn't support gen2 backends.
38
-
| version || no |Returns lithopscloud's package version|
37
+
|version || no |Returns ibm-ray-config's package version|
38
+
39
39
40
-
<br/>
41
40
42
-
#### Verify Additional ways of configuration
43
-
Using the ```verify-config``` option enables verification of additional valid ways of configuration, that otherwise
44
-
left unchecked. This mode scans for any possible subset of valid parameters and extract them to output a new
45
-
lithops config file (e.g., verify cos configured by HMAC credentials).
46
-
To utilize simply run ```lithopscloud --verify-config CONFIG_FILE_PATH -o OUTPUT_FILE_PATH```
47
-
<br/> Please note that this feature doesn't currently support the verification of gen2 backends.
### Using lithopscloud to generate config file without user interaction
91
-
In order to let lithopscloud generate config file based on some defaults and create vpc and all its peripherial assets automatically, please run:
41
+
### Using ibm-ray-config to generate config file without user interaction
42
+
In order to let ibm-ray-config generate config file based on some defaults and create vpc and all its peripheral assets automatically, please run:
92
43
93
44
```
94
-
lithopscloud -a <API_KEY> -b <BACKEND> --defaults
45
+
ibm-ray-config -a <API_KEY> --defaults
95
46
```
96
47
97
-
* currently, lithops `gen2` is the only supported backend
98
-
99
-
### Using lithopscloud config tool programmatically
48
+
### Using ibm-ray-config config tool programmatically
100
49
Notice, not all fields are mandatory. Unspecified resources will be created automatically on the backend.
101
50
102
51
E.g.
103
-
If existing vpc id not provided - vpc will be created automatically with all required peripherial resources like security groups, gateway.. etc following minimal default requierments
52
+
If existing vpc id not provided - vpc will be created automatically with all required peripheral resources like security groups, gateway.. etc following minimal default requirements
104
53
If ssh key details not provided - new ssh key pair will be generated and registered in ibm cloud
105
54
106
-
107
-
##### Lithops Gen2
108
-
```
109
-
from lithopscloud import generate_config
110
-
from lithopscloud import LITHOPS_GEN2, LITHOPS_CF, LITHOPS_CE, RAY_GEN2, LOCAL_HOST
2. add your implementation under __provider__ package
161
-
3. add reference to your implementation in the list of exported modules, e.g. [lithops modules](src/lithopscloud/modules/lithops/__init__.py__)
162
-
163
-
164
-
#### If the new configuration is common for multiple providers
165
-
166
-
1. implement [__config_builder.py__](src/lithopscloud/modules/config_builder.py) interface to hold common logic
167
-
2. add your implementation to __modules__ package
168
-
3. extend your common implementation under each provider package, e.g. [lithops image.py](src/lithopscloud/modules/lithops/image.py) and [ray image.py](src/lithopscloud/modules/ray/image.py) to have config file specific logic
@click.option('--compute-iam-endpoint', help='IAM endpoint url used for compute instead of default https://iam.cloud.ibm.com')
59
+
@click.option('--endpoint', help='IBM Cloud API endpoint')
60
+
@click.option('--defaults', help=f'Create defaults if not exist and generate default config', is_flag=True)
61
+
@click.option('--pr', '-g', help=f'Temporary workaround for ray gen2 only. If specified, use provider setup from PR github', is_flag=True, default=False)
0 commit comments