Developers
menu
menu

Feature overview for developers

Qarnot workflow

The following steps are common to almost all Qarnot computing applications.

  1. Find an already existing Docker container or prepare a new one with your application binaries.
  2. Upload the resources to be processed to a Qarnot disk. You can upload your files programmatically with the REST API or by using the console.
  3. Create a task programmatically with the REST API. To create a task, you need to specify a task profile an the desired number of instances.
  4. Attach your disk and your Docker container to your task.
  5. Submit your task.
  6. Monitor the progress and retrieve the task output.

Create your Qarnot account and retrieve your authentication token from the console.

Qarnot computing components

The following elements are common in the Qarnot computing environment:

Account

The Qarnot account is your unique identifier within all Qarnot services. To access the REST API and create tasks, you need the authentication token associated with your account.

Create your Qarnot account for free now if you don't already have one.

Authentication token

The authentication token is an hexadecimal string that grants you access to the REST API

It can be found in the console by clicking on the top right buddy icon > API Token.

Compute node

A compute node is a bare metal server embedded inside Qarnot's digital heaters or its industrial version.

  1. CPU are high-end Intel® Core™ i7 (4c/8t) with a frequency of 3.5 GHz or more and 16 GB of RAM.

  2. The entire CPU is reservered for your task, CPUs are not shared between customers.

  3. Compute nodes are diskless, when your task arrives on a compute node, the entire node is rebooted. So your task is guaranteed to start in a clean and safe environment.

  4. As the compute nodes are rebooted between different tasks, no data leakage is possible on the compute node.

The frequency could be adjusted if a task is running for a long time on a digital heater that goes beyond the target temperature.

For practical raisons, the deployment of application is done by using Docker container which limits the supported operating system to the Linux environment. If you need to run Microsoft Windows applications, you can contact us.

The features included in your batch environment depends on the chosen profile.

Docker container

Docker is an innovative technology to easily package, deploy and run your applications. It is the world’s leading software containerization platform. Moreover a wide variety of images already exists and are freely available on Docker Hub. And most of them are already Qarnot ready!

Profile

Profiles define the way your task behaves, and are configured by constants. We provide some profiles to let you run your own Docker images, or to use our Blender application. Each of those profiles come with a set of constants to configure them, for instance to select the appropriate Docker image to run, or the Blender file to render.

Depending on the profile, there can be several flavors with different characteristics such as Internet access or inbound connections. See the detailed profiles section for more information.

Disk

Disks are used to store the files you want to process and your task results. Your application's working directory, $TASK_PATH, contains the resources, and anything you write into it will be available as a result on our REST Api.

Find more information about disks in the disks section.

Task

A task describes the computations to perform on compute nodes. A task has the following properties:

You can find more information about tasks, their lifecycle, and how to monitor them in the tasks section, about tasks with multiple instances in ranges section, and about the execution environment and directories layout in the environment section.

Next steps