{"id":329310,"date":"2023-03-13T07:00:00","date_gmt":"2023-03-13T07:00:00","guid":{"rendered":"http:\/\/itteacheritfreelance.hk\/wordpress\/?guid=1aabd16a0b424aaca35167a09e7a4e9e"},"modified":"2023-03-13T07:00:00","modified_gmt":"2023-03-13T07:00:00","slug":"how-to-use-automation-controller-to-install-ms-sql","status":"publish","type":"post","link":"https:\/\/itteacheritfreelance.hk\/wordpress\/index.php\/2023\/03\/13\/how-to-use-automation-controller-to-install-ms-sql\/","title":{"rendered":"How to use automation controller\u00a0to install MS SQL"},"content":{"rendered":"

<\/p>\n

How to use automation controller\u00a0to install MS SQL<\/span><\/p>\n

The purpose of this article is to demonstrate how to create an execution environment with custom dependencies and how to execute Ansible playbooks using the automation controller’s GUI, a component of Red Hat Ansible Automation Platform<\/a>. For this article, we will use Ansible Roles to install Microsoft SQL on Red Hat Enterprise Linux 8<\/a>.<\/p>\n

Make sure you have the Ansible Automation Platform<\/a> installed on your machine before you begin. For more information about Ansible Automation Platform installation, please refer to our previous article, How to install Red Hat Ansible Automation Platform on RHEL 9<\/a>. Follow these five steps to complete this demonstration.<\/p>\n

Step 1. Setting up the automation\u00a0execution environment<\/h2>\n

Automation execution environments provide a defined, consistent, and portable environment for executing automation jobs. Unlike legacy virtual environments, automation execution environments are Linux<\/a> container<\/a> images that make it possible to incorporate system-level dependencies and collection-based content. Each automation execution environment allows you to have a customized image to run jobs, and each of them contains only what you need when running the job.<\/p>\n

There are dependencies for the automation execution environment, such as Python<\/a> 3 and Podman. Make sure these tools are installed. We have provided instructions for installing and using Podman in this video<\/a>.<\/p>\n

Before you can complete any of the following tasks, you must create a registry service account<\/a>. To log in, open up your terminal and type the following commands:<\/p>\n

\npodman login registry.redhat.io\nUsername: {REGISTRY-SERVICE-ACCOUNT-USERNAME}\nPassword: {REGISTRY-SERVICE-ACCOUNT-PASSWORD}\nLogin Succeeded!<\/code><\/pre>\n
Once we are successfully logged in, we need to create a container image by using a Containerfile<\/strong> containing the following context:<\/p>\n
\n\u200b\u200b\u200b\u200b\u200b\u200b\u200bFROM registry.redhat.io\/ansible-automation-platform-22\/ee-29-rhel8:latest\n\nRUN ansible-galaxy collection install microsoft.sql<\/code><\/pre>\n
To build an image using Podman, enter the following:<\/p>\n
\n\u200b\u200b\u200b\u200b\u200b\u200b\u200bpodman build -t .<\/code><\/pre>\n
The image should be pushed into the container image registry. Log in to the private container image registry using the command ‘podman login’ before pushing.<\/p>\n
\npodman push <\/code><\/pre>\n
Add the image name in the automation execution environment, as shown in Figure 1.<\/p>\n
\n
\n
\n
\n  \"The<\/a>\n<\/div>\n
\n
Figure 1: The Execution Environment page.<\/div>\n<\/div>\n<\/article>\n<\/div>
<\/figcaption><\/figure>\n
\u00a0<\/p>\n
Step\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u00a02. Set up the inventory<\/h2>\n
An inventory is a collection of hosts against which jobs may be launched. To create inventory in Ansible Automation Platform, follow these steps and refer to Figure 2:<\/p>\n
    \n
  1. Select the inventory from the left menu.<\/li>\n
  2. Click on add<\/strong>.<\/li>\n
  3. Select add inventory<\/strong>.<\/li>\n
  4. Give a name to the inventory and\u00a0save it.<\/li>\n
  5. Select the hosts from inventories and click\u00a0add hosts<\/strong>.<\/li>\n
  6. Give the targeted server IP or name and save it.<\/li>\n<\/ol>\n
    \n
    \n
    \n
    \n  \"The<\/a>\n<\/div>\n
    \n
    Figure 2: The Inventory page.<\/div>\n<\/div>\n<\/article>\n<\/div>
    <\/figcaption><\/figure>\n
    \u00a0<\/p>\n
    Step 3. Set up the credentials<\/h2>\n
    To connect with the target server, we need credentials such as username, password, or ssh key. By using credentials, we can pass the required credentials during the playbook execution.<\/p>\n
    Follow these steps and refer to Figure 3:<\/p>\n
      \n
    1. Select the credentials from the left menu.<\/li>\n
    2. Click on new credentials and\u00a0select Machine credentials type.<\/li>\n
    3. Add your username, password, or ssh key in the corresponding\u00a0fields.<\/li>\n<\/ol>\n
      \n
      \n
      \n
      \n  \"The<\/a>\n<\/div>\n
      \n
      Figure 3: The credentials page.<\/div>\n<\/div>\n<\/article>\n<\/div>
      <\/figcaption><\/figure>\n
      \u00a0<\/p>\n
      Step 4. Configuring a project<\/h2>\n
      A project is a logical collection of Ansible Playbooks represented in the controller. You can manage playbooks and playbook directories\u00a0on your controller server either manually or by using a source code management (SCM) system such as Git, Subversion, or Mercurial supported by the controller.<\/p>\n
      Follow these steps to create a project and refer to Figure 4:<\/p>\n
        \n
      1. Create a new project for our git repository from the left menu.<\/li>\n
      2. Click on\u00a0the +<\/strong> icon in the right corner.<\/li>\n
      3. Give the project a name.<\/li>\n
      4. Select your organization (or choose Default<\/strong>).<\/li>\n
      5. Select the SCM TYPE (GIT in our case).<\/li>\n
      6. Add RESOURCE DETAILS\n