Skip to main content

Scheduling & Off-Hours

Scheduling and off‑hours optimization reduce cost by stopping or scaling down non‑production and batch resources when they are not in use. Cloudaware combines CMDB context, tagging, and automation to help you identify schedulable resources and manage their lifecycle safely.

Use this guide to decide which workloads are safe to schedule, define the metadata needed to control scheduling, and choose an implementation approach that avoids disrupting critical services.

What to Schedule​

Typical candidates include:

  • Development, test, QA, and sandbox environments.
  • Training, demo, or lab environments.
  • Batch processing jobs that run on predictable schedules.
  • Non‑critical shared services with known maintenance windows.

Avoid scheduling resources that support customer‑facing or mission‑critical workloads unless you have strong safeguards and SLAs in place.

Inputs and Tagging​

Use tags and CMDB attributes to mark resources for scheduling, such as:

  • Environment=dev|test|qa|lab
  • Schedule=office-hours|nightly|weekends-only
  • Owner or Team for escalation and coordination.

Consistent tagging makes it easier to build lists of schedulable resources and avoid accidental stops.

See also: Tagging Strategy and Tag Analyzer

Scheduling Patterns​

Common patterns include:

  • Office‑hours schedules — run during business hours on weekdays, stop nights and weekends.
  • Nightly batch — start for a processing window, then stop automatically.
  • Weekend or maintenance windows — scale down over weekends or planned maintenance periods.

Be explicit about time zones and holiday behavior when defining schedules.

Implementation Approaches​

In practice, you can:

  • Use Cloudaware automation or orchestration tools to:
    • Discover schedulable instances and services from CMDB and tags.
    • Apply stop/start or scale‑down actions on a schedule.
  • Integrate with existing cloud‑native schedulers or third‑party tools, using Cloudaware for inventory, tagging, and reporting.

Whichever mechanism you choose, track both realized savings and any incidents related to scheduling to refine your approach.