Manage ISO Virtual Servers

OnApp Cloud gives you high-end cloud management features for virtual servers that are built from ISOs including:

Ensure that ISO permissions are on before managing ISO virtual servers. For more information about permissions, refer to the OnApp Permissions section of this guide.

This document provides the information on how you can manage the virtual servers built from ISO.

Edit ISO Virtual Server 

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 on the way the VS resources were selected: either manually or using an instance package. To adjust VS resources:

1. Go to your Control Panel > Cloud > Virtual Servers menu.
2. Click the label of the server you want to resize, to show its details screen.
3. Click the Actions button, point to Options, and select the Edit Virtual Server link.

   For virtual servers built by selecting resources manually:
   
   

   • Change CPU cores, CPU priority/units and RAM values.
   
   For virtual servers built using instance packages:
   
   

   • 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.

     After you select a new instance package you can use the extra disk size to create a new disk for the VS or make the existing VS disk larger.

   You can also edit the Time Zone parameter for all Windows KVM 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 the 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.

4. Click Save.

Segregate ISO Virtual Server

If required, you can instruct OnApp to make sure a VS is never booted on the same compute resource as another specific VS (contact OnApp Support or your account manager on amteam@onapp.com). 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:

1. Go to your Control Panel > Cloud > Virtual Servers menu.
2. Click the label of the virtual server you want to segregate.
3. On the screen that appears, click the Actions button, point to Performance, and then click Segregate Virtual Server.
4. In the dialogue box that pops up, use the drop-down menu to choose a VS you want to keep away from.
5. Click the Segregate Virtual server button to finish.

Clone ISO Virtual Server

You can create a clone based on the same resources as the origin ISO virtual server. The cloned virtual server inherits resources from the origin as follows. 

To clone a virtual server, follow the next procedure:

1. Go to your Control Panel > Cloud > Virtual Servers.
2. Click a label of the virtual server that you want to clone.
3. Click Actions, point to Options, and then click Clone Virtual Server. 
4. In the dialog box, you can change the following properties for the KVM VS:
   • Label 

   • Hostname - a hostname of the virtual server. The hostname can consist of letters [A-Z a-z], digits [0-9], and dash [ - ]. For more info on hostname validation, refer to RFC documentation.

      Additional Consideration for Windows

     The following symbols are not allowed for Windows-based virtual servers:

     • percent  [%]
     • quotation marks [“ “]
     • angle brackets [<>]
     • vertical bar [ | ]
     • caret [^]
     • ampersand [&]
     • parentheses [( )]

     • Password - password for the virtual server. It can consist of 6-99 symbols, including letters [A-Z a-z], digits [0-9], dash [ - ], underscore [ _ ], and the following special characters: ~ ! @ # $ * _ - + = ` \\ { } [ ] : ; ' , . ? /. You can use both lower and uppercase letters. If you don't enter a password, it will be generated automatically.

     • Password confirmation - repeat the password to confirm it

     • Encrypt password - move the slider to the right to encrypt your password

5. Then click Clone Virtual Server to confirm the action. 

After you confirm the action, several transactions are run to complete the cloning process. You can check a status of each transaction in Activity Log of the virtual server. After the virtual server is cloned, it is powered off until you start it. 

Migrate ISO Virtual Server

 Hot migration is available for VSs created from ISO if Allowed hot migrate slider was enabled during ISO upload or during ISO editing.

OnApp allows migration of ISO virtual servers between compute resources that share common data stores (or data store zones).

To migrate a virtual server:

1. Go to your Control Panel > Cloud > Virtual Servers menu.
2. Click the label of the virtual server you want to migrate.
3. Click the Actions button, point to Options, and click the Migrate Virtual Server link.
4. In the window that appears, choose the target compute resource from the drop-down menu.
5. Click the Start Migration button.

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.

Delete ISO Virtual Server

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:

1. Go to your Control Panel > Cloud > Virtual Servers menu.
2. On the screen that appears, you'll see the list of all virtual servers in the cloud. Click the label of the virtual server you want to delete.
3. On the virtual server's screen, click the Actions button, point to Options, then select Delete Virtual Server.
4. Confirm by clicking the Destroy button.

IMPORTANT:

• You won't be able to restore a virtual server after deleting it.
• Deleting a virtual server removes all data stored on that virtual server.

ISO Virtual Server Power Options

To manage a virtual server power options:

1. Go to your Control Panel > Cloud > Virtual Servers menu.
2. Click the label of the required virtual server.
3. Click the Actions button on the VS's screen and then point to Power to expand the menu.
4. This menu enables you to perform the following power actions on VSs (the exact list shown depends on the VS status):

• • Reboot Virtual Server - powers off and then restarts the VS.

  • Reboot in Recovery - powers off and then restarts the VS in the recovery mode.

  • Suspend  - stops a VS, changes its status to suspended and disables all the other actions on VS, unless unsuspended.
  • Shut Down Virtual Server – pops up a dialogue box, where you can either Shut Down VS (terminates the VS gracefully) or Power Off VS (terminates the VS forcefully).

  • 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.

  • Startup on Recovery - starts the VS in recovery mode.

  • 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.

Change Owner of ISO Virtual Server

To change owner of the ISO virtual server:

1. Go to your Control Panel > Cloud > Virtual Servers menu.
2. Click the label of the required virtual server.
3. Click the Actions button on the VS's screen, point to Administrations and select Change Owner.
4. Choose a user to whom you want to pass ownership of the VS from the drop-down list.
5. Click the Change Owner button.

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 bucket. Otherwise you will not be able to change the ownership of this VS.

See also:

• ISOs
• ISO Virtual Server Networks
• ISO Virtual Server Disks
• ISO Virtual Server Statistics

Leave feedback