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)
New Compute Instance¶
Users are provided with a wizard based shopping cart style experience. They can select from the available list of SKUs and launch compute instances. Users have to follow a simple workflow:
- Provide a name for their compute instance (optional description)
- Select type from the list of available compute profiles
- Click on Launch
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 "active" compute instances in their workspace. In the example below, the user has launched eight (8) compute instances in their workspace.
- Name
- Size
- Operational Status
- Launch date
View Specific Instance Details¶
Users can view details about a specific instance by clicking on the "view" icon on the actions menu for the instance. In the example below, the user is provided with a combination of details about the instance and the option to perform actions
The user is provided with metadata about the instance. For example, when was it launched, what size is it, how long has it been running?
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.