A job template is a definition and set of parameters for running an Ansible job. Job templates are useful to execute the same job many times.
Before you can create a job template with a new playbook, you must first sync your Project so that Controller knows about it. To do this, visit Controller, click Projects and then click the sync icon next to your project. Once this is complete, you can create the job template.
Click the icon, and select Job Template
Complete the form using the following values
|Name||IIS Basic Job Template|
|Description||Template for the iis-basic playbook|
|PROJECT||Ansible Workshop Project|
|Execution Environment||windows workshop execution environment|
|CREDENTIAL||Name: Windows Credential|
|OPTIONS||[*] ENABLE FACT STORAGE|
Click SAVE . On the resulting page, select the Survey tab and press the Add button
Complete the survey form with following values
|PROMPT||Please enter a test message for your new website|
|DESCRIPTION||Website test message prompt|
|ANSWER VARIABLE NAME||
|MINIMUM/MAXIMUM LENGTH||Use the defaults|
|DEFAULT ANSWER||Be creative, keep it clean, we’re all professionals here|
After configuring your survey, click Save. On the resulting page, turn on the survey you just created.
Now that you’ve successfully created your Job Template, you are ready to launch it. Once you do, you will be redirected to a job screen which is refreshing in real time showing you the status of the job.
Click the rocketship icon for the IIS Basic Job Template
When prompted, enter your desired test message
Select NEXT and preview the inputs.
Sit back, watch the magic happen
Once again you should be presented with a Job log page. Selecting the Details tab should show you the variable you passed into the playbook among other details.
Next you will be able to see details on the play and each task in the playbook.
When the job has successfully completed, you should see a URL to your website printed at the bottom of the job output.
If all went well, you should see something like this, but with your own custom message of course.
Now that you have IIS Installed, create a new playbook called remove_iis.yml to stop and remove IIS.
Hint: First stop the
W3Svc service using the
then delete the
Web-Server service using the
Optionally, use the
win_file module to delete the index page.
At this point in the workshop, you’ve experienced the core functionality of Automation Controller. But wait… there’s more! You’ve just begun to explore the possibilities of Automation Controller. The next few lessons will help you move beyond a basic playbook.