In late 2007 I installed and configured z/VM 5.3 and switched it to production in two very hectic months, mostly by myself. But, I have more than 25 years experience with VM, I was replicating an existing configuration, I took some really dodgy shortcuts. I spent a couple of months afterwards cleaning up. I think if you have two z/OS system programmers working more or less full time, that six months would be about right to have things really neat and tidy. This assumes that you know relatively little about VM tools and processes, so that you will be spending a fair amount of the time just learning. (Reading the manual before doing the work is so unpopular, but has many benefits.)
It might be desirable to get a trained project manager involved. In any case, make a detailed list of every task you can think of to accomplish your goal. Assign your best guess of time to each task. Be generous. Add one 'catch-up' day every two weeks. Revise the estimates as you gain more experience. Peter -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Le Grande Valerie Sent: March 26, 2009 10:39 To: IBMVM@LISTSERV.UARK.EDU Subject: Time Estimate to Create a "Fully Production Ready" z/VM System! We have our first z/VM 5.4 system up and running. DIRMAINT is currently installed, but we have not learned how to really use it. We have RACF and need to configure and make security decisions regarding Linux guests. We need to install Performance Toolkit and likely another monitor on top of that to monitor from the Mainframe perspective. Processes and procedures need to be defined, and day to day automation tasks built/addressed. We have not yet defined how we are going to handle maintenance, backup and recovery of z/VM and Linux guests. I realize this is a subset of the list of tasks. We just started in November with 2 z/OS System programmers going to one "getting started" class. Now we are being asked to estimate how long it will take us to have a "production ready" z/VM system (not including the Linux guest installs) and develop a timeline. Anyone out there been through the pain of doing this who can give us some idea of timeline and people resource required?? Thanks for any suggestions. Valerie Le Grande Systems Engineer Senior Sentry Insurance System Programming and Support Email: valerie.legra...@sentry.com Phone: (715)346-7074 This e-mail is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this e-mail in error, please tell us immediately by return e-mail to email.cont...@sentry.com and delete the document. E-mails containing unprofessional, discourteous or offensive remarks violate Sentry policy. You may report employee violations by forwarding the message to email.cont...@sentry.com. No recipient may use the information in this e-mail in violation of any civil or criminal statute. Sentry disclaims all liability for any unauthorized uses of this e-mail or its contents. This e-mail constitutes neither an offer nor an acceptance of any offer. No contract may be entered into by a Sentry employee without express approval from an authorized Sentry manager. Warning: Computer viruses can be transmitted via e-mail. Sentry accepts no liability or responsibility for any damage caused by any virus transmitted with this e-mail. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot be guaranteed on the Internet. The sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on the basis of information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is property of the TTC and must not be altered or circumvented in any manner.
