02-07-2020
Normally if we are making upgrades to mission critical applications in 100s of servers in a large organization with a risk management team we should notify them if if we plan any upgrades which may cause an outage.
You should test in a test bed, make a plan, identify the risks and notify your risk management team.
Upgrading the core "mission critical" application on 200-300 web servers requires planning and team work.
What happens if you make a mistake and bring down the application(s)? Do you want your organization to be caught off guard when customers are calling in, angry their service is down?
You have described a major infrastructure upgrade. You certainly do not want to upgrade with YUM over a manually installed configuration until you have completed tested this idea in a test bed, insure you have backups of each application and database before hand, etc. In other words, you need a plan in coordination with your IT risk management team, customer service, etc.
This is how we work as IT professionals.
9 More Discussions You Might Find Interesting
1. Programming
Is there anyone who still uses CMI to connect to the legacy system , my c applications do uses the binaries and libraries for using the CMI functionality but i do not have access to the original source code , and since this is a very old stuff , i just could not get any source to get to knwo the... (0 Replies)
Discussion started by: dino_leix
0 Replies
2. IP Networking
Hello friends I'm running Redhat 9.0 with linux kernel 2.4.20-8 & have iptables version 1.2.7a & encountering a problem that I narrate down.
I need to apply patch to my iptable and netfilter for connection tracking and load balancing that are available in patch-o-matic distribution by netfilter.... (0 Replies)
Discussion started by: Rakesh Ranjan
0 Replies
3. Red Hat
Hello,
I am using Redhat Linux Enterprise 4 AS.
To upgrade NFS, I had to browse the internet and finally I got the latest rpm https://rhn.redhat.com/errata/RHBA-2005-727.html
That was a time-consuming procedure. On Solaris, I am used to go to sunfreeware.sun.com and download the latest... (3 Replies)
Discussion started by: melanie_pfefer
3 Replies
4. Programming
I need help locating the tables that hold the demograhic data in this system on an AIX box. Does anyone know the path? (0 Replies)
Discussion started by: Chelcye
0 Replies
5. Slackware
Hi!
Let me introduce a project for find and download Slackware packages and browse Slackware repositories.
The site provides following features:
* Large, daily updated database with RPM, DEB, TGZ, TXZ packages for well-known repositories of the Slackware, Fedora, CentOS, RHEL, Debian,... (2 Replies)
Discussion started by: lystor
2 Replies
6. Solaris
I have a Solaris 10 OS having kernal patch level 138888-03 on several servers but recenlty I upgraded it into 142900-12 on some T-Series servers & v890 server after install them my syslog is increasing at a rate of 1GB on average on all servers . I believe its a bug, can somebody help me in... (1 Reply)
Discussion started by: sb200
1 Replies
7. What is on Your Mind?
Watched it. Major disappointment. (10 Replies)
Discussion started by: ni2
10 Replies
8. Ubuntu
Hi folks,
Ubuntu 9.04
I have an old box not running for years. I just dig it out from the store room. On running;
$ sudo aptitude update
......
......
Err http://hk.archive.ubuntu.com jaunty/main Packages
404 Not Found
Err http://hk.archive.ubuntu.com jaunty/restricted Packages
... (1 Reply)
Discussion started by: satimis
1 Replies
9. Solaris
Hi Folks,
Just a quick question here, about Legacy Zones. Well more about how to determine if you are actually in one, on logging into a legacy zone - is there a quick way of checking that?
Regards
Gull04 (7 Replies)
Discussion started by: gull04
7 Replies
LEARN ABOUT DEBIAN
test::pod
Test::Pod(3pm) User Contributed Perl Documentation Test::Pod(3pm)
NAME
Test::Pod - check for POD errors in files
VERSION
Version 1.44
SYNOPSIS
"Test::Pod" lets you check the validity of a POD file, and report its results in standard "Test::Simple" fashion.
use Test::Pod tests => $num_tests;
pod_file_ok( $file, "Valid POD file" );
Module authors can include the following in a t/pod.t file and have "Test::Pod" automatically find and check all POD files in a module
distribution:
use Test::More;
eval "use Test::Pod 1.00";
plan skip_all => "Test::Pod 1.00 required for testing POD" if $@;
all_pod_files_ok();
You can also specify a list of files to check, using the "all_pod_files()" function supplied:
use strict;
use Test::More;
eval "use Test::Pod 1.00";
plan skip_all => "Test::Pod 1.00 required for testing POD" if $@;
my @poddirs = qw( blib script );
all_pod_files_ok( all_pod_files( @poddirs ) );
Or even (if you're running under Apache::Test):
use strict;
use Test::More;
eval "use Test::Pod 1.00";
plan skip_all => "Test::Pod 1.00 required for testing POD" if $@;
my @poddirs = qw( blib script );
use File::Spec::Functions qw( catdir updir );
all_pod_files_ok(
all_pod_files( map { catdir updir, $_ } @poddirs )
);
DESCRIPTION
Check POD files for errors or warnings in a test file, using "Pod::Simple" to do the heavy lifting.
FUNCTIONS
pod_file_ok( FILENAME[, TESTNAME ] )
"pod_file_ok()" will okay the test if the POD parses correctly. Certain conditions are not reported yet, such as a file with no pod in it
at all.
When it fails, "pod_file_ok()" will show any pod checking errors as diagnostics.
The optional second argument TESTNAME is the name of the test. If it is omitted, "pod_file_ok()" chooses a default test name "POD test for
FILENAME".
all_pod_files_ok( [@entries] )
Checks all the files under @entries for valid POD. It runs all_pod_files() on directories and assumes everything else to be a file to be
tested. It calls the "plan()" function for you (one test for each file), so you can't have already called "plan".
If @entries is empty or not passed, the function finds all POD files in files in the blib directory if it exists, or the lib directory if
not. A POD file is one that ends with .pod, .pl and .pm, or any file where the first line looks like a shebang line.
If you're testing a module, just make a t/pod.t:
use Test::More;
eval "use Test::Pod 1.00";
plan skip_all => "Test::Pod 1.00 required for testing POD" if $@;
all_pod_files_ok();
Returns true if all pod files are ok, or false if any fail.
all_pod_files( [@dirs] )
Returns a list of all the Perl files in @dirs and in directories below. If no directories are passed, it defaults to blib if blib exists,
or else lib if not. Skips any files in CVS, .svn, .git and similar directories. See %Test::Pod::ignore_dirs for a list of them.
A Perl file is:
o Any file that ends in .PL, .pl, .PL, .pm, .pod, or .t.
o Any file that has a first line with a shebang and "perl" on it.
o Any file that ends in .bat and has a first line with "--*-Perl-*--" on it.
The order of the files returned is machine-dependent. If you want them sorted, you'll have to sort them yourself.
TODO
STUFF TO DO
Note the changes that are being made.
Note that you no longer can test for "no pod".
AUTHOR
Currently maintained by David E. Wheeler, "<david@justatheory.com>".
Originally by brian d foy.
Maintainer emeritus: Andy Lester, "<andy at petdance.com>".
ACKNOWLEDGEMENTS
Thanks to Andy Lester, David Wheeler, Paul Miller and Peter Edwards for contributions and to "brian d foy" for the original code.
COPYRIGHT AND LICENSE
Copyright 2006-2010, Andy Lester. Some Rights Reserved.
This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.10.1 2010-04-26 Test::Pod(3pm)