{"id":516948,"date":"2018-11-21T10:11:38","date_gmt":"2018-11-21T09:11:38","guid":{"rendered":"https:\/\/www.devoteam.com\/expert-view\/using-ansible-tower-to-deploy-openshift-on-azure-episode-4\/"},"modified":"2018-11-21T10:11:38","modified_gmt":"2018-11-21T09:11:38","slug":"using-ansible-tower-to-deploy-openshift-on-azure-episode-4","status":"publish","type":"expert-view","link":"https:\/\/devoteam.info\/lu\/expert-view\/using-ansible-tower-to-deploy-openshift-on-azure-episode-4\/","title":{"rendered":"Using Ansible Tower to deploy OpenShift on Azure: episode 4"},"content":{"rendered":"

Add more job templates to configure hosts & install OpenShift OKD<\/span><\/h2>\n

In the fourth episode of our blog series<\/a>, we are going to add two more job templates to our Ansible Tower.<\/span><\/i><\/p>\n

The first job template will use playbook-2.yml<\/code>, which executes the following roles:<\/span><\/p>\n

    \n
  1. osPrerequisites: installs needed packages, configures system file, starts docker<\/span><\/li>\n
  2. osDNS: modifies \/etc\/hosts and adds the correct hostname to your machine<\/span><\/li>\n<\/ol>\n

    Explore the playbook on <\/span>Gitlab<\/span><\/a>.<\/span><\/p>\n

     <\/p>\n

    The second job template will use playbook-3.yml<\/code> and has the following roles:<\/span><\/p>\n

      \n
    1. osStart: starts OpenShift OKD and sets the routing-suffix parameter to {{public ip}}.nip.io<\/code>. We will go deeper into this matter later on in this episode<\/span><\/li>\n
    2. osReStart: checks it will be able to restart via systemd<\/code><\/span><\/li>\n
    3. osConigureUsers: creates the user developer with password developer and gives it clusteradmin<\/code> rights<\/span><\/li>\n
    4. osInstallPHPApplication: creates a new project, installs php 7.1<\/code> together with a php application<\/code> from Devoteam\u2019s GitLab server<\/span><\/li>\n<\/ol>\n

      Explore the playbook on Gitlab<\/span><\/a>.<\/span><\/p>\n

       <\/p>\n

      In Ansible Tower click on RESOURCES\/Template<\/code>.<\/span><\/p>\n

      Click on the <\/span>+ ADD <\/span><\/code>button and choose ‘<\/span>Job Template’.<\/span><\/p>\n

      NAME: OKD Azure Part 2
      \n<\/span>JOB TYPE: Run
      \n<\/span>INVENTORY: OKD
      \n<\/span>PROJECT: Azure Deployment OKD
      \n<\/span>PLAYBOOK: playbook-2.yml
      \n<\/span>CREDENTIAL: Add the machine credential clusteradmin we created in <\/span>      episode 2<\/span><\/a>
      \nVERBOSITY: 1 (Verbose)<\/span><\/p>\n

      Save <\/span><\/code><\/p>\n

       <\/p>\n

      In Ansible Tower click on RESOURCES\/Template<\/code>.<\/span><\/p>\n

      Click on the <\/span>+ ADD<\/span><\/code> button and choose ‘<\/span>Job Template'<\/b><\/code>.<\/span><\/p>\n

      NAME: OKD Azure Part 3
      \n<\/span>JOB TYPE: Run
      \n<\/span>INVENTORY: OKD
      \n<\/span>PROJECT: Azure Deployment OKD
      \n<\/span>PLAYBOOK: playbook-3.yml
      \n<\/span>CREDENTIAL: Add the machine credential clusteradmin we created in       episode 2<\/a>
      \n<\/span>VERBOSITY: 1 (Verbose)<\/span><\/p>\n

      Save <\/span><\/code><\/p>\n

       <\/p>\n

      For now we only created job templates. The real power of Ansible Tower lays in the Workflow Templates. With these templates you can link different job templates together, synchronize projects and inventories on demand.<\/span><\/p>\n

      In Ansible Tower click on RESOURCES\/Template<\/code>.<\/span><\/p>\n

      Click on the <\/span>+ <\/span><\/code>button and choose ‘<\/span>Workflow Template'<\/b><\/code>.<\/span><\/p>\n

      In the Details tab we name the template.<\/span><\/p>\n

      NAME: OKD Azure Workflow<\/span><\/p>\n

      Save <\/span><\/code><\/p>\n

       <\/p>\n

      Because we will start our playbooks from this workflow from now on, we have to create the survey also here. We did the same in episode 3<\/a> for template OKD Azure Part 1.<\/span><\/p>\n

      EDIT SURVEY<\/code><\/p>\n

      PROMPT: Machine prefix
      \n<\/span>DESCRIPTION: This prefix will be used both on the machines deployed on Azure, as well as for the dns creation. It must be unique in the .<\/span>westeurope.cloudapp.azure.com domain
      \n<\/span><\/i>ANSWER VARIABLE NAME: azure_virtualMachineName
      \n<\/span>ANSWER TYPE: Text
      \n<\/span>MINIMUM LENGTH: 5       MAXIMUM LENGTH: 50
      \n<\/span>REQUIRED: Checked<\/span><\/p>\n

      +ADD<\/code>  <\/span><\/p>\n

       <\/p>\n

      The second variable is the openSSH<\/code> public matching the private key we added in episode 2<\/a>. You can get it via: <\/span><\/p>\n

      \"\"<\/p>\n

      PROMPT: ssh public key.  This is the key we created in <\/span>episode 1<\/span><\/a>
      \n<\/span>DESCRIPTION: .
      \n<\/span>ANSWER VARIABLE NAME: ssh_sshPubKey
      \n<\/span>ANSWER TYPE: Text
      \n<\/span>DEFAULT ANSWER: <paste the public key>
      \n<\/span>REQUIRED: Checked<\/span><\/p>\n

      +ADD<\/span>  <\/span><\/code><\/p>\n

       <\/p>\n

      The next variable is the Azure resource group that will be used to create the machines.<\/span><\/p>\n

      PROMPT: Azure resource group
      \n<\/span>DESCRIPTION: The resource group you created on Azure where you want the machines deployed
      \n<\/span>ANSWER VARIABLE NAME: azure_ResourceGroup
      \n<\/span>ANSWER TYPE: Text
      \n<\/span>REQUIRED: Checked<\/span><\/p>\n

      +ADD<\/code>  <\/span><\/p>\n

       <\/p>\n

      Now we only need the user and password for Azure.<\/span><\/p>\n

      PROMPT: Azure AD user
      \n<\/span>DESCRIPTION:
      \n<\/span>ANSWER VARIABLE NAME: AZURE_AD_USER
      \n<\/span>ANSWER TYPE: Text
      \n<\/span>REQUIRED: Checked<\/span><\/p>\n

      +ADD <\/span> <\/span><\/code><\/p>\n

       <\/p>\n

      PROMPT: Azure password
      \n<\/span>DESCRIPTION:
      \n<\/span>ANSWER VARIABLE NAME: AZURE_PASSWORD
      \n<\/span>ANSWER TYPE: Password
      \n<\/span>REQUIRED: Checked<\/span><\/p>\n

      +ADD <\/span> <\/span><\/code><\/p>\n

      Save <\/span><\/code><\/p>\n

      Attention<\/strong>: don’t forget to save or you’ll need to enter the survey again from scratch.<\/span><\/p>\n

       <\/p>\n

      Now you should also be able to click on the<\/span> WORKFLOW VISUALIZER <\/code><\/b>button.<\/span><\/p>\n

      From the start we click on <\/span>+ <\/span><\/code>and we add a project sync block. Select the Azure Deployment ODK project and click on <\/span>Select <\/span><\/code>.  <\/span><\/p>\n

      \"\"<\/p>\n

      Starting from this block we will add a jobs block and select the OKD Azure Part 1 job template. Select and check to run \u2018Always\u2019.<\/span><\/p>\n

      Starting from this job template block, we will add a block Inventory Sync and we select the OKD inventory. Select and check to run \u2018On Success\u2019.<\/span><\/p>\n

      From this block, we will add again a jobs block OKD Azure part 2. Select and check to run \u2018On Success\u2019.<\/span><\/p>\n

      The last block we add, will also be a jobs block OKD Azure part 3. Select and check to run \u2018On Success\u2019.<\/span><\/p>\n

      Now click <\/span>Save<\/code> <\/span>to create this workflow. <\/span>Your workflow should look like this:<\/span><\/p>\n

      \"\"<\/p>\n

      This workflow consists of the following steps:<\/span><\/p>\n

        \n
      1. A project sync to make sure we have the last version from git<\/span><\/li>\n
      2. Running of the first playbook that creates the VM on Azure and creates the inventory hosts for our next playbooks<\/span><\/li>\n
      3. An inventory sync for the next playbooks<\/span><\/li>\n
      4. Running of the playbook, which runs the prerequisites for the OKD installation on the VM<\/span><\/li>\n
      5. Running of the playbook which installs OKD and the demo application<\/span><\/li>\n<\/ol>\n

        Now we will run this workflow template and sit back and watch what happens.<\/p>\n

        RESOURCE\/Template<\/code> and click the \u2018launch\u2019 icon after the OKD Azure Workflow template.<\/span><\/p>\n

        \"\"<\/p>\n

        During runtime, you can follow what Tower is doing at this point. <\/span>If you go to the RESOURCE\/Template<\/code> screen, you see this layout:<\/span><\/p>\n

        \"\"<\/p>\n

        If you click on the first blinking green icon you should be able to see what this first playbook does.<\/span><\/p>\n

        After the three job templates are finished, the application is ready. This can take about 30 minutes.<\/span><\/p>\n

        After running this workflow template you should be able to login to Openshift OKD. <\/span>The url to use is: https:\/\/master0<\/span>yourUniqueString<\/span>.westeurope.cloudapp.azure.com:8443\/console<\/span><\/p>\n

        yourUniqueString<\/span><\/code> is the value you entered in the survey.<\/span><\/p>\n

        You can login with user \u2018developer\u2019 by using \u2018developer\u2019 as password.<\/span><\/p>\n

        This user has cluster admin rights. If you login, you should be able to see the project we made for the php demo project. The \u2018devoteam php countdown project\u2019.<\/span><\/p>\n

        \"\"<\/p>\n

        When you enter this project, you will be able to open the project and see the following screen:<\/span><\/p>\n

        \"\"<\/p>\n

        At the top right you see the link of the php<\/code> application, for this we use the nip.io<\/code> service.<\/span><\/p>\n

        NIP.IO allows you to map any IP Address in the following DNS wildcard entries:<\/span><\/p>\n