Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Excerpt

Anchor
packages
packages
Upgrade CloudBoot Packages




Info
  • Create a backup of the /tftpboot directory in case storage packages rollback will be needed.
  • If you are updating to the OnApp 5.0 Patch 4 1 CloudBoot Update, note that NIC naming has been changed from MGT to mgt in this update. This improvement affects CloudBoot compute resources that have custom scripts with advanced networking configuration including MGT NIC manipulations. You need to change 'MGT' to 'mgt' in the compute resource custom scripts during the update, if 'mgt' NIC manipulations are performed there.

To upgrade the OnApp Storage packages:

  1. Upgrade the repo:

    Code Block
    CP_host#> rpm -Uvh http://rpm.repo.onapp.com/repo/onapp-repo-5.0.noarch.rpm
    
  2. Upgrade the packages:

    Code Block
    CP_host#> yum update onapp-store-install
  3. Run the script:

    Code Block
    CP_host#> /onapp/onapp-store-install/onapp-store-install.sh
    Note

    Be aware that the disk-less nodes password is the root password for the CloudBoot compute resources. By default it is blank.

    When run in the interactive mode, enter the required information.

Upgrade CloudBoot Backup Servers



Info

Make sure to update CloudBoot packages on your Control Panel server before proceeding to the upgrade of CloudBoot backup servers.


CloudBoot backup servers are CloudBooted KVM compute resources that can be be used as backup servers. The CloudBoot backup server upgrade procedure is almost the same as the CloudBoot compute resource upgrade. Follow the instructions provided in this section to upgrade CloudBoot backup servers in your cloud.

Once you have upgraded the CloudBoot dependencies, you have to reboot your Cloud Boot compute resource to update the Cloud Boot RPM. You do not need to perform any backup server upgrade operations using console.

To do so:

  1. Go to your Control Panel Settings menu.

  2. Click the Compute resources icon.

  3. Click the label of the CloudBoot compute resource the backup server is based on.

  4. On the compute resource details screen, click the Actions button, then click Reboot Compute resource.

  5. A new screen will open asking for confirmation before reboot:

    • Are you sure you want to reboot this compute resource? Confirm that you want the compute resource to reboot.

  6. When you're certain you want to proceed with the reboot, click the Reboot button.

  7. Repeat these steps for all CloudBoot backup servers in your cloud.

  8. Once all are rebooted, proceed to CloudBoot compute resources upgrade.

Upgrade CloudBoot Compute Resources


Simple RebootThis method is the simplest method technically. It also ensures all tools are updated. However, it will result in some limited downtime (its duration depends on how many virtual servers are running on each compute resource).
Migrate and rebootThis method involves migrating all virtual servers off each CloudBoot compute resource in turn. The compute resource can then be safely rebooted, picking up the upgraded Integrated Storage and CloudBoot packages. Virtual servers that do not support hot migrate will have to be stopped.

In case you have applied any custom configuration to your CloudBoot servers, it is recommended to recheck that this customization does not break new cloud boot image version. For this, reboot a compute resource and run Storage Health Check and Network Health Check. Make sure that Vdisks hosted on a compute resource are redundant and healthy before rebooting a CloudBoot compute resource.

Note

If you are using Integrated Storage with caching, please contact support before upgrade.


Anchor
simple
simple
Simple Reboot

Follow the below procedure to upgrade the CloudBoot compute resources with reboot:
 

1. Upgrade CloudBoot Packages.
2. When the CloudBoot packages upgrade is complete, stop all virtual servers which reside on the CloudBoot compute resources.

3. Reboot all CloudBoot compute resources.

Once the compute resources are booted, the upgrade is complete. Before starting all Virtual Servers please ensure that the diagnostics page does not report any issue. In case of any issue, please press repair button to resolve it, then continue with starting Virtual Servers.


Info

Note that virtual servers cannot be stopped simultaneously, but must be stopped in sequence. This can result in considerable downtime if there are a large number of virtual servers.

Anchor
migrate
migrate
Migrate and reboot

Use this procedure if you prefer migrating all virtual servers to another compute resource and conducting overall upgrade of your CloudBoot and Integrated Storage. Virtual servers that do not support hot migrate will have to be stopped.

Once you have upgraded the CloudBoot packages, you have to reboot your CloudBoot compute resources to update them.

