{"id":1332,"date":"2021-05-26T12:16:56","date_gmt":"2021-05-26T12:16:56","guid":{"rendered":"https:\/\/www.nicktailor.com\/?p=1332"},"modified":"2021-05-26T12:44:23","modified_gmt":"2021-05-26T12:44:23","slug":"how-to-remove-snapshots-with-ansiblevmware","status":"publish","type":"post","link":"https:\/\/nicktailor.com\/tech-blog\/how-to-remove-snapshots-with-ansiblevmware\/","title":{"rendered":"How to remove snapshots with Ansible(VMware)"},"content":{"rendered":"

Okay, so lots of folks ask me about this, and there are a number of ways you can do this.\u00a0<\/strong><\/p>\n

But if you\u2019re using vmware and redhat satellite for central patch management for your redhat environment. <\/strong><\/p>\n

Then depending on how you patch your systems. If you snapshot every group prior to patching. Then this post will be perfect for you.<\/strong><\/p>\n

Process:<\/strong><\/p>\n

\n
\n
1.<\/span>Remove snapshot once patching is all done and servers are confirmed OKAY<\/span><\/strong><\/div>\n<\/div>\n<\/div>\n

Pre-requisites: Assumed.<\/strong><\/p>\n

\n
\n
\u2022<\/span>\u00a0<\/span>Ansible 2.9 <\/span>installed and configured \u2013<\/span><\/strong><\/div>\n<\/div>\n
\n
\u2022<\/span>\u00a0<\/span>Vmware<\/span> Community modules configured<\/span><\/strong><\/div>\n<\/div>\n
\n
\u2022<\/span>\u00a0<\/span>Vmware<\/span> group variables previously defined for <\/span>vmware<\/span> deployments(<\/span>Is helpful)<\/span><\/strong><\/div>\n<\/div>\n
\n
\u2022<\/span>\u00a0<\/span>Vmware<\/span> user\/password configure with being able to <\/span>remove<\/span> snaphots<\/span> in either <\/span>datacenters<\/span> you have<\/span><\/strong><\/div>\n<\/div>\n<\/div>\n

Step by Step:<\/strong><\/p>\n

\n
\n
\n

1.<\/span>Create a roles directory inside \/etc\/ansible\/roles<\/strong><\/p>\n

 <\/p>\n<\/div>\n

\n
\n
a.<\/span>mkdir -p \/etc\/ansible\/roles\/remove-snapshot\/tasks<\/strong><\/em><\/div>\n<\/div>\n
\n
\n

b.<\/span>mkdir -p \/etc\/ansible\/roles\/remove-snapshot\/defaults<\/strong><\/em><\/p>\n

 <\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

\n
\n

2.<\/span>Now you want to create a task for the snapshots.<\/strong><\/p>\n

 <\/p>\n<\/div>\n

\n
\n
c.<\/span>Inside \/etc\/ansible\/roles\/remove-snapshot\/tasks\/<\/strong><\/em><\/div>\n<\/div>\n
\n
\n

d.<\/span>Create a file called main.yml<\/strong><\/em><\/p>\n

 <\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

\n
3.<\/span>Add the following code and save the file<\/strong><\/div>\n<\/div>\n<\/div>\n

– name: Login into vCenter and get cookies<\/h2>\n

\u00a0\u00a0delegate_to: localhost<\/h2>\n

\u00a0\u00a0uri:<\/h2>\n

url: https:\/\/{{ vcenter_host }}\/rest\/com\/vmware\/cis\/session<\/h2>\n

\u00a0\u00a0\u00a0\u00a0force_basic_auth: yes<\/h2>\n

\u00a0\u00a0\u00a0\u00a0validate_certs: no<\/h2>\n

method: POST<\/h2>\n

user: ‘{{ vcenter_username }}’<\/h2>\n

password: ‘{{ vcenter_password }}’<\/h2>\n

register: login<\/h2>\n

 <\/p>\n

Note: Okay so what we want to do is find the virtual machine in <\/em><\/span>vsphere<\/em><\/span> by name and then grab its folder value and pass it as a variable so you don\u2019t need to define it statically in your <\/em><\/span>host_var<\/em><\/span>. The main reason is, say you deployed a <\/em><\/span>vm<\/em><\/span> and months later moved it to another folder, your code will likely have the origin folder which would be <\/em><\/span>annoying, and the ansible documentation doesn\u2019t really cover this approach, you basically figure it out as you do it. So <\/em><\/span>im<\/em><\/span> going to save you all time. Here is how you do it. The below will gather <\/em><\/span>vm_facts<\/em><\/span> based on the <\/em><\/span>inventory_hostname<\/em><\/span><\/strong><\/p>\n

– name: Find Guest’s Folder using name<\/h2>\n

\u00a0\u00a0vmware_guest_find:<\/h2>\n

hostname: “{{ vcenter_host }}”<\/h2>\n

username: “{{ vcenter_username }}”<\/h2>\n

password: “{{ vcenter_password }}”<\/h2>\n

\u00a0\u00a0\u00a0\u00a0\u00a0validate_certs: no<\/h2>\n

name: “{{ inventory_hostname }}”<\/h2>\n

\u00a0\u00a0delegate_to: localhost<\/h2>\n

\u00a0\u00a0ignore_errors: true<\/h2>\n

register: vm_facts<\/h2>\n

<\/h2>\n

Note: It will than gather those facts and find the folder value<\/span>. You then register the facts to a variable \u201c<\/span>vm_facts<\/span>\u201d Now it will spit out what it finds when you do –<\/span>vvvv<\/span> when you do your play. From there you can see the folder setting. You now want to set that that folder setting as its own variable that you can pass to another task as indicated below.<\/span><\/em><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

ok: [<\/span>ansible-server<\/span>] => {<\/span><\/p>\n

“changed”: false,<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0<\/span>“folders”: [<\/span><\/strong><\/p>\n

“\/<\/span>SysUnix<\/span>\/<\/span>Teststuff<\/span>“<\/span><\/strong><\/p>\n

],<\/span><\/strong><\/p>\n

“invocation”: {<\/span><\/p>\n

“<\/span>module_args<\/span>“: {<\/span><\/p>\n

“<\/span>datacenter<\/span>“: null,<\/span><\/p>\n

“hostname”: “<\/span>vmware.nicktailor.com<\/span>“,<\/span><\/p>\n

“name”: ” <\/span>ansible-server<\/span>“,<\/span><\/p>\n

“password”: “VALUE_SPECIFIED_IN_NO_LOG_PARAMETER”,<\/span><\/p>\n

“port”: 443,<\/span><\/p>\n

“<\/span>proxy_host<\/span>“: null,<\/span><\/p>\n

“<\/span>proxy_port<\/span>“: null,<\/span><\/p>\n

“<\/span>use_instance_uuid<\/span>“: false,<\/span><\/p>\n

“username”: “<\/span>svc_ans<\/span>“,<\/span><\/p>\n

“<\/span>uuid<\/span>“: null,<\/span><\/p>\n

“<\/span>validate_certs<\/span>“: false<\/span><\/p>\n

}<\/span><\/p>\n

}<\/span><\/p>\n

}<\/span><\/p>\n

– name: “vm_folder – setting folder value”<\/h2>\n

\u00a0\u00a0set_fact:<\/h2>\n

\u00a0\u00a0\u00a0\u00a0folder : “{{ vm_facts.folders }}”<\/h2>\n

 <\/p>\n

Note:<\/span> So you can see that the facts has a sub fact called \u201cfolders\u201d. We want to pass that by setting that value as its own variable by making it a fact. Ansible way to set variables is setting facts. So we make that value above into a variable \u201c<\/span>vm_<\/span>facts.folders<\/span>\u201d and then pass that into the next task where it asks for folders.<\/span> This will get around the having to provide the exact folder the <\/span>vm_resides<\/span> to create snapshotting for an array of hosts.<\/span> This section is basically identical to create except the \u201cstate\u201d is set to <\/span>absent<\/span><\/strong><\/p>\n

<\/h2>\n

– name: Remove Snapshot<\/h2>\n

\u00a0\u00a0vmware_guest_snapshot:<\/h2>\n

hostname: “{{ vcenter_host }}”<\/h2>\n

username: “{{ vcenter_username }}”<\/h2>\n

password: “{{ vcenter_password }}”<\/h2>\n

\u00a0\u00a0\u00a0\u00a0\u00a0datacenter: “{{ vcenter_dc }}”<\/h2>\n

\u00a0\u00a0\u00a0\u00a0\u00a0validate_certs: no<\/h2>\n

name: “{{ inventory_hostname }}”<\/h2>\n

\u00a0\u00a0\u00a0\u00a0\u00a0state: absent<\/strong><\/h2>\n

\u00a0\u00a0\u00a0\u00a0\u00a0snapshot_name: “Ansible Managed Snapshot”<\/h2>\n

\u00a0\u00a0\u00a0\u00a0\u00a0folder: “‘{{ vm_facts.folders }}'”<\/strong><\/h2>\n

description: “This snapshot is created by Ansible Playbook”<\/h2>\n

\u00a0\u00a0delegate_to: localhost<\/h2>\n

.<\/span><\/span><\/p>\n

\n
\n
4.<\/span>Save the file<\/strong><\/div>\n<\/div>\n<\/div>\n

.<\/span><\/span><\/strong><\/p>\n

\n
\n
5.<\/span>You can either have group_vars<\/span> set up for individual datacenters, but for now just define the variables under \/etc\/ansible\/roles\/remove-snapshot\/defaults<\/strong><\/div>\n

.<\/span><\/span><\/strong><\/p>\n

Note: You will likely have a <\/em><\/span>group_var<\/em><\/span> from you <\/em><\/span>vmdeploy<\/em><\/span> role that you can use for here.<\/em><\/span><\/strong><\/p>\n

.<\/span><\/span><\/strong><\/p>\n

\n
\n
e.<\/span>Create a file called main.yml and the following variables<\/strong><\/div>\n

vcenter_username<\/span>: <\/span>admin<\/span><\/strong><\/p>\n

vcenter_password<\/span>: <\/span>should be vault encrypted variable<\/span><\/strong><\/p>\n

vcenter_host<\/span>: <\/span>vmware.nicktailor.com<\/span><\/strong><\/p>\n

vcenter_dc<\/span>: <\/span>London<\/span><\/strong><\/p>\n

.<\/span><\/span><\/strong><\/p>\n

.<\/span><\/span><\/strong><\/p>\n<\/div>\n

\n
f.<\/span>Save the file<\/span><\/strong><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

.<\/span><\/span><\/strong><\/p>\n

\n
\n
\u2022<\/span>\u00a0<\/span>Note: Ensure your host<\/span> \u201cnicktest1\u201d<\/span> is listed in your inventory host file. <\/span><\/strong>
\n\/etc\/ansible\/inventory\/TEST\/hosts<\/em><\/span><\/strong><\/div>\n<\/div>\n<\/div>\n

Run your playbook: from <\/span>\/etc\/ansible<\/span><\/strong><\/p>\n

.<\/span><\/span><\/strong><\/p>\n

\n
\n
1.<\/span>ansible-playbook –<\/span>i<\/span> inventory\/TEST\/hosts <\/span>just<\/span>remove<\/span>vmsnap.yml<\/span> –ask-vault-pass –limit=’<\/span>nicktest1<\/span>‘ <\/span><\/strong><\/div>\n

.<\/span><\/span><\/strong><\/p>\n

Playbook log:<\/span><\/strong><\/p>\n

.<\/span><\/span><\/strong><\/p>\n

[<\/span>root@ansible-<\/span>server<\/span>]#<\/span> ansible-playbook –<\/span>i<\/span> inventory\/TEST\/hosts <\/span>just<\/span>remove<\/span>vmsnap.yml<\/span> –ask-vault-pass –limit=’<\/span>nicktest1<\/span>‘<\/span><\/strong><\/p>\n

Vault password:<\/span><\/strong><\/p>\n

.<\/span><\/span><\/strong><\/p>\n

PLAY [all] **********************************************************************************************************************************<\/span><\/strong><\/p>\n

.<\/span><\/span><\/strong><\/p>\n

TASK [<\/span>remove<\/span>_<\/span>snapshot<\/span> :<\/span> Login into vCenter and get cookies] *********************************************************************************<\/span><\/strong><\/p>\n

ok: [<\/span>nicktest1<\/span>]<\/span><\/strong><\/p>\n

.<\/span><\/span><\/strong><\/p>\n

TASK [<\/span>remove<\/span>_<\/span>snapshot<\/span> :<\/span> Find Guest’s Folder using name] *************************************************************************************<\/span><\/strong><\/p>\n

ok: [<\/span>nicktest1<\/span>]<\/span><\/strong><\/p>\n

.<\/span><\/span><\/strong><\/p>\n

TASK [<\/span>remove<\/span>_<\/span>snapshot<\/span> :<\/span> vm_folder<\/span> – setting folder value] ***********************************************************************************<\/span><\/strong><\/p>\n

ok: [<\/span>nicktest1<\/span>]<\/span><\/strong><\/p>\n

.<\/span><\/span><\/strong><\/p>\n

TASK [<\/span>remove<\/span>_<\/span>snapshot<\/span> :<\/span> remove<\/span> Snapshot] ****************************************************************************************************<\/span><\/strong><\/p>\n

ok: [<\/span>nicktest1<\/span>]<\/span><\/strong><\/p>\n

.<\/span><\/span><\/strong><\/p>\n

PLAY RECAP **********************************************************************************************************************************<\/span><\/strong><\/p>\n

nicktest1<\/span> : ok=4 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0<\/span><\/strong><\/p>\n

.<\/span><\/span><\/strong><\/p>\n<\/div>\n

\n
2.<\/span>Go log into <\/span>vsphere<\/span> and check to see the <\/span>vm<\/span>\u00a0no longer has the snapshot name listed.<\/span><\/strong><\/div>\n

.<\/span><\/span><\/strong><\/p>\n

Note: This uses the snapshot name to remove as the one you used to create. If another snapshot exists with a different name it will ignore it entirely. If you pass snapshot variable with another name and run the book again, it will remove another snapshot. The same applies to removing snapshots, it will remove based on the name.
\n<\/em><\/span><\/strong><\/p>\n

 <\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Okay, so lots of folks ask me about this, and there are a number of ways you can do this.\u00a0 But if you\u2019re using vmware and redhat satellite for central patch management for your redhat environment. Then depending on how you patch your systems. If you snapshot every group prior to patching. Then this post will be perfect for you.Read More …<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[51,133,129],"tags":[],"class_list":["post-1332","post","type-post","status-publish","format-standard","hentry","category-ansible","category-snapshots","category-vmware"],"_links":{"self":[{"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/posts\/1332","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/comments?post=1332"}],"version-history":[{"count":23,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/posts\/1332\/revisions"}],"predecessor-version":[{"id":1358,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/posts\/1332\/revisions\/1358"}],"wp:attachment":[{"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/media?parent=1332"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/categories?post=1332"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/tags?post=1332"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}