Power Schedules

CloudBolt supports setting a schedule to power off servers for periods of the day. This can be useful for servers that do not need to run at night, to save on public cloud costs/resource consumption during those times of the day. You can set a schedule on an individual server or a resource containing servers, allowing you to schedule multiple servers as a group.

End users or admins can set the Power Schedule on an existing server or resource by navigating to its detail page and using the Power Schedule tab as described below. A prediction of the schedule’s impact on costs will be shown on this tab once a schedule is set. Admins can also view the Savings from Power Schedules report to see savings by resource technology over various time periods as well as by group.

There are permissions specific to viewing and managing power schedules. These include server.view_power_schedule, server.manage_power_schedule, resource.view_power_schedule, and resource.manage_power_schedule. To learn more, read the docs on Users and Permissions.

Note that the local time on the CloudBolt server is used to determine when servers should be powered on/off.

If you want to use more complex logic, you can send us a request for enhancement via our support team, and you can also make the change to the recurring job’s plugin code yourself if you do not want to wait.

Power Scheduling Servers

CloudBolt is able to power off & on servers on a daily schedule, with times specified on a per-server basis.

To enable this feature:

  1. Go to Admin > Recurring Jobs and enable the Auto-power control servers recurring job.
  2. Navigate to a server to test with and click on its Power Schedule tab.
  3. Click the Edit button to set a schedule for that server.
  4. Run the Auto-power control servers recurring job to test. If the server is scheduled to be powered on or off at a time that matches the current hour of the current day, the job will power it on or off, respectively.

If you would like to set the schedule on multiple servers at the same time, that can be done from the servers list page by selecting the desired servers and using the calendar button near the top. The servers list page can also, if the column is included, indicate which servers have a Power Schedule and let you view what it is by clicking their calendar icon in that column.

To set the Power Schedule at order time:

  1. Add the Power Schedule parameter to a group or environment so it is included on the order form.
  2. Choose a schedule on the order form with the custom widget, or select from a set of options defined on the group or environment.
  3. During provision, the parameter value will be transformed into a power schedule.
  4. After provision, the Power Schedule parameter will not be seen on the server’s Parameters tab, but the defined schedule will be on the Power Schedule tab.

If you would like to have all servers provisioned within a certain environment or for a certain group get the same power schedule, you can set the value of the Power Schedule parameter on the environment or group, and CloudBolt will set that value on all servers provisioned for that environment or group.

Power Scheduling Resources

Resources enable you to schedule multiple servers to be powered on or off in a specified sequence. This is useful for multi-server applications where shutdown and startup order of servers is significant. The recurring job will power on the resource’s servers in the same sequence as they were originally built, which is derived from the server tiers in the blueprint’s Build tab. The servers are powered off in the reverse sequence.

To enable this feature:

  1. Go to Admin > Recurring Jobs and enable the Auto-power control resources recurring job.
  2. Navigate to a resource to test with and click on its Power Schedule tab.
  3. Click the Edit button to set a schedule for that resource.
  4. Run the Auto-power control resources recurring job to test. If the resource is scheduled to be powered on or off at a time that matches the current hour of the current day, the job will power its servers on or off, respectively.