431 results found

1. OpenVZ 7 supports cloud-init and live migration on SolusVM 2

   It would be great if we have this feature in SolusVM 2.

   Live migration and cloud-init support OpenVZ 7

   https://docs.openvz.org/openvz_users_guide.webhelp/_using_cloud_init_for_virtual_machine_guest_initialization.html

   https://docs.openvz.org/openvz_users_guide.webhelp/_live_migration_of_virtual_machines_and_containers.html

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  OpenVZ  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Servers created through the WHMCS Module and the Solusvm interface should be separated.

   Customers can create Virtual servers in 2 ways.

   1. You can purchase a "prepaid" virtual server through WHMCS.
   2. Can create "pay-as-you-go" virtual server via SolusVM administration panel.

   If the user wants to use 2 billing methods:
   Will make purchases through WHMCS to create a "prepaid" virtual server.
   To purchase "pay-as-you-go" packages, Solusvm will create a server through the administration panel.

   But using it this way causes a problem like this.
   The user purchased 2 "prepaid" virtual servers from WHMCS.
   And he created 1 "pay-as-you-go" package via the Solusvm management panel.
   If the user enters the Solusvm Administration panel, he will see 3 servers. 2 of them are servers created via WHMCS module and 1 is via Solusvm. The user may accidentally delete the server he/she purchased prepaid while managing it as he/she wishes from the solusvm management panel. For this reason, the order must be created again via WHMCS. In order to avoid mixing two types of billing methods,

   Servers created with the module and servers created through the Solusvm administration panel should be separated.

   Customers can create Virtual servers in 2 ways.

   1. You can purchase a "prepaid" virtual server through WHMCS.
   2. Can create "pay-as-you-go" virtual server via SolusVM administration panel.

   If the user wants to use 2 billing methods:
   Will make purchases through WHMCS to create a "prepaid" virtual server.
   To purchase "pay-as-you-go" packages, Solusvm will create a server through the administration panel.

   But using it this way causes a problem like this.
   The user purchased 2 "prepaid" virtual servers from WHMCS.
   And he created 1 "pay-as-you-go" package via the Solusvm management panel.
   If the user enters the Solusvm Administration panel, he will see… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  VPS Creation Options  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. When the user tries to create a "pay-as-you-go" Cloud hosting account after the "Prepaid" module, he encounters an error.

   When the user purchases a vps through WHMCS. When the admin approves this virtual server, the Solusvm module creates this virtual server in the SVM panel and a user account is created in SVM with the e-mail address of the user in WHMCS.

   To use Cloud hosting "pay-as-you-go" billing, the user clicks on the cloud hosting tab in WHMCS and confirms his e-mail address. Then, when he presses the "I accept" button on the "Accept Terms of Use" screen, he encounters the following error:

   Email address already in use on the SolusVM 2.0 system. Please use a different email address or contact support.

   For the virtual server purchased by WHMCS on behalf of the user, the module created a user account when creating the virtual server (but the user cannot access this account). For this reason, the user encounters this error when trying to activate the Cloud hosting service and cannot access the SolusVM management panel.

   When the user purchases a vps through WHMCS. When the admin approves this virtual server, the Solusvm module creates this virtual server in the SVM panel and a user account is created in SVM with the e-mail address of the user in WHMCS.

   To use Cloud hosting "pay-as-you-go" billing, the user clicks on the cloud hosting tab in WHMCS and confirms his e-mail address. Then, when he presses the "I accept" button on the "Accept Terms of Use" screen, he encounters the following error:

   Email address already in use on the SolusVM 2.0 system. Please use a different email address… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Billing Modules  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. DNS Settings - All System Variables in both fields

   As you know, rDNS PTR should match the hostname (domain) value. This means that the created domain should resolve to the IP address and vice versa.
   For this reason, it would be desirable to have the ability to set something like the following in both fields of the template settings, for example:

   Default hostname template for new servers: {{random-prefix}}.super.cloud
   Default reverse DNS record template: {{random-prefix}}.super.cloud
   or
   Default hostname template for new servers: {{random-prefix}}.{{ ip-dashed }}.super.cloud
   Default reverse DNS record template: {{random-prefix}}.{{ ip-dashed }}.super.cloud

   Right now, in the first field, only {{random-prefix}} is available, and other macros, such as {{ ip-dashed }}, etc., are not available.
   In the second field, {{random-prefix}} does not work. It is necessary that all system variables can be used in both fields.

   As you know, rDNS PTR should match the hostname (domain) value. This means that the created domain should resolve to the IP address and vice versa.
   For this reason, it would be desirable to have the ability to set something like the following in both fields of the template settings, for example:

   Default hostname template for new servers: {{random-prefix}}.super.cloud
   Default reverse DNS record template: {{random-prefix}}.super.cloud
   or
   Default hostname template for new servers: {{random-prefix}}.{{ ip-dashed }}.super.cloud
   Default reverse DNS record template: {{random-prefix}}.{{ ip-dashed }}.super.cloud

   Right now, in the first field, only {{random-prefix}} is available, and other macros, such as {{ ip-dashed… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Networking & IP Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Add route for project ssh key deletion

   It would be awesome if it would be able to delete project ssh keys via api

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Welcome email with server logins along with the Application details.

   In SolusVM 2, it would be better to have the installed application details with the VM IP, and root password details in the welcome email if someone selects the Application based OS image.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Admin & User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Modify individual resource like CPU for a VM and in plan on SolusIO

   There are limitations in resource upgrades for the VM and modifying the plan. Allowing to change the unique resource for VMs and plan on the SolusIO will make it more feasible.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Admin & User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Qcow2 filesystem support for OpenVZ in SolusIO

   SolusIO creates the OpenVZ VM on Virtuozzo 7 environment in Ploop format now. It would be great to have an option to create the VM in qcow2 images.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  OpenVZ  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Add ability to modify VPS Notes via API

   Add ability to modify VPS Notes via API

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. automate the recovery process of vps backups in nodes

    automate the recovery process of vps backups in nodes even if the node is not available in another node, allowing the recovery of all the vps of a node A not accessible in another node B

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backups  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Zstd for backup and restores

    Zstd for backup and restores

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backups  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. recursos flotantes

    la opcion de poder asignar un minimo y maximo de recursos que un vps pueda llegar a ocupar por un tiempo determinado.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  OpenVZ  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Add VIM editor plugin support for HTML5 Console.

    VIM editor support isn't added into HTML5 Console. It would be better to have this feature with HTML5 feature.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin & User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Button to activate docker on a container

    Hello,
    We want to have a button to toggle on / off docker (net filter) on OpenVZ 7 containers.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin & User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. IPv6 Mac Address

    Allow custom mac address assignment for IPv6 addresses. Some network providers require mac assignments for individual IPv6 addresses, and this currently requires manual work every time you want to assign an IPv6 to a KVM VM currently.

    IPv6 and IPv4 should be allowed to be paired in this instance, since IPv4 and IPv6 mac address would need to be the same for the individual VM. If IPv6 have a custom mac address, and are assigned automatically, this could cause mix ups.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backend Automation  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Add ability to apply default QoS settings for KVM VPS

    Add ability to apply default QoS settings for KVM VPS

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin & User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. add ability to set up QoS of KVM VPSes via API

    add ability to set up QoS of KVM VPSes via API

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Ability to change language for Administrator area

    Add ability to change language for Administrator area

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin & User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Add ability to change default VNC ports range for qemu KVM images

    By default, SolusVM operates VNC ports in its database and adds it to .xml config file, so changes to qemu.conf do not affect the VNC ports for VPS. It would be great to be able to switch it on other range of ports.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  KVM  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. add ability to set default NIC card type for KVM VPSes via API, plan or template

    add ability to set default NIC card type for KVM VPSes via API, plan or template

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating