Page tree
Skip to end of metadata
Go to start of metadata

This guide explains how to upgrade OnApp Cloud v4.0 to the v4.1. OnApp 4.1 updates only Control Panel server. Follow the procedure listed below in the correct order to upgrade your cloud. 

You must be running OnApp 4.0 to upgrade to 4.1. If you are using an earlier version, please upgrade to 4.0. first.

On this page:

Introduction and Important Notes


Before you begin

  1. Check the Activity Log in your OnApp CP dashboard if there are no transactions running in your cloud. If so, wait until all transactions are complete.
  2. Make sure no Control Panel files are open for editing under the root user account.

  3. If you are using a third-party billing platform, please ensure that this is compatible with OnApp 4.1 before proceeding with the upgrade! The latest WHMCS modules can be found here.

  4. If you are using WHMCS modules, make sure to update the PHP Wrapper after you update OnApp Cloud. Download the latest wrapper.

  5. We strongly recommend that you test all your custom scripts before upgrading your production environment.

  6. Be aware that OnApp does not support UEFI on static compute resources. You should disable UEFI on your compute resources before installing OnApp.
  7. Installer output is redirected to ./onapp-cp-install.log

  8. All installer critical errors are in /var/log/messages

    Drives assigned for use by Integrated Storage are identified using a disk signature that is generated using SCSI page query mechanism to the device. Please note that disk signatures may change across different kernel versions following an upgrade and reboot. If this occurs, go to the compute resource edit page to re-identify and select the correct drives. Please contact support if you have any concerns regarding this operation.

Getting support for your upgrade

You can use the information in this document to perform your own upgrade to the 4.1 version of the OnApp Cloud. However, if you have a full OnApp Cloud license, you are entitled to free upgrade support from the OnApp Support team.

If you would prefer to have the Support team perform the upgrade for you, just raise a ticket in the normal way. Please be aware, however, that there may be a queue!

For help with your upgrade, visit the OnApp community forum: http://forum.onapp.com.

 

Upgrade Control Panel Server


 

