Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
Similaire à Mainframe cloud computing presentation
Similaire à Mainframe cloud computing presentation (20)
Plus de xKinAnx
Plus de xKinAnx (20)
Dernier
Dernier (20)
Mainframe cloud computing presentation
- 1. © 2011 IBM Corporation A Mainframe Guy Is Still Thinking About Cloud Computing Glenn Anderson, IBM Training St. Louis CMG February 2011
- 2. 2 © 2011 IBM Corporation
- 3. 3 © 2011 IBM Corporation Computing models: A bit of history…… 1950’s / 60’s / 70’s - Centralized • Sharing and reliability Dumb, text-based terminals ----> PC’s 1980’s - Distributed client server • Low costs and simplicity PC’s ----> mobile devices and sensors Mid 1990’s - Internet / Web • On demand computing
- 4. 4 © 2011 IBM Corporation Dissatisfiers Disruptions / Technology Shifts 1980’s - how long it took IT to meet departmental needs 1990’s - thousands of physicists in the world who wanted access to data at CERN Today - IT apps are too costly and too difficult to use
- 5. 5 © 2011 IBM Corporation The New Cloud Computing Model Internet / Web Linux / Open Source Grid…Autonomic…..SOA…..On Demand Web 2.0 Social Networking Explosive rise of intelligent mobile devices - Blackberrys, iPhones, notebooks, sensors A confluence of forces building over the past decade….the evolution of the internet
- 6. 6 © 2011 IBM Corporation What is cloud computing? A user experience and a business model Cloud computing is an emerging style of IT delivery in which applications, data, and IT resources are rapidly provisioned and provided as standardized offerings to users over the web in a flexible pricing model. An infrastructure management and services delivery methodology Cloud computing is a way of managing large numbers of highly virtualized resources such that, from a management perspective, they resemble a single large resource. This can then be used to deliver services with elastic scaling. Monitor & Manage Services & Resources Cloud Administrator Datacenter Infrastructure Service Catalog, Component Library Cloud consumers Staff and cloud facilitators Publish & Update Components, Service Templates Cloud Access Services
- 7. 7 © 2011 IBM Corporation = OPTIMIZED BUSINESS …allowing you to optimize new investments for direct business benefits =AGILITY + BUSINESS & IT ALIGNMENT +SERVICE FLEXIBILITY INDUSTRY STANDARDS + Cloud-onomics… CLOUD COMPUTING = Reduced Cost ….leverages virtualization, standardization and automation to free up operational budget for new investment =VIRTUALIZATION + ENERGY EFFICIENCY +STANDARDIZATION AUTOMATION +
- 8. 8 © 2011 IBM Corporation Some Characteristics of Cloud Computing Internet of Services • User experience • Decouple delivery from technology Process-oriented, industrialized approach Virtualized Assets • Security • Green footprint • Multi-tenant Flexible acquisition model
- 9. 9 © 2011 IBM Corporation ...service sourcing and service value Cloud Computing Delivery Models ORGANIZATION CULTURE GOVERNANCE Flexible Delivery Models Public … •Service provider owned and managed. •Access by Subscription. •Delivers select set of standardized business process, application and/or infrastructure services on a flexible price per use basis. Private … •Privately owned and managed. •Access limited to client and its partner network. •Drives efficiency, standardization and best practices while retaining greater customization and control Cloud Services Cloud Computing Model .… Customization, efficiency, availability, resiliency, security and privacy .…Standardization, capital preservation, flexibility and time to deploy Hybrid … •Access to client, partner network, and third party resources
- 10. 10 © 2011 IBM Corporation Why the crazy interest in cloud computing today? IT needs to deliver service, to meet the needs of the business you are supporting IT has not been doing a good job of this. Users are not satisfied A private cloud is a model for IT to do a better job of delivering services to end users IT needs to operate as a value center. When IT is a cost center, the only thing they ask you to do is cut costs!
- 11. 11 © 2011 IBM Corporation Infrastructure as a Service Platform as a Service High Volume Transactions Software as a Service Servers Networking Storage Middleware Collaboration Business Processes CRM/ERP/HR Industry Applications Data Center Fabric Shared virtualized, dynamic provisioning Database Web 2.0 Application Runtime Java Runtime Development Tooling The layers of IT-as-a-Service
- 13. SaaS or POWA? (Plain Old Web App) Amount of stored data? Criticality of data? Customizable? Complexity? Organization mandate? Customer-side Admins? Payment? SLA? Compliance? On-premise alternative? On-demand? Scalable? Pay-per-use? Computational service? APIs? Standards? Etc…
- 15. © 2010IBM Corporation15 A “Service” A discrete set of business or technical functionality that can be identified, has a defined set of input and output, and is reusable User “Consumer” Service “Producer”Input Output Discrete – can be contained within a definite and known “fence” Identified -- it’s recognized as a service and people acknowledge it as a service Defined – the input and the outputs are known and understood Reusable – is not just a one-time thing There’s nothing revolutionary about this. What’s different is that we’re coming to a point where improvements in technology have allowed us to do this better than before: • Settled on a universal and common networking protocol -- TCP/IP • Networking bandwidth is increasingly available, cheap and reliable • The idea of “industry standards” has matured and is embraced rather than resisted • Java as a platform-unaware language has opened up a new world of interoperability Interface Implementation Exactly how the service is implemented behind the interface doesn’t really matter to the consumer of the service
- 16. © 2010IBM Corporation16 Two Perspectives of the Same Thing Depending on who you are and how you approach this, the concept of a “Service” takes on different meanings Business manager or business consultant IT specialist or architect Receiving Stocking Order Creation Fulfillment Shipping • Match to Purchase Order • Quantity Reconciliation • Initiate payment to vendor • Reserve stocking location • Create order record • Reserve stock quantity • Create order pick ticket • Create shipping label • Update order record View business process as a set of functional services linked in a specified flow View as a set of computing actions – programs, subroutines, transactions, etc. Both important! This is why you often see discussions that cross over from technology into business consulting language This is where discussions of process re- engineering and business alignment to services orientation comes from. More business consulting than I/T architecture
- 17. © 2010IBM Corporation17 SOA – Service Oriented Architecture and Cloud Computing?? A standard that supports cloud computing. SOA makes it possible to integrate new cloud- optimized workloads and platforms with the company’s existing infrastructure
- 18. © 2010IBM Corporation18 Composite Applications Built on a String of Services Extending the concept … once a library of reusable services has been built, future applications can be built by stringing services together: Start Check Inventory In Stock? Reserve Item for Sale Process Backorder Request Stock Replenish Application A Application B Application C This illustrates the benefits of re-use.
- 19. © 2007 IBM Corporation19 Web Service Inside of WebSphere Application Server Is implemented as a Java program -- EJB or Javabean. The interface provides the standard Web Service features; the rest may do whatever you wish to provide the service. And with WebSphere, many options exist: Application Server Standard Web Service interface Implemention of the service JDBC JCA JMS / MQ HTTP / SOAP RMI/IIOP DB2, Oracle, etc. CICS, IMS, SAP, etc. Any message based resource A website, or another web service EJB Web Service Client Two key points: 1. WebSphere Application Server can access a wide range of resources on z/OS 2. When WebSphere and the resources are both on z/OS, you can benefit from close proximity Cross memory speed; reduced TCP processing; potential reduced security complexity
- 20. 20 © 2011 IBM Corporation Approaches to Cloud Computing 1. Build a public cloud and market its services externally 2. Purchase services from a public cloud 3. Build your own private cloud, using technology that exhibits the characteristics of cloud computing 4. Enhance your service delivery to embrace the public cloud computing model
- 21. 21 © 2009 IBM CorporationIBM Confidential21 End to End Cloud Computing Issues Consider Disaster Recovery Replication between machines in a room is not DR Compliance How will Cloud providers put you at risk Security Secure the data. Multi Tenancy issues Selecting appropriate workloads Cloud technical models do not solve all problems. Translating what you know into corporate value Legal definitions of technical issues
- 22. 22 © 2011 IBM Corporation The mainframe for cloud computing • Strong TCO • Energy efficient • Near-linear scalability • Capacity management & upgrades on demand • Delivers a specialized IT environment • Virtualizes from the silicon to the app • Enables transparent multi-tenancy of applications • Improves performance • Comprehensive industry-leading security • Enables seamless reliability "It's a mainframe model where things run together but in isolation. The issue is whether the machines will bear up under the load of diverse work or will they grind down and you'll need to provision another machine. You need reliability, security, auditing, privacy, data integrity, automation and full isolation." - Steve Mills, IBM Sr VP
- 23. 23 © 2011 IBM Corporation System z provides a hybrid -aaS hosting environment The core infrastructure of System z is multi-tenant by nature and highly efficient, resources (HW and SW) are shared and virtualized to ensure max utilization enabling you to deploy workload for fit. DB2 (Data Sharing) z/OS Sysplex zVM/Linux Multi-Tenancy virtualization HyperSockets Shared Infrastructure zSaaS Landscape Biz Svc 1 Biz Svc 3 Virtual Servers Biz Svc 2 SaaS Data warehouse SaaS virtual server warehouse
- 24. 24 © 2011 IBM Corporation IFL1 IFL2 IFL3CP1 CP2 CP3 CP4 CP5 LPAR1 z/OS LPAR2 z/OS LPAR3 Linux z/VM Linux LPAR4 z/VM z/VM Linux Linux IBM Mainframe Real CPUs Logical CPUs Real CPUs Logical CPUs Virtual CPUs Virtual2 CPUs Virtualized from the silicon to the app The core infrastructure of System z is multi-tenant by nature and highly efficient, resources (HW and SW) are shared and virtualized to ensure utilization up to 100% without degradation.
- 25. Pain Point System z Power x86 Avoiding downtime Best Unmatched system reliability and redundancy of server hardware assets. Better Good Managing growth Best Dynamically add real hardware; share system resources with multiple hypervisors in a single machine. Better Good Underutilized Resources Best (up to 100%) Extensive hardware sharing as you scale; extremely granular sharing of system resources. Better (~ 80%) Moderate hardware sharing as you scale Good (~ 50%) Very little hardware sharing as you scale Need for flawless system monitoring Best Superior statistics and operational insight. Better Good Workload management Extensive Also able to span architectures with zEnterprise (z/p/x). Moderate Minimal Time to market Best Server cloning can be achieved in seconds; granular and efficient sharing of resources facilitates rapid provisioning. Better Good
- 26. Number of Tenants SizeofTenants Large tenants Medium tenants Long tail of small tenants Medium Tenants Small TenantsLarge Tenants Isolation: Databases Shared: Hardware Isolation: Tables Shared: Database Isolation: Rows Shared: Tables MT ApplicationMT Application MT Application or non-MT application Database-as-a-Service and Multi-tenancy with DB2 on z/OS Multi-tenancy: multiple companies or users using the same software with a level of isolation – Tenants are companies or users that would have historically installed and used a single instance of software solely for their own use – Multi-tenancy allows companies/users to use the same software with a level of isolation Multi-tenancy can further reduce hardware and maintenance costs of DBaaS Analogous to users running various applications on the same operating system – The point is to share management and hardware costs among a number of tenants – Tenants, like the distinct users on an operating system require a level isolation
- 27. 27 Role and Value of System z Function Cloud Model z/VM z/OS Hardware Configuration CMDB HMC HMC Hw/SW Relationships CMDB System Directory SYS1.PARMLIB Monitoring ITM Performance toolkit SMF/RMF/OMEGAMO N Software configs DSL VMSES SMP Usage TUAM Performance Toolkit SMF/RMF Image Repository Hipervisor / SAN System Directory + Guest MiniDisks SYS1.PARMLIB + DASD Provisioning TPM + HiperVisor TPM Support No TPM Support yet Automation TPAE Netview MPF - Netview Service Request Management TSRM NA NA Pervasive Security None RACF/ACF2 etc. RACF/ACF2 etc.
- 28. Multi-System Cloud Management on IBM zEnterprise The Big Picture Going Forward SystemzHardwareManagementConsole(HMC) withUnifiedResourceManager zBX Select IBM Blades Blade HW Resources Optimizers IBMSmartAnalyticsOptimizer z HW Resources z/OS Support Element Linux on System z z/VM Private data network (IEDN) System z Host Linux on System x 1 AIX on POWER7 DataPower1 FutureOffering FutureOffering Blade Virtualization Blade Virtualization System z PR/SM z/TPF z/VSE Linux on System z SystemzHardwareManagementConsole(HMC) withUnifiedResourceManager SystemzHardwareManagementConsole(HMC) withUnifiedResourceManager zBX Select IBM Blades Blade HW Resources Optimizers IBMSmartAnalyticsOptimizer z HW Resources z/OS Support Element Linux on System z z/VM Private data network (IEDN)Private data network (IEDN) System z Host Linux on System x 1 AIX on POWER7 DataPower1 FutureOffering FutureOffering Blade Virtualization Blade Virtualization System z PR/SM z/TPF z/VSE Linux on System z IBM Tivoli Service Management IBM Systems Director VMControl Future Future Enables optimal workload placement in a multi-system cloud infrastructure: spend less and deliver higher qualities of service Allows clients to manage all the hypervisors in a zEnterprise system with consistency Extends same management capabilities to Power and System x servers elsewhere in the enterprise IBM Power IBM System x Note: All statements regarding IBM's plans, directions, and intent are subject to change or withdrawal without notice, and represent goals and objectives only.
- 29. 29 © 2011 IBM Corporation29 Cloud Computing 07/28/15 Develop a cloud strategy and implementation plan Without a strategy, Public Cloud computing can be a threat to the CIO and the IT team • Reduced control of IT services delivered over the Internet • Perceived cost gap between a cloud service delivered by providers outside of the IT team and “traditional” services delivered by IT With a strategy, Cloud computing is a huge opportunity for the CIO • Lower costs, more responsive IT, optimized delivery • Greater range of services and capabilities • Greater visibility in billing / chargeback to LOBs • Better control of the users’ systems, desktops, and services access IT Roadmap Architecture Workload Assessment Enterprise & Public Cloud Mix Implementation Systems Storage Network Computing Infrastructure Platform & Applications Email Bus Apps BPM Sys Mgmt Info Mgmt Web Svr E-Mail, Collaboration Software Development Test and Pre- Production Data Intensive Processing Database ERP Enterprise Private Public Hybrid Trad IT Capital Private Cloud Hybrid Cloud Tim e Trad IT Rent Financial Workload CustomStandard Service Definition Tools Service Publishing Tools Service Fulfillment & Config Tools Service Reporting & Analytics Service Planning Role Based Access OSS BSS Infrastructure Platform Software End Users, Operators Service Catalog Operational Console Cloud Services Cloud Platform
- 30. 30 © 2011 IBM Corporation What IT Services workloads are we seeing move to a Public cloud delivery? Single virtual appliance workloads Test and pre-production systems Mature packaged offerings – email & collaboration • See www.lotuslive.com Software development environments Batch process jobs with limited security requirements Isolated workloads where latency between components is not an issue Storage as a Service Backup & restore as a Service Some data intensive workloads – if the provider has a cloud storage offering to complement the cloud compute offering
- 31. 31 © 2011 IBM Corporation What IT Services workloads may not be ready for a Public cloud delivery today? Workloads which depend on sensitive data normally restricted to the Enterprise Employee Information - Most companies are not ready to move their LDAP server into a public cloud because of the sensitivity of the data Health Care Records - May not be ready to move until the security of the cloud provider is well established Workloads composed of multiple, co-dependent services High throughput online transaction processing Workloads requiring a high level of auditability, accountability Workloads based on 3rd party software which does not have a virtualization or cloud aware licensing strategy Workloads requiring detailed chargeback or utilization measurement as required for capacity planning or departmental level billing Workloads requiring high degrees of customization
- 32. 32 Enterprise focus on private cloud Infrastructure as a Service Development and Test Instances Best place to start Quicker instance availability Change the time to value of development Easier to demonstrate value Non production Sophisticated user profile Challenges Cloud crosses multiple Silos Building consensus takes time Immaturity of support processes
- 33. Cloud implementation snapshot End Users Service Portal Service Request Catalog Provisioning Engine Workflows Expert Systems Scripts Optional Service Modules e.g. Metering/ Usage Billing, Monitoring, etc. Virtualized Cloud Infrastructure Easy to access, easy to use Service Request Catalog Hides underlying complex infrastructure from user and shifts focus to services provided Enables the ability to provide standardized and lower cost services Facilitates a granular level of services metering and billing Workload standardization eases complexity
- 34. 34 © 2011 IBM Corporation What does all this mean to a mainframe person? Distributed models are learning what the mainframe already does Clients are beginning to use z/VM and zLinux to provide IaaS and PaaS Linux images can be built up quickly Address spaces on z/OS can be spun up We can be the private cloud for the enterprise
- 35. 35 © 2011 IBM Corporation One more time…What are you doing with cloud computing……? 1. Build a public cloud and market its services externally 2. Purchase services from a public cloud 3. Build your own private cloud, using technology that exhibits the characteristics of cloud computing 4. Enhance your service delivery to emulate the public cloud computing model
- 36. 36 © 2011 IBM Corporation Closing Thought…..Doesn’t Every Business Want What Cloud is Trying to Deliver? Wide variety of consumer and business services delivered to a large number of clients around the world Operate highly scalable, well-engineered, efficient data centers delivering service with high quality and reasonable cost Green Secure Service Level Agreements in place
Notes de l'éditeur
- 07/28/15 In today’s economy, many businesses are faced with the challenge of “taking cost out” of their infrastructure while continuing to deliver new , innovative business services - basically they need to “do more with less” There are two primary levers to achieve cost optimization – operating expense and capital expense, and for many businesses its not just a question of lowering costs its also important to strike the right balance between Op-ex and Cap-Ex On the horizontal axis, you have virtualization, or the ability to pool the IT resources to reduce capital expense of hardware, software and facilities. On the vertical axis, is standardization…with common software stacks , operational policies, and improved service management. The farther you can drive standardize the more you reduce operating expense – like labor and downtime – which is far and away the fastest growing piece of the IT spend. The more standardization you are able to achieve within your infrastructure, the greater the economies of your operating expenses become. Similarly, the more you leverage virtualization within your IT infrastructure, the greater the economies of your capital expenditures will be. So addressing both standardization and virtualization is key to reduce infrastructure costs, while still meeting the dynamic needs of the business. The need to achieving cost optimization has also provided fertile ground for Cloud Computing. The cloud paradigm is an attempt to improve service delivery by applying engineering discipline and economies of scale in an Internet inspired architecture. Cloud computing can be an important new option in helping businesses optimize the IT expense equation while maintaining fast, high quality service delivery. NOTE: If asked to discuss public vs. private clouds: - A private cloud drives efficiency, while retaining control and greater customization. - Public clouds today are for processes deemed more easily standardized and a lower security risk. There some functions that already exhibit a high degree of standardization, that are more easily moved to a public cloud – things like search, e-commerce, and discreet business processes like sales force management.
- 07/28/15
- So we get to the point where we can introduce the concept of a “Service.” We’ll use this for the rest of this workshop. The top of the chart offers the definition, with further explanation about what some of the keywords are relating to. For now, let’s focus on the picture. A “Service” is a something that someone else can use … or in computer language, “invoke.” To use or invoke a service, the requester (or service “consumer”) needs only to know that the service exists, where it’s located, and what’s required to invoke it and what can be expected in return. In this sense the service has a kind of standardized, defined set of input and output requirements. Note: a service does not need to be a computer program. It can be a human behind a desk who does something on your behalf. But for the purposes of this workshop, we’re focusing on a service being a computer-implemented thing. The key to this is that the actual implemention of the service -- what goes on behind the interface, in other words -- is something the service consume doesn’t care about. I don’t care how the Post Office gets my letter from here to there … all I know is that I have to put an address and ZIP code on the envelope and turn it over to them. There’s absolutely nothing revolutionary about this. We’ve been striving to achieve something like this in the computer industry for decades. (Subroutines are a kind of “service,” the whole client/server thing had elements of this in mind, distributed objects and remote procedure calls also share this basic notion.) What’s different is the times in which we live -- things have come to be that facilitate SOA much better -- a common networking protocol (TCP/IP … you can’t begin to imagine how important it is that debate is over); cheap and readily available bandwidth; the coming of age of industry standards … not only the standards but the idea of embracing standards rather than seeing them as a threat; and finally Java as a kind of common runtime language. All have made the adoption of SOA much easier. Let’s now look at an example of a service.
- At this point we need to pause and point out that “Service Oriented Architecture” means different things to different people. It depends on what perspective one takes. To the IT specialist or architect, they’re going to view “services” as IT-related components. So to them the hypothetical shipping and receiving application flow is represented by a series of IT components -- a service to match a received shipment to the purchase order; another service to make sure the quantity received is equal to the quantity ordered; another service to reserve the stocking location in the warehouse, etc. But to the business manager or consultant, they’ll be viewing it not necessarily as computer-related application functions, but discrete functional components of the business. Both views or perspectives are important, and they serve different purposes. Both will be part of any SOA discussion, depending on who you’re talking to. We bring this up because this is why you’ll see many write-ups on SOA switch between pure computer talk to business-speak, and back again. Now we can try to define what “Service Oriented Architecture” means.
- Again, imagine you’ve built up an inventory of reusable services, all with defined interfaces. Now you’re getting ready to construct a new application (we’ll call it “Application A”). Rather than rewrite the same function over again, or do “tightly coupled” things like link-edit the other function into the application or make sure some CLASSPATH is updated, all you need to do is code the new application to go out and invoke the services in the order it needs. The whole application probably won’t be just invoking one service after another, but hopefully a large portion of it will be that. But here’s the value -- imagine you’ve got two other applications -- B and C -- and they also need to use some of the same services as Application A. All those applications would need to do is invoke them. Application A doesn’t need to know about B or C at all. Further, if you ever had to go into those two services that all the apps are use -- “Process Backorder” and “Request Stock Replenishment” -- and tweak the internal implementation, applications A, B and C remain unaffected … provided the interface remains as it was. This is good … the connectivity has been decoupled a bit. This helps illustrate the benefits of reuse.
- We mentioned how WebSphere is an excellent and natura HTTP handler. That means it can host a Web Service. That service will be written in Java as an EJB or a Javabean. It will provide the interface for the service. The implementation of the service -- what does the actual work -- is whatever you create behind the interface. That implementation has available to it all the resources WebSphere Application Server itself provides. This includes the full range of “data connector” technologies that permit access to data outside of WebSphere Application Server. The chart above shows you what those include. The final point listed on the chart above is one that should be noted. If the data resource and the WebSphere Application Server web service is co-located on the same MVS image, there are benefits related to that proximity. In many cases cross-memory speed can be realized accessing the data. Or, if the connection is TCP, then a reduced code-path TCP connection service can be used that greatly speeds up communications.
- Performance and Scalability 70% system capacity performance improvement over z9 EC 54-way Networking and connectivity Policy-based networking helps create a network responsive to your application needs Availability Basic HyperSwap for high-availability disk, continued Parallel Sysplex clustering and GDPS enhancements Simplified Operations New z/OS Management Facility: Support for a Web-based management console for z/OS Energy Management z10 EC displays energy efficiency on SAD screens Utilizes IBM Systems Director Active Energy Manager for Linux on System z for trend calculations and managing other servers
- [self-explanatory]
- [self-explanatory]