OnApp 4.3.0-54 Update

Release NotesAffects Version/s
Improved statistics collection from VMware products to avoid memory bloat.4.1, 4.2
Improved High Availability cluster's management in Advanced Deployment scheme when Control Panel and Data servers run on separate boxes.4.3
EnsureComputeResourceOffline process is now run in a separate queue to speed up the cloud performance.4.2, 4.3
Added possibility to perform vCloud Director related tasks as a separate process in OnApp engine to increase performance. For this, if you have the OnApp and vCloud Director integration, it is recommended to set the Amount of service instances parameter in Settings > Configuration menu to 3 and up. 
Implemented ability to use MySQL Community Server as OnApp Control Panel's database server: added '–community' installer option.   
Configured MySQL Server's memory to use maximum 4GB (relatively to amount of RAM) even when more is available to eliminate the problems with service starting. 
Fixed the problem when OnApp database dumps weren't rotated correctly on remote host.3.5, 4.0, 4.1, 4.2, 4.3

Patch Installation

The instructions below are relevant if you already run OnApp 4.3.0 version. If you are upgrading from OnApp 4.2.x. version, run the full upgrade procedure. For more information refer to the Get Started guide.

To apply the patch into Control Panel (running 4.3.0 version):

  1. Upgrade OnApp Control Panel installer package:

    # yum update onapp-cp-install
  2. Run the Control Panel installer:

    # /onapp/onapp-cp-install/onapp-cp-install.sh

Patch Installation for Clouds with High Availability

If you are a High Availability customer, it is recommended that you contact support for help with the procedure described below. Be aware, that if the configuration below is performed incorrectly it may cause damage to your cloud.


To apply the patch for clouds with High Availability enabled:
  1. Switch the cloud to maintenance mode at Control Panel > Sysadmin Tools > Control Panel Maintenance


    Run the following commands on all three Control Panel servers:

  2. Upgrade the OnApp installer package:

    # yum update onapp-cp-install
  3. Upgrade your server OS components (if required):

    # /onapp/onapp-cp-install/onapp-cp-install.sh -y
  4. Run the Control Panel installer:

    # /onapp/onapp-cp-install/onapp-cp-install.sh

After you have successfully run the previous commands on all Control Panel servers, issue the following two commands on one of the CP servers:

  1. Switch all nodes back online by running the following command once on any of the nodes:

    # crm configure property maintenance-mode=false
  2. Enable file synchronization on all nodes by running the following command once on any of the nodes:

    # crm resource start lsyncd-cluster