What\u2019s needed<\/b><\/h3>\n\n- Ansible – the latest<\/strong><\/a> version<\/li>\n
- Infoblox Ansible Collection\n
\n- For installation\/setup, refer to the GitHub repository<\/a><\/strong> or ansible-galaxy collection<\/strong><\/a>.<\/li>\n<\/ul>\n<\/li>\n
- The collection of Playbooks and Task – github.com\/seefor<\/strong><\/a><\/li>\n<\/ul>\n
DTC Server Task<\/b><\/h3>\n
Here we are going to take a look at \u201ctask_dtc_server.yml.\u201d<\/p>\n
![](\"\/wp-content\/uploads\/infoblox-blog-dtc-server-task.png\")
<\/a><\/p>\nAs you can see above, I made \u201cname,\u201d \u201chost,\u201d and \u201ccomment\u201d variables, and that will read the values from the \u201cdata.yml\u201d file. With Ansible, when you use \u201citem<\/strong><\/a>,\u201d it’s reading a list of variables from a YAML file.<\/p>\nDTC Pool Task and Jinja2 Template<\/b><\/h3>\n
To create the \u201cPool,\u201d we have to leverage Jinja2 Templates<\/strong><\/a>. For example, here is the Jinja2 template \u201ctemp_pool.j2.\u201d<\/p>\n![](\"\/wp-content\/uploads\/infoblox-blog-dtc-pool-task.png\")
<\/a><\/p>\nWe are reading \u201cname\u201d for the pool and \u201cservers\u201d from the data.yml file. When you run the \u201ccreate_everything.yml,\u201d it will create a new playbook called \u201cc_pool.yml\u201d that looks like this.<\/p>\n
![](\"\/wp-content\/uploads\/infoblox-blog-dtc-pool-task-2.png\")
<\/a><\/p>\nThen execute the \u201cc_pool.yml\u201d for \u201cPool\u201d creation; now we have the Servers and Pool time for the LBDN creation.<\/p>\n
DTC LBDN Task<\/b><\/h3>\n
Now let\u2019s wrap this all up with the last Task, \u201ctask_dtc_lbdn.yml.\u201d<\/p>\n
![](\"\/wp-content\/uploads\/infoblox-blog-dtc-lbdn-task.png\")
<\/a><\/p>\nThe above will create the \u201cLBDN,\u201d and again, we are reading the \u201cname,\u201d \u201cpool,\u201d \u201cauth_zones,\u201d and \u201cpatterns\u201d from the data.yml file.<\/p>\n
Data File<\/b><\/h3>\n
Here is the \u201cdata.yml\u201d layout<\/p>\n
![](\"\/wp-content\/uploads\/infoblox-blog-dtc-data-yml-file.png\")
<\/a><\/p>\nAs you can see, this is where we get all the data points that we used above in each \u201ctask\u201d file.
\nLet\u2019s see how we call the \u201cdata.yml\u201d and all the \u201ctasks\u201d from one playbook called \u201ccreate_everything.yml.\u201d<\/p>\n
Let\u2019s Create Everything<\/b><\/h3>\n
We are going to look at the file \u201ccreate_everything.yml.\u201d<\/p>\n
![](\"\/wp-content\/uploads\/infoblox-blog-dtc-create-everything-yml.png\")
<\/a><\/p>\nThe first thing to notice is that we use \u201cvars_files<\/strong><\/a>\u201d to read the \u201cdata.yml\u201d file into the playbook. Next, we have \u201cincluded_tasks<\/strong><\/a>\u201d under \u201ctasks\u201d that will run each instance of the \u201ctask\u201d files for us. For example, in line 11, we will create \u201cc_pool.yml\u201d from a \u201ctemplate<\/strong><\/a>.\u201d The last \u201ctask\u201d I did not cover in this article is \u201crestart_serverices.yml,\u201d which is self-explanatory.<\/p>\nDemo Time<\/b><\/h3>\n
- \n
- For installation\/setup, refer to the GitHub repository<\/a><\/strong> or ansible-galaxy collection<\/strong><\/a>.<\/li>\n<\/ul>\n<\/li>\n
- The collection of Playbooks and Task – github.com\/seefor<\/strong><\/a><\/li>\n<\/ul>\n
DTC Server Task<\/b><\/h3>\n
Here we are going to take a look at \u201ctask_dtc_server.yml.\u201d<\/p>\n
<\/a><\/p>\nAs you can see above, I made \u201cname,\u201d \u201chost,\u201d and \u201ccomment\u201d variables, and that will read the values from the \u201cdata.yml\u201d file. With Ansible, when you use \u201citem<\/strong><\/a>,\u201d it’s reading a list of variables from a YAML file.<\/p>\n
DTC Pool Task and Jinja2 Template<\/b><\/h3>\n
To create the \u201cPool,\u201d we have to leverage Jinja2 Templates<\/strong><\/a>. For example, here is the Jinja2 template \u201ctemp_pool.j2.\u201d<\/p>\n
<\/a><\/p>\nWe are reading \u201cname\u201d for the pool and \u201cservers\u201d from the data.yml file. When you run the \u201ccreate_everything.yml,\u201d it will create a new playbook called \u201cc_pool.yml\u201d that looks like this.<\/p>\n
<\/a><\/p>\nThen execute the \u201cc_pool.yml\u201d for \u201cPool\u201d creation; now we have the Servers and Pool time for the LBDN creation.<\/p>\n
DTC LBDN Task<\/b><\/h3>\n
Now let\u2019s wrap this all up with the last Task, \u201ctask_dtc_lbdn.yml.\u201d<\/p>\n
<\/a><\/p>\nThe above will create the \u201cLBDN,\u201d and again, we are reading the \u201cname,\u201d \u201cpool,\u201d \u201cauth_zones,\u201d and \u201cpatterns\u201d from the data.yml file.<\/p>\n
Data File<\/b><\/h3>\n
Here is the \u201cdata.yml\u201d layout<\/p>\n
<\/a><\/p>\nAs you can see, this is where we get all the data points that we used above in each \u201ctask\u201d file.
\nLet\u2019s see how we call the \u201cdata.yml\u201d and all the \u201ctasks\u201d from one playbook called \u201ccreate_everything.yml.\u201d<\/p>\nLet\u2019s Create Everything<\/b><\/h3>\n
We are going to look at the file \u201ccreate_everything.yml.\u201d<\/p>\n
<\/a><\/p>\nThe first thing to notice is that we use \u201cvars_files<\/strong><\/a>\u201d to read the \u201cdata.yml\u201d file into the playbook. Next, we have \u201cincluded_tasks<\/strong><\/a>\u201d under \u201ctasks\u201d that will run each instance of the \u201ctask\u201d files for us. For example, in line 11, we will create \u201cc_pool.yml\u201d from a \u201ctemplate<\/strong><\/a>.\u201d The last \u201ctask\u201d I did not cover in this article is \u201crestart_serverices.yml,\u201d which is self-explanatory.<\/p>\n
Demo Time<\/b><\/h3>\n
- The collection of Playbooks and Task – github.com\/seefor<\/strong><\/a><\/li>\n<\/ul>\n