Skip to content

Compute Instances

A newly created workspace will have no active compute instances or any services. The end user can select from the available list of compute profiles in the Org and launch compute instances. The end user is provided with a vending machine type experience and presented with a list of available options that will map to the list of compute profiles that are curated and managed by the administrator (or GPU Cloud Provider for their customer orgs)

Create Compute Instance

To create a compute instance, access the Developer Hub and navigate to the home page. The page provides options to create and manage compute instances, which are predefined configurations for allocating resources such as CPU, GPU, memory, and storage to support various workloads. On the Developer Hub home page, users can either click on View All to access the Compute Instances page or click on New Compute to create a new compute instance. Users can also click on the Compute Instances menu on the left to directly access the Compute Instances page.

Hierarchy

New Compute Instance

Users are provided with a wizard that allows them to select from the available Compute Profiles

Hierarchy

Once the profiles are selected, provide the below details:

  • Name: Enter a unique name for the compute instance
  • Description: Provide a brief summary of the instance
  • Compute Profile: Proceed with the selected profile or select an alternate profile
  • Workspace: Select the workspace from the drop-down menu and click Deploy

Create Compute Instance

The instance initially displays a status of In Progress. Upon successful deployment, the status updates to Success.

Create Compute Instance

Important

The list of compute profiles presented to the end user is dynamic i.e. if the administrator updates or publishes a new profile, it will be immediately available to the end user as an option to consume.

View Compute Instances

When the user clicks on Instances, they are presented with the list of compute instances in their workspace.

  • Name
  • Workspace
  • Created At
  • Publish Status
  • Actions

Compute Instances

Actions

Once an instance has been launched and is operational, users can perform a number of actions on it. This section describes the list of actions that can be performed.

Remote Access

The end user will need access to the remote instance that is operating behind a firewall in a private data center or public cloud. These instances can be either a Kubernetes namespace or a Virtual Cluster or a Dedicated Kubernetes cluster. The secure remote access capability is powered by Rafay's Zero Trust Kubectl (ZTKA) feature.

The user can download the ZTKA "kubeconfig" file, configure their KubeCTL CLI utility to use it and access the instance remotely. The user can also click on the "kubectl" button which will open a web shell that will allow them to securely interact with the instance.

Collaborators

It is common for end users to work with both internal (i.e. employees) and external (i.e. outside the company) collaborators. Users can easily add/remove other users to a specific instance. Once the user enters the collaborator's "email address", an email invitation is sent to the user with details on how they can access this instance. Once they login, they will have the same level (i.e. role/privilege) of access to the instance.

Delete Compute Instance

If the user does not require a compute instance, they can delete it by clicking on the delete icon on the right of the compute instance

Note

This action is irreversible and cannot be undone.