Applications

Overview

The Applications tab within Marketplace is a dedicated section designed to present users with a collection of function packages. These packages are curated sets of functionalities that users can directly install as services into their projects. These packages are pre-built and ready-to-use components that can extend the capabilities of projects on the platform.

Here’s a detailed explanation of this feature:

Use the Application tab

Browse and Explore: Users start by browsing the Applications tab to explore the available function packages. Detailed descriptions and documentation are provided to help users understand the capabilities and requirements of each package.

Select and Install: Once a suitable package is identified, users can select it and proceed with the installation process.

Integration and Use: After installation, the new service is integrated into the project, ready to be used as part of the workflow. Users can then utilize the added functionalities to achieve their project goals more effectively.

In the card view, the following details about each model are presented:

• Application's Image
• Application's Name
• Application's Description
• Application's Category (for example, Provider, Applications Type, etc.)
• Last Updated Timestamp

Utilize the filter, search, and sort features to easily locate a specific Applications based on your requirements. Additionally, upon selecting an Application's card from the list, a detailed information panel will appear on the right side.

The following sections will help you understand the Application in detail.

Search an Application

Use the Search an Application field to type in the name and description of the Application to search it.

Filter Applications by Category

Marketplace allows you to filter applications using categories. In the left-side panel, search Applications using the following categories. Select one or more categories to refine the list of Applications according to your choice. To remove the filter, simply click on the selected filter category once more.

Provider

Filter by the organization or company that created the pipeline templates such as Hugging Face, Microsoft, Meta, AWS, and others.

Deployed By

Filter applications based on the deployer, including third-party deployments via API services.

Application Type

Filter applications based on the types, the various forms of functions. For example, Studio, Model, Pipeline Node, Image, Text, Video, etc.

Media type

Filter applications by the type of media they process—such as audio, image, text, video, or LiDAR.

Converters

Filter applications by converter types, including COCO, YOLO, VOC, DICOM, HEIC, and others.

Gen AI

Filter applications by generative AI model based applications.

Filter by installation status

Marketplace allows you to filter applications based on their installation status, learn more.

Filter by privacy level

Marketplace offers a flexible filtering system that categorizes the Application according to their privacy level, enhancing navigation and selection within the Dataloop platform. Learn more

Manage applications

Actions based on use cases

You can perform actions that are available on each application based on the scope and installation status. Learn more section.

Create an application

1. Open the Marketplace from the left-side menu.
2. Click on the Actions > Create Application. The Create Application window is displayed.
3. Make required updates in the following fields:
   1. Application Name: Provide a name for the new application.
   2. Codebase Type: You can upload the codebase by zip files as Item or providing git URL.
      1. item: By default, Item is displayed. Select the ZIP file of the Codebase.
      2. git: The Git URL is how you locate and clone a repository, while a Git tag is a reference to a specific point in that repository's history.
         1. git URL: Enter the Git URL.
         2. git tag: Enter the Git tag.
         3. Add Secret Credentials: This allows you to add a secret username and password for the Git codebase.
   3. Requirements: If your code requires additional python libraries to run, please upload a requirements.txt file specifying which python libraries need to be installed.
   4. Modules: Multiple functions may be defined in a single package under a module entity. This way, you will be able to use a single codebase for various services (applications). Make changes in the following fields:
      1. Modules Name: Define the module name (no limitations). By default, default_module is displayed.
      2. Entry Point: The main.py file you created should be defined as the module entry point. By default, main.py is displayed.
      3. Class Name: By default, ServiceRunner is displayed. Make changes, if required.
      4. INIT Inputs: Click on the Plus icon to add a new init input.
         1. Name: Enter a name for the input.
         2. Type: Select the type of the input from the list.
      5. Functions: Provide a Name and Description for the function. By default, run is displayed as a function name.
         1. Input: Click on the Plus icon to add new input. Enter the input name and select the type from the list. By default, item is displayed as the name and type of the input.
         2. Output: Click on the Plus icon to add new output. Enter the out name and select the type from the list. By default, item is displayed as the name and type of the output. Provide an action name, if required.