To upgrade your Control Panel server:

  1. Run the following command from the CP server to stop the OnApp service:

    service onapp stop
  2. Download and install the latest OnApp YUM repository file:

    bash#> rpm -Uvh http://rpm.repo.onapp.com/repo/onapp-repo-4.1.noarch.rpm
  3. Upgrade OnApp Control Panel installer package:

    bash#> yum update onapp-cp-install


  4. Update your server OS components (if required):

    bash# /onapp/onapp-cp-install/onapp-cp-install.sh -y
  5. (Optional) If you need some custom Control Panel configuration, set the values before the installer script runs.

     Edit the /onapp/onapp-cp.conf file to set Control Panel custom values

    # Template server URL

    TEMPLATE_SERVER_URL='http://templates-manager.onapp.com/'


    # IPs (separated with coma) list for the snmp to trap

    SNMP_TRAP_IPS=


    # OnApp Control Panel custom version

    ONAPP_VERSION=


    # OnApp MySQL/MariaDB connection data (database.yml)

    ONAPP_CONN_WAIT_TIMEOUT=15
    ONAPP_CONN_POOL=30
    ONAPP_CONN_RECONNECT='true'
    ONAPP_CONN_ENCODING='utf8'
    ONAPP_CONN_SOCKET='/var/lib/mysql/mysql.sock'


    # MySQL/MariaDB server configuration data (in case of local server)

    MYSQL_WAIT_TIMEOUT=604800
    MYSQL_MAX_CONNECTIONS=500
    MYSQL_PORT=3306


    # Use MariaDB instead of MySQL as OnApp database server

    WITH_MARIADB=0



    # Configure the database server relative amount of available RAM

    TUNE_DB_SERVER=0



    # The number of C data structures that can be allocated before triggering the garbage collector. It defaults to 8 million

    RUBY_GC_MALLOC_LIMIT=16000000



    # sysctl.conf net.core.somaxconn value

    NET_CORE_SOMAXCONN=2048



    # The root of OnApp database dump directory (on the Control Panel box)

    ONAPP_DB_DUMP_ROOT=



    # Remote server's (to store database dumps) IP, user, path, openssh connection options ans number of dumps to keep

    DB_DUMP_SERVER=
    DB_DUMP_USER=root
    DB_DUMP_SERVER_ROOT=/onapp/backups
    DB_DUMP_SERVER_SSH_OPT="-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o PasswordAuthentication=no"
    KEEP_DUMPS=168
    DB_DUMP_CRON='40 * * * *'



    # Enable monit - tool for managing and monitoring Unix systems

    ENABLE_MONIT=1



    # If enabled (the 1 value is set) - install (if local box) and configures RabbitMQ Server (messaging system) for the vCloud support.

    ENABLE_RABBITMQ=1



    # Rotate transactions' log files created more then TRANS_LOGS_ROTATE_TIME day(s) ago

    TRANS_LOGS_ROTATE_TIME=30



    # Maximum allowed for uploading file size in bytes, from 0 (meaning unlimited) to 2147483647 (2GB). Default is 1GB

    MAX_UPLOAD_SIZE=1073741824



    # Timeout before ping Redis Server to check if it is started. Default is 5 sec.

    REDIS_PING_TIMEOUT=5



    # OnApp Control Panel SSL certificates (please do not change if you aren't familar with SSL certificates)
    # * The data below to generate self-signed PEM-encoded X.509 certificate

    SSL_CERT_COUNTRY_NAME=UK
    SSL_CERT_ORGANIZATION_NAME='OnApp Limited'
    SSL_CERT_ORGANIZATION_ALUNITNAME='OnApp Cloud'
    SSL_CERT_COMMON_NAME=`hostname --fqdn 2>/dev/null`


    #   SSLCertificateFile, SSLCertificateKeyFile Apache directives' values
    #   ssl_certificate, ssl_certificate_key Nginx directives' values

    SSLCERTIFICATEFILE=/etc/pki/tls/certs/ca.crt
    SSLCERTIFICATECSRFILE=/etc/pki/tls/private/ca.csr
    SSLCERTIFICATEKEYFILE=/etc/pki/tls/private/ca.key


    # * PEM-encoded CA Certificate (if custom one exists)
    #   SSLCACertificateFile, SSLCertificateChainFile Apache directives' values
    #   ssl_client_certificate Nginx directives' values

    SSLCACERTIFICATEFILE=
    SSLCERTIFICATECHAINFILE=


    #   SSLCipherSuite, SSLProtocol Apache directives' values
    #   ssl_ciphers, ssl_protocols Nginx directives' values

    SSLCIPHERSUITE=
    SSLPROTOCOL=

     

    bash# vi /onapp/onapp-cp.conf
  6. Run Control Panel installer:

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

    See the installer options below for details.

     The full list of Control Panel installer options:

    Usage:

    /onapp/onapp-cp-install/onapp-cp-install.sh [-c CONFIG_FILE] [-m MYSQL_HOST] [-p MYSQL_PASSWD] [-d MYSQL_DB] [-u MYSQL_USER] [-U ADMIN_LOGIN] [-P ADMIN_PASSWD] [-F ADMIN_FIRSTNAME] [-L ADMIN_LASTNAME] [-E ADMIN_EMAIL] [-v ONAPP_VERSION] [-i SNMP_TRAP_IPS] [--redis-host=REDIS_HOST] [--redis-passwd[=REDIS_PASSWD] [--redis-port=REDIS_PORT] [--redis-sock=REDIS_PATH] [-a] [-y] [-D] [-h]

     

    Where:

     
    MYSQL_*Options are useful if MySQL is already installed and configured.
    -m MYSQL_HOST MySQL host
    -p MYSQL_PASSWDMySQL password
    -d MYSQL_DBOnApp MySQL database name
    -u MYSQL_USERMySQL user
      
    REDIS_*Options are useful if Redis Server is already installed and configured.
    --redis-host=REDIS_HOST


    IP address/FQDN where Redis Server runs.
    The Redis Server will be installed and configured on the current box if localhost/127.0.0.1 or box's public IP address (listed in SNMP_TRAP_IPS) is specified.
    If local Redis, it will serve as well on the unix socket '/tmp/redis.sock'.
    Default value is 127.0.0.1.
    --redis-port=REDIS_PORTRedis Server listen port.
    Defaults are:
    0 - if local server
    6379 - if remote server
    --redis-passwd[=REDIS_PASSWD]Redis Server password to authentificate.
    Random password is generated if the option's argument isn't specified.
    By default no password is used for local Redis.
    --redis-sock=REDIS_PATH : Path to the Redis Server's socket. Used if local server only.
    Default is /tmp/redis.sock
      
    ADMIN_*Options are used to configure OnApp Control Panel administrator data.
    Please note, that these options are for NEW INSTALL only and not for upgrade
    -P ADMIN_PASSWD CP administrator password
    -F ADMIN_FIRSTNAMECP administrator first name
    -L ADMIN_LASTNAMECP administrator last name
    -E ADMIN_EMAILCP administrator e-mail
      
    -v ONAPP_VERSIONInstall custom OnApp CP version
    -i SNMP_TRAP_IPSIP addresses separated with coma for snmp to trap
    -c CONFIG_FILECustom installer configuration file. Otherwise, preinstalled one is used.
    -yupdate OS packages (except of OnApp provided) on the box with 'yum update'.
    -ado not be interactive. Process with automatic installation.
    -Ddo not make database dump, and make sure it is disabled in the cron and not running at the moment
    -hprint this info

    You may wish to reboot your Control Panel server to take advantage of a new kernel if it is installed. It is not required immediately as a part of the upgrade process though.

     

  7. In the OnApp UI navigate to Settings > Configuration and click Save to complete the process.

  • No labels