https:\/\/github.com\/Perfect10NickTailor\/ansible-hyperv\u00a0<\/a><\/p>\n.<\/span><\/span><\/p>\n<\/div>\n<\/div>\n<\/div>\n\n
2.<\/span>Now you want edit the <\/span>hosts.client<\/span> file <\/span>name file or create it if it doesn\u2019t exist<\/span> under your \u201c<\/span>ansible\/inventory\/<\/span>dev:staging:prod<\/span>\u201d directory. This is a good way to separate environments with ansible, inside each environment you should have a <\/span>hosts.file<\/span> like indicated below.<\/span><\/div>\nExample file<\/span>: <\/span>hosts.<\/span>dev<\/span>, <\/span>hosts.staging<\/span>, <\/span>hosts.prod<\/span><\/p>\n\n
\n
b.<\/span>Put your server under the appropriate group inside the file and save<\/span><\/div>\n\n
\n
i.<\/span>t<\/em><\/span>estmachine1<\/em><\/span>.nicktailor.<\/em><\/span>com<\/em><\/span> ansible_host<\/em><\/span>=192.168.<\/em><\/span>1.101<\/em><\/span> (the <\/em><\/span>ip<\/em><\/span> is pointed to the hypervisor)<\/em><\/span><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\nNote: If there is no group simply list the server outside group<\/span>ing, the –limit flag will pick it <\/span><\/p>\nup.<\/span><\/p>\n\n
\n
3.<\/span>Now inside this directory you should see <\/span>hosts<\/span><\/strong> & <\/span>host_vars<\/span>, <\/span>group_vars<\/span><\/strong><\/div>\nDescriptions:<\/span><\/strong><\/p>\n\n
\n
c.<\/span>Hosts. <\/span><\/strong>\u2013 is where you will list your servers under specific groups which tell the playbook (what the server is, if it the server should have a specific task run on it, and how to find it)<\/span><\/div>\n<\/div>\n\n
d.<\/span>Host_vars<\/span> <\/strong>\u2013 Inside this directory is where you list the server by name which is you will list under hosts. Inside these files you pass variable parameters to the specific roles when running your playbook. Without these the playbook <\/span>cant<\/span> do the tasks you want it to.<\/span><\/div>\n<\/div>\n\n
e.<\/span>Group_vars<\/span> \u2013 <\/span><\/strong>Are how a way to group variables for sets of servers and this keeps code cleaners and easier to manage<\/span>.<\/span><\/strong><\/div>\n<\/div>\n<\/div>\nOperational Use:<\/span><\/strong><\/p>\n<\/div>\n\n
4.<\/span>Move inside <\/span>host_var<\/span><\/strong><\/div>\n\n
\n
f.<\/span>cd <\/span>host_var<\/span><\/div>\n<\/div>\n\n
g.<\/span>create a file called <\/span>{{ <\/span>servername<\/span> }} and save it for us its<\/span> testmachine1.nicktailor.com<\/span><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n.<\/span><\/span><\/p>\n\n
\n
5.<\/span>Now inside this directory you should see <\/span>hosts<\/span><\/strong> & <\/span>host_vars<\/span>, <\/span>group_vars<\/span><\/strong><\/div>\nDescriptions:<\/span><\/strong><\/p>\n\n
\n
h.<\/span>Hosts. <\/span><\/strong>\u2013 is where you will list your servers under specific groups which tell the playbook (what the server is, if it the server should have a specific task run on it, and how to find it)<\/span><\/div>\n<\/div>\n\n
i.<\/span>Host_vars<\/span> <\/strong>\u2013 Inside this directory is where you list the server by name which is you will list under hosts. Inside these files you pass variable parameters to the specific roles when running your playbook. Without these the playbook <\/span>cant<\/span> do the tasks you want it to.<\/span><\/div>\n<\/div>\n\n
j.<\/span>Group_vars<\/span> \u2013 <\/span><\/strong>Are how a way to group variables for sets of servers and this keeps code cleaners and easier to manage<\/span>.<\/span><\/strong><\/div>\n<\/div>\n<\/div>\nOperational Use:<\/span><\/strong><\/p>\n<\/div>\n\n
6.<\/span>Move inside <\/span>host_var<\/span><\/strong><\/div>\n\n
\n
k.<\/span>cd <\/span>host_var<\/span><\/div>\n<\/div>\n\n
l.<\/span>create a file called <\/span>{{ <\/span>servername<\/span>