Overview
Create a new instance to deploy and manage your services. This option will show up if there are one or more KVM clusters attached.
Creating a New Instance
In the User Panel, locate the instances table, or start from any view which shows the Create button.
Click the Create Instance button directly or Click the Createbutton followed by theCreate Instance option
This opens a modal window where you can select the team for the instance, this will show any teams which the user is a member of and has permission to create instances.
Select a team from the list and click Select.
You are presented with a new screen and a Choose a scenario section.
Select your desired scenario from the list and click Select.
Choosing a Service
Select a service from the list directly or use the filter buttons or search bar to narrow your options.
If a service is not available to a Team when deploying, common reasons are:
The Service is not included into the Teams Service Policy
There is a locked image for the service not available in the available regions or in the Teams Image Policy
There are not enough available resources within the region(s) which the Team has access to via their Resource Policy
There is a Recipe attached to the Service, which is not currently available/enabled
Configuring Instance Settings
Choose your preferred region.
This determines the physical location of your instance. Next, select your desired operating system (OS) image. Next, select your desired instance type. The instance type determines the compute resources available to your instance.
Now you will see the number of CPUs and memory (RAM) based on the chosen instance type and be able to customise the initial disk space for your instance based on the available Storage Blocks if the storage size is not locked by the service.
If available you can click Additional discs to expand this section and add more disks to your instance.
Choose the desired disk size space in the field provided, use the + button to add another, you can add a maximum of 3 disks during instance deployment, 1 root disk, plus 2 additional disks.
Note - the monthly price estimate is based on the chosen specifications for a 31 day month
Configure access settings, depending on the service, this may allow you to select a public network, or it may be automatically configured. You can optionally choose add an exiting public SSH key from your profile, or add a new key.
Manage SSH Keys by selecting an existing key from the SSH Keys dropdown or adding a new key. To add a new key, click the Add button next to SSH Keys.
This will open a modal where you can enter your SSH key and provide a description.
Paste the key into the SSH key textbox. Add a descriptive name in the Description field. Click Add SSH key to save the key.
After adding a key, you should see a confirmation message and it becomes available for use during this and future instance deployments, if there are any issues with the format of the key you may see an error such as "Failed to generate fingerprint".
Select your newly added SSH key from the dropdown menu.
Now provide a descriptive Instance Name in the Instance Name field.
Select a workspace using the Select workspace dropdown menu to select from any of the exisitng workspaces within the team. You can always migrate workspace later if you need to.
Finalizing and Deploying the Instance
Review the summary to confirm your choices and see the total cost.
Click Deploy instance to deploy.
If there are any issues, such as insufficient resources or incorrect settings, a notification will appear (as shown in the example).