420 results found
-
Reseller API SolusVM 2
Add reseller API Support for SolusVM 2.
4 votes -
iSCSI/FC Support
We are using big Storage Arrays which can export via FibreChannel or iSCSI, we would like to see an easy way to Use Multiple LUNs in maybe an LVM Pool to keep the functionality with Snapshots.
And if you are considering this, please add an easy Way to Enable Multipathing, not like PVE at the moment ^^2 votes -
Enhance SolusVM with Comprehensive Usage Monitoring & Logging
Hello SolusVM team and fellow users,
I would like to request an important enhancement to SolusVM: the ability to monitor and log historical usage data more effectively. Currently, the system provides very limited historical tracking, making it difficult to see detailed client traffic usage or filter their consumption over time.
Having a more comprehensive monitoring and logging feature would be highly beneficial. This could include:
✅ Detailed traffic usage logs per client
✅ Historical usage tracking with filtering options
✅ Real-time and past resource consumption insightsSuch a feature would greatly improve management efficiency and provide better oversight for administrators.…
7 votes -
Propose the addition of a configurable option for plan parameters as an add-on for virtual machine resources
Currently, the configurable option functions as an override during the checkout process. It would be beneficial if it were to serve as an add-on to the selected plan.
12 votes -
Proper migration progress
Hello team, we would like to recommend that you fix the migration status (progress) of VMs between Compute Resources. Currently, the migration status is 0%, and then it jumps to 100%.
3 votes -
Implement an option clear old tasks in SolusVM 2
Implement a way to clean that history of tasks or set a cut off date to rotate those entries from the SolusVM 2 panel.
2 votes -
2 votes
-
To add customize email templates/notifications in SolusVM2
To be able to setup custom template for e-mail notification for adding additional IP by the customer.
2 votes -
Feature Request: Interface Selection for VPC Configuration in SolusVM 2
Description:
Add an option in SolusVM 2 that allows users to select a specific network interface when defining the VPC IP address for a Compute Resource.
Expected Behavior:
SolusVM 2 should automatically list all physical and virtual interfaces of the Compute Resource for selection.
The selected interface should be automatically added to the Open vSwitch structure.
- Use the selected interface for traffic transfer between Compute Resources for VXLAN bridges.
Configure VPC bridges by adding a trunk.
- Enable traffic tagging using a VXLAN key.
This feature would ensure that SolusVM 2 configures the VPC on physically available networks, improving flexibility and…
7 votes -
Allow SMTP traffic for specific VMs in SolusVM 2 UI
The SolusVM 2 UI > Settings > Network rules > Disable SMTP traffic option disables it globally for all CRs and VMs.
Add a feature to allow SMTP traffic for specific VMs in SolusVM 2 UI13 votes -
Add support for changing IP addresses to those in different VLANs
Add support for changing IP addresses to those in different VLANs
For example, changing from a.a.a.a to c.c.c.c, where each belongs to a different VLAN.
2 votes -
Adding the "firmware option" to the OS image settings
Adding the "firmware option" to the individual image operating system settings -
Always spin up the new VPS'es with UEFI when using a specific image.
Example: adding a Windows 2024 image or newer should always use UEFI when used for VPS creation instead of manually performing this.10 votes -
Filtering options for IP Management - SolusVM 2
There is a lack of effective filtering and bulk management capabilities for IP addresses within blocks. At present, both reserved and available IP addresses require manual review, which restricts bulk operations to deletion only. It is essential for the panel to facilitate mass actions, such as reserving IP addresses that have not yet been assigned to a virtual machine, as the current process necessitates manual intervention for each individual address.
12 votes -
To change Mixpanel module cross_subdomain_cookie to false
Set crosssubdomaincookie: false during SDK initialization. For example:
mixpanel.init('PROJECTTOKEN', {
crosssubdomain_cookie: false,
});This will prevent cookies from spreading to all subdomains.
1 vote -
Improve the SolusVM 2 functionality on adding the additional disk.
SolusVM 2 could allow for the addition of secondary disks to the VM without the need for Guest Tools, yet it still treats this as a required feature.
Therefore, it is essential to enable the capability to add secondary or additional disks to the VM without relying on Guest Tools.
11 votes -
krastyo.todorov@webpros.com
Option to exclude from backup extra drivers added to VPS.
4 votes -
Handling Rescue Passwords - SolusVM 2
Migrated VPS instances may not always have a password stored in the database. Consequently, even if the current root password is known, connecting via SSH through the rescue environment is not feasible. The rescue image includes Guest Tools, which allows you to obtain a new root password by booting into the rescue mode, similar to the process in SolusVM1.
10 votes -
Editing the Cloud-init configuration for an existing VM - SolusVM 2
In SolusVM 2, the ability to modify the Cloud-init configuration is limited to before the creation of the VM and during OS reinstallation.
It would be beneficial to have a feature in SolusVM that allows for the editing and reloading of the Cloud-init configuration at any time.
7 votes -
Add implementation of path-style URLs for S3 storage based services as Contabo.
The implementation of path-style URLs for SolsuVM2 to be compatible with various backend services, such as those offered by Contabo. It will allow users to customize their URL handling, enhancing integration in diverse systems.
1 vote -
Central management of migration_timeout_minutes
Migration of VMs between CRs is limited by migrationtimeoutminutes which has a "hidden" default of 180 minutes, denoted by "migrationtimeoutminutes": 0 in /etc/solus/agent.json
Increasing the timeout (e.g. to allow successful migration of large servers) requires manually editing the agent.json on source and destination CRs.
However, if you run VMs large enough that it makes sense to increase the timeout, you will most likely need to increase this across all CRs - otherwise you'll hit intermittent failures as you migrate VMs around over time.
It should be possible to manage the timeout centrally from the management node,…
1 vote
- Don't see your idea?