IBM SmartCloud Application Services: Why You Should Care

1. IBM SmartCloud Application Serviceswhy you should care

2. Agenda • SCAS early pilot status and lessons learned • SCAS 2013 planning

3. Ready for SCAS pilot ISV validation status STATUS as of Nov 20, 2012 • Existing 5 ISVs: partial success • Zend and Alphinat completed validation successfully with < 1 week of time • Silvermoon, OneTree and Corent are all blocked by SCAS bug/system availability in validation phase. Denis’ team is engaged and actively working on these problems. • Lessons learned • Enable once and deploy everywhere is not there (yet), it is a YMMV experience. • Corent find some of its PureAS VSP pattern parameter is no there in SCAS • Silvermoon VAP pattern needs tweaking in order to deploy on SCAS • SCE/SCAS system availability is not reliable • OneTree saw inconsistent deployment time, sometimes the same pattern can take hours to deploy. • Supporting SCAS ISV enablement needs to be high touch in the beginning. A self service forum is not enough.

4. 2013 Ready for SCAS: how do we scale out? SCAS showcase Recruit Validate Enable • Need to build our hybrid cloud story (Pure+Smart) to ISV so that we are aligned with ISV’s cloud strategy, and not being felt fragmented. • Because the extended dev audience, we need on demand education material online so that we can easily scale. • Cross link between SCAS-PureSystem ready for workflow. • One step enablement at IIC will need to work on both Pure/SCAS. • Bug preventing “enable once and deploy everywhere” needs to be fixed. • High touch support from SCAS is needed in the beginning. • Provide no-charge trial environment for the pattern validation. • Ideally we should target to validate both Pure and SCAS at the same validation apt. if not, then we have to balance between Pure vs SCAS resource demand.

5. IBM Cloud Story Sell your pattern as a service (SaaS) Go beyond the hybrid cloud story, now change your business model Deploy pattern to hybrid cloud – FAST! Make your app cloud centric and enable usage based biz model • Customer buy your provisioned app/services and use it right away • Maximize your infrastructure utilization through multitenant deployment on a single app instance • Leverage cloud centric DevOps to enable SaaS billing and metering without writing your own code • Lowest cost to scale • Automated provisioning, authentication, metering and billing Create a Pattern Ready for Ready for PureSystem SmartCloud Enterprise grade private and public cloud • Customers buy your app and deploy app to their private/public clouds in <1 hr • Common workload deployment technology enabling seamless integration and cross clouds portability. Enable once, deploy anywhere • Rapid deployment of applications, databases, and services • Providing industry’s best SLA and HA and disaster recovery. Adopt PureAS PaaS • Simplified middleware consumption support wide range of programming languages • Enterprise class auto scalability and reliability • Built in enterprise computing best practice

6. Recruitment • Core/Invest • Need to train coverage team about the consolidated cloud story, • ISVs need to understand they want a a hybrid cloud strategy, and • stitch a long term cloud strategy rather than taking a baby steps. • What is the role of IDR cloud sales guys (fighter pilots) ? • For existing PureAS ISVs, focus on improved value prop around Demo/PoC for their solution. (and for production usage, what is the story behind SCAS on SCE+)? • For new ISV onboard, always tell them to do both SCAS and PureAS? • Opportunistic • Need self-service on-demand IBM cloud story training (youtube, IBM Education Assistant) around patterns, how IBM’s cloud can make they develop/sale faster to enterprise customers, and how to get started etc • Workflow management of “Ready for” programs • On the “Ready for PureSystem” ISV self nomination form (partnerworld form), always cross link to the Ready for SCAS program. • For existing PureApp ISVs with patterns, bypass the enablement step, go directly to validation.

7. Enablement and validation – enable once, deploy everywhere • To avoid duplicate effort IIC (and competition for resources), suggest we combine SCAS/PureAS enablement • For existing ISV patterns from PureSystem, there will be work needed to port their Pure pattern to SCAS. We need to SCAS team provide such details. • For new ISV enablement, the pattern needs to be created for both, IIC consultants need to articulate the minor differences between Pure and SCAS and get one enablement creating two outputs if necessary • SCAS Training/Support to IIC/ISV is essential • IIC’s skill over SCE/E+/SCAS has not been up to speed, we need SCAS team to arrange such training. • Current SCAS trial’s self service does not work adequately here for a 2 week enablement, need strong project management and ISV issue tracking and resolution.

8. Enablement and Validation: where to run these? Proposal: leverage SmartCloud Service Trial/PureSystem Trial (N00080 account special account) infrastructure and administration process, currently it is paid by IDR/SWG • Pro: biz process reuse, minimal overhead • Cons: ISV account went away after validation, tied to Puresystem trial Cost estimate • Assumption: • $500/Per account-month: 5 VMs running 64 bit RHEL instances with 12 CPUs running 12/7/30 with 5GB/month Data transfer in/out using 60 GB of storage during half the trial and 1 reserved IPs – reserved instance pricing • 20 concurrent accounts: each IIC owns 2 accounts

9. SmartCloud and PureSystem share the same Pattern technology High SCAS Virtual App Pattern Easily build and configure application patterns, and rapidly deploy into private cloud PureApp System SCAS Business Agility Virtual System Pattern Middleware Image Virtualization Integrated middleware combined into patterns representing middleware workloads PureApp System SmartCloud Enterprise/E+ Virtual Appliance Server Image Virtualization SmartCloud Virtualized infrastructure leads to creation of “virtual” software images PureFlex System Low PureSystem Low High Standardization & Automation

10. Enablement – for existing PureApp ISVs • Apply for a SCE account • Import your pattern Fastest Virtual System Pattern Virtual App Pattern A little bit more work, but gives you more flexibility In most cases, no engineering effort needed If your pattern contains custom image, regenerate your custom image using ICCT Import your pattern using CLI tool, check the images your pattern points to are already in SCAS Deploy ISV work steps (2-4 weeks) • Import your pattern to your SCAS Cloud app builder using GUI • Deploy