To reboot a Compute resource:
- Go to your Control Panel's Compute resources menu (or click a Compute zone name underneath the main Compute resource menu link).
- Click the label (name) of the Compute resource you want to reboot.
- On the Compute resource details screen that follows, click the Tools button, then click Reboot Compute resource.
- A new screen will open asking for confirmation (via three checkboxes) before reboot:
Start running virtual servers after reboot? If this option enabled the system will initiate the failover process.
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.
When you're certain you want to proceed with the reboot, click the Reboot button.
To fix your custom config settings, use one of the following options provided in the examples below (you will have to specify your own device names):
- If you have a separate partition for backups and templates (/dev/sda1 and /dev/sda2)
mkdir -p /onapp/backups
mkdir -p /onapp/template
s mount /dev/sda1 /onapp/backups
mount /dev/sda2 /onapp/templates
If you current array is detected as /dev/sda1 and currently everything is located in /onapp within templates and backup directories within:
mkdir -p /onapp
mount /dev/sda1 /onapp