From 8b12f9dcda93a6d61b4951ce9866858a835a63b4 Mon Sep 17 00:00:00 2001 From: David Rojas Date: Fri, 25 Sep 2020 06:53:38 -0700 Subject: [PATCH] adding new chocolatey conig demo --- docs/infrastructure/chocolatey_config.md | 90 +++++++++++++++++++ .../infrastructure/chocolatey_config.yml | 18 ++++ .../infrastructure/chocolatey_app_install.yml | 2 +- .../main/infrastructure/chocolatey_config.yml | 52 +++++++++++ 4 files changed, 161 insertions(+), 1 deletion(-) create mode 100644 docs/infrastructure/chocolatey_config.md create mode 100644 playbooks/infrastructure/chocolatey_config.yml create mode 100644 roles/install_demo/vars/main/infrastructure/chocolatey_config.yml diff --git a/docs/infrastructure/chocolatey_config.md b/docs/infrastructure/chocolatey_config.md new file mode 100644 index 0000000..4159149 --- /dev/null +++ b/docs/infrastructure/chocolatey_config.md @@ -0,0 +1,90 @@ +# Demo: Chocolatey Config + +[Click here to return to master demo list](../../README.md#demo-repository) + +## Table of Contents + +* [Objective](#objective) +* [What business problem is solved?](#what-business-problem-is-solved) +* [Features show cased](#features-show-cased) +* [Video](#video) +* [Guide](#guide) + +# Objective + +Demostrate how Anisble can be used not only to enable or disable Chocolatey configuration parameters but to set specifc values for those parameters + +# What business problem is solved? + +- **Operational Efficiency**: + Ansible provides the ability to save dozen to hundreds of hours of reconfiguration work by systems admins through the configuration automation +- **Increase Compliance**: + Ansible provides the means to get and stay in compliance throughout all your systems + + + + +# Features show cased + +- Configuration as code +- Self Service IT - Surveys + +For description of these and other features of the Red Hat Ansible Automation Platform please refer to the [features README](../features.md) + +# Video + +Coming Soon + +# Guide + +1. Login to Ansible Platform UX + +2. Navigate to **Templates** + + ![job templates](../../images/templates.png) + +3. Click the rocket next to **INFRASTRUCTURE / Chocolatey Features Config** to launch the Job + + ![rocket launch](../../images/rocket.png) + +4. The survey will prompt you to install an application. + + ![survey choice](../../images/choco_features_survey.jpeg) + +5. Choose an application and press **NEXT** + + ![survey preview](../../images/choco_features_survey_preview.jpeg) + + Explain to audience what is happening here depending on audience persona + + **Persona A**: Technical audience that has written Ansible Playbooks before: + Surveys create variables that the Job can use within Ansible Playbooks. This gives you the ability to create one playbook that can be used to enable or disable any feature instead of having to create or maintain many job templates. The survey also gives you the ability to select if the feature will be enabled or disabled. Again saving you time and effort to write seperate playbooks for each use case. In the screenshot you will see the variables are named **feature** and **state** with values of **virusCheck** and **enabled** + + **Persona B**: Decision maker audience, IT manager or above: + reiterate business values above. This allows a systems admin to automate the reconfiguration of Chocolatey in a low risk repeatable manner. This will free up IT staff for larger more mission critical projects all while reducing risk to your production operations. In the event that your IT process does not allow the Red Hat Ansible Automation Platform to be the front end, it has a rich and powerful API that can work with existing workflows such as ServiceNow. + +6. Execute the job by pressing the green **LAUNCH** button + +7. Explain what is happening: + + - Job has started executed in the background. The user can navigate off this page and the job will continue to execute. + - On the left is the **Job Details Pane** labeled simply with **DETAILS**. This information is logged and tells you who, what, when and how. + - **who** - who launched the job, in this example is the admin user + - **what** - the project and Ansible Playbook used, and which credential to login to the infrastructure + - **when** - time stamps for start, end and duration of the job run. + - **how** - the job status (pass, fail), enviornment and execution node + - The larger window on the right is the **Standard Out Pane**. This provides the same console output the user would be used to on the command-line for troubleshooting purposes. Some important takeways to showcase are: + - aggregate info is at the top including the amount of Plays, tasks, hosts and time duration. + - this pane can be expanded to take up entire browser window + - Ansible Playbook can be downloaded for troubleshooting purposes + - **click on task output** to show them task-by-task JSON output that can be used for troubleshooting or just getting additional information + ![task breakdown](../../images/choco_features_task_output.jpeg) + +8. Circle back and summarize + + You need to circle back what has been showcased to the [business reasons listed above](#what-business-problem-is-solved). You are welcome to verify on the Windows hosts that the application(s) was actually installed but unless you have a very technical audience you are going to start losing folks. The real business solution here is automating away the mundane and repetative. + + + +--- +You have finished this demo. [Click here to return to master demo list](../../README.md#demo-repository) diff --git a/playbooks/infrastructure/chocolatey_config.yml b/playbooks/infrastructure/chocolatey_config.yml new file mode 100644 index 0000000..6503c8f --- /dev/null +++ b/playbooks/infrastructure/chocolatey_config.yml @@ -0,0 +1,18 @@ +--- +- name: configuring Chocolatey + hosts: windows + + vars: + config_item: cacheLocation + state: present + value: C:\chocolatey_temp2 + + collections: + - chocolatey.chocolatey + tasks: + + - name: set configuration parameter + win_chocolatey_config: + name: "{{ config_item }}" + state: "{{ state }}" + value: "{{ value }}" \ No newline at end of file diff --git a/roles/install_demo/vars/main/infrastructure/chocolatey_app_install.yml b/roles/install_demo/vars/main/infrastructure/chocolatey_app_install.yml index 5e0d359..c546d23 100644 --- a/roles/install_demo/vars/main/infrastructure/chocolatey_app_install.yml +++ b/roles/install_demo/vars/main/infrastructure/chocolatey_app_install.yml @@ -1,5 +1,5 @@ --- -chocolatey_app_install: +chocolatey_config: author: "David Rojas" readme: "https://github.com/ansible/product-demos/blob/master/docs/infrastructure/chocolatey_app_install.md" category: infrastructure diff --git a/roles/install_demo/vars/main/infrastructure/chocolatey_config.yml b/roles/install_demo/vars/main/infrastructure/chocolatey_config.yml new file mode 100644 index 0000000..8a86411 --- /dev/null +++ b/roles/install_demo/vars/main/infrastructure/chocolatey_config.yml @@ -0,0 +1,52 @@ +--- +chocolatey_config: + author: "David Rojas" + readme: "https://github.com/ansible/product-demos/blob/master/docs/infrastructure/chocolatey_config.md" + category: infrastructure + name: "INFRASTRUCTURE / Chocolatey Config" + description: "Configure Chocolatey parameters that require not just enabling but adding values" + job_type: "run" + inventory: "Workshop Inventory" + playbook: "playbooks/infrastructure/chocolatey_config.yml" + credential: "Workshop Credential" + survey_enabled: true + survey_spec: + name: Chocolatey Config + description: Select a chocolatey parameter and config the value for it + spec: + - type: multiplechoice + question_name: Select the parameter you would like to add change or remove + question_description: Select one from drop-down + variable: config_item + required: true + default: + choices: + - virusCheckMinimumPositives + - commandExecutionTimeoutSeconds + - cacheLocation + - type: multiplechoice + question_name: Do you want to enable or disable this parameter? + question_description: Select Present or Absent + variable: state + required: true + default: present + choices: + - present + - absent + - type: text + question_name: Enter the value for the parameter + question_description: This is free form as each parameter has different values + variable: value + required: true + default: + + #video: "https://www.youtube.com/watch?v=pU8ZgSBuEJw&list=PLdu06OJoEf2bp-PNtxPP_2n7Avkax8TED" + project: + name: "Ansible official demo project" + description: "prescriptive demos from Red Hat Management Business Unit" + organization: "Default" + scm_type: git + scm_url: "https://github.com/davidrojas25/product-demos" + workshop_type: + - windows + - demo