Kansas City Finance

Sep 8 2017

Linux Enterprise Distribution and Central Patch Management #linux,enterprise,distribution,central,patch,management, #linux #enterprise #distribution #and #central #patch #management,


#

Welcome to LinuxQuestions.org. a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here .

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux – A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author’s experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

Click Here to receive this Complete Guide absolutely free.

Linux Enterprise Distribution and Central Patch Management

We’re in the process of evaluating candidates for a new Linux OS and patch management system for our corporate environment. Up until now, we were unable to do this due to internal opposition by developers. Our previous solution was Gentoo, which has become nearly impossible to administer. Our environment necessitates high availability and thorough testing. We have several application environments; each consists of at least 1 dev, 1 staging, and 1 production environment. Staged rollouts are the norm. Admin resources are spread thin.

We’ve identified the following requirements:

Centralized Patch Management
-tracking of applied/unapplied patches
-phased rollout to a large # of server groups (business, dev, staging, production, etc.)
-patch success auditing/reporting
-central console for managing patches
-ability to provision a server and bring it to a group’s current patch level

Versioned Releases
-Specific versioned releases
-Long-term support of releases for security fixes (3+ years)

Strong User-Base/Industry Support

We’ve been looking at RHEL 5.1, CentOS 5.1, and Debian 4.0 so far. We think that SLES 10 and Ubuntu Server may also be viable options, but haven’t had time to look at them yet. We’ve looked at both vendor- and third party-based solutions for patch management. CentOS doesn’t appear to have any support for centralized patch management. We’re wondering if we’ll run into this problem with Ubuntu as well.

What solutions are out there to accomplish this?

What do you use in your environments for a Linux OS? Patch Management?

UNIX isn’t an option, since we already have a lot of code developed specifically for Linux that can’t be easily ported.


Written by admin


Leave a Reply

Your email address will not be published. Required fields are marked *