aarch0x40

It sounds like you’re trying to learn but have an “all or nothing” mentality to going about it. Nothing is mastered all of a sudden and expecting mastery out the gate is a recipe for burn out. If you’re goal is absolute perfection then you’ll never even start.

Go through the online docs and training resources first to gain an understanding of how to assemble playbooks without a direct implementation target attached.

Once you have a sense of what Ansible is and what it can do for you, pick something small to do for yourself. For example, create a playbook that sets up nginx for a single purpose.  When there are a 100 different ways to do something, you’ll never do it right. You’ll do it acceptably, then you’ll do it again better and then you’ll do it again more flexibly, etc.  If you know or pick up Python then you’ll start being able to dive into custom modules and plugins.

A toolkit is something you build over time. You build it over time because it’s impossible to know what you’ll need before you start. If you do end up pulling together a toolkit that you think it appropriate and complete before you start working then you’ll have a mess of configurations that are not applicable and mostly inappropriate that you’ll end up debugging forever.

Start small. Start where you are.

Reinstall shouldn’t be required but you’ll likely need to build a new initrd to ensure the boot process has the right drivers.

Starting to remember more about how this is done.  It’s been over 10 years since I had a similar setup working.  Are you VLANing first then slaving to the VLANS?

This post is a bit difficult to follow without being able to examine actual configurations. The bridged VLAN setup is a chain of configs in the RedHat configuration methodology. One of those configs is definitely clobbering the others but it seems you’re close. I’m sure a careful review of your work so far will be enough to find the error.