Manageability Matters

2,602 views

Published on

A presentation by Luke Kanies, the founder of the Puppet project, on why manageability matters during your development, and how considering it can make the difference between success and failure in the modern software world.

Published in: Technology, News & Politics
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,602
On SlideShare
0
From Embeds
0
Number of Embeds
72
Actions
Shares
0
Downloads
15
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Manageability Matters

  1. 1. Manageability Matters Luke Kanies Founder of the Puppet project luke@reductivelabs.com @puppetmasterd
  2. 2. Question Authority
  3. 3. Manageability
  4. 4. So you’re a software developer
  5. 5. And you’ve written some software
  6. 6. But no one’s using it
  7. 7. Marketing!
  8. 8. Docs!
  9. 9. Usability!
  10. 10. Docs || Usability
  11. 11. Good enough docs can skip usability
  12. 12. Good enough usability can skip docs
  13. 13. Two kinds of usability
  14. 14. Can I use it?
  15. 15. Can I configure it?
  16. 16. Not the same thing
  17. 17. Consumers? Sure
  18. 18. Enterprise? Not so much
  19. 19. Configuration is meta
  20. 20. Manageability is meta- usability
  21. 21. Or, manageability is usability for sysadmins
  22. 22. Two audiences for manageability
  23. 23. Humans
  24. 24. Machines
  25. 25. Gentoo is for humans
  26. 26. XML is for machines
  27. 27. You want the best of both worlds
  28. 28. Humans configure your software at first
  29. 29. Machines do it at scale
  30. 30. The costs of ignoring manageability
  31. 31. “I will have to second the recommendation for postfix. I was an old sendmail user and postfix configuration is a piece of cake by comparison.” http://forum.slicehost.com/comments.php?DiscussionID=153
  32. 32. It’s a Darwinian world
  33. 33. Manageability is the sysadmin selection mechanism
  34. 34. These people are haters
  35. 35. The users care, too
  36. 36. 2 mins to start a VM + 20 mins to configure your software = ?
  37. 37. You slow your customer down
  38. 38. MySQL started out in prototypes
  39. 39. You create more downtime
  40. 40. You piss them off
  41. 41. The benefits of manageability
  42. 42. No cost, all gravy
  43. 43. Users use it
  44. 44. Sysadmins don’t think about it
  45. 45. It gets plugged into everything
  46. 46. Is your software manageable?
  47. 47. Does it just work?
  48. 48. Are all of the inputs machine-produceable?
  49. 49. Are all of the outputs machine readable?
  50. 50. Yup
  51. 51. Manageability antipatterns
  52. 52. Turing-complete configuration languages
  53. 53. Tarball installation
  54. 54. Generating Configurations
  55. 55. An ecosystem around managing your software
  56. 56. Extremely profitable professional services
  57. 57. How do you avoid poor manageability?
  58. 58. Minimal, entirely optional configuration
  59. 59. Convention over configuration
  60. 60. Structured data everywhere
  61. 61. Subystems for everything
  62. 62. Complexity is modeled
  63. 63. Examples
  64. 64. A disclaimer
  65. 65. Software for humans
  66. 66. FreeBSD Some package Text management problems cannot be automated http://www.freebsd.org/layout/images/beastie.png
  67. 67. Where to start? http://www.oracle.com/index.html
  68. 68. Apache • Turing-complete configurations • Any file can hold any content • No conventions http://apache.org/images/feather.gif
  69. 69. Gentoo Every binary is unique http://www.gentoo.org/
  70. 70. Software for computers
  71. 71. Sendmail M4 to generate configurations And they’re still unusable
  72. 72. XML
  73. 73. Conclusion
  74. 74. Used more
  75. 75. Retained longer
  76. 76. Hated less
  77. 77. Questions?

×