DevOps: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
== Infrastructure as Code Paradigm == | ==Infrastructure as Code Paradigm== | ||
=== Automate Everything === | ===Automate Everything=== | ||
1. Redesign or reconfigure things so the task isn't necessary at all. <br/> | 1. Redesign or reconfigure things so the task isn't necessary at all. <br /> | ||
2. Implement automation that handles the task transparently, without anyone needing to pay attention. <br/> | 2. Implement automation that handles the task transparently, without anyone needing to pay attention. <br /> | ||
3. Implement a self-service tool so that the task can be done quickly, by someone who doesn't need to know the details, preferably the user or person who needs it done. <br/> | 3. Implement a self-service tool so that the task can be done quickly, by someone who doesn't need to know the details, preferably the user or person who needs it done. <br /> | ||
4. Write documentation so that users can easily carry out the task on their own. | 4. Write documentation so that users can easily carry out the task on their own. | ||
Yevgeniy Brikman, author of a book on Terraform and founder of Gruntwork, wrote a great summary of the book (which cannot be reproduced here because Goodreads apparently has exclusive rights over reviews. Never writing anything there again.)<br/> | Free resource to learn the basics: <br />https://assets.thoughtworks.com/assets/infrastructure-as-code/Infrastructure_as_Code_ThoughtWorks_Preview_Edition.pdf | ||
An excellent tutorial on the topic: <br />https://github.com/Artemmkin/infrastructure-as-code-tutorial | |||
Yevgeniy Brikman, author of a book on Terraform and founder of Gruntwork, wrote a great summary of the book (which cannot be reproduced here because Goodreads apparently has exclusive rights over reviews. Never writing anything there again.)<br /> | |||
https://www.goodreads.com/review/show/1808566933 | https://www.goodreads.com/review/show/1808566933 | ||
Revision as of 08:23, 13 March 2019
Infrastructure as Code Paradigm
Automate Everything
1. Redesign or reconfigure things so the task isn't necessary at all.
2. Implement automation that handles the task transparently, without anyone needing to pay attention.
3. Implement a self-service tool so that the task can be done quickly, by someone who doesn't need to know the details, preferably the user or person who needs it done.
4. Write documentation so that users can easily carry out the task on their own.
Free resource to learn the basics:
https://assets.thoughtworks.com/assets/infrastructure-as-code/Infrastructure_as_Code_ThoughtWorks_Preview_Edition.pdf
An excellent tutorial on the topic:
https://github.com/Artemmkin/infrastructure-as-code-tutorial
Yevgeniy Brikman, author of a book on Terraform and founder of Gruntwork, wrote a great summary of the book (which cannot be reproduced here because Goodreads apparently has exclusive rights over reviews. Never writing anything there again.)
https://www.goodreads.com/review/show/1808566933
