├── LICENCE ├── README.md └── katas ├── enigma.md └── etched-in-stone.md /LICENCE: -------------------------------------------------------------------------------- 1 | CC0 1.0 Universal 2 | 3 | Statement of Purpose 4 | 5 | The laws of most jurisdictions throughout the world automatically confer 6 | exclusive Copyright and Related Rights (defined below) upon the creator and 7 | subsequent owner(s) (each and all, an "owner") of an original work of 8 | authorship and/or a database (each, a "Work"). 9 | 10 | Certain owners wish to permanently relinquish those rights to a Work for the 11 | purpose of contributing to a commons of creative, cultural and scientific 12 | works ("Commons") that the public can reliably and without fear of later 13 | claims of infringement build upon, modify, incorporate in other works, reuse 14 | and redistribute as freely as possible in any form whatsoever and for any 15 | purposes, including without limitation commercial purposes. These owners may 16 | contribute to the Commons to promote the ideal of a free culture and the 17 | further production of creative, cultural and scientific works, or to gain 18 | reputation or greater distribution for their Work in part through the use and 19 | efforts of others. 20 | 21 | For these and/or other purposes and motivations, and without any expectation 22 | of additional consideration or compensation, the person associating CC0 with a 23 | Work (the "Affirmer"), to the extent that he or she is an owner of Copyright 24 | and Related Rights in the Work, voluntarily elects to apply CC0 to the Work 25 | and publicly distribute the Work under its terms, with knowledge of his or her 26 | Copyright and Related Rights in the Work and the meaning and intended legal 27 | effect of CC0 on those rights. 28 | 29 | 1. Copyright and Related Rights. A Work made available under CC0 may be 30 | protected by copyright and related or neighboring rights ("Copyright and 31 | Related Rights"). Copyright and Related Rights include, but are not limited 32 | to, the following: 33 | 34 | i. the right to reproduce, adapt, distribute, perform, display, communicate, 35 | and translate a Work; 36 | 37 | ii. moral rights retained by the original author(s) and/or performer(s); 38 | 39 | iii. publicity and privacy rights pertaining to a person's image or likeness 40 | depicted in a Work; 41 | 42 | iv. rights protecting against unfair competition in regards to a Work, 43 | subject to the limitations in paragraph 4(a), below; 44 | 45 | v. rights protecting the extraction, dissemination, use and reuse of data in 46 | a Work; 47 | 48 | vi. database rights (such as those arising under Directive 96/9/EC of the 49 | European Parliament and of the Council of 11 March 1996 on the legal 50 | protection of databases, and under any national implementation thereof, 51 | including any amended or successor version of such directive); and 52 | 53 | vii. other similar, equivalent or corresponding rights throughout the world 54 | based on applicable law or treaty, and any national implementations thereof. 55 | 56 | 2. Waiver. To the greatest extent permitted by, but not in contravention of, 57 | applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and 58 | unconditionally waives, abandons, and surrenders all of Affirmer's Copyright 59 | and Related Rights and associated claims and causes of action, whether now 60 | known or unknown (including existing as well as future claims and causes of 61 | action), in the Work (i) in all territories worldwide, (ii) for the maximum 62 | duration provided by applicable law or treaty (including future time 63 | extensions), (iii) in any current or future medium and for any number of 64 | copies, and (iv) for any purpose whatsoever, including without limitation 65 | commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes 66 | the Waiver for the benefit of each member of the public at large and to the 67 | detriment of Affirmer's heirs and successors, fully intending that such Waiver 68 | shall not be subject to revocation, rescission, cancellation, termination, or 69 | any other legal or equitable action to disrupt the quiet enjoyment of the Work 70 | by the public as contemplated by Affirmer's express Statement of Purpose. 71 | 72 | 3. Public License Fallback. Should any part of the Waiver for any reason be 73 | judged legally invalid or ineffective under applicable law, then the Waiver 74 | shall be preserved to the maximum extent permitted taking into account 75 | Affirmer's express Statement of Purpose. In addition, to the extent the Waiver 76 | is so judged Affirmer hereby grants to each affected person a royalty-free, 77 | non transferable, non sublicensable, non exclusive, irrevocable and 78 | unconditional license to exercise Affirmer's Copyright and Related Rights in 79 | the Work (i) in all territories worldwide, (ii) for the maximum duration 80 | provided by applicable law or treaty (including future time extensions), (iii) 81 | in any current or future medium and for any number of copies, and (iv) for any 82 | purpose whatsoever, including without limitation commercial, advertising or 83 | promotional purposes (the "License"). The License shall be deemed effective as 84 | of the date CC0 was applied by Affirmer to the Work. Should any part of the 85 | License for any reason be judged legally invalid or ineffective under 86 | applicable law, such partial invalidity or ineffectiveness shall not 87 | invalidate the remainder of the License, and in such case Affirmer hereby 88 | affirms that he or she will not (i) exercise any of his or her remaining 89 | Copyright and Related Rights in the Work or (ii) assert any associated claims 90 | and causes of action with respect to the Work, in either case contrary to 91 | Affirmer's express Statement of Purpose. 92 | 93 | 4. Limitations and Disclaimers. 94 | 95 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 96 | surrendered, licensed or otherwise affected by this document. 97 | 98 | b. Affirmer offers the Work as-is and makes no representations or warranties 99 | of any kind concerning the Work, express, implied, statutory or otherwise, 100 | including without limitation warranties of title, merchantability, fitness 101 | for a particular purpose, non infringement, or the absence of latent or 102 | other defects, accuracy, or the present or absence of errors, whether or not 103 | discoverable, all to the greatest extent permissible under applicable law. 104 | 105 | c. Affirmer disclaims responsibility for clearing rights of other persons 106 | that may apply to the Work or any use thereof, including without limitation 107 | any person's Copyright and Related Rights in the Work. Further, Affirmer 108 | disclaims responsibility for obtaining any necessary consents, permissions 109 | or other rights required for any use of the Work. 110 | 111 | d. Affirmer understands and acknowledges that Creative Commons is not a 112 | party to this document and has no duty or obligation with respect to this 113 | CC0 or use of the Work. 114 | 115 | For more information, please see 116 | 117 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Devops katas 2 | 3 | A kata is an exercise performed repeatedly with deliberate intent to improve with each iteration. 4 | 5 | A DevOps kata is an exercise designed to make you think deeply about problems and patterns 6 | that occur repeatedly in the world of DevOps. 7 | 8 | Get started with one of the [katas](#list-of-katas). 9 | 10 | Read the [FAQs](#faqs) to know more. 11 | 12 | This collection of katas is intended to be created and curated by the community, 13 | we welcome your [contributions](#contributing). 14 | 15 | This work is licenced under CC0, so feel free to 16 | use it as you see fit. 17 | 18 | ## List of katas 19 | 20 | - [Etched In Stone](katas/etched-in-stone.md) 21 | - [Enigma](katas/enigma.md) 22 | 23 | # FAQs 24 | 25 | ## Where are the katas? 26 | 27 | Katas are located in the [katas](katas/) directory. They all have unique names. 28 | They are not in any particular order, feel free to start with any that you find interesting. 29 | 30 | You can contribute your own katas. To know how, look at the [Contributing](#contributing) section. 31 | 32 | ## Tell me more about kata 33 | 34 | To paraphrase from the [Wikipedia entry on kata](http://en.wikipedia.org/wiki/kata): 35 | 36 | The basic goal of kata is to preserve and transmit proven patterns and techniques. 37 | By practicing in a repetitive manner the learner develops the ability to execute those patterns and techniques in a natural, reflex-like manner. Systematic practice does not mean permanently rigid. The goal is to internalize the patterns and techniques of a kata so they can be executed and adapted under different circumstances, without thought or hesitation. 38 | 39 | ## Tell me more about DevOps kata 40 | 41 | In order to define a DevOps kata, we must first define DevOps. The philosophy is that you want to adopt practices that enable you to build quality and flexibility into your software. You also want to adopt a culture that enables members of your team to collaborate effectively. 42 | 43 | Coming back to DevOps kata, perhaps it is best to start with an example: 44 | 45 | Make a change to a web application without taking it down. Users must not be interrupted at any time during the change. 46 | 47 | This can be solved in different ways - for example perform rolling restarts on your application server, OR 48 | provision an entirely new server and switch over your load balancer. Each approach 49 | has costs and benefits. Practicing them both will let you make a better informed decision the next 50 | time such a requirement comes up. 51 | 52 | We do these things regularly, but a kata would let you take a more systematic approach to things, 53 | by writing down what you did and sharing it with a wider audience for feedback. 54 | 55 | ## Contributing 56 | 57 | A good DevOps kata: 58 | 59 | - has a tangible objective 60 | - is a common problem/pattern addressed by DevOps 61 | - is solvable in more than one way 62 | - is designed to help a learner get better 63 | - is framed as a question and a set of considerations that guide the learner along 64 | 65 | This repository is built by and for the community. We would love to get inputs from you. 66 | Feel free to add your own kata in the katas directory and send us a PR. 67 | Remember to also add the kata to the list of katas on this README. 68 | 69 | ## See also 70 | 71 | [CodeKata](http://codekata.com/) 72 | 73 | ## License 74 | 75 | CC0 1.0 Universal 76 | -------------------------------------------------------------------------------- /katas/enigma.md: -------------------------------------------------------------------------------- 1 | # Enigma 2 | 3 | [Enigma](http://en.wikipedia.org/wiki/Cryptanalysis_of_the_Enigma) is the name of 4 | the machine that allowed the Germans to encrypt their radio messages during the 5 | Second World War. Alan Turing's work on breaking the Enigma cipher is considered 6 | to have played a crucial role in the Allies winning the war. 7 | 8 | In today's world of SaaS applications, with consumer keys and secrets, you are faced with the constant threat of your keys being discovered and your systems being hacked. 9 | 10 | This kata is about protecting your secrets - such as service credentials, database 11 | passwords, etc. For example, if you use Stripe to process payments, you don't 12 | store credit card details. But you do store tokens that identify the card on Stripe. 13 | What if your tokens and Stripe API key got stolen? It is almost as bad as losing 14 | the credit cards themselves. 15 | 16 | So, how do you keep your secrets *secret*? Here are a few questions to guide you: 17 | 18 | - How many secrets do you have? Where do they live? 19 | 20 | - Who all can see the secrets? 21 | 22 | - Are your secrets ephemeral or persistent on your systems - for e.g. environment 23 | variables are scoped to the lifetime of the shell, while files live for ever. 24 | 25 | - Are your secrets of the right kind? For example would a key be better than 26 | a username/password? 27 | 28 | - Are your secrets in source control? Is that a risk? 29 | 30 | - Is your sensitive data encrypted at rest? Should that credit card token DB 31 | be encrypted? 32 | 33 | - Do you need encryption or one-way transforms for each kind of secret? For example 34 | passwords are better saved as one-way transforms with high work factors (for e.g. bcrypt) 35 | 36 | - Can you cycle your secrets if you suspect a security breach? How quickly can 37 | you cycle and expire compromised credentials? 38 | 39 | 40 | Remember, that these questions are intended to serve as guide posts. You may want to get started 41 | with attacking the simple problems first, and as you gain confidence, think about the harder problems. 42 | 43 | The goal of kata is not to get things done in a rush, but to contemplate the 'why' of things. So, 44 | take your time, and enjoy yourself. 45 | -------------------------------------------------------------------------------- /katas/etched-in-stone.md: -------------------------------------------------------------------------------- 1 | # Etched In Stone 2 | 3 | Anthropologists have found stone carvings with pre-historic writing in an excellent state of 4 | preservation. Modern data unfortunately is not as resilient! Data loss or corruption happens, 5 | due to a variety of reasons - power outages, disks going bad, etc. 6 | 7 | This kata is about having a plan B. How do you ensure that your database is backed up at regular intervals? 8 | 9 | Think about factors like: 10 | - How often do you take backups? 11 | - Where are backups stored - no point storing them on the same disk as the data, right?! 12 | - Can backups be quickly and easily restored? 13 | - Is the backup process automated? 14 | - Do you have confidence that the backups you generate are valid? 15 | - Are there different strategies for relational v/s NoSQL DBs? 16 | - What if your DB is distributed with eventual consistency - where do you take backups from? 17 | 18 | Remember, that these questions are intended to serve as guide posts. You may want to get started 19 | with attacking the simple problems first, and as you gain confidence, think about the harder problems. 20 | 21 | The goal of kata is not to get things done in a rush, but to contemplate the 'why' of things. So, 22 | take your time, and enjoy yourself. 23 | --------------------------------------------------------------------------------