Create new users and a new team in automation controller and create users and groups in a private automation hub.
Outcomes
Create organizations, users, and teams in automation controller.
Create users and groups in a private automation hub.
As the student user on the workstation machine, use the lab command to prepare your system for this exercise.
This command ensures that automation controller and private automation hub are installed. The command also removes resources created in previous chapters and downloads content collections to the /home/student/content-collections directory.
[student@workstation ~]$ lab start compreview-users
Specifications
Configure organizations, users, and teams on your automation controller at https://controller.lab.example.com based on the following specification. The admin user on your automation controller has redhat as its password.
In addition, configure users and groups on your private automation hub at https://hub.lab.example.com, based on the following specification. An Ansible Content Collection also must be uploaded to your private automation hub and approved for use. The admin user on your private automation hub also has redhat as its password.
On your automation controller, create a new organization based on the following information:
| Field | Value |
|---|---|
BLA
| |
Business Line Applications
|
On your automation controller, create a new team based on the following information:
| Field | Value |
|---|---|
SRE
| |
Site Reliability Engineering
| |
BLA
|
On your automation controller, create three new users based on the following information:
| Field | Value |
|---|---|
Site Reliability Engineer 1
| |
sre1@lab.example.com
| |
sre1
| |
redhat123
| |
redhat123
| |
Normal User
| |
BLA
|
| Field | Value |
|---|---|
Site Reliability Engineer 2
| |
sre2@lab.example.com
| |
sre2
| |
redhat123
| |
redhat123
| |
Normal User
| |
BLA
|
| Field | Value |
|---|---|
System Admin
| |
sysadmin@lab.example.com
| |
sysadmin
| |
redhat123
| |
redhat123
| |
System Administrator
| |
BLA
|
On your automation controller, assign team roles to users on the SRE team based on the following information:
| User | Role |
|---|---|
sre1
|
Admin
|
sre2
|
Member
|
On your private automation hub, add a group named Infrastructure Team, and assign that group permissions that allow it to manage Ansible Content Collections and containers.
On your private automation hub, add two users using the information in the following table.
| Field | Value for the first user | Value for the second user |
|---|---|---|
infra1
|
super
| |
Infrastructure Engineer 1
|
Super User
| |
infra1@lab.example.com
|
super@lab.example.com
| |
redhat123
|
redhat123
| |
redhat123
|
redhat123
| |
Infrastructure Team
| (no group) | |
On your private automation hub, use the infra1 user to create a namespace called community and select the Infrastructure Team group as the namespace owner.
On your private automation hub, as the infra1 user, upload the Ansible Content Collection archive, located at /home/student/content-collections/community/community-mysql-3.1.1.tar.gz on the workstation machine to that namespace, and then approve the community.mysql Ansible Content Collection.
Create a new organization called BLA in automation controller.
Navigate to https://controller.lab.example.com and log in as the admin user with redhat as the password.
Navigate to → and then click .
On the page, fill in the following details:
| Field | Value |
|---|---|
BLA
| |
Business Line Applications
|
Click to create the new organization.
Create a new team called SRE in automation controller.
Navigate to → and then click .
On the page, fill in the following details:
| Field | Value |
|---|---|
SRE
| |
Site Reliability Engineering
| |
Click to create the new team.
Create three new users in automation controller.
Navigate to → and then click .
On the page, fill in the following details:
| Field | Value |
|---|---|
Site Reliability Engineer 1
| |
sre1@lab.example.com
| |
sre1
| |
redhat123
| |
redhat123
| |
Normal User
| |
BLA
|
Click to create the new user.
Repeat the steps to create the sre2 user and fill in the following details:
| Field | Value |
|---|---|
Site Reliability Engineer 2
| |
sre2@lab.example.com
| |
sre2
| |
redhat123
| |
redhat123
| |
Normal User
| |
BLA
|
Repeat the steps to create the sysadmin user and fill in the following details:
| Field | Value |
|---|---|
System Admin
| |
sysadmin@lab.example.com
| |
sysadmin
| |
redhat123
| |
redhat123
| |
System Administrator
| |
BLA
|
Assign the sre1 user the Admin role on the SRE team.
Navigate to → and then click the link for the team.
Click the tab and then click .
Click and then click .
Select and then click .
Select and then click to assign the role.
Assign the sre2 user the Member role on the SRE team.
Navigate to → and then click the link for the team.
Click the tab and then click .
Click and then click .
Select and then click .
Select and then click to assign the role.
Verify the permissions for the SRE team.
Navigate to → and then click the link for the team.
Click the tab.
Notice that the sre1 user has the Admin role and the sre2 user has the Member role on the SRE team. The sysadmin user automatically inherited the System Administrator role on all resources.
Add a new group in your private automation hub called Infrastructure Team and assign permissions to manage Ansible Content Collections and containers.
Navigate to https://hub.lab.example.com and log in as the admin user with redhat as the password.
Navigate to → and then click .
Enter Infrastructure Team in the field and then click .
Click . In the object list, select the following permissions:
In the object list, select the following permissions:
In the object list, select the following permissions:
In the object list, select the following permissions:
In the object list, select the following permissions:
Click to create the new group.
Add two private automation hub users.
Navigate to → and then click .
On the page, fill in the details for infra1 as follows and click to create the new user.
| Field | Value |
|---|---|
infra1
| |
Infrastructure Engineer 1
| |
infra1@lab.example.com
| |
redhat123
| |
redhat123
| |
Infrastructure Team
| |
Repeat the step to create the super user with the following details:
| Field | Value |
|---|---|
super
| |
Super User
| |
super@lab.example.com
| |
redhat123
| |
redhat123
| |
| (no group) | |
Notice that the super user displays the icon next to the name.
Verify the permissions for the Infrastructure Team group. Using the infra1 user, create a namespace and then upload and approve a content collection.
Log out from the private automation hub web UI and log in as infra1 with redhat123 as the password.
Navigate to → and then click .
On the page, fill in the following details and click to create the new namespace.
| Field | Value |
|---|---|
community
| |
Infrastructure Team
|
Assigning a namespace owner allows that group to upload to the namespace. Adding a group as a namespace owner provides the and permissions to the group.
Click .
Click , select the archive located at /home/student/content-collections/community/community-mysql-3.1.1.tar.gz, and then click .
After the upload completes successfully, navigate to → .
Click to approve the community.mysql content collection.
Navigate to → and verify that your private automation hub server displays the automation content collection.