Skip to content

Commit

Permalink
Minor doc fixes and missing image
Browse files Browse the repository at this point in the history
  • Loading branch information
catttam committed May 23, 2024
1 parent a50bb09 commit 1512417
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion docs/expose_services.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,3 @@
## Exposed services

OSCAR supports the deployment and elasticity management of long-running services that must be directly reachable outside the cluster. This functionality answers the need to support the fast inference of pre-trained AI models that require close to real-time processing with high throughput. In a traditional serverless approach, the AI model weights would be loaded in memory for each service invocation. Exposed services are also helpful when stateless services created out of large containers require too much time to start processing a service invocation.

Expand Down Expand Up @@ -29,6 +28,7 @@ https://{oscar_endpoint}/system/services/{service_name}/exposed/{path_resource}
Notice that if you get a `502 Bad Gateway` error, it is most likely because the specified port on the service doesn't match the API port.

Additional options can be defined in the "expose" section of the FDL (some previously mentioned), such as:

- `min_scale`: The minimum number of active pods (default: 1).
- `max_scale`: The maximum number of active pods (default: 10) or the CPU threshold, which, once exceeded, will trigger the creation of additional pods (default: 80%).
- `rewrite_target`: Target the URI where the traffic is redirected. (default: false)
Expand Down
Binary file added docs/images/interlink.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
4 changes: 2 additions & 2 deletions docs/interlink_integration.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
# Interlink
# InterLink integration

InterLink aims to provide an abstraction for executing a Kubernetes pod on any remote resource capable of managing a Container execution lifecycle.

OSCAR uses the Kubernetes Virtual Node to translate a job request from the Kubernetes pod into a remote call. We have been using Interlink to interact with an HPC cluster. For more infomation check the [Interlink landing page](https://intertwin-eu.github.io/interLink).

![Diagram](just_interlink2.png)
![Diagram](images/interlink.png)

## Installation and use of Interlink Node in OSCAR cluster

Expand Down

0 comments on commit 1512417

Please sign in to comment.