Feature Request: Mass Suspend VMs

Description:
Currently, SolusVM 2 requires administrators to suspend virtual machines (VMs) individually. While this works for small-scale operations, it becomes time-consuming and inefficient when managing a large number of VMs, especially during critical maintenance tasks such as network upgrades, compute resource reboots, or hardware updates.

I propose adding a "Mass Suspend VMs" feature that allows administrators to suspend all VMs on a specific compute resource or across multiple resources with a single action. This feature would ensure data stability and safety by preventing clients from losing unsaved work during maintenance windows.

Use Case:
When performing network maintenance or rebooting compute resources, administrators often need to suspend all running VMs to avoid data corruption or loss. Currently, suspending each VM individually is not only tedious but also increases the risk of human error, especially in environments with hundreds of VMs. A "Mass Suspend VMs" feature would streamline this process, allowing administrators to prepare all VMs for maintenance quickly and efficiently.

Benefits:

Data Safety : Suspending all VMs ensures that clients' unsaved work is preserved, reducing the risk of data loss during maintenance.
Time Efficiency : Administrators can suspend multiple VMs simultaneously, saving significant time during large-scale operations.
Reduced Human Error : Automating the suspension process minimizes the chance of overlooking VMs during manual operations.
Improved Client Experience : Clients will appreciate the proactive steps taken to safeguard their data, enhancing trust and satisfaction.
Implementation Suggestions:
Add a "Suspend All" button in the compute resource management interface, allowing administrators to suspend all VMs on a specific node or cluster.
Provide an option to filter VMs by status (e.g., only suspend running VMs).
Include a confirmation dialog to prevent accidental mass suspensions.
Optionally, allow administrators to send a notification to clients informing them of the suspension and the reason (e.g., scheduled maintenance).

Example Workflow:
Administrator navigates to the compute resource or cluster requiring maintenance.

They click the "Suspend All VMs" button.
A confirmation dialog appears, listing the number of VMs to be suspended and any relevant warnings.

After confirmation, all selected VMs are suspended, and clients receive a notification (if enabled).

Conclusion:

The addition of a "Mass Suspend VMs" feature would greatly enhance the efficiency and reliability of maintenance operations in SolusVM 2. It would provide administrators with a powerful tool to ensure data integrity while improving the overall client experience. I believe this feature would be a valuable addition to the platform and would benefit both service providers and end users.

Thank you for considering this suggestion!