You can edit resources for all VSs. Depending on the OS it is built on, some VSs can have their CPU and RAM resized without needing to be powered off ("resize without reboot"). If the VS template allows resize without reboot, the resize should be completed automatically: you will be returned to the VS details screen and see a message indicating the resize was successful. If the template does not allow this, you will be asked to confirm that the VS will need rebooting so that the resize can take place.
Windows virtual servers cannot be resized without reboot.
The Edit Virtual Server screen will differ depending the way the VS resources were selected: either manually or using an instance package. To adjust VS resources:
For virtual servers built by selecting resources manually:
Choose the new instance package for your virtual server. Click the instance package to select it. After that, the instance package you have chosen will be highlighted in green.
Those instance packages that have resources incompatible with the compute zone, on which the VS is built, will be greyed out. Greyed out instance packages cannot be selected.
You can only choose from those instance packages that offer more disk size than the VS currently uses.
You can also edit the Time Zone parameter for all Windows KVM and Xen virtual servers. After you edit the server's time zone, you need to stop and then start up the VS. Currently, the time zone is set at the Compute resource side only. Therefore, users need to set the target time zone inside a Windows VS manually. Setting correct time zone at the Compute resource side helps to keep correct time inside a VS after starting it if time synchronization is not completed for some reason.
If required, you can instruct OnApp to make sure a VS is never booted on the same Compute resource as another specific VS. This may be important if, for example, you have two name servers or a load balanced web server, and you need to keep VSs on separate physical servers.
To isolate one VS from another:
OnApp allows cold migration of ISO virtual servers between compute resources that share common data stores (or data store zones). Cold migration means moving virtual servers that are shut down.
To migrate a virtual server:
After migration, the power status of your virtual server remains the same as before the migration.
OnApp administrators can control user access over virtual server migration. Using OnApp permissions, you can allow/forbid users to perform migration of all virtual servers, or their own servers only. This is handled via the Control Panel's Roles and Sets menu.
Shut down the virtual server before destroying it. If you are deleting a VS that is running, the VS will be deleted after the time set in Timeout Before Shutting Down VSs configuration parameter.
To remove the virtual server from the cloud:
To manage a virtual server power options:
Reboot in Recovery- powers off and then restarts the VS in the recovery mode.
Startup Virtual Server - queues a start-up action for a VS that's currently powered off.
When you start up a VS, it might be implicitly cold migrated if the current compute resource does not have sufficient resources. For more information, refer to Virtual Server Provisioning.
Boot from ISO - boots the VS from an ISO. You can boot virtual servers from your own ISOs or the ISOs that are uploaded and made publicly available by other users. If you boot a VS from an ISO with the RAM requirement larger than the VS's RAM, the transaction will fail. Make sure that you have enabled the Any power action on own virtual servers and Allow own virtual servers to boot from ISO permissions for the user to have access to this feature.
As soon as you boot a VS from the installation ISO, OnApp may lose control of any components (networks, disks etc.) !!! The only available actions will be start and stop a VS. Be aware, that all the contents of the disk may be also deleted.
To change owner of ISO virtual server:
If you want to change an owner of the VS, which was built using an instance package, ensure that the new owner has permission to create VS using instance package and appropriate instance package in the billing plan. Otherwise you will not be able to change the ownership of this VS.