Accelerating Organizations with Flexible IT - AWS Summit 2012 - NYC
•
1 gostou•784 visualizações
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (20)
Semelhante a Accelerating Organizations with Flexible IT - AWS Summit 2012 - NYC
Semelhante a Accelerating Organizations with Flexible IT - AWS Summit 2012 - NYC (20)
Mais de Amazon Web Services
Mais de Amazon Web Services (20)
Último
Último (20)
Accelerating Organizations with Flexible IT - AWS Summit 2012 - NYC
- 1. Accelerating Organizations with Flexible IT Dr. Matt Wood
- 2. Welcome to the Executive Track Migration and adoption, TCO, security, use cases
- 3. Infrastructure building blocks Storage, compute, databases and orchestration tools.
- 4. 10 gigabit non-blocking, full duplex Ethernet placement groups
- 5. 10 gigabit non-blocking, full duplex Ethernet placement groups
- 6. How can these services help your business?
- 7. Concept Release
- 8. 70% Concept Release Undifferentiated heavy lifting
- 9. 70% Concept Release Core competency
- 10. Information Technology for competitive advantage Remove constraints. Decrease time to market.
- 11. Focus
- 12. Flexibility, speed and agility Increased productivity. Reduced cap-ex.
- 13. Full spectrum of teams and businesses Start-up. SMB. Enterprise. Social gaming. Life sciences. Government.
- 14. Why?
- 15. How?
- 16. On board Cloud adoption and migration strategy. Full application life cycle. New service adoption.
- 17. 1. Adoption and migration 2. Pro tips for integration
- 18. 1. Adoption and migration 2. Pro tips for integration
- 19. Towards cloud benefits On-demand provisioning. Scale. Automation.
- 20. New applications “Cloud ready” design Cloud Strategy Existing Applications Planned migration
- 21. Cloud ready architectures Design for availability. Build for failure. Elastic. Decoupled. Automated. Price aware.
- 22. New applications “Cloud ready” design Cloud Strategy Existing Applications Planned migration
- 24. Assessment Select service or product which will result in a successful migration.
- 25. Collect and classify IT assets Build a dependency tree of services and products.
- 26. Dash board Web CRM Auth LDAP Service DB Search OLAP Engine ERP Report Logs
- 27. Dash board Security class Compliance requirements Web CRM Auth Internal, partner, external Coupling DB LDAP Service Licensing requirements Search OLAP Engine ERP Report Logs
- 28. Identify a good migration target Low impact in terms of security level, compliance, coupling and licensing.
- 29. Identify a good migration target Web applications, batch processing, development and build systems, CMS, asset management.
- 30. Successful migration Create awareness and enthusiasm.
- 32. Start a proof of concept project Build experience with the AWS cloud platform
- 33. Dive in to AWS Up and running quickly
- 34. Map AWS services to requirements Relational database or NoSQL model
- 35. Don’t retool unnecessarily Flexible platform. Bring existing tools and skills.
- 38. Validate infrastructure for legacy projects Due diligence. Benchmark. Trust but validate.
- 40. Data migration Move datasets to the cloud. Canonical source for collaboration.
- 41. Data migration Data mobility services can help: Multipart upload. AWS Direct Connect. Import/Export.
- 42. Data migration Encryption where necessary.
- 43. AWS Storage Gateway On-premise software appliance to backup data to S3. 99.999999999% durability. Disaster recovery.
- 44. Application migration Automate where appropriate. Machine images via VM Import.
- 45. “Forklift” migration Move full application stack as one. Good for simple n-tier applications and tightly coupled products.
- 46. “Forklift” migration Traditional Data Center AWS cloud Billing Search Service service Billing Search DB DB Full application stack
- 47. “Forklift” migration Traditional Data Center AWS Cloud Billing Search Billing Service service Service Billing Search Billing DB DB DB Full application Full application stack stack
- 48. Service oriented migration Encapsulated services
- 49. Service Migration Traditional Data Center AWS cloud Process Search Billing
- 50. Service Migration Traditional Data Center AWS cloud Process Search Search Billing
- 51. Service Migration Traditional Data Center AWS cloud Process Search Search Billing
- 52. Service Migration Traditional Data Center AWS cloud Process Search Search Billing Billing
- 53. Minimize service disruption Plan migration. Spin up, test, rewire.
- 54. Storage and backup Plan storage and automated backup schedule. Test.
- 56. Maximize cloud benefits High availability. Automation.
- 57. Evaluate and adopt new cloud services Rapid pace of innovation.
- 58. Relational database < Amazon RDS Remove undifferentiated heavy lifting.
- 59. Message queues < Amazon Simple Workflow Remove undifferentiated heavy lifting.
- 60. NoSQL < DynamoDB Remove undifferentiated heavy lifting.
- 61. Make elasticity a first class goal Increase availability. Scale. Decrease costs.
- 62. Optimize for cost Utilize pricing options: reserved capacity, spot instances.
- 63. Optimize for cost 19 price drops
- 65. The ex.fm story Lucas Hrabovsky, CTO
- 66. Start with AWS Previous Experience with Colos Used EC2 and S3 from the start Manage instances using Fabric Use Identity Access Management
- 67. Embrace Elasticity and Ephemerality Easily handle unexpected successes “Let’s try a different machine configuration” “Where’d the database go?”
- 68. Move Dev Machines to Instances Dev box and production box look exactly alike Update packages & configuration silently Use cheats to replace lack of GUI’s • bit.ly/exfmgitcheatsheet Bonus: sharing and collaboration
- 69. Move to Managed Services Cloudsearch • bit.ly/exfmcloudsearch Avoiding lock-in Anticipated next steps: Apache Zookeeper, and more Focus more on your application; less on infrastructure
- 70. 1. Adoption and migration 2. Pro tips for integration
- 71. Or… Five things we’ve learnt working with customers
- 72. 1. Educate and evangelize Build a culture of knowledge exchange and enthusiasm. Drive by successful proof of concepts and migrations.
- 73. 2. Engage stakeholders Early. Often. Regular sync/stand-up meetings. Define success criteria.
- 74. 3. Engage with AWS Self-service platform. Engagement driven by customers. Solutions Architecture team ready to help.
- 75. 4. Understand and evaluate service offering Ephemeral. Block. Object. Relational. NoSQL. Batch processing. Hadoop. Security. Compliance. TCO.
- 76. 5. Pro-actively adopt new services Rapid release. Significant competitive advantage.
- 77. 1. Adoption and migration Cloud adoption and migration best practices. Full application life cycle.
- 78. 1. Adoption and migration Cloud adoption and migration best practices. Full application life cycle. 2. Pro tips for integration Engage early and often. Educate. Success criteria.
- 79. Thank you!
Notas do Editor
- Previous ExperiencesLate night colo runs to restart machinesHave to pay union fee to bring in new hardware through the freight elevator“Where’d that disk go?”Ever had to move colos in the middle of the night?All that being said, didn’t want to deal with any of that again.Use micros, larges, XL’s and 2XL’s. Assets, like avatars, embeddable assets served directly from S3. Can’t wait to get more integration with cloudfront.No one offs. Everything scripted and reproducible. Use the excellent python package Fabric. Handles everything from launching new instances, installing packages to deploys.Also a big user of IAM. Every dev gets their own console login and keys. Easily have “app” users. Isolated set of keys we can rotate out through configuration.
- Easily handle unexpected successUh… requests just doubledAdd 2 new app servers and back to normalDon’t autoscale now, but shouldLet’s try a different configuration different instance sizes CPU vs RAM vs Disk Typically, you rack three classes of machines: LB App DB What if things change? Switch from memcache to redis?Where’d the database go?I misconfigured RAID for shared MongoDBFix RAID configuration script, launch new instanceNo cab fare to run to colo
- Dev box looks exactly like a production box just smaller. Same stack. Nginx, uwsgi. Each can be independent or share data sources.Micros extremely cost effective.Actually must faster cycle time than running locallyBringing up a new dev instance takes less than 5 minutes. Even adds cnames for itself in route53Update packages & configuration silently Reuse all ops scriptingDownside: No more git GUI’s...Everyone please make your way to the command lineFrontend team more comfortable with Github for Mac or GitX Not an option as the fuse mount is just to slow Simplify git with bash aliases bit.ly/exfmgitcheatsheetJust need to know four commands a, c, f, pMuch easier to share prototypesCollab between stakeholdersGive sneak peaks to users, investors, friends and family
- Pay now for scalability instead of having to make longer term investments Over hiring too soon Sinking dev time into solutions that may not pan outCloudsearch. Been running in production for 4 months now. 15 minutes of downtime. Scales itself out of the box. Horizontal / vertical scaling. For free.Not concerned about lock in. There are open source solutions that can all of this. But need bigger more long term investments More self maintained instances More specialized hiresLooking forward to even more managed services in the future. Currently use mongoDB and Redis. DynamoDB extremely attractive. What would really round things out for us and solve yet another set of problems would be a managed apache zookeeper for distributed configuration management and cluster coordination Worry about the app, not Solr or mysql configuration and maintenance. Oops one of the shard instances died.