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.

Cloud automation strategies

354 views

Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Cloud automation strategies

  1. 1. Automation:Delivering the Promise of Cloud Computing Teyo Tyree, Co-founder
  2. 2. How is the Cloud different?
  3. 3. On Demand
  4. 4. ~∞
  5. 5. fast
  6. 6. DuhOn Demand + ~∞ + Fast = Elastic
  7. 7. The promise of Cloud computing is to commoditize the availabilityof dynamic/scalable/fault tolerantcompute resources and to rapidly construct them to meet organizational needs.
  8. 8. How is the Cloud the same?
  9. 9. Applications
  10. 10. Murphy
  11. 11. + + + Murphy= “The same as it ever was”
  12. 12. Expectations
  13. 13. Automation
  14. 14. Images
  15. 15. What is awesome about images?
  16. 16. What is awesome about images? ✓ Fast
  17. 17. What is awesome about images? ✓ Fast ✓ Cloneable
  18. 18. What is awesome about images? ✓ Fast ✓ Cloneable ✓ Simple
  19. 19. What is not awesome about images?
  20. 20. What is not awesome about images? ✓ Opaque
  21. 21. What is not awesome about images? ✓ Opaque ✓ Unique
  22. 22. What is not awesome about images? ✓ Opaque ✓ Unique ✓ Static
  23. 23. Automated Configuration Management Approach
  24. 24. CM should provide the ability to:
  25. 25. CM should provide the ability to:✓ specify node configuration as a set of components
  26. 26. CM should provide the ability to:✓ specify node configuration as a set of components✓ specify the relationships between components
  27. 27. CM should provide the ability to:✓ specify node configuration as a set of components✓ specify the relationships between components✓ inspect the state of a node or component
  28. 28. CM should provide the ability to:✓ specify node configuration as a set of components✓ specify the relationships between components✓ inspect the state of a node or component✓ simulate synchronization to the spec
  29. 29. CM should provide the ability to:✓ specify node configuration as a set of components✓ specify the relationships between components✓ inspect the state of a node or component✓ simulate synchronization to the spec✓ build a query-able inventory
  30. 30. What is awesome about CM?
  31. 31. What is awesome about CM? ✓ Transparent
  32. 32. What is awesome about CM? ✓ Transparent ✓ Portable
  33. 33. What is awesome about CM? ✓ Transparent ✓ Portable ✓ Composable
  34. 34. What is awesome about CM? ✓ Transparent ✓ Portable ✓ Composable ✓ Dynamic
  35. 35. What is not awesome about CM?
  36. 36. What is not awesome about CM? ✓ Slower
  37. 37. What is not awesome about CM? ✓ Slower ✓ More complex
  38. 38. What is not awesome about CM? ✓ Slower ✓ More complex ✓ Overhead
  39. 39. What about a hybrid approach?
  40. 40. Use CM to build your images!
  41. 41. Hey, that sounds like building software?
  42. 42. Process:
  43. 43. Process:Develop configuration manifests.
  44. 44. Process:Develop configuration manifests.Build images using configurations manifests.
  45. 45. Process:Develop configuration manifests.Build images using configurations manifests.Validate that the image is built correctly.
  46. 46. Process:Develop configuration manifests.Build images using configurations manifests.Validate that the image is built correctly.Deploy images and complete any final configurationusing configuration management.
  47. 47. Hey, that smells like Devops.
  48. 48. What is awesome about a hybrid approach?
  49. 49. What is awesome about a hybrid approach? ✓ Fast
  50. 50. What is awesome about a hybrid approach? ✓ Fast ✓ Cloneable
  51. 51. What is awesome about a hybrid approach? ✓ Fast ✓ Cloneable ✓ Transparent
  52. 52. What is awesome about a hybrid approach? ✓ Fast ✓ Cloneable ✓ Transparent ✓ Portable
  53. 53. What is awesome about a hybrid approach? ✓ Fast ✓ Cloneable ✓ Transparent ✓ Portable ✓ Composable
  54. 54. What is awesome about a hybrid approach? ✓ Fast ✓ Cloneable ✓ Transparent ✓ Portable ✓ Composable
  55. 55. Cloud Agnostic
  56. 56. Adhoc Changes
  57. 57. Summary:
  58. 58. Summary:Images have limitations and are not generally sufficientto manage complex applications.
  59. 59. Summary:Images have limitations and are not generally sufficientto manage complex applications.Configuration Management can significantly slowdown provisioning time while providing transparency andcontrol.
  60. 60. Summary:Images have limitations and are not generally sufficientto manage complex applications.Configuration Management can significantly slowdown provisioning time while providing transparency andcontrol.A Hybrid approach can speed up deployment time whileproviding composable infrastructure component and atransparent image building process that better delivers thepromise of Cloud computing.
  61. 61. Questions?
  62. 62. @brainfinger

×