Ready for PureSystem ISV solution validation plan

1. Brian Inness Sherwood Yao Ready for PureSystem ISV solution validation plan

2. Agenda • PureSystem IIC status update • Validation Process • Next Steps

3. PureSystem 3Q availability @ IIC Assume 100% system utilization to ISV validation

4. Potential issues with the system • These system will also be shared with SWG/STG sales team to do demo/POC, we expect to have ~60% of system usage. This implies we should target finishing 70 ISVs by Sep 30. • Current build has security/isolation issues that preventing we run 3 ISVs concurrently on the same box. • Some ISVs will take longer to validate if they have custom images that need to be rebuilt with newer OS/MW, we suggest they finish that using Dev Kit before come to IIC.

5. Validation test goals • Ensure ISV solution adhere to PureSystem “Ready for” quality standard. • Ensure ISV solution delivers the promised out of the box experience on customer’s PureAS. • Collect performance measurement around deployment and scaling (if auto-scaling enabled)

6. Task 1 : Collect ISV answers to solution quality questionnaire • Send the ISV solution quality questionnaire • Explain the quality standard will keep involving, as we strive to achieve the best possible “integrated expertise”, we will enhance the standard overtime. (meaning, some optional criteria will become mandatory in the future)

7. Task 2 : prepare/deploy ISV solution on PureAS • ISV submit PureAS 1.0 compatible patterns created during enablement phase. • Recreate images if ISV solution contains custom build images with RHEL 5.7 • Once at IIC, ISV deploys the ready solution on the pre-populated PureSystem instance • Perform functional test to ensure the whole solution is operational without any low level (ssh etc) post deployment tasks • For ISV solution implemented auto-scaling (built-in to VAP, and optional to VSP via Intelligent Mgmt Pack), validate their auto-scaling functions properly. (there will be a manual command that invokes

8. Task 3 : Measure the deployment performance (concurrently with task 2) • To reduce time requirement, we will collect performance number as part of task 2, no extra deployment is needed here • Create quote for deployment performance, ISV to agree to release to IBM.

9. Thoughts about the performance testing • We chose to focus on deployment/scaling performance to align with PureSystem marketing team need • Why not measure run time performance? • because PureSystem is a Virtualized environment, very few ISVs have done perf testing on Virtualized system, it is not meaningful to compare runtime performance between physical system and virtualized system. • Auto-scaling performance might not beat ISV’s expectation. • From development team, we were told the VAP auto-scaling on average takes 15 mins, this is good, but not great. • In case ISV ask, this not HA/DR test (fault tolerance etc).

10. Call to action • Schedule your ISV validation engagement using AAA tool • Send ISV solution questionnaire and collect answers before they show up at IIC. • For ISVs that will do performance testing, seek legal approval on IBM using their quotes. • If ISV solution contains custom images, need to educate them on how to refresh their images with latest RHEL 6.2. • Questions? Contact Brian (binnes@uk.ibm.com) or Sherwood (syao@us.ibm.com)