You are now logged in to SolusVM 2.0. Before you or your customers can start creating their servers, you need to do some setting up in SolusVM 2.0. This topics explains step-by-step how to do it.
To start any SolusVM 2.0 setup, you need to install a SolusVM 2.0 license first. The SolusVM 2.0 uses the same licensing and price model as SolusVM, refer the link for details.
To install a license:
- Go to Settings > Licensing.
- Click Activate License, paste the license key you've got, and then click Activate.
You're now ready to set up SolusVM 2.0.
2. Adding a compute resource¶
Compute resources are hypervisors that are connected to the management physical server. Compute resources provide resources (CPU, RAM, and disk space) the customers consume to deploy their own isolated servers. The industry also calls these servers virtual private servers (shortly VPSs). However, we will stick to the term "servers".
The SolusVM 2.0 term "compute resources" has a different meaning compared with a common one. By compute resources, we mean both actual compute resources (CPU and RAM) and also storage resources (disk space).
Servers that you want to connect as compute resources must meet the following requirements:
|OS||AlmaLinux 8, CentOS 7, CentOS Stream, Debian 10, Debian 11, Ubuntu 18, Ubuntu 20, Ubuntu 22, Virtuozzo 7.0.14 and later, Virtuozzo Hybrid Server|
|Architecture||x86_64 for CentOS 7, Ubuntu 18, Virtuozzo 7.0.14 and later x86_64 or ARM64 (aarch64) for AlmaLinux 8, CentOS Stream, Debian 10, Debian 11, Ubuntu 20, Ubuntu 22|
|RAM||Minimum 8 GiB|
|Free disk space||Minimum 100 GiB|
|Allowed connections to ports||TCP 22 (SSH) TCP 8080 (Agent) TCP 7778 (VNC)|
For resiliency reasons, we do not recommend that you use the management server as a compute resource (even if it is technically possible).
You can add a Compute Resource even if its CPU core count exceeds the limits of your license. A Compute Resource is not counted until there is a virtual server on it.
To add a compute resource:
- Go to Compute Resources and click Add Compute Resource.
- Give your resource a name.
- Specify the hostname or IP address of a server that you want to connect as a compute resource.
Choose how to connect to the server:
- If via SSH, type
rootas the SSH login and the root password.
If via SSH keys, select "SSH Key" and paste an existing private SSH key or generate a new key pair.
SolusVM 2.0 uses the server’s credentials only once (while connecting the server as a compute resource) and does not store them anywhere.
- If via SSH, type
SolusVM 2.0 now checks if the server you are trying to connect as a compute resource meets the requirements. If the server does not support virtualization, you will see the following error message:
In this case, enable virtualization in the server BIOS settings. To do so, refer to the documentation of your processor manufacturer.
If the server passed the checks and was connected as a compute resource, you will see the screen that suggests selecting a network interface and configuring network.
Select the network interface and click Configure Network.
Configuring network poses the risk of permanently losing network access to the server. Proceed only if you have one of the following:
- Physical access to the server
- Access to the server’s serial console
- 24/7/365 server support
Click OK to start network configuration.
Once the network configuration is finished, you will see the connected server in the "Compute Resources" list.
By default, SolusVM 2.0 creates compute resources that have the routed network type.
If this type isn’t suitable for your network,
change the compute resource’s network type to bridged <administration:8>.
You are now ready to create a plan.
3. Adding a plan¶
Plans are templates according to which servers are deployed. Plans preconfigure what amount of resources (CPU, RAM, and disk space) will be allocated to servers and which storage type a compute resource will have.
To add a plan:
- Go to Compute Resources > Plans and click Add Plan.
- Give your plan a recognizable name.
Select a storage type:
- File Based, LVM, and ThinLVM are local storage types. They define how the compute resource's disk is partitioned and its data is packed.
- NFS is a remote storage type.
There are various reasons why you may prefer one storage type over another. However, we recommend that you take the following considerations into account:
- Each storage requires that you configure a storage point for it (a directory, a volume group, a thin pool, or a separate server with mounted NFS). If you do not have experience with any of that, select File Based. In this case, SolusVM 2.0 can create a storage point for you.
- To be able to create snapshots, select File Based or ThinLVM. A snapshot is a copy of a server at a particular point in time. If anything goes wrong with the server (for example, after software update), you can return to the successful server configuration by restoring a snapshot.
- To save resources and deploy a maximum number of servers, select ThinLVM.
- Compute resources require that you monitor the resources consumed by customers to prevent overusing resources. ThinLVM requires additional efforts to monitor available disk space. To make monitoring easier, select either FB or LVM.
- To share a storage point between multiple compute resources, select NFS. However, certain operations may take more time and servers may run slower because NFS is a remote storage type.
If you selected File Based or NFS during the previous step, select an image format: qcow2 or raw. With qcow2, you can enable snapshots.
- Type a number of tokens. The tokens are units used to calculate and show the exact price for a plan for customers.
- Specify the desired amount of virtual CPU, storage (HDD), and memory.
Locations, Operating Systems, and Application fields define for which locations, OS versions, and applications the plan can be used. Locations, Operating Systems, and Applications that are not bound with the plan will be visible but can’t be selected for new virtual server creation.
Filling Location, Operating Systems, and Application you can allow only desired combinations for new virtual server creation like on the following image, where “Windows 2022“ can be created only in the “London” location and only on the “Enterprise“ plan.
Keep the plan visible.
- (Optional) To prevent resources overuse, you can limit bandwidth and IOPS for each server created under the plan. To do so, click Change resource limits, click Limit, and then set the desired limits.
- If you selected File Based with qcow2, ThinLVM, or NFS, you can turn on snapshots.
- Click Save.
The plan was created. You can now see it in the "Plans" list.
4. Adding a storage point¶
Each compute resource requires a storage point depending on a storage type:
- A directory for File Based
- A volume group for LVM
- A thin pool for ThinLVM
- A separate server with mounted NFS
A directory for File Based is just a normal directory, while a volume group and a thin pool are storage abstractions.
SolusVM 2.0 can create a directory for the File Based storage type but you need to create other storage points yourself.
To add a storage point to a compute resource:
The procedure of creating a storage point depends on the storage type you have selected while creating the plan:
Log in to SolusVM 2.0 and go to Compute Resources.
- Click the name of the created compute resource, go to the "Storage" tab, and then click Add Storage.
- Select a storage type that your created plan has.
Depending on your storage type:
- Provide the directory path for File Based.
- In the drop-down list, select the volume group, thin pool, or NFS storage, which you created during step 1.
(Optional) By default, the storage will be used for balancing new servers according to the chosen balancing algorithm (random or round-robin in Settings > Compute Resources) if the "Use for New Servers" setting is turned on. Keep this setting on because you now have only one storage point. If later you have multiple storage points and one of them is overloaded compared to others, you can prevent new servers from being created in this storage point by turning off "Use for New Servers".
If you share NFS storage between compute resources, you won't be able to turn off "Use for New Servers" on one particular compute resource. At the moment, turning off "Use for New Servers" affects all compute resources the storage was assigned to.
The storage point was added.
5. Adding an IP block¶
IP block is a range of IP addresses from which each created server receives its IP address. Assigning an IP address turns a mere server partition into a real server.
An IP address identifies a server and allows it to communicate with other devices in the Internet, which is essential if the server is used for hosting websites.
You can add either an IPv4 or an IPv6 block. An IPv6 block is more difficult to add. For this reason, the procedure of adding an IPv6 block is as a separate topic in the Administration guide.
By default, each server has only single IP address assigned.
To add an IPv4 block:
- Get a range of IP addresses. Usually you buy IP addresses from data centers and hosting providers or allocate a range of IP addresses within your local network.
- Go to Network and click Add IP Block.
- Give your IP block a name.
- Keep "IPv4" selected.
Specify the following values:
- The beginning and the end IP addresses of the IP block
- Primary and secondary name servers
Select one or more compute resources to assign the IP block to.
- Click Save.
The IP block was added.
You have created the compute resource, the plan, the IP block, and the storage point. You are more than halfway through. You now need to create a location.
6. Adding a location¶
A location is a label that informs customers where a particular node is actually geographically placed. Usually customers want to choose a compute resource closest to their geographical location to decrease network latency. To give customers information about geographical locations of available nodes, you need to create locations and assign them to compute resources.
By default, SolusVM 2.0 creates the "Default" location. You can edit it or add new locations.
To add a location:
- Go to Compute Resources > Locations and click Add Location.
- Give your location a name and description.
- (Optional) If all your nodes are located in the same region, your customers do not have a variety of locations to choose from. In this case, you can hide this single location from customers: they will not see it when creating servers. To hide the location, turn off visibility.
- Select the Plan, it defines which plans can be used for new virtual server creation in this location. Plans that are not bound with the location will be visible but can’t be selected for new virtual server creation.
- Select the icon (a flag that represents a country) according to the actual geographical location of the node that was added as a compute resource.
- Select one or more compute resources to assign the location to.
- Click Save.
You have added the location and assigned it to the compute resource.
If you chose not to create a new location but to use the default location, you need only to assign the existing location to a compute resource.
To assign an existing location to a compute resource:
- Select the icon next to the location that you want to assign.
- Select one or more compute resources to assign the location to and then click Save.
You are almost there! The last step left before customers are ready to create servers.
7. Setting up sending out email notifications¶
SolusVM 2.0 can send automatic email notifications to your customers when
their servers are deployed. These emails contain information necessary for
connecting to the server command line via SSH: the IP address of a created server
To start sending out these email notifications, you need to get an SMTP server and then specify its settings in SolusVM 2.0.
To set up email notifications:
- Get an SMTP server. You can use such email services as SendGrid, MailGun, Mailchimp, or others or set up you own mail server (for example, Postfix).
- Log in to SolusVM 2.0 and go to Settings > Mail.
Specify the following settings:
- Outgoing mail server hostname
- SMTP port (usually one of the following: TCP 25, 465, or 587)
- SMTP username and password
- The email from which email notification will be sent
- The name that will be specified in the email notifications’ signature
Select the "Use TLS" checkbox.
- (Optional) To check if the specified SMTP settings are correct, you can send a test email. To do so, select the Send test email checkbox and type the desired email address.
- Click Save.
Everything is done from your side as the administrator. Customers are now ready to create their servers.
Let’s see how they do it.