# Ansible Role: cnos_conditional_template_sample - Manages switch configuration using templates with respect to conditions specified in the inventory --- This role is an example of using the *cnos_conditional_template.py* Lenovo module in the context of CNOS switch configuration. This module allows you to work with the running configuration of a switch. It provides a way to execute a set of CNOS commands on a switch by evaluating the current running configuration and executing the commands only if the specific settings have not been already configured. The configuration source can be a set of commands or a template written in the Jinja2 templating language. This module functions the same as the *cnos_template.py* module. The only exception is that the following inventory variable can be specified: condition = <flag string> When this inventory variable is specified as the variable of a task, the template is executed for the network element that matches the flag string. Usually, templates are used when commands are the same across a group of network devices. When there is a requirement to skip the execution of the template on one or more devices, it is recommended to use this module. The results of the operation can be viewed in *results* directory. For more details, see [Lenovo modules for Ansible: cnos_conditional_template](http://systemx.lenovofiles.com/help/index.jsp?topic=%2Fcom.lenovo.switchmgt.ansible.doc%2Fcnos_conditional_template.html&cp=0_3_1_0_4_11). ## Requirements --- - Ansible version 2.2 or later ([Ansible installation documentation](http://docs.ansible.com/ansible/intro_installation.html)) - Lenovo switches running CNOS version 10.2.1.0 or later - an SSH connection to the Lenovo switch (SSH must be enabled on the network device) ## Role Variables --- Available variables are listed below, along with description. The following are mandatory inventory variables: Variable | Description --- | --- `ansible_connection` | Has to be `network_cli` `ansible_network_os` | Has to be `cnos` `ansible_ssh_user` | Specifies the username used to log into the switch `ansible_ssh_pass` | Specifies the password used to log into the switch `enablePassword` | Configures the password used to enter Global Configuration command mode on the switch (this is an optional parameter) `hostname` | Searches the hosts file at */etc/ansible/hosts* and identifies the IP address of the switch on which the role is going to be applied `deviceType` | Specifies the type of device from where the configuration will be backed up (**g8272_cnos** - G8272, **g8296_cnos** - G8296, **g8332_cnos** - G8332, **NE10032** - NE10032, **NE1072T** - NE1072T, **NE1032** - NE1032, **NE1032T** - NE1032T, **NE2572** - NE2572, **NE0152T** - NE0152T) `condition` | If `condition=` is specified in the inventory file against any device, the template execution is done for that device in case it matches the flag setting for that task The values of the variables used need to be modified to fit the specific scenario in which you are deploying the solution. To change the values of the variables, you need to visits the *vars* directory of each role and edit the *main.yml* file located there. The values stored in this file will be used by Ansible when the template is executed. The syntax of *main.yml* file for variables is the following: ```