Virtualization in the Real World A customer experience Session 9214 Speaker: Mike Reeves

Download Virtualization in the Real World A customer experience Session 9214  Speaker: Mike Reeves

Post on 08-Jan-2016




0 download


Virtualization in the Real World A customer experience Session 9214 Speaker: Mike Reeves Virtualization in the Real World A customer experience. Virtualization in the Real World. zSeries & s/390 Linux. The zSeries Linux Implementation Formula - PowerPoint PPT Presentation


<ul><li><p>Virtualization in the Real WorldA customer experience</p><p>Session 9214 </p><p>Speaker: Mike</p><p>Fidelity InvestmentsOne Destiny Way MZ CC2OWestlake, Tx 76262</p></li><li><p>Virtualization in the Real WorldA customer experience</p></li><li><p>zSeries &amp; s/390 LinuxThe zSeries Linux Implementation FormulaUnix versus z/VM &amp; Linux Infrastructure Reduction Grid on zSeriesSupport Model Practical ExamplesTCO Model Workload management</p></li><li><p>((((RIT * PT)NITP)M2)V3)NTWISVPTABNYDzSeries &amp; s/390 LinuxPITRITPTNITPMVNTWISVPTABNYD- Project Implementation Time- Real Implementation Time- Project Time- Needlessly Involved Technical People- Managers- Vice Presidents- Number of Turf Wars- ISV Products- Talked About But Not Yet DeliveredThe zSeries Linux Implementation FormulaPIT=</p></li><li><p>Unix versus z/VM &amp; Linux</p></li><li><p>Unix versus z/VM &amp; LinuxIEEE VLANDiscrete compared to virtualized with z/VM</p></li><li><p>LinuxLinuxLinuxManageability of the Virtual EnvironmentCMSVM OPER (REXX)LinuxCPHypervisoroperationsCP MonitorVirtual ConsolesSingle Console Image FacilityPROP(CA) or VM/Oper (CA)Performance ToolkitStandard VM monitor dataMICS and/or Merrills MXGIntegrate with z/OS dataRMF LPAR reportingRMF for LinuxVirtual ConsoleSCIFMonitorDataz/VMCMSPerf. ToolkitWorkload Management</p></li><li><p>zSeries HardwarezSeries Hardware layerAutomationz/VM Virtualization layerManagementUnix versus z/VM &amp; LinuxOn Demand is there today!!Dynamic addition of resources is possible for certain resources and is expanding rapidly in the zSeries infrastructure.</p></li><li><p>Typical Open environmentUnix versus z/VM &amp; LinuxDiscrete compared to virtualized with VMWareServerUNIXAppCableServerAIXAppServerWin..AppCableCableWindows &amp; Linux on VMWare</p></li><li><p>Unix versus z/VM &amp; LinuxWhat are some differences?Virtualization with 3 decades of IBM software and hardware experience behind it. Instruction based VirtualizationEnd-to-End Error RecoveryWorkload ManagementDynamic pathing to DiskHipersockets between LPARs On Demand Infrastructure Simplified Administration, Monitoring and AutomationInfrastructure simplificationShared Segments &amp; Disk SharingMaintenance and Upkeep</p></li><li><p>Unix versus z/VM &amp; LinuxVirtualization Considerations for Mainframe Users</p><p>Considerationz/VMEnd-to-End Error RecoveryAutonomic Workload ManagementHipersocket connectivity to other LPARsDisk I/O subsystem dynamic pathingEnvironment requires high degree of sharingCentralized Administration and Capacity ManagementDynamic On Demand resource allocationLinux automation capabilityDynamic provisioning (creating &amp; manipulate guests on the fly)Total Cost of Ownership (infrastructure for power/cooling)Total Cost of Acquisition (initial cost for small implementation)Virtualization of Windows</p></li><li><p>Infrastructure ReductionFirewallWeb ServereMail ServerApplication ServerDatabase ServerSecurity ServerBackup ServerSecurity ServerWeb ServerWeb ServereMail ServerApplication ServerApplication ServerDatabase ServerDatabase ServerBackup ServerFirewallFirewallFirewallTypical Server Environment What are the Problems?What is Missing?</p></li><li><p>Something will always be broken or malfunctioningSomething in this infrastructure needs upgradeHardware/software upgradeUpgrade (technology exchange) is very disruptiveNo provision for dynamic upgradesThe majority of this infrastructure will be underutilizedBut when processing spikes occur, there will always be a bottleneck somewhereUnknown SPOFsEnd-to-End management is difficult to impossibleMonitoring Management &amp; control does not span silos Administration is difficult and requires to many levels of interaction to solve problemsNo real way to achieve significant infrastructure &amp; administrative cost reductionAutomation is difficult so autonomic computing and Disaster Recover are nearly impossible to achieve Infrastructure ReductionWhat are the problems with the distributed Infrastructure?</p></li><li><p>Infrastructure ReductionWhats Missing? Support Infrastructure!FirewallWeb ServereMail ServerApplication ServerDatabase ServerSecurity ServerBackup ServerSecurity ServerWeb ServerWeb ServereMail ServerApplication ServerApplication ServerDatabase ServerDatabase ServerBackup ServerFirewallFirewallFirewallIntranetThis configuration contains 50+ levels of infrastructure </p></li><li><p>In this configuration, 14+ levels of infrastructure have been eliminatedInfrastructure ReductionReduce Infrastructure with Linux on zSeriesFirewallWeb ServereMail ServerApplication ServerDatabase ServerSecurity ServerBackup ServerSecurity ServerWeb ServerWeb ServereMail ServerApplication ServerApplication ServerDatabase ServerDatabase ServerBackup ServerFirewallFirewallFirewallIntranet</p></li><li><p>Virtualization simplifies the infrastructure Common software provides for simpler upgrades and hardware can be transparently upgradedAdministration and management simplifiedReal cost savings can be achieved because levels are moved from real to virtualResources can be better utilizedOn Demand dynamic addition of resourcesBetter automation, autonomic computing Disaster recovery actually possibleInfrastructure ReductionConsolidation on zSeries What are the Benefits?</p></li><li><p>Grid on zSeries</p></li><li><p>WebSphere A Grid?Sysplex Websphere gridServers dynamically added &amp; quiescedResources balanced across sysplexWebSphere Application ServerCan take advantage of z/OS security, crypto and zAAP featuresWork Load ManagerDynamic Management of WAS application serversWork loads prioritized and balanced Running hardware at 100% with heterogeneous workloadsOn Demand resource additionActivate standard processors, zAAPs, IFLs and Memory dynamicallyDeactivate resources dynamicallyGrid on zSeriesWork Load ManagerParallel SysplexNetworkServeletJavaEJB</p></li><li><p>DB2 Data Sharing A Grid?WebSphere &amp; CICS CICS Web ServerJ2EE, Java transactionsBusiness transformation logicDB2 Data SharingEnterprise Java BeansStored ProceduresDB2 ConnectVSAM Record Level SharingSysplex wide sharing of VSAM filesWeb enabled VSAM connectorsOn Demand resource additionAdd resources manually or automaticallyScale up and/or outGrid on zSeriesWorkload ManagerParallel SysplexNetworkDB2VSAMJavaJavaJavaJava</p></li><li><p>Job ManagerGrid on zSeriesData Grid Exploitation with zSeriesWe could this, but our applications groups would have to recode all of our applications to fit this model.Eventually this will happen, but not in the short term.Resource LibraryProcessProcessProcessProcessClientGatekeeperSecurity InfrastructureOpen Grid Services ArchitectureResource ManagerHosting EnvironmentGrid Service ContainerUser-Defined ServicesBase ServicesSystem-Level ServicesOGSI Spec ImplementationSecurity InfrastructureWeb Service EngineSecurity admin. RSL admin.</p></li><li><p>z/VM 1</p><p>z/OS 1 OSA/Xz/VM 2z/OS 2OSA/XData Grid Exploitation with zSeries Linux &amp; DB2 ConnecthipersocketsDB2 ConnGuest 1DB2 ConnGuest 2DB2 ConnGuest 3DB2 ConnGuest ..nDB2/DSDB2/DSDB2/DShipersocketsDB2/DSDB2/DSDB2/DSDB2 ConnGuest 1DB2 ConnGuest 2DB2 ConnGuest 3DB2 ConnGuest ..nsysplexCompute environment taking advantage of zSeries data grid to provide a high speed connection to DB2 data on the zSeries sysplex. Low network latency &amp; high data rates can be achieved with hipersockets.Example of this configuration in Practical Example.Grid on zSeriesCompute Intensive Processing</p></li><li><p>Middleware &amp; DBMS SupportOS support with IBM for level1 &amp; 2 level 3 support with RedHat.Support ModelHow we do zSeries Linux installation &amp; supportzSeries Hardwarez/VM &amp; Virtual GuestsWASWASMQDBDBTest/Dev/QA Mainframez/OS SupportProduction UNIX Technical SupportMainframeHardware &amp;StorageManagementWASDBJava</p></li><li><p>LinuxMQSeriesLinuxDB2 Connz/VM (ZVMx)LinuxWAS 5z/OS (CPUx)LPAR1LPAR2Server CreationServers can be provisioned through Server Central. Once the request is received it takes about hour to create the server and in many cases the server can be completely provisioned in less than one day. Test/Dev/QA supported by z/OS support group. Production supported by UNIX Technical Support group. Middleware &amp; DBMS supported by Open Systems DBMS support.Server CreationSupport Model</p></li><li><p>LinuxmailLinuxJavaLinuxc++/ftpLinuxMQSeriesLinuxDB2 Connz/VMLinuxWAS 5z/OSzSeries Test/QADev Test QA TestPlexQA PlexSupport Model</p></li><li><p>LinuxmailLinuxJavaLinuxc++/ftpLinuxMQSeriesLinuxDB2 Connz/VMLinuxWAS 5z/OSzSeries ProdOther PlexesSite 1 Site 2Other PlexesProduction zOS/zVMzOS/zVMzOS/zVMzOS/zVMSupport Model</p></li><li><p>DB2 Connect</p><p>AIX Servers in a High Availability multi-site configuration resulting in unused capacity</p><p>Maintenance difficult to schedule because all connects share the same DB2 binaries</p><p>Multiple network hops increase latency resulting in higher response times</p><p>Memory configuration limited to total memory available on hardwarez/OS 2DBMSDBMSDBMSDBMSz/OS 1DBMSDBMSDBMSDBMSIPDist.SiteDist.Site 1AIXC1C2C3Site 2AIXC1C2C3Old ConfigurationPractical Examples</p></li><li><p>DB2 Connect</p><p>Shares hardware in a continuous availability configuration</p><p>Maintenance can be easily scheduled because each instance has its own DB2 binaries</p><p>One network hop reduces network latency to near zero</p><p>Memory can be customized for each server guestz/VM 1z/VM 2IPDist.New ConfigurationPractical Examples</p></li><li><p>WAS 5.1.0 applicationsCSC Hostbridge &amp; EOS</p><p>High availability configuration</p><p>Mainframe centric applications with low utilization.</p><p>One network hop reduces network latency to near zero (except in failover)</p><p>Both Hostbridge and EOS are running on a single guest to leverage server costs.Practical Examples</p></li><li><p>DB2 Connect/Java</p><p>High availability configuration</p><p>Maintenance can be easily scheduled because each instance has its own DB2 binaries</p><p>One network hop reduces network latency to near zero (except in failover)</p><p>Low utilization server allows for consolidation, simplification and low network latencyMerrimackz/VM 1z/OS 1DBMSIPDist.z/VM 1z/OS 1DBMSDallasHigh AvailabilityFailoverPractical Examples</p></li><li><p>SNAWANOSA/ez/OS EESNAAppSNARemoteData CenterTCP/IPSNA environments will be around for some time and have evolved to become a complex infrastructure. SNA over IP requires many levels of infrastructure. DLSw and EE gateway technologies are not always compatible and when a problem occurs, diagnosis is very difficult.Channel AttachedCIP RoutersTN327037xx37xx37xxz9xxz9xxTCP/IPSNA37xxLoadBalancingSNA AppsSNA AppsSNA Elimination Current EnvironmentPractical Examples</p></li><li><p>OSA/ez/OSSNA AppRemoteData CenterzSeries Linux Communications Server, Communications Controller, and SSL server provide the ability to collapse the SNA infrastructure back into the mainframe platform eliminating the need for distributed SNA appliance technology which is reaching end-of-life status over the next 12-24 months.TN3270SNASNA AppsSNA AppsCSCCSNA Elimination Future EnvironmentPractical Examples</p></li><li><p>We project that improving UNIX/Intel workload management will drive average utilization rates from the 15% to 20% to 40% to 50% within three years. When the significant Intel/zSeries annual price/performance improvement gap is overlaid on these projections, it becomes clear that any business case for mainframe Linux will evaporate by 2005/06, in the face of the Linux on Intel juggernaut.</p><p>(Meta Group, Mainframe Linux Server Consolidation: The Near-Term Business Case, Delta 2107 Mar 03)TCO versus TCA!</p></li><li><p>Action Item: Investigate all options to consolidate. Closely evaluate the migration costs, all assumptions (including staffing efficiency and over-provisioning for peak workloads), availability requirements and alternative mechanisms for reducing TCO. Those who dismissed Linux on the zSeries two years ago may wish to revisit itbecause IBM has made progress.</p><p>(Gartner, The IBM Mainframe: 40 Years, Now What?, 30 November 2 December 2004)TCO versus TCA!</p></li><li><p>Long Term costs versus initial cost!How long before hardware push-pull is required?Total Infrastructure costs versus server hardware cost!!How much infrastructure resources does the server require?How much capacity will go unused?Low utilization equals poor ROIUtilization only during certain time framesDowntime does have a cost!Server outages should include appropriate resolution costsBusiness outages do cost real dollarsOngoing maintenance, monitoring and capacity planning costs real dollars!What real networking, monitoring, admin &amp; capacity planning costs are visible to the project?TCO versus TCA!</p></li><li><p>Benchmarks are not real workloads!! Benchmarks dont represent real production workloadsOne-to-One hardware comparisons dont work!!Single application hardware comparison: ex. blade-IFL $$$Sharing not considered as part of the model!!Workload sharing is become a necessity in all environments24X7 utilizationDowntime not considered as part of the model!!Outages should include appropriate resolution costsInfrastructure reduction not considered!!Networking, monitoring, admin &amp; capacity planning cost $$$On Demand versus excess capacity is a reality on zSeries!Add and remove resources dynamicallyNo unused infrastructure for capacity is requiredTCO versus TCA!</p></li><li><p>zSeries20%2 IFLOne-to-One Comparisons are MisleadingCost ComparisonIntel40%3 GhzThe comparison is done on one box but the deployment is implemented in the standard high availability configuration which is much more costly.TCO versus TCA!</p></li><li><p>So far all of the testing has focused on Primary Shift projects. This only takes advantage of a window of resources available on zSeries Linux. This leaves more than 60% of the resources available for other application deployments.8:00 5:005:00 8:00WASOracleUDBJava/DB2 ConnectWeb PortalOffshore developmentExtracts and reportingOther exploitation of unused timeframe Great area of opportunity liesbetween end and start of primary shiftTCO versus TCA!What are the Opportunities</p></li><li><p>Prime Shift ApplicationsNon-Prime Hours Applications TCO versus TCA!</p></li><li><p>TCO versus TCA!z/VMz/OSHeterogeneous workloads can reduce costsUse the workload management capability of z/VM to allow production peaks to utilize the test &amp; development resources.Provision Test/DevBuild as many test/development guests as you can to fill unused resourcesSet the priority of the test/dev guests lowProvision ProductionBuild production guests with the intent of satisfying peaks by stealing resources from test/devSet the priority of the production guests highConfigure the LPAR with sufficient resources to run both</p></li><li><p> Current Unix Life Cycle StrategyTCO versus TCA!The Boundless Proliferation loop!Provision serverFloor space, Power &amp; HardwareOS, Network &amp; MiddlewareTest the configurationInstall the applicationQA the configurationRun parallel to validate the applicationCutover to productionDecommission the old server</p></li><li><p>zSeries Linux Life Cycle StrategyOLDTCO versus TCA!Ending the loop with zSeries Linux!</p></li><li><p>TCO versus TCA!What works in zSeries Linux!</p></li><li><p>How do you decide what works? TCO versus TCA!</p><p>Workload CharacteristicszLinuxNeeds access to mainframe data or applicationDB2 Connect &amp; MQSeries ConcentrationTest &amp; DevelopmentLow CPU utilizationHigh I/O activityInfrastructure Simplification/ReductionNon-primary shift workloadsTime to MarketDynamic On Demand resource allocationCPU intensive workloads (where CPU is not I/O related)Mainframe reliability requirementsScalability beyond 4 CPUs</p></li><li><p>LinuxLinuxLinuxManageability of the Virtual Environ...</p></li></ul>