1 / 11

IBM PureSystems: Cloud Centric Workload Support Approach

Explore the strategic positioning & key design tenets of IBM PureSystems to address cloud-centric workload challenges in partnership with cloud providers. Learn about potential plays with vendors & steps towards integration.

carstarphen
Download Presentation

IBM PureSystems: Cloud Centric Workload Support Approach

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Support Cloud Centric workload on PureSystemsA partner approachsherwood yao (syao@us.ibm.com)June 25, 2012

  2. As we celebrate the successful launch of PureSystemsWe also hear noise like the following…what is going on? • It is because the analyst believes PureSystems lacks critical cloud centric workoad support http://www.cloudave.com/19378/ibm-pureapplication-systems-it-is-not-paas-period-but/

  3. Three steps to the Cloud Epiphony Cloud enabled Cloud centric Cloud optimized SAP Facebook like app SAP Oracle NoSQL, Cassandra DB2 vCloud Openstack Nova Workload/pattern websphere websphere PHP, Ruby Linux Linux Linux VMware vCenter Xen, KVM, VWware VMware vCenter X86 X86 X86 EMC Commodity storage v7000 Cisco Cisco Cisco Legacy enterprise apps Born on the web ent apps Applications Data Cloud platform Middleware O/S Virtualization Servers Storage Networking • Design tenets – scale & elasticity, share nothing (low level component designed to fail) & distribute everything • Design tenets – intelligent PaaS, full system integration, pretuned out of the box • Design tenets – highly scalable though low level component, high IaaS layer SLA

  4. Strategic positioning of PureSystems in the workload spectrum • Key questions: • Should Puresystem be expanded here? • How should we get here, build, buy or partner? System Z Mainframe PureSystems SmartCloud App Svc IBM Revenue Cloud centric workload Legacy Enterprise workload Process critical Mission critical

  5. Key characteristics of Cloud centric applications

  6. PureAS: can it handle Cloud Centric Workload (CCW)?

  7. What are the Cloud runtime vendors doing in CCW space? • Two particular PaaS vendors are pretty interesting IBM Revenue Cloud centric workload Legacy Enterprise workload Process critical Mission critical

  8. Potential plays with CCW vendors – step 1 • Step 1 Add IBM technology to CCW stack • How do we play • Add Websphere 8.5 (Liberty) runtime to CCW vendor supported list • Value gain: • existing websphere customers can continue to run on Websphere using CCW management stack

  9. Potential plays with CCW vendors – step 2 • Step 2 Support CCW management stack on PureAS as new App type • How do we play • Directly support CCW management layer on top of PureAS/IWD management so that apps is deployed to partner CCW stack • PureAS/IWD is still the central management portal and actual runtime • Value gain: • Fastest way to add support of polyglot programming models (Ruby, node.js, Scala etc) • Leverage CCW partners to promote PureAS SmartCloud AppSvc usage

  10. Business models of CCW built by partners • When workload runs on Partner cloud • Outbound OEM license of websphere and DB2? • When workload runs on IBM Public cloud – Smartcloud family • Partner CCW pattern is built in to SCAS – no additional install needed • OEM license from partner and revenue sharing on workload revenue generated by partner • When wokrload runs on Private cloud – PureSystem family • Partner CCW pattern is option download from PureSystems Centre • License based sales from partner and IBM promote/endorse these CCW patterns

  11. Next steps • IDR initiate conversation with the partners to build interest and PoC • Decide whether to invest here, who (IBM or Partner) is going to own the integration work. • Close on the partnership agreement

More Related