What is a "Fat" Template (for Ansible Tower automation)

I am coming across references to “Fat” template in context of AWX automation. The only definition I’ve seen is “no kickstarting”. What does that mean?

Thank you,

My understanding (and my use) of the term is that a “fat” template is one that is fully configured with operating system, applications, probably patched to a fairly recent version. You can just quickly deploy/clone and you have a fully functional VM up and running.

The opposite to this (“thin”?) is a bare VM template that contains just an empty disk, and this needs some kind of unattended, probably PXE boot initiated installation such as a kickstart to complete the provisioning.

I’m not saying that my understanding is correct however :slight_smile:

There are pros and cons of each method of deployment - cloud instances are generally “fat” by default for speed of deployment, whereas some customers prefer to have a unified deployment process for bare-metal and virtual servers, so a PXE booted Kickstart/AutoYaST etc would be more suitable in this case.

Hope this helps.

Ah that makes sense @pemcg. Thanks!!!