Onboarding an Application with OneCompute

This section summarizes the steps required to onboard an application with OneCompute:

  1. Register the application
  2. Get access to the OneCompute API
  3. Authenticating with the OneCompute API
  4. Build the Application Worker
  5. Create and Submit Jobs through the OneCompute API

Register the application

OneCompute supports two different application registries, depending on which authentication model is used by the application (see the Authentication Topics section for details):

Get Access to the OneCompute API

When authenticating, the client must request which APis it needs access to. In the Veracity API registry, each OneCompute deployment has a separate API id. In the OneCompute Service Registry, the same API id is shared between all OneCompute deployments.

Authenticating with the OneCompute API

See Authentication Topics for details on the types of authentication supported by the OneCompute API.

When choosing the authentication model to use, the following guidelines can be used:

  • If the OneCompute job is initiated by from an interactive session and it is required to associate the job with the interactive user, use Veracity authentication
  • Otherwise, use client credentials authentication (typically in a service-to-service scenario)

Build the Application Worker

See Application Worker.

Create and Submit Jobs through the OneCompute API

The following sections in the documentation are relevant for creating and submitting a OneCompute job: