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: jobs/ml-ops/README.md
+15-2Lines changed: 15 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,14 +37,22 @@ Set your Scaleway access key, secret key and project ID in environment variables
37
37
export TF_VAR_access_key=<your-access-key>
38
38
export TF_VAR_secret_key=<your-secret-key>
39
39
export TF_VAR_project_id=<your-project-id> # you can create a separate project for this example
40
+
```
41
+
42
+
By default, both jobs and container trigger in the example run regularly on a schedule. The default values for these schedules are configured in `jobs/ml-ops/terraform/variables.tf`, and can be overridden using Terraform variables, e.g. `export TF_VAR_data_fetch_cron_schedule="0 10 * * *"`.
40
43
44
+
Then deploy MLOps infrastructure using the following:
45
+
46
+
```console
41
47
cd terraform
42
48
terraform init
43
49
terraform plan
44
50
terraform apply
45
51
```
46
52
47
-
### Step 2. Run the data and training Jobs
53
+
### Step 2. Optional: trigger jobs manually
54
+
55
+
The pipeline is automatic, all jobs will be run at their respective scheduled time. This step can be ignored unless for debugging or test purposes.
48
56
49
57
To run the jobs for the data and training, we can use the Scaleway CLI:
50
58
@@ -60,12 +68,17 @@ You can also trigger the jobs from the [Jobs section](https://console.scaleway.c
60
68
61
69
### Step 3. Use the inference API
62
70
71
+
Load model with the latest version using:
72
+
63
73
```
64
74
cd terraform
65
75
export INFERENCE_URL=$(terraform output raw endpoint)
0 commit comments