Cloud VMs, plafond and creation
The resource plafond of the customer, the wizard that creates a cloud virtual machine, private networks, backups, public IP and credentials.
A cloud VM is a virtual machine running on the Sefthy infrastructure, which the customer manages independently from the Console within a predefined resource limit. It is a separate service from Disaster Recovery, although the two services can coexist on the same account.
The plafond
The plafond is the maximum amount of resources the company can use. It covers CPU, RAM, disk, number of private networks, public IPs, uploaded ISOs and backups per VM. Sefthy sets the plafond on the customer company, and it cannot be changed from the customer Console or from the partner Console.
Before acting on the infrastructure, every operation that consumes resources checks the plafond, shows usage before and after the operation, and stops if the total exceeds the limit. The message states which resource is short, the amount requested and the amount still available. The network cards of a single VM do not consume plafond and are only subject to a technical limit. The plafond counts the number of private networks instead.
Creating a VM
Anteprima video temporaneamente non disponibile.
Apri il file direttamente →- From the menu open Deploy new VM. The wizard has five steps.
- In Resources you set CPU in virtual cores, RAM and disk in GB. The Console automatically decides where on the infrastructure the machine runs.
- In Networks you add the network cards. For each one you choose one of the company’s private networks and the NIC model, VirtIO or e1000. Keep VirtIO, except for older systems that do not recognise it and need e1000. You can also continue without any card and add them later.
- In Source you choose what the machine boots from, an ISO image from the library or a ready-made system, which is cloned on the fly. The list of ready-made systems includes Debian, Ubuntu, AlmaLinux, CentOS Stream, Windows 10 and 11 Pro and Windows Server 2019, 2022 and 2025.
- In Boot order you set the order of the boot devices with the arrows. If you boot from an ISO you also choose the firmware, UEFI or legacy BIOS for systems that only boot that way. A ready-made system inherits the firmware from its template.
- In Review you enter the VM name and an optional description, and choose whether to start the VM as soon as it is ready. If you chose a ready-made system, this is also where you set the initial password and any SSH keys.
- Click the confirm button. The deploy is queued and you can follow it from the VM detail page.
Private networks
In the Private networks section you define the customer networks. Each network is isolated from the others and sits in the company’s private space, which Sefthy prepares when it sets the plafond. With New network you add a network, up to the number the plafond allows. These networks appear in the Networks step of the wizard.
VM backups
On the VM detail page, the Backups card lists the existing backups with date, size, storage and protection state. From the card you can perform these operations.
- run a Backup now, choosing the destination storage
- schedule recurring backups with their retention
- protect a backup, so that rotation does not delete it
- restore with Restore snapshot, which opens a calendar where you choose the day and then the snapshot
The number of backups per VM is part of the plafond. If you have reached the limit, the Console reports it and offers to delete the oldest backup to make room for the new one. If the VM is running, the restore shuts it down and starts it again at the end.
Public IP and credentials
From the Public IPs card you assign an address from the company pool. Choose the Internet-facing network card to assign it to and confirm. When the pool is exhausted, the Console blocks the assignment and tells you to contact your distributor to expand it.
The Credentials card holds the user, password and SSH keys of the machine. On some VMs the change is applied to the machine and requires a reboot. On others, typically VMs created from an external ISO, the credentials are only stored encrypted for reference, and the Console states this in the panel.