Manage User VSs


This document applies to buyers. Otherwise refer to the Sellers or Users sections of this guide.


OnApp allows you to monitor the virtual servers created by your customers on federated zones. When customers create VSs in federates zones, you can view and moderate these VSs. Also there is a possibility to report a problem VS directly into OnApp support portal with a click of a button.


View User VSs



To view virtual servers, created by users within federated zone:

  1. Go to your Control Panel's Virtual Servers menu to view the list of all VSs created on federated zones and their details:
    • operating system - the OS of the virtual server
    • label - the name of the virtual server
    • VIP - whether the VIP status is enabled or disabled. Click the icon to enable/disable VIP status of a particular VS.
    • IP addresses - the IP addresses of the virtual server
    • disk size - disk size allocate to this virtual server
    • RAM - the amount of RAM available for this virtual server
    • backups - the number of backups and the space these backups take.
    • user - the owner of this VS. Click the user name to see the owner details.
    • power - the power status. Click the on/off buttons to change the status.
    • actions - the Actions button for quick access to the list of VS actions
  2. Click the virtual server's label to view its details.


Manage User VSs 



When your customers create VSs in federates zones, you can view and moderate these VSs under the Virtual Servers menu as normal VSs of your users. Refer to corresponding sections of Administration Guide for details.

Be aware, that during VS creation you can not set greater network port speed than indicated by seller when adding zone to federation.



Manage User vCenter VSs



When your customers create vCenter VSs in federates zones, you can view and moderate these VSs under the Virtual Servers menu as normal vCenter VSs of your users. Refer to corresponding sections of vCenter Implementation Guide for details.



Accelerate VS



If you are running OnApp 6.0, the federated virtual servers are accelerated by default. After the upgrade, virtual servers created in previous versions become accelerated as well.

If you and the seller you are subscribed to are running OnApp version 5.5 or later, you can turn on acceleration for virtual servers in Federation. Acceleration empowers any websites/VSs hosted on OnApp Cloud to use CDN. It provides all the benefits of a global CDN without any of the hassle of configuring and maintaining a CDN platform. Acceleration requires no modifications to the web applications running on virtual servers. All optimization is entirely automatic, and using minification & lossless compression of pages, scripts and images, will not modify or reduce the quality of the source content.

You can enable/disable acceleration for existing VSs at Control Panel > Virtual Servers > Label by using the Accelerate slider.

Acceleration can be enabled on a federated VS in a case there is at least one accelerator VS in the same network the original VS is using. You can check it using API: POST virtual_machines/accelerator_presence?ip_id=X where X is VS IP. If it returns true - you can enable acceleration on a VS.

For more information refer to CDN Accelerator.

When acceleration is enabled by a buyer, OnApp will bill directly the buyer. The price is $10/month/VS.

The Accelerate slider is available if the following conditions are met:

  • Accelerator is available in the network
  • IP Address, selected during VS creation, is in the same network as Accelerator
  • VS is created by setting own virtual server's resources, not by selecting a predefined instance package
  • The Show IP address selection for new VS slider is activated in the Control Panel Settings menu > Configuration
  • Only HTTP is supported. Other protocols, including HTTPS, will be passed through to the VS directly.
  • In order to route the VS’s traffic, the VS must be on the same network with the Accelerator.
  • CDN Accelerator does not support the Internet Protocol version 6 (IPv6).



Purge Content 



When acceleration is enabled for a virtual server, you can remove cache content for this VS. You can purge all content or particular files. When you want to purge particular files, the system will compare the checksum of the cached file and the new one. The cached file will be purged only if the checksums vary, that is the files are different. If the checksum of the two files is the same, the cached file will not be purged. When you purge all content, the checksums of the cached and new files are not taken into account.

Limitations and prerequisites:

  • The purge tool applies only to virtual servers with acceleration enabled.
  • You need to have the Allow to purge content of all Virtual Servers or the Allow to purge content of Own Virtual Servers permissions enabled to use this feature. For more information, refer to List of all OnApp Permissions.
  • If several users accelerate their VSs using one Accelerator, they can purge each other's files, provided that they enter the correct URL.


To purge a single file:

  1. Go to your Control Panel > Virtual Servers menu.
  2. Click a label of an accelerated virtual server.

  3. Click Acceleration Settings > Purge.
  4. In the Paths to Purge box, specify the destination path(s). You can enter only one path per line. You can enter either the original URL (the one prior to acceleration) or the accelerated URL.
  5. Click the Submit button to purge files.


To purge all content:

  1. Go to your Control Panel > Virtual Servers menu.
  2. Click a label of an accelerated virtual server.

  3. Click Acceleration Settings > Purge.
  4. Click the Purge All Contents of This Site button to purge all content.


Report Problem with VS



To report a problem with virtual server:

  1. Go to your Control Panel's Virtual Servers menu.
  2. Click the Label of appropriate VS.
  3. Go to the Tools menu.
  4. Click the Report A Problem button.
  5.  On the screen that appears describe a problem and click Submit.

The Report A Problem button will fire an email to Federation support.

The email will contain:

  • Reporter's login
  • Reporter's email
  • IP address or hostname of reporter's CP
  • Label, IP adress and hostname of reporter's virtual server
  • IP address or hostname of supplier/seller
  • IP address or hostname of trader/buyer
  • Message with problem description

We strongly recommend that you do not enable Report a federation problem on any virtual server and Report a federation problem on user's own virtual server permissions for your end customers, who you have provided a Federated VS to. For more details refer to the Permissions section.

Virtual Server Failed Actions



After a VS is built, any action you or your user schedules are executed on the Seller CP. In case any of the scheduled actions fail, the Failed Actions screen will enlist them. You can view the list of failed actions either for a particular virtual server, or for all VSs you or your users have built.


Failed Actions on All Virtual Servers



To view the list of failed actions for all virtual servers built, go to Dashboard > SysadminFailed Actions tab. The page that loads shows the list of failed actions for the servers with the following details:

  • Ref - the ID of the failed action. Click the Ref number to see the log details.
  • Date - the date when the failure occurred
  • Action - the name of the action that failed
  • Virtual Server - the label of the VS on which the action failed. Click the VSs label to see its Overview page.

If required, you can clean the failed actions for all virtual servers in the cloud, by clicking the Clean failed actions button. For this action, you require the necessary permissions.


Failed Action on Particular Virtual Server




You can view the list of failed actions for a particular VS. To view the last 10 failed actions that occurred on a specific virtual server:

  1. Go to Dashboard > Virtual Servers > VS label.
  2. On the page that loads under the Notes section, you will see the Failed Actions section that enlists the last 10 failed actions on that virtual server. The failed actions are displayed with the following details:
    • Ref - the ID of the failed action. Click the Ref number to see the log details.
    • Date - the date when the failure occurred
    • Action - the name of the action that failed

To view all the failed actions that occurred on a specific virtual server since it's been built:

  1. Go to Dashboard > Virtual Servers > VS label > Overview tab > Failed Actions.
  2. The page that loads shows all the failed actions that occurred on that virtual server with the following details:
    • Ref - the ID of the failed action. Click the Ref number to see the log details.
    • Date - the date when the failure occurred
    • Action - the name of the action that failed

If required, you can clean the failed actions for the virtual server, by clicking the Clean failed actions button. For this action, you require the necessary permissions.