Audit inventory

[acozine]

Now that we have consolidated automation in this repo, audit the inventory.

• [ ] run a report in vSphere to confirm that all existing VMs appear on the list (eventually, can we automate this part and avoid having to maintain a static inventory of our vSphere VMs?)
• [ ] confirm the status of the legacy boxes and add comments to the inventory list for Future Us (for example, what does libserv53 do?)
• [ ] test the new inventory with a simple playbook that gathers facts and returns a list of VMs by OS flavor & version We should be able to answer questions like:
• [ ] is everything listed in inventory active/being used?
• [ ] is everything we want to automate listed in inventory?
• [ ] do the groups and groups-of-groups accurately reflect our use cases?

[acozine]

For instructions on exporting a list of all VMs, see https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-C0E8DD52-677E-464F-A3EA-044EE20B7B92.html and/or https://masteringvmware.com/export-reports-from-vsphere-web-client/.

[acozine]

VMs to decommission:

• [x] oawaiver-prod1
• [x] ojs-prod2
• [x] prds-prod1
• [x] prds-staging1
• [x] pulfa3-staging1
• [x] pulfalight-prod1
• [x] pulfalight-prod2
• [x] pulfalight-worker1
• [x] repec-prod1

[acozine]

We added the QA NFS servers to the QA group in #4583 but the Staging and Prod groups for NFS are not in the larger production and staging groups (so they are not getting touched by Patch Tuesday). Is that on purpose @kayiwa?

[acozine]

Decommissioned VMs to remove from inventory:

• [ ] lib-monitor1
• [ ] libserv31

We could also look at the list of failed hosts in Ansible Tower to see if any of those are obsolete.

[VickieKarasic]

List of failed hosts on weekly staging os_updates as of 10/28/24 (checkmarks means we've figured out why they failed and either fixed the issues or we know they will continue to fail because of other issues (e.g. outdated os, cloud machines, network disconnected, etc.):

• [x] abid-staging2.lib.princeton.edu
• [x] bastion-staging.pulcloud.io
• [x] cdh-dev-sandbox1.princeton.edu
• [x] cicognara-staging1.princeton.edu
• [x] fpul-staging1.lib.princeton.edu
• [x] fpul-staging2.lib.princeton.edu
• [x] gcp_dataspace_staging1
• [x] gcp_oar_staging1
• [x] iiif-staging1.princeton.edu
• [x] lib-fs-staging.princeton.edu
• [x] lib-postgres-staging1.princeton.edu
• [x] lib-redis-staging1.princeton.edu
• [x] lib-sc-staging1.princeton.edu
• [x] lib-sc-staging2.princeton.edu
• [x] lib-sftp-staging1.princeton.edu
• [x] lib-solr-staging1.princeton.edu
• [x] lib-solr-staging2.princeton.edu
• [x] lib-solr-staging3.princeton.edu
• [x] lib-zk-staging1d.princeton.edu
• [x] lib-zk-staging2d.princeton.edu
• [x] lib-zk-staging3d.princeton.edu
• [x] library-staging1.lib.princeton.edu
• [x] library-staging2.lib.princeton.edu
• [x] nomad-client-staging1.lib.princeton.edu
• [x] pdc-describe-staging1.princeton.edu
• [x] pdc-describe-staging2.princeton.edu
• [x] prds-dataspace-staging-endpoint1
• [x] sandbox-bd4538.lib.princeton.edu
• [x] sandbox-vkarasic.lib.princeton.edu