Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Andy West – Director of Technology Architecture, Pearson

1,190 views

Published on

RightScale User Conference NYC 2011

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Andy West – Director of Technology Architecture, Pearson

  1. 1. Welcome!<br />RIGHTSCALE USER CONFERENCECUSTOMER PRESENTATIONS<br />June 2011<br />
  2. 2. Andy West - Director of TechnologyPearsonRightScale Customer Presentations<br />
  3. 3. SuccessMaker in the Cloud<br />Images, Templates, Builds, Deployments, Management, Provisioning, and the rest of the Universe<br />
  4. 4. Elementary (K-8) <br />Essential concepts, skills, and strategies in reading and math<br />Adaptive initial placement learning<br />High stakes management reporting<br />15 years old with several platform incarnations<br />Currently in over 3500 schools with 2M kids<br />Successmaker.com<br />
  5. 5. Original Deployment Model<br />All software installed on a single server per school<br />Called it a ‘schoolhouse’ product<br />No district functionality or aggregated reporting<br />This was the SM2 release<br />
  6. 6. District Deployment Model<br />Deployed in district data center<br />Lots of reports<br />Release SM3<br />
  7. 7. What Our Customers Want<br />They want it all of course (!)<br />Lots of customers want hosted solutions while some actually ‘say’ they don’t<br />
  8. 8.
  9. 9.
  10. 10.
  11. 11.
  12. 12. Proxy Cache<br />A proxy cache can be used for local content delivery in the case of a slow WAN<br />Amazon Load Balancer<br />EC2 Instance<br />(Tomcat)<br />EC2 Instance<br />(Tomcat)<br />All static content is served from a content server farm<br />Content<br />
  13. 13. EC2 Instance<br />Amazon instances are provided according to scale needs. A single instance can be provisioned for a small district.<br />App Server<br />(Tomcat)<br />DB Server<br />(Postgres)<br />
  14. 14. Amazon Load Balancer<br />App Server Tier<br />EC2 Instance<br />(Tomcat)<br />EC2 Instance<br />(Tomcat)<br />Database Server Tier<br />EC2 Instance<br />(Postgres)<br />EC2 Instance<br />(Postgres)<br />
  15. 15. Management of Deployments<br />Automation, Automation, Automation<br />Desired: ‘pushbutton’ deployments<br />Desired: ‘definitional’ deployments<br />Desired: automatic recovery<br />Desired: monitoring and alerts<br />
  16. 16. Let’s talk (Deployment) Architecture<br />How to get from ‘named’ build to cloud server?<br />How to manage from an operations standpoint?<br />How to size the instances correctly? <br />What advantages/disadvantages over Pearson Data Center?<br />What are the opportunities for using ‘elastic’ provisioning?<br />
  17. 17. More (Deployment) Architecture<br />Several different configurations for different scale<br />Single server, dual server, multi-server<br />Tools and frameworks spread across servers<br />How to manage?<br />Considered ‘rolling our own’<br />Looked at Scalr, RightScale, Amazon console, Rackspace<br />
  18. 18.
  19. 19. Again with the Management<br />Automation, Automation, Automation<br />Desired: ‘pushbutton’ deployments<br />Desired: ‘definitional’ deployments<br />Desired: automatic recovery<br />Desired: monitoring and alerts<br />
  20. 20. Takeaway #1<br />Development team should design a deployment architecture<br />Loop in Operations as soon as you have a reasonable plan<br />Automate your application deployments(!)<br />
  21. 21. Instance Types and Sizing<br />Different instance types based on computing capacity and needs<br />Types: On Demand, Reserved, Spot <br />Testing strategy to incrementally move up <br />Combinatorial explosion of possibilities in multi-server configurations<br />
  22. 22. Takeaway #2<br /><ul><li>Be prepared to test capacity on lots of instance types
  23. 23. Forget about small instances in production</li></li></ul><li>Developer Usage<br />Each sprint team can now have its own environment<br />QA had already worked this out with a VM environment<br />Can help devs especially with QA since there is a bottleneck with ‘testing’ servers being available<br />
  24. 24. Takeaway #3<br />Developers will love the ability to provision themselves<br />Allow it to happen<br />Force it to happen<br />
  25. 25. Application Health<br />Monitor KPI’s like memory usage, CPU, local disk, etc. <br />Scripts are defined to alert based on thresholds<br />
  26. 26. Key Features of for Us<br />Automation, Automation, Automation<br />Allows ‘ServerTemplate’ definition<br />Includes all the scripts necessary to bring up a server<br />Allows input variables for ‘instance’ specific criteria such as tuning parameters<br />Allows ‘Deployment’ definition<br />A group of templates that work together<br />Allows input variables for ‘instance’ specific criteria such as a subdomain name<br />
  27. 27. More …<br />Monitoring<br />Uses tools installed with the template that can talk to the RightScale platform application<br />Macros<br />Enable higher level scripting of the deployments<br />User management<br />Can constrain access and control for deployments and templates<br />
  28. 28. Takeaway #4<br />Don’t shortchange operations involvement<br />Lead the way with the control and monitoring strategy for your app<br />
  29. 29. Summary<br />Engage all stakeholders early<br />Design a deployment architecture<br />Testing and automation are your friends<br />Use it now in development and testing<br />Pick a management strategy that will work for Operations<br />Etc.<br />Questions - andy.west@pearson.com<br />
  30. 30. We hope to see you at our next RightScale User Conference!<br />See all presentations and videos at RightScale.com/Conference.<br />

×