Managing Large RH Estate

Any experienced Engineer who can suggest the best way to manage OS Patches and Packages across hundreds of Red Hat virtual and physical servers?
The best way to build an inventory of RH environments along with system parameters and installed packages?
The best way to determine how a particular RH environment was built. E.g. Kickstart, manual?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

A Q ChoudaryJunior Linux EngineerCommented:
we have same kind of environment. we are using kwok information server .It is open source,capable with windows and linux,it have many you should try kwok information server
David FavorLinux/LXD/WordPress/Hosting SavantCommented:
I run a private hosting company for high speed WordPress sites + use this approach.

1) At machine level run a common version of Ubuntu (Zesty right now, as Artful changes to netplan) + LXD.

2) Each LXD container may contain a single site or several/many sites.

3) One machine only runs an LXD DNS instance (container) + many low traffic dev sites, so if this machine goes down, not big problems.

4) I apply all machine updates to dev machine + if all goes well, stream machine updates to other machines. I use custom tools + likely I'll change over to using shortly.

5) Then I go through the same process on a container basis. Update one container running a full LAMP Stack + if all goes well, stream updates to all containers.

6) For machine level, full OS updates, I take a slightly different approach.

I migrate all dev containers to another machine.

Then do a fresh install on my dev machine, then move one live machine's containers to the dev site + to a fresh install on this machine + move all containers back. The repeat this for all machines.

I do fresh installs, rather than updates, as updates can occasionally Brick a machine. Taking this approach means I never have to worry about an OS upgrade taking down production sites.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Have you seen this product?

I dont think is cheap. i remember looking at it awhile ago.  for inventory,  patch management and OS deployments
A Q ChoudaryJunior Linux EngineerCommented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.