Thanks. If this is something the community is interested in, then I don’t mind giving it a shot via FOG post-deploy scripting. Maybe it would be something that could be integrated into the code base eventually.

Yeah I didn’t expect FOG to assume responsibility for that. My plan is to make the image non-resizable in FOG; have FOG deploy the OS; and then automate this process in my ansible awx setup and make it part of the deployment process there since I’m already using ansible to setup the OS anyways.

Thanks for the explanations.

Initially, I was thinking if I deploy to hardware, then I’ll stick with LVM and run a post-deploy script. And if I’m deploying to a vm then make another image that doesn’t use LVM to take advantage of autoresizing.

But I think the best solution for me is to be consistent and use LVM and a post-deploy script for both hardware and vm deployments. FOG would be handling ~95% of my hardware deployments.

You got it:

Here’s from the base image that it was created from:

Let me know if you need anything else or if there’s anything else I can do to help.

Hey everyone!

Using FOG 1.5.9 on CentOS 8.2.2004

I’ve been testing FOG. I created a 20GB CentOS 8 image. I was able to deploy this image just fine to another vm of the same 20GB size.

I ran a test to deploy it on a 40GB disk and it resizes the /boot - /dev/sda1 partition to take up the remaining 20GB of space:

What I really want is for /dev/sda2 to be resized to take the increased space. Is there a way to make that happen in FOG config or should I create a new image that doesn’t use LVM partitions?

Sorry if I missed something in the documentation. Any help is appreciated.