Cloud Messaging. Graham Wallis STSM, WebSphere MQ

Transcription

1 Cloud Messaging Graham Wallis STSM, WebSphere MQ 1

2 Disclaimer THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILST EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IN ADDITION, THIS INFORMATION IS BASED ON IBM S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, OR SHALL HAVE THE EFFECT OF: CREATING ANY WARRANTY OR REPRESENTATION FROM IBM (OR ITS AFFILIATES OR ITS OR THEIR SUPPLIERS AND/OR LICENSORS); OR ALTERING THE TERMS AND CONDITIONS OF THE APPLICABLE LICENSE AGREEMENT GOVERNING THE USE OF IBM SOFTWARE. 2

3 Contents Cloud Computing review Cloud Messaging IBM Workload Deployer IWD 3.0 MQ External Connector Evolution of IWD Messaging HVEs and Custom images HVE for Redhat Custom image construction Public Cloud SmartCloud Enterprise[+] Amazon EC2 Summary Strategic evolution Demos 3

4 Cloud Computing Primary Characteristics On-demand self-service Ubiquitous network access Location independent resource pooling Request driven provisioning and scheduling Measured service / Pay-per-use 4

5 Cloud computing - Definitions Technology description: Cloud computing is a model for enabling convenient,ondemand network access to a shared pool of configurable computing resources (e.g. networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. NIST Business value proposition: Cloud computing is a model for enabling cost effective business outcomes through the use of shared application and computing services..resulting in better economics in the execution of business processes. Steve Mills, IBM 5

6 Cloud Computing Service Models Cloud Services Software as a Service (SaaS) incl BPaaS Customers use applications (e.g. CRM, ERP, ) or business services from multiple client devices through a Web browser on multi-tenant and shared infrastructures without the need to manage or control the underlying resources Services Platform as a Service (PaaS) Customers use programming languages, tools and platforms to develop and deploy applications on multitenant and shared infrastructures with ability to control deployed applications and environments without the need to manage or control the underlying resources Software Infrastructure as a Service (IaaS) Customers use processing, storage, networks, other computing resources with ability to rapidly and elastically provision and control resources to deploy and run software and services without the need to manage or control the underlying resources Hardware 6

7 Cloud Delivery Models A private cloud is one in which both the consumer of cloud services and the provider of those services exist within the same enterprise. The ownership of the cloud assets resides within the same enterprise providing and consuming cloud services. A public cloud is one in which the consumer of cloud services and the provider of cloud services exist in separate enterprises. The ownership of the assets used to deliver cloud services remains with the provider. A hybrid cloud combines multiple elements of public and private cloud, including any combination of providers and consumers, and may also contain multiple service layers. Consumer and provider of cloud services exist within the same enterprise Isolates workload; initial foray into cloud computing Exploratory Cloud Few participants, all Internal IT organization and cloud users exist within one management domain Department Cloud PRIVATE CLOUD IT organization and cloud users exist across internal boundaries Enterprise Cloud Organizational Scope One-to-one relationship between service provider and the consumer organization CLOUD DELIVERY MODELS Consumer and provider of cloud services exist in separate enterprises Exclusive Cloud One-to-many relationship between service provider and consumers Open Cloud PUBLIC CLOUD Many participants, Internal and External 7

8 Principle areas of interest In a recent IBM Cloud Computing survey, respondents were asked whether each of the delivery models is appealing : Private 64% Hybrid 38% Public 30% Our recent focus has therefore currently been on: provision of images (HVE or Custom) for virtualised environments integrated deployment and management for on-premise clouds 8

9 Cloud Messaging 9

10 IBM Workload Deployer (3.0) Patterns-based middleware platform that provides easy and repeatable creation of application environments in a private cloud. IWD will deliver capabilities across cloud delivery models (private, public, hybrid) Enhanced hardware appliance for access to IBM middleware images and patterns IWD is the next generation of WCA (WCA > IWD 3.0) Built on WebSphere CloudBurst firmware on updated DataPower form factor Topology patterns, including multi-image patterns: Using pre-defined HVE images for IBM products, certified by IBM Customisation by user-scripts Realised by a pattern deployment engine at the IaaS interface Workload patterns, for Java EE Web Applications Including dependencies on JDBC and JMS Realised by PaaS, which drives a pattern deployment engine, which in turn delegates to IaaS Supports locking of images and patterns for guaranted consistency Supports usage montoring, license tracking and charge back Supports VMware ESX, IBM PowerVM and IBM z/vm environments 10

11 IBM Workload Deployer and Messaging IWD 3.0 MQ External Connector Current function: Simplify the deployment of a Java EE messaging application using WMQ JMS resources IWD 3.0 does not automatically provision a messaging server MQ Queues/Topics are hosted in a remote WMQ queue manager Future requirements We may want to support applications written in other languages or containers, so messaging artifacts use generic properties applicable to all application environments 11

12 IBM Workload Deployer and Messaging An enterprise application uses a ConnectionFactory and Queue in JNDI, to connect to a remote queue manager, and sends or receives messages to a Queue. When the application is dragged onto the canvas, the system introspects the EAR file and prompts the user to resolve the JMS references A link to a Messaging Service is required to resolve the reference to jmsref/cf1 A link to a Queue is required to resolve the reference to jmsref/q1 The user drags messaging resources onto the canvas and names the links At deploy time: A ConnectionFactory is created with the name specified on the link and properties from the Queue Manager (see next slide). A Queue is created with the name specified on the link 12

13 IBM Workload Deployer and Messaging Evolution of the IWD Messaging Service Enhancements to the MQ External Connector Possibly further support for on-premise cloud Deployment of IWD topology patterns and workload patterns Provisioning of queue managers in the cloud Initially, manual explicit provisioning Intention to introduce a shared messaging service in the cloud Messaging as a Service (MaaS) Hosts queues and topics declared by user Improvements to MaaS, e.g. automatically elastic scaling 13

14 Hypervisor Editions (HVEs) and Custom Images Hypervisor Edition A full image (OS and middleware) HVEs are available for WAS, WPS, WMQ, WMB, DB2 Available 2Q11: WMQ HVE for Redhat on x86-64 Available as standalone product Also included in IBM Workload Deployer 3.0 Can be deployed using patterns: non-clustered queue manager clustered queue manager IBM may make other HVEs available in future Custom Images Expect to see improved support for custom image creation e.g. possible hardening of existing offerings for custom image construction 14

15 IBM Public Cloud support IBM SmartCloud Enterprise Quick access to an enterprise-ready development and test environment More responsive and reduced operating costs versus on-premise Windows Server and Linux (RHEL/SLES) IBM SmartCloud Enterprise+ Deploy production level workloads on a robust, secure, performant cloud infrastructure More responsive and reduced operating costs versus on-premise Hosted in an IBM Data Center or in an isolated environment for a single customer High SLA up to 99.9% allowing customers to shift workloads to cloud with confidence IBM also recognises 3 rd party public clouds (e.g. Amazon EC2) 15

16 WMQ Public Cloud support WMQ is included in Industry Application Platform WAS , DB2 Express-C and WMQ Includes sample financial services application Obvious application for development & test Potential application at edge of enterprise IBM SmartCloud Enterprise Restricted to development & test Keen to get a production ready WMQ image on SmartCloud Amazon EC2 Also restricted to development & test Considering pushing out a production ready WMQ AMI 16

17 Strategic Evolution What we expect to see over the next few years Continuing (growing) widespread use of private clouds simplified deployment; better integration; improvements to automation and lifecycle management; improved elasticity Increasing use of public clouds emergence of elastic messaging service 17

18 Cloud Demos WMQ HVE for Redhat IWD 3.0 MQ connectivity Mark Phillips & Charlie Martin, MQ Cloud Development 18