|
![]() Defining a `lights-out' environment requires making choices. We help you determine just what those choices are |
What exactly is a lights-out environment? We compare what you might want in regards to scheduling, security, and software distribution and in the realms of management -- change, configuration, event, network, problem, and storage -- to what is possible now. (700 words)
![]() Mail this article to a friend |
You need to automate...we need a lights-out environment. That's easier said than done. How many times have you heard this before from management? "I want you to implement a lights-out production environment, we need to reduce the cost of our operations environment." It roles off their tongues so easily, no big deal right?
Get a clue in reality. We've been in IT for a combined 50 years now and we've probably heard it a few dozen times from the management we've reported to over the years. Even with all our travels around the world (several times), we have yet to see such an environment.
So let's try our own definition of what a "lights-out" environment should look like. In the following chart, we visit each discipline and summarize two objectives:
|
||
---|---|---|
You need | Nice to have | Reality |
Change Management for online applications |
|
|
Configuration Management/Release Distribution |
Automated system
detection on network to:
|
|
Event Management |
|
|
Network Management |
|
|
Problem management |
|
|
Scheduling |
|
|
Security |
|
|
Software Distribution |
|
Standardize on 3-tiered
architecture to assure:
|
Storage Management |
|
|
Now it's time to put "lights-out" out for good. From now on, we'll refer to it
as a "world-class" production environment.
|
If you have technical problems with this magazine, contact webmaster@sunworld.com
URL: http://www.sunworld.com/swol-02-1997/swol-02-unix.html
Last modified: