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
* Once the model is deployed and shown as `Active` you can execute inference against it, the easier way to do it would be to use the integrated `Gradio` application in this example
213
215
* Go to the model you've just deployed and click on it
214
216
* Under the left side under `Resources` select `Invoking your model`
* Once you have tested the inference locally. You can build Gradio container by running:
268
+
```bash
269
+
make build.app
270
+
```
271
+
* Before we can push the newly build container make sure that you've created the `gradio-odsc` repository in your tenancy.
272
+
* Go to your tenancy [Container Registry](https://cloud.oracle.com/compute/registry/containers)
273
+
* Click on the `Create repository` button
274
+
* Select `Private` under Access types
275
+
* Set `gradio-odsc` as a `Repository name`
276
+
* Click on `Create` button
277
+
278
+
* You may need to `docker login` to the Oracle Cloud Container Registry (OCIR) first, if you haven't done so before been able to push the image. To login you have to use your [API Auth Token](https://docs.oracle.com/en-us/iaas/Content/Registry/Tasks/registrygettingauthtoken.htm) that can be created under your `Oracle Cloud Account->Auth Token`. You need to login only once.
* Click on `Next` at the bottom to review the configuration and then click `Create`
305
+
306
+
* Once container is up you should be able to open the application now on `http://<Private IP address>:<PORT>/` and use start chatting against the deployed model on OCI Data Science Service.
307
+
263
308
## Deploying using ADS
264
309
265
310
Instead of using the console, you can also deploy using the ADS from your local machine. Make sure that you've also created and setup your [API Auth Token](https://docs.oracle.com/en-us/iaas/Content/Registry/Tasks/registrygettingauthtoken.htm) to execute the commands below.
@@ -295,7 +340,7 @@ Following are identified as the most probable failure cases while deploying larg
295
340
#### Reason
296
341
Insufficient model deployment timeout.
297
342
298
-
#### Symptoms
343
+
#### Symptom
299
344
The Work Request logs will show the following error:
300
345
Workflow timed out. Maximum runtime was: <deployment_timeout> minutes.
0 commit comments