Comment on page

Create and Manage an Antlet

Create your Antlet
In antMan, click the 'Create' button. 
It will ask you for the details:
Fill in the Antlet info
Field
Description
Name
Enter a unique name for the new antlet
Template
Select a template from the list of templates. Click the 'Add more' option to download additional templates.
RAM
Select the amount of RAM
vCPUs
Select the number of vCPUs
IP
This is the last number in the IP address for this antlet. It will automatically populate with the next available address. The range is 10-210.
zPool
Select the storage pool the antlet will be created in.
Compression
Turn compression on or off for an individual antlet. Compression is off by default.
Click the "Create Antlet" button and the antlet will appear in the list of antlets.
Congratulations! You just created your first Antlet 🎉
Manage your Antlet
Controlling the Antlet at a glance
In the antlet listing in antMan you can perform the following functions:
Open the antlet details (click the name of the antlet) 
Start, Stop, Reboot and Delete the Antlet
Clone the Antlet
Copy the Antlet to another server
Pause or Force stop the Antlet
Open the antlet VNC Console (KVM antlets only)
Note: Reboot is an OS reboot of the antlet. The antlet itself does not Stop then Start.
Start, Stop or Reboot your Antlets from the Overview-page
Clone your Antlet
A clone of your antlet is a separate antlet that contains a copy of your antlet's existing data.
To clone your antlet: 
From the Dashboard, click the ... to open your antlet's actions. Select Clone this antlet.
Fill in the Clone info
Field
Description
New antlet name
Name of the cloned antlet
IP
This is the last number in the IP address for this antlet. It will automatically populate with the next available address. The range is 10-210.
Compression
Turn compression on or off for an individual antlet. Compression is off by default.
Click Create antlet to clone your antlet.
Copy your Antlet
You can Copy your Antlets between Antsle servers in one click with a Grow or Scale plan. See details.
Copying only works between similar platforms. Nano to Nano or antsle One/Two to antsle One/Two. 
You can quickly copy your Antlet from one Antsle server to another from your dashboard. The data present in the Antlet
To copy your antlet:
Make sure the destination Antsle server is configured. See this guide to add an Antsle server for multi-node access.
From the Dashboard, click the ... to open your antlet's actions. Select Copy this antlet.
Fill in the Copy info
Field
Description
Destination Node
Antsle server where the Antlet will be moved
Do you want to delete the VNICs?
Delete all existing VNICs. Doing so will prevent conflicts if VNICs are configured on both Antsle servers. This is recommended if you are using VNICs on either Antsle server.
Click Copy antletto copy the antlet. You will be able to see the progress of your copy in the Jobs menu on the top-right of the screen.
Pause your Antlet
When you pause your antlet it will consume no CPU and no I/O while paused but keeps the RAM. 

Last modified 2yr ago

Field	Description
Name	Enter a unique name for the new antlet
Template	Select a template from the list of templates. Click the 'Add more' option to download additional templates.
RAM	Select the amount of RAM
vCPUs	Select the number of vCPUs
IP	This is the last number in the IP address for this antlet. It will automatically populate with the next available address. The range is 10-210.
zPool	Select the storage pool the antlet will be created in.
Compression	Turn compression on or off for an individual antlet. Compression is off by default.

Field	Description
New antlet name	Name of the cloned antlet
IP	This is the last number in the IP address for this antlet. It will automatically populate with the next available address. The range is 10-210.
Compression	Turn compression on or off for an individual antlet. Compression is off by default.

Field	Description
Destination Node	Antsle server where the Antlet will be moved
Do you want to delete the VNICs?	Delete all existing VNICs. Doing so will prevent conflicts if VNICs are configured on both Antsle servers. This is recommended if you are using VNICs on either Antsle server.