Skip to content

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.
  • Labs icon Lab
  • A Cloud Guru
Google Cloud Platform icon

Ansible Cron

Scheduling jobs with Ansible by using the Cron module is one of the key skills for success with using Ansible, and now it's actually an objective of the *Red Hat Certified Ansible Specialist* exam. In this hands-on lab we will use a playbook with the Cron module, and make schedule a task at a specified time. Then we will check when it was created properly, with `crontab` command. Note: Ansible has been setup and configured for use on the Control server and two nodes. This will save time when doing the hands-on lab. *This course is not approved or sponsored by Red Hat.*

Google Cloud Platform icon

Path Info

Clock icon Intermediate
Clock icon 30m
Clock icon Sep 13, 2019

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.

Table of Contents

  1. Challenge

    Sign onto the Ansible Control Node Server as cloud_user and Change to the ansible User. Test to Ensure Ansible Has Been Set up for You

    Sign into the server called Ansible Control Node using the cloud_user and change to the ansible user via the su - ansible command.

    Test that Ansible is working via an ad-hoc command.

    A possible command to use is the following:

    ansible all -m ping

    Note: It may take several minutes after the start of the lab, for the test to work as expected.

  2. Challenge

    Create a Playbook Called cron-tasks.yml That Performs a Task ('df -h >> /tmp/diskspace') on the Nodes at 5:00AM and 5:00PM.

    Using the cron module, create a playbook that adds a cron job to the nodes. The job should run at 5AM and 5PM. The task to run is df -h >> /tmp/diskspace.

  3. Challenge

    Run the Playbook and Test Whether the Cron Job Exists on the Nodes

    Run the playbook and then log into the nodes and check that the cron job exists.

    It should look similar to this:

    0 5,17 * * * df -h >> /tmp/diskspace
  4. Challenge

    Create a Playbook to Remove the Cron Job. It Should Be Called delete-crontask.yml and Should Only Delete That Cron Job

    Create a new playbook. This new playbook should delete the cron job you just created, but leave any other cron jobs there.

  5. Challenge

    Run the Playbook, Then Confirm That the Job Added Earlier Has Been Deleted

    Run the playbook and confirm that the original cron job has been deleted.

The Cloud Content team comprises subject matter experts hyper focused on services offered by the leading cloud vendors (AWS, GCP, and Azure), as well as cloud-related technologies such as Linux and DevOps. The team is thrilled to share their knowledge to help you build modern tech solutions from the ground up, secure and optimize your environments, and so much more!

What's a lab?

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Provided environment for hands-on practice

We will provide the credentials and environment necessary for you to practice right within your browser.

Guided walkthrough

Follow along with the author’s guided walkthrough and build something new in your provided environment!

Did you know?

On average, you retain 75% more of your learning if you get time for practice.

Start learning by doing today

View Plans