Eric, Among the "must-haves" that we have found on z-Linux,
The usual hardware requirements: A good processor. G5 or better, with z-box recommended because of future developments anticipated with z/VM. Tape drives, OSA-express cards and LOTS of DASD. RAID-style DASD with a minimum of 3390-3 capability and 3390-9 recommended. z/VM 4.3 or later using guest LANs. A good security manager like VM:Secure and a tape manager like VM:Tape. A good backup strategy, both for disaster backups and file-level backups of Linux data. We are currently using CA:VMBackup for weekly disaster backups of Linux servers and daily backups of all the z/VM support stuff, and Tivoli TSM for daily file-level backups of Linux data. CA:Brightstor and Veritas:NetBackup are also candidates for this last one. A really good external firewall and proxy server to allow/prevent access to the net. If you have a lot of Microsoft servers around doing file and/or print serving, you'll need some access to the authentication servers for your Samba servers. Don't stint on IP addresses. Start out requesting a full class-C subnet for your Linux LPAR running VM. That way you don't have to keep running back to network every time you add a new server. A minimal service contract with your Linux vendor, to allow you to be notified of and to get security fixes and updates to programs. Either that or enough staff to allow you to keep up with the updates manually and apply them manually. This could be one or two full-time positions all by itself, so a service contract is really cost-effective (unless you don't believe in security fixes). A written strategy and set of written processes for handling service and updates to your virtual linux servers. A set of detailed written processes for creating/cloning new servers. The thing you'll need most, and the hardest to get, is buy-in from management and all the support groups like Network (including DNS), Machine accounting, Database (Oracle, DB2) support and the Microsoft server support. This latter will feel very threatened by the very existence of Linux. We're only six miles from Micro$oft headquarters here and we have a whole building here full of people whose attitude is "If Microsoft didn't produce it, it can't be any good." Things that we or our users are finding essential, but which do not in fact exist in the marketplace yet are: Virus-checking software for your Samba and e-mail Linux servers Web single-signon software "Thousands of years ago, cats were worshipped as gods. Cats have never forgotten this." _ Anonymous Gordon Wolfe, Ph.D. (425)865-5940 VM Technical Services, The Boeing Company > ---------- > From: Eric Sammons > Reply To: Linux on 390 Port > Sent: Thursday, January 22, 2004 6:23 AM > To: [EMAIL PROTECTED] > Subject: Success stories, planning for success? > > Here is a question for the group that I don't recall seeing. I have > recently been asked to compile a list of those things that are most > important, a must have, to realize success the implementation of Linux. > Anyone here have a success story they can share, either x/Linux or z/Linux > is welcome? What "things" were most important to realizing that success? > Or what things would be considered a must have for the successful > implementation of Linux, again x/Linux or z/Linux? > > Thoughts... > > Thanks! > Eric Sammons > >
