|Feature||Added full support for Xen 4 CentOS 6 CloudBoot compute resources.|
Ensured that repair process does not leave suspended VDisks in cases of failure.
|Fix||Added log epoch messages to the sys log (this was disabled earlier).|
|Fix||Fixed the issue with adding a node to a datastore.|
|Fix||Minor improvements to readability, when using onappstore diskinfo command with the readable flag.|
|Fix||Fixed the issue with epoch mechanism (it is temporarily disabled).|
|Fix||Fixed the issue related to advance doneblkptr when skipping block in repair.|
Fixed snapshot space counter inconsistency when snapshots were deleted, but counter was not decreased.
Upgrade Instructions (for Clouds running 4.1 OnApp Storage version and lower)
Upgrade Instructions (for Clouds running 4.2.0 OnApp Storage version and up)
To complete an upgrade, follow the steps below:
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:
This command will also show whether compute resources are eligible for live upgrade.
If the command liveUpdate is not available then it may be located in the sbin directory instead (cd /usr/local/sbin).
Run the following command for every compute resource:
Once all the toolstacks are updated run the following command for every compute resource:
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.
Run the following command for each compute resource in turn:
Make sure that the package versions are upgraded by running the following command on each compute resource:
Xen 4 CentOS 6 CloudBoot Compute Resources
- A Control Panel Server with the latest CloudBoot Packages installed is required to create Xen 4 CentOS 6 CloudBoot compute resources.
- Hot-migration for virtual servers from Xen 3 (CentOS 5) and Xen 4 (CentOS 6) and vice versa is not supported. An attempt to hot-migrate VSs will result in an instantly failed transaction to prevent virtual server breakage.
- OnApp does not support running virtual servers on mixed Xen 3 (CentOS 5) and Xen 4 (CentOS 6) CloudBoot compute resource zones simultaneously.
- It is recommended to create a staging environment with several Cloudboot compute resources to check if your hardware is fully compatible with Centos 6.
OnApp delivers the Xen-4.4 based Xen stack, a Linux Kernel based on the 3.18 LTS mainline tree using CentOS 6 for CloudBoot compute resources.
Using the new CloudBoot Compute Resource Creation Wizard it is possible to create Xen 4 CloudBoot compute resource (CentOS 6).
OnApp customers with a full license can contact OnApp support on issues related with CloudBoot compute resources running Centos 6 Xen 4 and Integrated Storage.