![Frequently used and File Commands
# To check ping status.
$ ansible [host_group_name_in_inventory_file] -i hosts -m
win_ping
# Gathering Hostnames
$ ansible [host_group_name_in_inventory_file] -i hosts -m
setup | grep Host_name
# Start the service
$ ansible [host_group_name_in_inventory_file] -m
win_service –a "name=ser _name“
# check specific file is exist or not
$ ansible [host_group_name] -m win_file –a
“path=c:filename” , “state=touch”
# Create a Directory
$ ansible [host_group] -i hosts -m win_file –a
“path=c:directory name state=directory”
# deleting a directory
$ ansible [host_group] -i hosts -m win_file –a
“path=c:directory name state=absent”
# download a file or image using url
$ ansible [host_group] -m win_get_url -a
"url=https://www.somewebsite.com/ansible.jpg
dest=c:fileansible.jpg"](https://image.slidesharecdn.com/ansibledemoppt-190725070913/85/Managing-windows-Nodes-like-Linux-Nodes-by-Ansible-13-320.jpg)
![Service and Update Commands
# Start the service in all the servers
$ ansible [host_group] -m win_service –a "name=ser _name
state=started“
# Retart the service in the servers
$ ansible [host_group] -m win_service –a "name=ser _name
state=restarted“
# Stop the service in servers
$ ansible [host_group] -m win_service –a "name=ser _name
state=stopped“
# Pause the service in servers
$ ansible [host_group] -m win_service –a "name=ser _name
state=pause“
# Install only security updates as a scheduled task for
Server
win_updates:
category_names: SecurityUpdates
use_scheduled_task: yes
# Install only particular updates based on the KB
numbers
win_updates:
category_name: - SecurityUpdates
whitelist:
- KB*******
- KB*******](https://image.slidesharecdn.com/ansibledemoppt-190725070913/85/Managing-windows-Nodes-like-Linux-Nodes-by-Ansible-14-320.jpg)
Managing windows Nodes like Linux Nodes by Ansible
- 1. Manage Windows like Linux using Ansible
- 2. Road Map 1.What is Ansible 2.Ansible Architecture 3.Installing Ansible 4.Inventory Files and host pattern 5.Configuring Control and Manage node 6.Adhoc- commands 7.Writing and Running Play book 8.Sample Play book 9.What is Chocolatey 10.Why Chocolatey 11.Demo
- 3. What is Ansible Ansible Is An IT Automation Tool. It Can Configure Systems, Deploy Software, And Orchestrate More Advanced IT Tasks Such As Continuous Deployments Or Zero Downtime Rolling Updates
- 4. Ansible Architecture & Installation #Add Ansible repository $ sudo apt-add-repository ppa:ansible/ansible #Run the update command $ sudo apt-get update #Install Ansible package $ sudo apt-get install ansible
- 6. Inventory and Host Pattern The inventory file of ansible lists all the platforms you want to automate across. Ansible at a instance can work on multiple hosts in the infrastructure. The host file can contain hostnames either individually or in groups. Host groups can be created by giving a group name within square brackets. Group members can then be listed under, till there is line break.
- 8. Configuration of Control Node and Managed Node
- 9. Control Node Configuration For Ansible to communicate to a Windows host and use Windows modules, the Control host must meet the following requirements: • A WinRM must be installed and activated . • pywinrm with support for basic, certificate, and NTLM auth, simply activated #To install pywinrm with support for basic, certificate, and NTLM auth, simply $ Pip install pywinrm # for Debian/Ubuntu/etc: $ sudo apt-get install python-dev libkrb5-dev $ pip install pywinrm # for RHEL/CentOS/etc: $ sudo yum install gcc krb5-devel krb5-workstation $ pip install pywinrm
- 10. Managed Node Configuration Ansible to communicate to a Windows host and use Windows modules, the Windows host must meet the following requirements: • Ansible’s supported Windows versions generally match those under current and extended support from Microsoft. Supported desktop OSs include Windows 7, 8.1, and 10, and supported server OSs are Windows Server 2008, 2008 R2, 2012, 2012 R2, 2016, and 2019. • Ansible requires PowerShell 3.0 or newer and at least .NET 4.0 to be installed on the Windows host. • A WinRM listener should be created and activated. More details for this can be found below. # Ensure the Power shell remote login is enabled or not $ Enable-PSRemoting -Force # Get version $ ansible --version # Download the below power shell script. ConfigureRemotingForAnsible.ps1 #Run the power shell script $ ./ConfigureremotingForAnsible.ps1
- 11. WINRM Configuration Windows Event Log Verbose Cert Validity ForceNewSSLCert EnableCredSSP DisableBasicAuth Skip N/w Profile check Windows Configuration
- 12. Ad-hoc Commands
- 13. Frequently used and File Commands # To check ping status. $ ansible [host_group_name_in_inventory_file] -i hosts -m win_ping # Gathering Hostnames $ ansible [host_group_name_in_inventory_file] -i hosts -m setup | grep Host_name # Start the service $ ansible [host_group_name_in_inventory_file] -m win_service –a "name=ser _name“ # check specific file is exist or not $ ansible [host_group_name] -m win_file –a “path=c:filename” , “state=touch” # Create a Directory $ ansible [host_group] -i hosts -m win_file –a “path=c:directory name state=directory” # deleting a directory $ ansible [host_group] -i hosts -m win_file –a “path=c:directory name state=absent” # download a file or image using url $ ansible [host_group] -m win_get_url -a "url=https://www.somewebsite.com/ansible.jpg dest=c:fileansible.jpg"
- 14. Service and Update Commands # Start the service in all the servers $ ansible [host_group] -m win_service –a "name=ser _name state=started“ # Retart the service in the servers $ ansible [host_group] -m win_service –a "name=ser _name state=restarted“ # Stop the service in servers $ ansible [host_group] -m win_service –a "name=ser _name state=stopped“ # Pause the service in servers $ ansible [host_group] -m win_service –a "name=ser _name state=pause“ # Install only security updates as a scheduled task for Server win_updates: category_names: SecurityUpdates use_scheduled_task: yes # Install only particular updates based on the KB numbers win_updates: category_name: - SecurityUpdates whitelist: - KB******* - KB*******
- 15. Writing and Running Playbook # writing a play book $ vim play_book name.yaml (or) $ vim play_book.yml # Run a play book $ ansible-playbook –m Module name –a arguments –i inventory # Run a play book interactively $ ansible –playbook_name –step # Run a play book at a particular task $ ansible-playbook playbook-name.yml --start-at- task=“task_name” --- - name: Getting started First play book hosts: win tasks: - name: Create directory structure win_file: path: C:Tempshellscripts state: directory - name: copy a shell script win_copy: src: /etc/ansible/localuser.ps1 dest: c:Tempshellscripts - name: run the powershell script win_shell: c:Tempshellscriptslocaluser.ps1 >> c:script.txt - name: create a user using ansible module win_user: name: Level3 password: Pass@123 state: present groups: - administrators - users
- 17. What is Chocolatey ? Chocolatey is a package manager for Windows (like apt-get or yum but for Windows). It was designed to be a decentralized framework for quickly installing applications and tools that you need. Package Manager for Windows Behaves much like Yum Uses NuGet packaging framework + PowerShell for automation scripts CLI tool - choco.exe Allows non-centralized/private repositories Secure Flexibility & GUI interface
- 18. Chocolatey integrates with your favorite configuration manager
- 20. DEMO
Editor's Notes
- #5: Let us start with Public/Private Cloud which is the Linux server. It can also act as a repository for all IT installation and configurations. The above architecture has a bunch of host machines to which ansible server connects and pushes the playbooks through SSH. It has ansible automation engine using which users can directly run a playbook which gets deployed on the hosts. There are multiple components in the ansible automation engine. The first is a host inventory. It’s a list of all the IP addresses of all the hosts. Next, there are modules. Ansible comes with hundreds of inbuilt modules and modules are those pieces of code that get executed when you run a playbook. A playbook contains plays, a play contains different tasks, and a task includes modules. When you run a playbook, it’s the modules that get executed on your hosts, and these modules contain action in them. So, when you run a playbook, those action takes place on your host machines. You can make your custom modules also. All you must do is write a few lines of code and make it your module, and you can run it anytime you want. Then the architecture has playbooks. Playbooks here actually define your workflow because whatever tasks that you write in a playbook, it gets executed in the same order that you have written them. For example, if you have written that install a package first and then start, it’ll do the same. Playbooks are very simple to write YAML code. YAML code is a very simple data serialization language; it’s pretty much like English. Next, in the architecture are plugins. Plugins here are special kind of modules. These plugins get executed before a module is getting executed on the nodes. Plugins get executed on the main control machine for logging purposes. You’ve got call-back plugins because this enables you to hook into different ansible events for display and logging purposes. Cache plugins are used to keep a cache of facts to avoid costly fact-gathering operations. Ansible also has action plugins, which are front-end modules, and they can execute tasks on the controller machine before calling the modules themselves. The architecture has connection plugins. It is not always needed to use an SSH for connecting with your host machines; you can also use a connection plug-in. For example, ansible provides you with a docker container connection plugin and using that connection plug-in, you can easily connect to all your Docker containers and start configuring right away.
- #6: Ansible works by connecting to nodes and pushing out small programs called as ansible modules. Ansible then executes these modules over SSH or WinRM by default and then remove them when finished. Ansible management node is the controlling node, which controls the entire execution of the Playbook. It’s the node from which you are running the installation, and the inventory file provides the list of the host where the modules need to be run. The management node makes ssh connection, and then it executes the modules on the host machines and installs the product. It removes the modules once they are installed. That’s how ansible works.