![\"Using](\"https:\/\/devoteam.info\/wp-content\/uploads\/2024\/11\/afbeelding-blog-coding.jpg\")
<\/a><\/figure>\n\n\t\t\n\t\tYou need to set-up a project, which is a logical collection of playbooks. You can create a project directly on the server and put it in a predefined directory, like \/var\/lib\/awx\/projects\/. However, it is better to use a versioning system like Mercurial, Subversion or Git. We prepared some playbooks for you on Gitlab.<\/p>\n
Let\u2019s go! Login to your Ansible Tower:<\/p>\n
1. Create a Project<\/h3>\n
First, create a project on Tower. A Project is a logical collection of Ansible playbooks, represented in Tower. We stored all the playbooks used in this Lab in a GITLab repository. We\u2019ll add this repo to the project.<\/p>\n
In Ansible Tower, click on RESOURCES\/Projects and then the NAME: Azure Deployment OKD You don\u2019t need a SCM CREDENTIAL, because this repo is public.<\/p>\n The dot before AzureDeploymentOKD should be green, meaning the repo synced just fine. You can click on the cloud-icon to force a new synchronisation. If you click on the dot, you will see the details of these actions. In the STANDARD OUT screen, you\u2019ll see that Ansible Tower uses a playbook to sync the repository from GitLab.<\/p>\n The next step is to create a key, so that Tower is able to communicate with the virtual machine we\u2019ll deploy.<\/p>\n Create a ssh key on your local machine.<\/strong> Generate your ssh key-pair. For this exercise, do NOT specify a passphrase and accept all the defaults.<\/p>\n Do NOT enter a passphrase.<\/p>\n To copy the PRIVATE key, you can use cat:<\/p>\n <\/p>\n <\/em><\/p>\n To copy the PUBLIC key, you can use cat:<\/p>\n <\/p>\n Tower utilizes credentials for authentication when launching Jobs against machines, synchronizing with inventory sources, and importing project content from a version control system.<\/p>\n You can grant users and teams the ability to use these credentials, without actually exposing the credential to the user. If you have a team member moving to a different team or leave the organization, you don\u2019t have to re-key all of your systems just because that credential was available in Tower.<\/p>\n Click on RESOURCES\/Credentials.<\/p>\n A <\/p>\n To view the key, copy this to your clipboard:<\/p>\n Click on the NAME: clusteradmin You may leave all other fields empty.<\/p>\n The Key is now encrypted and only Tower can access it.<\/p>\n An inventory is a collection of hosts managed by Tower. Ansible Tower 3.2 introduces the ability to choose an inventory file from source control, rather than creating one from scratch.<\/p>\n This function is the same as custom inventory scripts, except that the contents are obtained from source control instead of editing their contents browser. This means, the files are non-editable. As inventories are updated at the source, the inventories within the projects are also updated accordingly, including the group_vars and host_vars files or the associated directory.<\/p>\n In Tower click on RESOURCES\/Inventories.<\/p>\n You need two inventories. The localhost inventory will be used by our playbook 1. Beside this localhost we need one more inventory, one for playbook 2 and 3. These inventories will be dynamically updated by the first playbook we run, therefore we use a source.<\/p>\n Click on the NAME: localhost In the HOSTS tab click on the HOST NAME: localhost<\/p>\n The localhost inventory is created. Now we need one more inventory.<\/p>\n <\/p>\n Click on the NAME: okd In the SOURCES Tab.<\/p>\n Click on the <\/p>\n We use a SOURCE in order to update the INVENTORY dynamically.<\/p>\n NAME: okd Later, this inventory will be used by playbook 2 and 3.<\/p>\n Please note that this new Inventory isn\u2019t able to synchronise yet, because the chosen files are empty at the moment. They will be updated by our first playbook.<\/p>\n This blog post is part of the series \u201cUsing Ansible Tower to deploy OpenShift on Azure: a step-by-step guide<\/a>\u201d. In the next episode<\/a> we\u2019ll create our first job template in Ansible Tower<\/strong>. This template will use a playbook that installs the virtual machines needed for OKD in Azure.<\/p>\n+ ADD<\/code> – button to create a new project. In the DETAIL tab, fill in the following fields:<\/p>\n
\nORGANIZATION: Default
\nSCM TYPE: Git
\nSCM URL: https:\/\/odyssey.devoteam.be\/publicOKD\/deployOkdAzure.git<\/a>
\n<\/u>SCM UPDATE OPTIONS: check the Clean and only the Clean checkbox.<\/p>\n![\"\"](\"https:\/\/devoteam.info\/wp-content\/uploads\/2024\/11\/blog-e2-1-tt-width-1037-height-206-fill-0-crop-0-bgcolor-eeeeee-except_gif-1.png\")
<\/p>\n2. Create ssh-keys on your computer<\/strong><\/h3>\n
\n
\n\n
\n $<\/code><\/td>\nssh-keygen -f ~\/towerLabKeyPrivate<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n
\n $<\/code><\/td>\ncat ~\/towerLabKeyPrivate<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n
\n\n
\n $<\/code><\/td>\nssh-keygen -y -f ~\/towerLabKeyPrivate > ~\/towerLabKeyPublic<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n
\n $<\/code><\/td>\ncat ~\/towerLabKeyPublic<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n3. Create credentials in Tower<\/strong><\/h3>\n
Machine<\/code> credential is necessary to make it possible for Tower to connect to the VM\u2019s we will deploy. You need the private ssh key for this.<\/p>\n\n\n
\n $<\/code><\/td>\ncat ~\/towerLabKeyPrivate<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n+ ADD<\/code> button.<\/p>\n
\nCREDENTIAL TYPE: Machine
\nTYPE DETAILS:
\nUSERNAME: clusteradmin
\nSSH PRIVATE KEY: < paste id_rsa ><\/p>\nSave<\/code><\/p>\n4. Create inventories<\/h3>\n
+ <\/code> button, and choose Inventory <\/strong>in the DETAILS Tab:<\/p>\n
\nORGANIZATION: Default<\/p>\nSave<\/code><\/p>\n+ <\/code> button.<\/p>\nSave<\/code><\/p>\n+ <\/code> button and choose Inventory <\/strong>in the DETAILS Tab:<\/p>\n
\nORGANIZATION: Default<\/p>\nSave<\/code><\/p>\n+ <\/code> button.<\/p>\n
\nSOURCE: Sourced from a Project
\nPROJECT: Azure Deployment OKD
\nINVENTORY FILE: inventory\/hosts (This is not in the dropdown you need to enter it!)
\nVERBOSITY: 2 (DEBUG)
\nUPDATE OPTIONS:
\nflag: Overwrite, Overwrite variables, Update on Launch<\/p>\nSave<\/code><\/p>\nWhat\u2019s next?<\/strong><\/h2>\n