4. Add default app configuration: Click App Config. The edit service configuration window is displayed. Make changes in the following fields:
   1. Machine Type: By default, regular-s is displayed. Select a new one from the list, if required.
   2. Create Autoscaler: It enables the automatic adjustment of computing resources based on the workload.
      1. Min Replicas: This refers to the minimum number of instances (or "replicas") of your function that will be running at any given time, by default, it is set to 0. Make changes, if required.
      2. Max Replicas: This is the maximum number of instances that your function can scale up to. By default, it is set to 1. Setting it to 1 means your function will have at most one instance running at any time. Make changes, if required.
      3. Queue Size: The number of events or requests waiting to be processed. By default, it is set to 100. Make changes, if required.
   3. SDK Version: By default, the latest SDK version is displayed. Click Update SDK Version to update the new version, if available.
   4. Module: Select a model from the list.
   5. Concurrency: By default, 10 is displayed.
   6. Execution Timeout: The default timeout of an execution is, 3600 (seconds).
   7. Drain Time: To ensure the completion of parallel running executions before terminating the pod, provide a Drain Time delay. After this designated period, the execution restarts. By default, 600s is displayed.
   8. On Reset Action: An "On Reset Action" setting is related to how the application should respond when a specific trigger or condition necessitates resetting the state or execution of a function. Select one of the following when you reset the execution. By default, failed is displayed.
      1. failed: When the action is set to Failed for a reset condition, it implies that if the function encounters an issue requiring a reset (such as an execution error or a timeout), the system will mark the execution as failed. This option is typically used when it's critical to acknowledge that an error occurred, and it needs to be notified of the failure. Choosing Failed is appropriate for workflows where failure requires manual intervention, or where it's important to maintain strict error reporting and auditing.
      2. rerun: Setting the action to Rerun means that if the function hits a reset condition, the system automatically attempts to execute the function again. This approach is useful for handling transient errors or temporary issues that might not persist in a subsequent execution attempt.
   9. Max Attempts: Maximum number of execution attempts allowed. By default, 3 is displayed.
   10. Bot: A bot is a dummy project user with 'Developer' role permissions used for running services. By default, the latest Bot is displayed. Select a new one from the list, if needed.
   11. Docker Image: Provide your private or public docker image registry URL.
   12. Secrets and Integrations:
       1. Is service global:
       2. Preemptible:
       3. Run service execution as process:
   13. Click Confirm.
   14. Click Create Application. A success message is displayed, and the new application will be available in the Applications tab of the Marketplace.

Create an application from a GitHub repository

1. Open the Marketplace from the left-side menu.
2. Click on the Actions > Create Application. The Create Application window is displayed.
3. Make required updates in the following fields:
   1. Application Name: Provide a name for the new application.
   2. Codebase Type: Select the git from the list.
   3. git URL: Enter the Git URL. The Git URL is how you locate and clone a repository.
   4. git tag: Enter the Git tag. It is a reference to a specific point in that repository's history.
   5. Add Secret Credentials: This allows you to add a secret username and password for the Git codebase.
   6. Continue the steps available in the Create an Application.

Install an application

1. Open the Marketplace from the left-side menu.
2. In the Applications tab, select the application that you want to install.
3. Click Install from the right-side panel. An Install Application popup window is displayed, and it lists all the available functions specified in the package module with a description.
4. Click Install Application. The function is installed and available in the CloudOps -> Services tab.

Once you install an Application, there is a green tick icon is visible on the applications that are installed.

Install an application or a model with integrations

Dataloop requires integrations to be configured for certain applications and models during the installation process. While it is possible to complete the installation by selecting the Set up later option, these applications or models will remain inactive and cannot be used until the necessary integrations are fully configured.

1. Open the Marketplace from the left-side menu.
2. In the Applications or Models tab, select the application that you want to install.
3. Click Install from the right-side panel. An Install Application popup window is displayed, and it lists all the available functions specified in the package module with a description.
4. Click Proceed. A pop-up window is displayed.
5. Select the secrets or integrations as required. To set the integration later, click Set Up Later.
6. Click Install Application. The function is installed and available in the CloudOps -> Services tab.

Once you install an Application, there is a green tick icon is visible on the applications that are installed.

Set Integration (Edit Access Credentials) for an installed application

1. Open the Marketplace from the left-side menu.
2. In the Applications or Models tab, select the application.
3. Click Actions from the right-side panel and select Edit Access Credentials. The Edit Model pop-up window is displayed.
4. Select the secrets or integrations as required.
5. Click Save Changes.

Install a pipeline node application

1. Open the Marketplace from the left-side menu.
2. Select the Applications tab.
3. In the left-side filter -> Application Type, select the Pipeline Node.
4. Select a pipeline node from the list according to the requirement.
5. Click Install from the right-side panel. The Install Application popup is displayed.
6. Click Install Application. The node will be installed successfully, click View Application for more details.

Activate or deactivate an application

Installing an application activates the application. Once you install an Application to your project, the application becomes activated. Learn how to Activate or Deactivate.

More actions

For more actions, refer to the Manage Marketplace article.