1.5-controller-intro

Workshop Exercise 1.5 - Ansible Controller Introduction

Table of Contents

• Objective
• Step 1 - Logging In
• Step 2 - Your Controller Organization
• Step 3 - Credentials
• Step 4 - Project
• Step 5 - Inventories
• Step 6 - Job Templates
• Step 7 - Execution Environments

Objective

In this exercise, we are going to get logged in to Ansible Controller and validate the pre-configured resources.

This exercise will cover

• Logging in to Controller
• Validating pre-configured resources

Step 1 - Logging In

To get started, the URL for our instance of controller can be found on your student page, along with the login credentials to use.

After entering the URL in a browser, you will be greeted with the Ansible Controller login page. To log in, the username will be "student$(your_student_number)", such as student1, and the password is located on your student page.

Step 2 - Your Controller Organization

An organization has been created for you in Ansible Controller, and you have been given administrative permissions over it. This means you can create, edit, modify, and run any of the resources assigned to your organization. It also means that when authenticating to the Ansible Controller API, you'll only see your resources and not those of another students.

Ensure you can view the details and access information of your organization under Organizations > $(your_student_number) Organization > Details/Access tabs:

Step 3 - Credentials

Two credentials have been created for you:

1. Gitea Credentials - to be used to sync projects from our code repository. These match the credentials used to log in to the Gitea web interface, which can be found on your student page. More information on Gitea will be provided in a later exercise.
2. Edge Device SSH Credentials - to be used to access your edge device, regardless of it being virtual or physical.

Step 4 - Project

A project has been created that links to your source control repository (more info on this in the next excercise). It can be viewed under Projects > Device Edge Codebase:

Step 5 - Inventories

Two inventories have been created for you:

1. Local Actions - used when actions need to take place against a host entry of 'localhost'.
2. Edge Systems - where our edge systems will live.

Note

The Edge Systems inventory is empty right now (Total Hosts = 0), because we haven't connected our edge devices yet.

Step 6 - Job Templates

A sample job template has been created that can be used to test connectivity to edge devices. Feel free to copy or modify this job template during the course of the lab.

Step 7 - Execution Environments

An execution environment has been created that has all the necessary dependencies, including collections and python libraries built in. This EE is globally available so all students can leverage it.

Note

The details of this execution environment can be found in the code repository for device edge workshops, and are built using Ansible Builder.

---

Navigation

Previous Excercise | Next Exercise

Click here to return to the Workshop Homepage