Support Model for Linux on System z
We are in the process of writing a support model for Linux on System z that describes who in the IT organization will do what things from provisioning to problem diagnostics. Has anyone else attempted to address this; and more specifically, willing to share it or maybe portions of it? I am most curious as to whether organizations are attempting to incorporate their Unix/AIX support folks into the mix or maybe training only their z/OS folks to do both z/VM and Linux. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Support Model for Linux on System z
On Wed, Apr 23, 2008 at 2:20 PM, in message [EMAIL PROTECTED], Frank Lawrence [EMAIL PROTECTED] wrote: We are in the process of writing a support model for Linux on System z that describes who in the IT organization will do what things from provisioning to problem diagnostics. Has anyone else attempted to address this; and more specifically, willing to share it or maybe portions of it? I am most curious as to whether organizations are attempting to incorporate their Unix/AIX support folks into the mix or maybe training only their z/OS folks to do both z/VM and Linux. I've seen people go both ways. Some are being more rigid about it than others. In the various sessions I give at SHARE, WAVV, and System z Expo, I recommend that if you have in-house UNIX/Linux expertise (and not just in system administration, but security and so on), that you work together with them. And not just you do this, we'll do that, but actually work together. Cross-discipline knowledge transfer generates a number of benefits, greater teamwork among them. When you're working in a really complex environment, involving mainframe hardware, z/OS, z/VM, and Linux, I don't think any one group is going to be able to work effectively in isolation. Mark Post -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Support Model for Linux on System z
Thanks, Mark. In those situations where folks are working together as a cooperative team, can you comment on what kind of maintenance strategy they have adopted? More specifically, have they tried to adopt an aggreesive preventative program or have they only deployed fixes on servers where specific problems have surfaced? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Support Model for Linux on System z
Frank - our approach is that the mainframe support team will add z/VM support to their existing z/OS responsibilities along with bringing in one new sysprog with z/vm experience. The aix/unix team wasn't interested as they were already overworked and understaffed so we've created a new linux team. for system level security the support teams (mainframe and linux) will be responsible as only sysprogs/sysadmins will have direct access. User access will be at the application level and will continue to be controlled by our security team. For provisioning a new guest it will be a combined effort with the mainframe team responsible for the actual provisioning (using Rocket Software's Provisioning Expert for Linux aka PEL) with the Linux team supporting and maintaining the PEL base systems that are the basis for the cloning. During operation, should issues arise, the respective teams will provide support as appropriate. The mainframe team is responsible for the storage which is still FICON attached (no plans for fibre at this time) at least from the storage subsystem perspective. We are using Dirmaint for the allocation of space management and for backup our plans are to use FDR/UpStream at the Linux file system level and using FlashCopy combined with z/OS DF/DSS for the entire volume pool. For overall capacity and performance out existing performance and capacity team is involved (using Velocity Softwares ESALPS). We are also using the ESALPS to generate alerts based upon various performance indicators that it monitors with the alerts going into our normal Tivoli Enterprise Console alert system and then off to our problem tracking system. hope this helps Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: Our cause is health. Our passion is service. We're here to make lives better. I never guess. It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts. - Sir Arthur Conan Doyle NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