To do so:

  1.  Run the following command from the Control Panel server terminal to display the list of compute resources with their IP addresses. Make a note of the list of IPs:

    Code Block
    CP_host#> liveUpdate listHVs 

    This command will also show whether compute resources are eligible for live upgrade.

    Info

    If the command liveUpdate is not available then it may be located in the sbin directory instead (cd /usr/local/sbin).

  2. Run the following command for every compute resource:

    Code Block
    CP_host#> liveUpdate updateToolstack <HV IP Addr> 

    Once all the toolstacks are updated run the following command for every compute resource: 

    Code Block
    CP_host#> liveUpdate refreshControllers <HV IP Addr>
    Info

    Wait several minutes for all degraded disks to come to synchronized state. The synchronization will take approximately three minutes for each compute resource.

    After each controller restart, check for any issues on the backup server (or on one Compute resource from each zone):

    1. Log on via SSH to the backup server (or Compute resource).
    2. Run getdegradednodes from the SSH console.
    3. Run getdegradedvdisks from the SSH console.

  3. Migrate all the virtual servers from the CloudBoot compute resource to another compute resource. Follow the instructions described in the Migrate Virtual Server section of the Admin guide to migrate virtual servers.
  4. After that, go to your Control Panel Settings menu.
  5. Click the Compute Resources icon.
  6. Click the label of the CloudBoot compute resource you have migrated all VSs from.
  7. On the compute resource details screen, click the Actions button, then click Reboot Compute resource.

    Warning

    Rebooting a compute resource assigned to a data store with a single replica (single-replica compute resource) or degraded virtual disks may result in data loss.


  8. A new screen will open asking for confirmation (via two check boxes) before reboot:

    • Stop all virtual servers that cannot be migrated to another compute resource? Check this box if you want VSs that cannot be migrated to be powered off. When a compute resource is scheduled for a reboot, OnApp will first attempt to hot migrate all VSs it hosts. If hot migration is not possible for a VS, OnApp will attempt to cold migrate that VS. With this box checked, if cold migration fails, the VS will be stopped so the reboot may proceed. If you don't check this box, OnApp will attempt to hot and then cold migrate all VSs hosted by the compute resource being rebooted – but will stop the migration process if any VS cannot be migrated.
    • Are you sure you want to reboot this compute resource? A simple confirmation to confirm that you want the compute resource to reboot.

      Warning

      Before the reboot, please ensure that all vdisks are fully synced and redundant. If some of them are not fully synced, the virtual server, that is owner of a degraded (or non-redundant) vdisk, can loose access to the vdisk. It can be manifested as IO errors during writes or reads to/from the vdisk inside the virtual server.

  9. When you're certain you want to proceed with the reboot, click the Reboot button.
  10. Once the compute resource is booted, repair the disk that were degraded during the reboot.

    1. Make sure no disks are out of sync. To do so, check the Diagnostics page in CP at Dashbord > Integrated Storage > Compute zonelabel > Diagnostics. Alternatively, log into a compute resource and run the command below: 

      Code Block
      HV_host#> getdegradedvdisks
    2. Repair all the degraded disks before proceeding to the upgrade process. To do so, log in to your CP and go to Integrated Storage > Compute zonelabel > Diagnostics page. Alternatively, run one of the following commands:

      Code Block
      HV_host#> onappstore repair uuid=
      Code Block
      HV_host#> parallelrepairvdisks
  11. Repeat these steps for all CloudBoot compute resources in your cloud.

Configuration for Accelerator

Perform the following steps for your Cloudboot compute resources if you plan to deploy Accelerator.

  1. Run the following command on the CP server:

    • For all compute resources:

      Code Block
      rake hypervisor:messaging:configure
    • For certain compute resources only:

      Code Block
      rake hypervisor:messaging:configure['11.0.50.111 11.0.50.112']

      To perform the configuration for a number of compute resources, separate their IPs with a space.

  2. The command above should  be run after every reboot. However, you can avoid the necessity to run the command repeatedly after every reboot by coping the following information (using your parameters) from /home/mq/onapp/messaging/credentials.yml to the custom config:

    Code Block
     echo "---
    host: 10.0.50.4  # RABBITMQ SERVER IP/FQDN
    port: 5672      # RABBITMQ CONNECTION PORT(default: 5672)
    vhost: '/'
    user: accelerator-example # RABBITMQ USER NAME
    password: 'e{y31?s8l' #RABBITMQ ACCESS PASSWORD
    queue: 'hv-10.0.50.102' # hv-[IP Address of Compute Resource]
    exchange:
      name: 'acceleration'
      type: 'direct'
      durable: True" > /home/mq/onapp/messaging/credentials.yml
    chown -R mq:mq /home/mq
    service onapp-messaging restart
    Info

    For information on manual configuration for Accelerator, refer to RabbitMQ Configuration for Accelerator.