├── LICENSE ├── README.md ├── ansible_hosts ├── group_vars └── README.md ├── host_vars └── README.md ├── hosts ├── README.md ├── production └── staging ├── infrastructure.yml ├── roles ├── __layout_template__ │ ├── files │ │ └── README.md │ ├── handlers │ │ └── README.md │ ├── meta │ │ └── README.md │ ├── tasks │ │ └── README.md │ ├── templates │ │ └── README.md │ └── vars │ │ └── README.md ├── apache │ ├── handlers │ │ └── main.yml │ └── tasks │ │ └── main.yml ├── mongodb │ ├── files │ │ ├── mongod.conf │ │ └── mongodb.list │ ├── handlers │ │ └── main.yml │ └── tasks │ │ └── main.yml ├── nagios │ ├── handlers │ │ └── main.yml │ ├── tasks │ │ └── main.yml │ └── vars │ │ └── main.yml ├── nginx │ ├── handlers │ │ └── main.yml │ └── tasks │ │ └── main.yml ├── postgres │ ├── handlers │ │ └── main.yml │ └── tasks │ │ └── main.yml ├── rabbitmq │ ├── files │ │ └── rabbitmq.list │ ├── handlers │ │ └── main.yml │ └── tasks │ │ └── main.yml └── redis │ ├── files │ ├── redis-server │ └── redis.conf │ ├── handlers │ └── main.yml │ └── tasks │ └── main.yml └── vars ├── centos.yml ├── debian.yml └── ubuntu.yml /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | {one line to give the program's name and a brief idea of what it does.} 635 | Copyright (C) {year} {name of author} 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | {project} Copyright (C) {year} {fullname} 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ansible-playbooks 2 | ================= 3 | 4 | Ansible playbooks for basic installation of different components. 5 | 6 | Playbooks are written following ansible best practices. It makes use of ansible role framework and different modules. It ensures that consecutive execution of playbooks are safe. It is safe to be deployed as a cron job. 7 | 8 | -------------------------------------------------------------------------------- /ansible_hosts: -------------------------------------------------------------------------------- 1 | [all] 2 | ansible-test 3 | -------------------------------------------------------------------------------- /group_vars/README.md: -------------------------------------------------------------------------------- 1 | # Group variables 2 | 3 | Add ansible group variables to be used by playbooks. 4 | -------------------------------------------------------------------------------- /host_vars/README.md: -------------------------------------------------------------------------------- 1 | # Host variables 2 | 3 | Add ansible host variables to be used by playbooks. 4 | -------------------------------------------------------------------------------- /hosts/README.md: -------------------------------------------------------------------------------- 1 | # Hosts 2 | 3 | Inventory for storing server detsils. 4 | 5 | - production: Contains all production servers 6 | - staging: Contains all staging servers 7 | 8 | -------------------------------------------------------------------------------- /hosts/production: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rohit01/ansible-playbooks/1c81c82762bdd0c606b6d7fb29528aada507d2e0/hosts/production -------------------------------------------------------------------------------- /hosts/staging: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rohit01/ansible-playbooks/1c81c82762bdd0c606b6d7fb29528aada507d2e0/hosts/staging -------------------------------------------------------------------------------- /infrastructure.yml: -------------------------------------------------------------------------------- 1 | --- 2 | - hosts: all 3 | gather_facts: yes 4 | user: rohit 5 | sudo: yes 6 | vars: 7 | is_centos: "'{{ ansible_distribution|lower }}' == 'centos'" 8 | is_debian: "'{{ ansible_distribution|lower }}' == 'debian'" 9 | is_ubuntu: "'{{ ansible_distribution|lower }}' == 'ubuntu'" 10 | vars_files: 11 | - "vars/{{ ansible_distribution|lower }}.yml" 12 | 13 | roles: 14 | # Configured for nagios installation 15 | - { role: apache } 16 | - { role: nagios } 17 | -------------------------------------------------------------------------------- /roles/__layout_template__/files/README.md: -------------------------------------------------------------------------------- 1 | # Files 2 | 3 | Files for use with the copy module. 4 | 5 | -------------------------------------------------------------------------------- /roles/__layout_template__/handlers/README.md: -------------------------------------------------------------------------------- 1 | # Handlers 2 | 3 | Store handlers for the role. 4 | 5 | -------------------------------------------------------------------------------- /roles/__layout_template__/meta/README.md: -------------------------------------------------------------------------------- 1 | # Meta 2 | 3 | Role dependencies. 4 | 5 | -------------------------------------------------------------------------------- /roles/__layout_template__/tasks/README.md: -------------------------------------------------------------------------------- 1 | # Tasks 2 | 3 | Main playbook for executing tasks. 4 | 5 | -------------------------------------------------------------------------------- /roles/__layout_template__/templates/README.md: -------------------------------------------------------------------------------- 1 | # Templates 2 | 3 | Store jinja templates here. 4 | 5 | -------------------------------------------------------------------------------- /roles/__layout_template__/vars/README.md: -------------------------------------------------------------------------------- 1 | # Vars 2 | 3 | Define role level variables here. 4 | 5 | -------------------------------------------------------------------------------- /roles/apache/handlers/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | # Handler to handle common notifications. Handlers are called by other plays. 3 | # See http://ansible.cc/docs/playbooks.html for more information about handlers. 4 | 5 | - name: restart apache 6 | service: name={{ apache }} state=restarted 7 | -------------------------------------------------------------------------------- /roles/apache/tasks/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | # Apache installation 3 | - name: install apache 4 | yum: pkg={{ item }} state=present 5 | with_items: 6 | - php 7 | - httpd 8 | - libsemanage-python 9 | - libselinux-python 10 | when: is_centos 11 | 12 | - name: install apache 13 | apt: update_cache=yes cache_valid_time=86400 name={{ item }} state="present" 14 | with_items: 15 | - apache2 16 | - php5-gd 17 | - libgd2-xpm 18 | - libgd2-xpm-dev 19 | - libapache2-mod-php5 20 | when: is_debian 21 | 22 | - name: install apache 23 | apt: update_cache=yes cache_valid_time=86400 name={{ item }} state="present" 24 | with_items: 25 | - apache2 26 | - php5-gd 27 | - libgd2-xpm-dev 28 | - libapache2-mod-php5 29 | when: is_ubuntu 30 | 31 | - name: Activate Apache cgi on Ubuntu 14.04 32 | file: src=/etc/apache2/mods-available/cgi.load dest=/etc/apache2/mods-enabled/cgi.load state=link owner=root group=root 33 | notify: restart apache 34 | when: is_ubuntu 35 | 36 | - name: http service state 37 | service: name={{ apache }} state=started enabled=yes 38 | -------------------------------------------------------------------------------- /roles/mongodb/files/mongod.conf: -------------------------------------------------------------------------------- 1 | # mongod.conf 2 | 3 | # Where to store the data. 4 | 5 | # Note: if you run mongodb as a non-root user (recommended) you may 6 | # need to create and set permissions for this directory manually, 7 | # e.g., if the parent directory isn't mutable by the mongodb user. 8 | dbpath=/var/lib/mongodb 9 | 10 | #where to log 11 | logpath=/var/log/mongodb/mongod.log 12 | 13 | logappend=true 14 | 15 | #port = 27017 16 | 17 | # Listen to local interface only. Comment out to listen on all interfaces. 18 | bind_ip = 127.0.0.1 19 | 20 | # Disables write-ahead journaling 21 | # nojournal = true 22 | 23 | # Enables periodic logging of CPU utilization and I/O wait 24 | #cpu = true 25 | 26 | # Turn on/off security. Off is currently the default 27 | #noauth = true 28 | #auth = true 29 | 30 | # Verbose logging output. 31 | #verbose = true 32 | 33 | # Inspect all client data for validity on receipt (useful for 34 | # developing drivers) 35 | #objcheck = true 36 | 37 | # Enable db quota management 38 | #quota = true 39 | 40 | # Set oplogging level where n is 41 | # 0=off (default) 42 | # 1=W 43 | # 2=R 44 | # 3=both 45 | # 7=W+some reads 46 | #diaglog = 0 47 | 48 | # Ignore query hints 49 | #nohints = true 50 | 51 | # Disable the HTTP interface (Defaults to localhost:28017). 52 | #nohttpinterface = true 53 | 54 | # Turns off server-side scripting. This will result in greatly limited 55 | # functionality 56 | #noscripting = true 57 | 58 | # Turns off table scans. Any query that would do a table scan fails. 59 | #notablescan = true 60 | 61 | # Disable data file preallocation. 62 | #noprealloc = true 63 | 64 | # Specify .ns file size for new databases. 65 | # nssize = 66 | 67 | # Replication Options 68 | 69 | # in replicated mongo databases, specify the replica set name here 70 | #replSet=setname 71 | # maximum size in megabytes for replication operation log 72 | #oplogSize=1024 73 | # path to a key file storing authentication info for connections 74 | # between replica set members 75 | #keyFile=/path/to/keyfile 76 | -------------------------------------------------------------------------------- /roles/mongodb/files/mongodb.list: -------------------------------------------------------------------------------- 1 | deb http://downloads-distro.mongodb.org/repo/ubuntu-upstart dist 10gen 2 | -------------------------------------------------------------------------------- /roles/mongodb/handlers/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | # Handler to handle common notifications. Handlers are called by other plays. 3 | # See http://ansible.cc/docs/playbooks.html for more information about handlers. 4 | 5 | - name: restart mongod 6 | service: name=mongod state=restarted 7 | -------------------------------------------------------------------------------- /roles/mongodb/tasks/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | ## MongoDB installation 3 | - name: Add mongodb apt key 4 | apt_key: keyserver="hkp://keyserver.ubuntu.com:80" id="7F0CEB10" state="present" 5 | register: mongodb_apt_key 6 | 7 | - name: Add MongoDB apt repository 8 | copy: src=mongodb.list dest=/etc/apt/sources.list.d/mongodb.list 9 | register: mongodb_apt_repo 10 | 11 | - name: "Update apt cache - apt-get update" 12 | apt: update_cache=yes 13 | when: mongodb_apt_key.changed or mongodb_apt_repo.changed 14 | 15 | - name: Install MongoDB 16 | apt: update_cache=yes cache_valid_time=86400 name="mongodb-org" state=present 17 | 18 | - name: "Setting '/var/log/mongodb' directory permissions" 19 | file: dest=/var/log/mongodb owner=mongodb group=mongodb recurse=yes state=directory 20 | notify: restart mongodb 21 | 22 | - name: "Setting '/var/lib/mongodb' directory permissions" 23 | file: dest=/var/lib/mongodb owner=mongodb group=mongodb recurse=yes state=directory 24 | notify: restart mongodb 25 | 26 | - name: Copy MongoDB config file 27 | copy: src=mongod.conf dest=/etc/mongod.conf 28 | notify: restart mongod 29 | 30 | - name: Enable MongoDB to start on boot 31 | service: name=mongod runlevel="2345" enabled="yes" state="started" 32 | -------------------------------------------------------------------------------- /roles/nagios/handlers/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | # Nagios handlars 3 | - name: restart apache 4 | service: name={{ apache }} state=restarted 5 | 6 | 7 | -------------------------------------------------------------------------------- /roles/nagios/tasks/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | # Nagios installation 3 | - name: Ensure download directory is present 4 | file: path={{ ansible_env.HOME }}/nagios state="directory" 5 | 6 | - name: Downloading the EPEL repository definitions. 7 | get_url: url=http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm dest={{ ansible_env.HOME }}/nagios/epel-release-6-8.noarch.rpm 8 | when: is_centos 9 | 10 | - name: Downloading and enable the EPEL repository definitions. 11 | yum: name={{ ansible_env.HOME }}/nagios//epel-release-6-8.noarch.rpm state=present 12 | when: is_centos 13 | 14 | - name: Install Nagios prerequisites for CentOS 15 | yum: pkg={{ item }} state=present 16 | with_items: 17 | - gcc 18 | - glibc 19 | - glibc-common 20 | - gd 21 | - gd-devel 22 | - make 23 | - perl 24 | - perl-devel 25 | - wget 26 | - python-passlib 27 | when: is_centos 28 | 29 | - name: Install Nagios prerequisites for Debian 30 | apt: update_cache=yes cache_valid_time=86400 name={{ item }} state="present" 31 | with_items: 32 | - linux-headers-{{ ansible_kernel }} 33 | - build-essential 34 | - python-passlib 35 | when: is_debian 36 | 37 | - name: Install Nagios prerequisites for Ubuntu 38 | apt: update_cache=yes cache_valid_time=86400 name={{ item }} state="present" 39 | with_items: 40 | - linux-headers-{{ ansible_kernel }} 41 | - build-essential 42 | - python-passlib 43 | when: is_ubuntu 44 | 45 | - name: Install plugin prerequisites for CentOS 46 | yum: pkg={{ item }} state=present 47 | with_items: 48 | - openssl-devel 49 | - fping 50 | - openldap-devel 51 | - postgresql-devel 52 | - radiusclient-ng-devel 53 | - samba-client 54 | - libsmbclient 55 | when: is_centos 56 | 57 | - name: Install Plugin prerequisites for Debian 58 | apt: update_cache=yes cache_valid_time=86400 name={{ item }} state="present" 59 | with_items: 60 | - libssl-dev 61 | - dnsutils 62 | - fping 63 | - libldap2-dev 64 | - libpq-dev 65 | - libradiusclient-ng-dev 66 | - smbclient 67 | - gawk 68 | when: is_debian 69 | 70 | - name: Install Plugin prerequisites for Ubuntu 71 | apt: update_cache=yes cache_valid_time=86400 name={{ item }} state="present" 72 | with_items: 73 | - libssl-dev 74 | - dnsutils 75 | - fping 76 | - libldap2-dev 77 | - libpq-dev 78 | - libradiusclient-ng-dev 79 | - smbclient 80 | - gawk 81 | when: is_ubuntu 82 | 83 | - name: Create nagcmd group 84 | group: name=nagcmd state=present 85 | 86 | - name: Create nagios user 87 | user: name=nagios state=present groups=nagcmd 88 | 89 | - name: Add apache user to nagcmd group 90 | user: name={{ apacheuser }} state=present groups=nagcmd 91 | 92 | - name: GET Nagios 93 | get_url: url={{ nagiosurl }} dest={{ ansible_env.HOME }}/nagios/{{ nagiossrc }}.tar.gz 94 | 95 | - name: Get Plugins 96 | get_url: url={{ pluginsurl }} dest={{ ansible_env.HOME }}/nagios/{{ pluginssrc }}.tar.gz 97 | 98 | - name: Get NRPE 99 | get_url: url={{ nrpeurl }} dest={{ ansible_env.HOME }}/nagios/{{ nrpesrc }}.tar.gz 100 | 101 | - name: Unpack Nagios source files 102 | shell: cd {{ ansible_env.HOME }}/nagios && tar -xzvf {{ nagiossrc }}.tar.gz creates={{ ansible_env['HOME'] }}/nagios/{{ nagiossrc }} 103 | 104 | - name: Configure 105 | shell: cd {{ ansible_env.HOME }}/nagios/{{ nagiossrc }} && ./configure --with-command-group=nagcmd creates={{ ansible_env['HOME'] }}/nagios/{{ nagiossrc }}/Makefile 106 | when: is_centos 107 | 108 | - name: Configure 109 | shell: cd {{ ansible_env.HOME }}/nagios/{{ nagiossrc }} && ./configure --with-command-group=nagcmd creates={{ ansible_env['HOME'] }}/nagios/{{ nagiossrc }}/Makefile 110 | when: is_debian 111 | 112 | - name: Configure 113 | shell: cd {{ ansible_env.HOME }}/nagios/{{ nagiossrc }} && ./configure --with-command-group=nagcmd -with-httpd_conf=/etc/apache2/conf-available creates={{ ansible_env['HOME'] }}/nagios/{{ nagiossrc }}/Makefile 114 | when: is_ubuntu 115 | 116 | - name: Make all 117 | shell: cd {{ ansible_env.HOME }}/nagios/{{ nagiossrc }} && make all creates={{ ansible_env['HOME'] }}/nagios/{{ nagiossrc }}/base/nagios 118 | 119 | - name: Make install 120 | shell: cd {{ ansible_env.HOME }}/nagios/{{ nagiossrc }} && make install creates=/usr/local/nagios/bin/nagios 121 | 122 | - name: Make install-config 123 | shell: cd {{ ansible_env.HOME }}/nagios/{{ nagiossrc }} && make install-config creates=/usr/local/nagios/etc/nagios.cfg 124 | 125 | - name: Make install-commandmode 126 | shell: cd {{ ansible_env.HOME }}/nagios/{{ nagiossrc }} && make install-commandmode creates=/usr/local/nagios/var/rw 127 | 128 | - name: Make install-devel 129 | shell: cd {{ ansible_env.HOME }}/nagios/{{ nagiossrc }} && make install-devel creates=/usr/local/nagios/include/nagios/nagios.h 130 | 131 | - name: Make install-webconf 132 | shell: cd {{ ansible_env.HOME }}/nagios/{{ nagiossrc }} && make install-webconf creates=/etc/httpd/conf.d/nagios.conf 133 | notify: restart apache 134 | when: is_centos 135 | 136 | - name: Make install-webconf 137 | shell: cd {{ ansible_env.HOME }}/nagios/{{ nagiossrc }} && make install-webconf creates=/etc/apache2/conf.d/nagios.conf 138 | notify: restart apache 139 | when: is_debian 140 | 141 | - name: Make install-webconf 142 | shell: cd {{ ansible_env.HOME }}/nagios/{{ nagiossrc }} && make install-webconf creates=/etc/apache2/conf-available/nagios.conf 143 | when: is_ubuntu 144 | 145 | - name: Activate Nagios site on Ubuntu 14.04 146 | file: src=/etc/apache2/conf-available/nagios.conf dest=/etc/apache2/conf-enabled/nagios.conf state=link owner=root group=root 147 | notify: restart apache 148 | when: is_ubuntu 149 | 150 | - name: Make install-init 151 | shell: cd {{ ansible_env.HOME }}/nagios/{{ nagiossrc }} && make install-init creates=/etc/init.d/nagios 152 | 153 | - name: Set htpasswd for nagiosadmin 154 | htpasswd: path=/usr/local/nagios/etc/htpasswd.users name=nagiosadmin password={{ nagiosadminpass }} state=present 155 | 156 | - name: Unpack Plugin source files 157 | shell: cd {{ ansible_env.HOME }}/nagios && tar -xzvf {{ pluginssrc }}.tar.gz creates={{ ansible_env['HOME'] }}/nagios/{{ pluginssrc }} 158 | 159 | - name: Configure Plugins 160 | shell: cd {{ ansible_env.HOME }}/nagios/{{ pluginssrc }} && ./configure --with-nagios-user=nagios --with-nagios-group=nagios --with-openssl=/usr/bin/openssl creates={{ ansible_env['HOME'] }}/nagios/{{ pluginssrc }}/Makefile 161 | 162 | - name: Make Plugins 163 | shell: cd {{ ansible_env.HOME }}/nagios/{{ pluginssrc }} && make creates={{ ansible_env['HOME'] }}/nagios/{{ pluginssrc }}/plugins/check_ping 164 | 165 | - name: Make Install Plugins 166 | shell: cd {{ ansible_env.HOME }}/nagios/{{ pluginssrc }} && make install creates=/usr/local/nagios/libexec/check_ping 167 | 168 | - name: Unpack NRPE source files 169 | shell: cd {{ ansible_env.HOME }}/nagios && tar -xzvf {{ nrpesrc }}.tar.gz creates={{ ansible_env['HOME'] }}/nagios/{{ nrpesrc }} 170 | 171 | - name: Configure NRPE 172 | shell: cd {{ ansible_env.HOME }}/nagios/{{ nrpesrc }} && ./configure --with-ssl=/usr/bin/openssl --with-ssl-lib=/usr/lib/x86_64-linux-gnu creates={{ ansible_env['HOME'] }}/nagios/{{ nrpesrc }}/Makefile 173 | 174 | - name: Make NRPE 175 | shell: cd {{ ansible_env.HOME }}/nagios/{{ nrpesrc }} && make all creates={{ ansible_env['HOME'] }}/nagios/{{ nrpesrc }}/src/check_nrpe 176 | 177 | - name: Copy check_nrpe 178 | shell: cp {{ ansible_env['HOME'] }}/nagios/{{ nrpesrc }}/src/check_nrpe /usr/local/nagios/libexec/check_nrpe creates=/usr/local/nagios/libexec/check_nrpe 179 | 180 | - name: Ensure Nagios is started 181 | service: name=nagios state=started enabled=yes 182 | 183 | - name: Fix Nagios startup on Debian 184 | shell: cd /etc/rc2.d && ln -s ../init.d/nagios S18nagios creates=/etc/rc2.d/S18nagios 185 | #file: src=/etc/init.d/nagios dest=/etc/rc2.d/S99nagios state=link owner=root group=root 186 | when: is_debian 187 | 188 | - name: Check if SELinux is running in enforcing mode and change access 189 | file: path=/usr/local/nagios setype=httpd_sys_content_t state=directory recurse=yes 190 | when: ansible_selinux != False and ansible_selinux.mode == "enforcing" 191 | 192 | -------------------------------------------------------------------------------- /roles/nagios/vars/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | # Define the download url for the Nagios Core source files and the version you want to use. 3 | nagiosurl: http://prdownloads.sourceforge.net/sourceforge/nagios/nagios-4.0.6.tar.gz 4 | nagiossrc: nagios-4.0.6 5 | 6 | # Define the download url for the Plugins and the version you want to use. 7 | pluginsurl: http://www.nagios-plugins.org/download/nagios-plugins-2.0.2.tar.gz 8 | pluginssrc: nagios-plugins-2.0.2 9 | 10 | # This NRPE package is only used for the plugin, as the nrpe plugin on some distributions 11 | # require the distributions Nagios package to be installed. 12 | nrpeurl: http://sourceforge.net/projects/nagios/files/nrpe-2.x/nrpe-2.15/nrpe-2.15.tar.gz 13 | nrpesrc: nrpe-2.15 14 | 15 | # This will be the password for nagiosadmin which you use to login to your nagios site 16 | nagiosadminpass: Password1change 17 | -------------------------------------------------------------------------------- /roles/nginx/handlers/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | # Handler to handle common notifications. Handlers are called by other plays. 3 | # See http://ansible.cc/docs/playbooks.html for more information about handlers. 4 | 5 | - name: restart nginx 6 | service: name=nginx state=restarted 7 | -------------------------------------------------------------------------------- /roles/nginx/tasks/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | # Nginx installation 3 | - name: Install Nginx 4 | apt: update_cache=yes cache_valid_time=86400 name="nginx-full" state=present 5 | notify: restart nginx 6 | -------------------------------------------------------------------------------- /roles/postgres/handlers/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | # Handler to handle common notifications. Handlers are called by other plays. 3 | # See http://ansible.cc/docs/playbooks.html for more information about handlers. 4 | 5 | - name: restart postgres 6 | service: name=postgresql state=restarted 7 | -------------------------------------------------------------------------------- /roles/postgres/tasks/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | # Postgres installation 3 | - name: Installing PostgreSQL 4 | apt: update_cache=yes cache_valid_time=86400 name={{ item }} state="present" 5 | with_items: 6 | - postgresql-client 7 | - postgresql 8 | - postgresql-contrib 9 | notify: restart postgres 10 | -------------------------------------------------------------------------------- /roles/rabbitmq/files/rabbitmq.list: -------------------------------------------------------------------------------- 1 | deb http://www.rabbitmq.com/debian/ testing main 2 | -------------------------------------------------------------------------------- /roles/rabbitmq/handlers/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | # Handler to restart rabbitmq-server 3 | - name: restart rabbitmq-server 4 | service: rabbitmq-server state=restarted 5 | -------------------------------------------------------------------------------- /roles/rabbitmq/tasks/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | ## rabbitmq Installation 3 | - name: Add rabbitmq apt repository 4 | copy: src=rabbitmq.list dest=/etc/apt/sources.list.d/rabbitmq.list 5 | register: rmq_apt_repo 6 | 7 | - name: Add apt key for rabbit 8 | apt_key: url=http://www.rabbitmq.com/rabbitmq-signing-key-public.asc state=present 9 | register: rmq_apt_key 10 | 11 | - name: "Update apt cache - apt-get update" 12 | apt: update_cache=yes 13 | when: rmq_apt_repo.changed or rmq_apt_key.changed 14 | 15 | - name: Install rabbitmq 16 | apt: update_cache=yes cache_valid_time=86400 name="rabbitmq-server" state="present" 17 | notify: restart rabbitmq-server 18 | -------------------------------------------------------------------------------- /roles/redis/files/redis-server: -------------------------------------------------------------------------------- 1 | #! /bin/sh 2 | ### BEGIN INIT INFO 3 | # Provides: redis-server 4 | # Required-Start: $syslog $remote_fs 5 | # Required-Stop: $syslog $remote_fs 6 | # Should-Start: $local_fs 7 | # Should-Stop: $local_fs 8 | # Default-Start: 2 3 4 5 9 | # Default-Stop: 0 1 6 10 | # Short-Description: redis-server - Persistent key-value db 11 | # Description: redis-server - Persistent key-value db 12 | ### END INIT INFO 13 | 14 | 15 | PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin 16 | DAEMON=/usr/bin/redis-server 17 | DAEMON_ARGS=/etc/redis/redis.conf 18 | NAME=redis-server 19 | DESC=redis-server 20 | 21 | RUNDIR=/var/run/redis 22 | PIDFILE=$RUNDIR/redis-server.pid 23 | 24 | test -x $DAEMON || exit 0 25 | 26 | if [ -r /etc/default/$NAME ] 27 | then 28 | . /etc/default/$NAME 29 | fi 30 | 31 | . /lib/lsb/init-functions 32 | 33 | set -e 34 | 35 | case "$1" in 36 | start) 37 | echo -n "Starting $DESC: " 38 | mkdir -p $RUNDIR 39 | touch $PIDFILE 40 | chown redis:redis $RUNDIR $PIDFILE 41 | chmod 755 $RUNDIR 42 | 43 | if [ -n "$ULIMIT" ] 44 | then 45 | ulimit -n $ULIMIT 46 | fi 47 | 48 | if start-stop-daemon --start --quiet --umask 007 --pidfile $PIDFILE --chuid redis:redis --exec $DAEMON -- $DAEMON_ARGS 49 | then 50 | echo "$NAME." 51 | else 52 | echo "failed" 53 | fi 54 | ;; 55 | stop) 56 | echo -n "Stopping $DESC: " 57 | if start-stop-daemon --stop --retry forever/TERM/1 --quiet --oknodo --pidfile $PIDFILE --exec $DAEMON 58 | then 59 | echo "$NAME." 60 | else 61 | echo "failed" 62 | fi 63 | rm -f $PIDFILE 64 | sleep 1 65 | ;; 66 | 67 | restart|force-reload) 68 | ${0} stop 69 | ${0} start 70 | ;; 71 | 72 | status) 73 | echo -n "$DESC is " 74 | if start-stop-daemon --stop --quiet --signal 0 --name ${NAME} --pidfile ${PIDFILE} 75 | then 76 | echo "running" 77 | else 78 | echo "not running" 79 | exit 1 80 | fi 81 | ;; 82 | 83 | *) 84 | echo "Usage: /etc/init.d/$NAME {start|stop|restart|force-reload|status}" >&2 85 | exit 1 86 | ;; 87 | esac 88 | 89 | exit 0 90 | -------------------------------------------------------------------------------- /roles/redis/files/redis.conf: -------------------------------------------------------------------------------- 1 | # Redis configuration file example 2 | # Based on the default redis.conf shipped with Redis 2.6.9 3 | 4 | # Note on units: when memory size is needed, it is possible to specify 5 | # it in the usual form of 1k 5GB 4M and so forth: 6 | # 7 | # 1k => 1000 bytes 8 | # 1kb => 1024 bytes 9 | # 1m => 1000000 bytes 10 | # 1mb => 1024*1024 bytes 11 | # 1g => 1000000000 bytes 12 | # 1gb => 1024*1024*1024 bytes 13 | # 14 | # units are case insensitive so 1GB 1Gb 1gB are all the same. 15 | 16 | # By default Redis does not run as a daemon. Use 'yes' if you need it. 17 | # Note that Redis will write a pid file in /var/run/redis.pid when daemonized. 18 | daemonize yes 19 | 20 | # When running daemonized, Redis writes a pid file in /var/run/redis.pid by 21 | # default. You can specify a custom pid file location here. 22 | # pidfile /var/run/redis.pid 23 | pidfile /var/run/redis/redis-server.pid 24 | 25 | 26 | # Accept connections on the specified port, default is 6379. 27 | # If port 0 is specified Redis will not listen on a TCP socket. 28 | port 6379 29 | 30 | # If you want you can bind a single interface, if the bind option is not 31 | # specified all the interfaces will listen for incoming connections. 32 | # 33 | # bind 127.0.0.1 34 | 35 | # Specify the path for the unix socket that will be used to listen for 36 | # incoming connections. There is no default, so Redis will not listen 37 | # on a unix socket when not specified. 38 | # 39 | # unixsocket /tmp/redis.sock 40 | # unixsocketperm 755 41 | 42 | # Close the connection after a client is idle for N seconds (0 to disable) 43 | timeout 0 44 | 45 | # Set server verbosity to 'debug' 46 | # it can be one of: 47 | # debug (a lot of information, useful for development/testing) 48 | # verbose (many rarely useful info, but not a mess like the debug level) 49 | # notice (moderately verbose, what you want in production probably) 50 | # warning (only very important / critical messages are logged) 51 | loglevel notice 52 | 53 | # Specify the log file name. Also 'stdout' can be used to force 54 | # Redis to log on the standard output. Note that if you use standard 55 | # output for logging but daemonize, logs will be sent to /dev/null 56 | logfile /var/log/redis/redis.log 57 | 58 | # To enable logging to the system logger, just set 'syslog-enabled' to yes, 59 | # and optionally update the other syslog parameters to suit your needs. 60 | # syslog-enabled no 61 | 62 | # Specify the syslog identity. 63 | # syslog-ident redis 64 | 65 | # Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7. 66 | # syslog-facility local0 67 | 68 | # Set the number of databases. The default database is DB 0, you can select 69 | # a different one on a per-connection basis using SELECT where 70 | # dbid is a number between 0 and 'databases'-1 71 | databases 16 72 | 73 | ################################ SNAPSHOTTING ################################# 74 | # 75 | # Save the DB on disk: 76 | # 77 | # save 78 | # 79 | # Will save the DB if both the given number of seconds and the given 80 | # number of write operations against the DB occurred. 81 | # 82 | # In the example below the behaviour will be to save: 83 | # after 900 sec (15 min) if at least 1 key changed 84 | # after 300 sec (5 min) if at least 10 keys changed 85 | # after 60 sec if at least 10000 keys changed 86 | # 87 | # Note: you can disable saving at all commenting all the "save" lines. 88 | # 89 | # It is also possible to remove all the previously configured save 90 | # points by adding a save directive with a single empty string argument 91 | # like in the following example: 92 | # 93 | # save "" 94 | 95 | save 900 1 96 | save 300 10 97 | save 60 10000 98 | 99 | # By default Redis will stop accepting writes if RDB snapshots are enabled 100 | # (at least one save point) and the latest background save failed. 101 | # This will make the user aware (in an hard way) that data is not persisting 102 | # on disk properly, otherwise chances are that no one will notice and some 103 | # distater will happen. 104 | # 105 | # If the background saving process will start working again Redis will 106 | # automatically allow writes again. 107 | # 108 | # However if you have setup your proper monitoring of the Redis server 109 | # and persistence, you may want to disable this feature so that Redis will 110 | # continue to work as usually even if there are problems with disk, 111 | # permissions, and so forth. 112 | stop-writes-on-bgsave-error yes 113 | 114 | # Compress string objects using LZF when dump .rdb databases? 115 | # For default that's set to 'yes' as it's almost always a win. 116 | # If you want to save some CPU in the saving child set it to 'no' but 117 | # the dataset will likely be bigger if you have compressible values or keys. 118 | rdbcompression yes 119 | 120 | # Since verison 5 of RDB a CRC64 checksum is placed at the end of the file. 121 | # This makes the format more resistant to corruption but there is a performance 122 | # hit to pay (around 10%) when saving and loading RDB files, so you can disable it 123 | # for maximum performances. 124 | # 125 | # RDB files created with checksum disabled have a checksum of zero that will 126 | # tell the loading code to skip the check. 127 | rdbchecksum yes 128 | 129 | # The filename where to dump the DB 130 | dbfilename dump.rdb 131 | 132 | # The working directory. 133 | # 134 | # The DB will be written inside this directory, with the filename specified 135 | # above using the 'dbfilename' configuration directive. 136 | # 137 | # Also the Append Only File will be created inside this directory. 138 | # 139 | # Note that you must specify a directory here, not a file name. 140 | dir /var/lib/redis 141 | 142 | ################################# REPLICATION ################################# 143 | 144 | # Master-Slave replication. Use slaveof to make a Redis instance a copy of 145 | # another Redis server. Note that the configuration is local to the slave 146 | # so for example it is possible to configure the slave to save the DB with a 147 | # different interval, or to listen to another port, and so on. 148 | # 149 | # slaveof 150 | 151 | # If the master is password protected (using the "requirepass" configuration 152 | # directive below) it is possible to tell the slave to authenticate before 153 | # starting the replication synchronization process, otherwise the master will 154 | # refuse the slave request. 155 | # 156 | # masterauth 157 | 158 | # When a slave lost the connection with the master, or when the replication 159 | # is still in progress, the slave can act in two different ways: 160 | # 161 | # 1) if slave-serve-stale-data is set to 'yes' (the default) the slave will 162 | # still reply to client requests, possibly with out of date data, or the 163 | # data set may just be empty if this is the first synchronization. 164 | # 165 | # 2) if slave-serve-stale data is set to 'no' the slave will reply with 166 | # an error "SYNC with master in progress" to all the kind of commands 167 | # but to INFO and SLAVEOF. 168 | # 169 | slave-serve-stale-data yes 170 | 171 | # You can configure a slave instance to accept writes or not. Writing against 172 | # a slave instance may be useful to store some ephemeral data (because data 173 | # written on a slave will be easily deleted after resync with the master) but 174 | # may also cause problems if clients are writing to it because of a 175 | # misconfiguration. 176 | # 177 | # Since Redis 2.6 by default slaves are read-only. 178 | # 179 | # Note: read only slaves are not designed to be exposed to untrusted clients 180 | # on the internet. It's just a protection layer against misuse of the instance. 181 | # Still a read only slave exports by default all the administrative commands 182 | # such as CONFIG, DEBUG, and so forth. To a limited extend you can improve 183 | # security of read only slaves using 'rename-command' to shadow all the 184 | # administrative / dangerous commands. 185 | slave-read-only yes 186 | 187 | # Slaves send PINGs to server in a predefined interval. It's possible to change 188 | # this interval with the repl_ping_slave_period option. The default value is 10 189 | # seconds. 190 | # 191 | # repl-ping-slave-period 10 192 | 193 | # The following option sets a timeout for both Bulk transfer I/O timeout and 194 | # master data or ping response timeout. The default value is 60 seconds. 195 | # 196 | # It is important to make sure that this value is greater than the value 197 | # specified for repl-ping-slave-period otherwise a timeout will be detected 198 | # every time there is low traffic between the master and the slave. 199 | # 200 | # repl-timeout 60 201 | 202 | # The slave priority is an integer number published by Redis in the INFO output. 203 | # It is used by Redis Sentinel in order to select a slave to promote into a 204 | # master if the master is no longer working correctly. 205 | # 206 | # A slave with a low priority number is considered better for promotion, so 207 | # for instance if there are three slaves with priority 10, 100, 25 Sentinel will 208 | # pick the one wtih priority 10, that is the lowest. 209 | # 210 | # However a special priority of 0 marks the slave as not able to perform the 211 | # role of master, so a slave with priority of 0 will never be selected by 212 | # Redis Sentinel for promotion. 213 | # 214 | # By default the priority is 100. 215 | slave-priority 100 216 | 217 | ################################## SECURITY ################################### 218 | 219 | # Require clients to issue AUTH before processing any other 220 | # commands. This might be useful in environments in which you do not trust 221 | # others with access to the host running redis-server. 222 | # 223 | # This should stay commented out for backward compatibility and because most 224 | # people do not need auth (e.g. they run their own servers). 225 | # 226 | # Warning: since Redis is pretty fast an outside user can try up to 227 | # 150k passwords per second against a good box. This means that you should 228 | # use a very strong password otherwise it will be very easy to break. 229 | # 230 | # requirepass foobared 231 | 232 | # Command renaming. 233 | # 234 | # It is possible to change the name of dangerous commands in a shared 235 | # environment. For instance the CONFIG command may be renamed into something 236 | # of hard to guess so that it will be still available for internal-use 237 | # tools but not available for general clients. 238 | # 239 | # Example: 240 | # 241 | # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52 242 | # 243 | # It is also possible to completely kill a command renaming it into 244 | # an empty string: 245 | # 246 | # rename-command CONFIG "" 247 | 248 | ################################### LIMITS #################################### 249 | 250 | # Set the max number of connected clients at the same time. By default 251 | # this limit is set to 10000 clients, however if the Redis server is not 252 | # able ot configure the process file limit to allow for the specified limit 253 | # the max number of allowed clients is set to the current file limit 254 | # minus 32 (as Redis reserves a few file descriptors for internal uses). 255 | # 256 | # Once the limit is reached Redis will close all the new connections sending 257 | # an error 'max number of clients reached'. 258 | # 259 | # maxclients 10000 260 | 261 | # Don't use more memory than the specified amount of bytes. 262 | # When the memory limit is reached Redis will try to remove keys 263 | # accordingly to the eviction policy selected (see maxmemmory-policy). 264 | # 265 | # If Redis can't remove keys according to the policy, or if the policy is 266 | # set to 'noeviction', Redis will start to reply with errors to commands 267 | # that would use more memory, like SET, LPUSH, and so on, and will continue 268 | # to reply to read-only commands like GET. 269 | # 270 | # This option is usually useful when using Redis as an LRU cache, or to set 271 | # an hard memory limit for an instance (using the 'noeviction' policy). 272 | # 273 | # WARNING: If you have slaves attached to an instance with maxmemory on, 274 | # the size of the output buffers needed to feed the slaves are subtracted 275 | # from the used memory count, so that network problems / resyncs will 276 | # not trigger a loop where keys are evicted, and in turn the output 277 | # buffer of slaves is full with DELs of keys evicted triggering the deletion 278 | # of more keys, and so forth until the database is completely emptied. 279 | # 280 | # In short... if you have slaves attached it is suggested that you set a lower 281 | # limit for maxmemory so that there is some free RAM on the system for slave 282 | # output buffers (but this is not needed if the policy is 'noeviction'). 283 | # 284 | # maxmemory 285 | 286 | # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory 287 | # is reached? You can select among five behavior: 288 | # 289 | # volatile-lru -> remove the key with an expire set using an LRU algorithm 290 | # allkeys-lru -> remove any key accordingly to the LRU algorithm 291 | # volatile-random -> remove a random key with an expire set 292 | # allkeys-random -> remove a random key, any key 293 | # volatile-ttl -> remove the key with the nearest expire time (minor TTL) 294 | # noeviction -> don't expire at all, just return an error on write operations 295 | # 296 | # Note: with all the kind of policies, Redis will return an error on write 297 | # operations, when there are not suitable keys for eviction. 298 | # 299 | # At the date of writing this commands are: set setnx setex append 300 | # incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd 301 | # sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby 302 | # zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby 303 | # getset mset msetnx exec sort 304 | # 305 | # The default is: 306 | # 307 | # maxmemory-policy volatile-lru 308 | 309 | # LRU and minimal TTL algorithms are not precise algorithms but approximated 310 | # algorithms (in order to save memory), so you can select as well the sample 311 | # size to check. For instance for default Redis will check three keys and 312 | # pick the one that was used less recently, you can change the sample size 313 | # using the following configuration directive. 314 | # 315 | # maxmemory-samples 3 316 | 317 | ############################## APPEND ONLY MODE ############################### 318 | 319 | # By default Redis asynchronously dumps the dataset on disk. This mode is 320 | # good enough in many applications, but an issue with the Redis process or 321 | # a power outage may result into a few minutes of writes lost (depending on 322 | # the configured save points). 323 | # 324 | # The Append Only File is an alternative persistence mode that provides 325 | # much better durability. For instance using the default data fsync policy 326 | # (see later in the config file) Redis can lose just one second of writes in a 327 | # dramatic event like a server power outage, or a single write if something 328 | # wrong with the Redis process itself happens, but the operating system is 329 | # still running correctly. 330 | # 331 | # AOF and RDB persistence can be enabled at the same time without problems. 332 | # If the AOF is enabled on startup Redis will load the AOF, that is the file 333 | # with the better durability guarantees. 334 | # 335 | # Please check http://redis.io/topics/persistence for more information. 336 | 337 | appendonly no 338 | 339 | # The name of the append only file (default: "appendonly.aof") 340 | # appendfilename appendonly.aof 341 | 342 | # The fsync() call tells the Operating System to actually write data on disk 343 | # instead to wait for more data in the output buffer. Some OS will really flush 344 | # data on disk, some other OS will just try to do it ASAP. 345 | # 346 | # Redis supports three different modes: 347 | # 348 | # no: don't fsync, just let the OS flush the data when it wants. Faster. 349 | # always: fsync after every write to the append only log . Slow, Safest. 350 | # everysec: fsync only one time every second. Compromise. 351 | # 352 | # The default is "everysec" that's usually the right compromise between 353 | # speed and data safety. It's up to you to understand if you can relax this to 354 | # "no" that will let the operating system flush the output buffer when 355 | # it wants, for better performances (but if you can live with the idea of 356 | # some data loss consider the default persistence mode that's snapshotting), 357 | # or on the contrary, use "always" that's very slow but a bit safer than 358 | # everysec. 359 | # 360 | # More details please check the following article: 361 | # http://antirez.com/post/redis-persistence-demystified.html 362 | # 363 | # If unsure, use "everysec". 364 | 365 | # appendfsync always 366 | appendfsync everysec 367 | # appendfsync no 368 | 369 | # When the AOF fsync policy is set to always or everysec, and a background 370 | # saving process (a background save or AOF log background rewriting) is 371 | # performing a lot of I/O against the disk, in some Linux configurations 372 | # Redis may block too long on the fsync() call. Note that there is no fix for 373 | # this currently, as even performing fsync in a different thread will block 374 | # our synchronous write(2) call. 375 | # 376 | # In order to mitigate this problem it's possible to use the following option 377 | # that will prevent fsync() from being called in the main process while a 378 | # BGSAVE or BGREWRITEAOF is in progress. 379 | # 380 | # This means that while another child is saving the durability of Redis is 381 | # the same as "appendfsync none", that in practical terms means that it is 382 | # possible to lost up to 30 seconds of log in the worst scenario (with the 383 | # default Linux settings). 384 | # 385 | # If you have latency problems turn this to "yes". Otherwise leave it as 386 | # "no" that is the safest pick from the point of view of durability. 387 | no-appendfsync-on-rewrite no 388 | 389 | # Automatic rewrite of the append only file. 390 | # Redis is able to automatically rewrite the log file implicitly calling 391 | # BGREWRITEAOF when the AOF log size will growth by the specified percentage. 392 | # 393 | # This is how it works: Redis remembers the size of the AOF file after the 394 | # latest rewrite (or if no rewrite happened since the restart, the size of 395 | # the AOF at startup is used). 396 | # 397 | # This base size is compared to the current size. If the current size is 398 | # bigger than the specified percentage, the rewrite is triggered. Also 399 | # you need to specify a minimal size for the AOF file to be rewritten, this 400 | # is useful to avoid rewriting the AOF file even if the percentage increase 401 | # is reached but it is still pretty small. 402 | # 403 | # Specify a percentage of zero in order to disable the automatic AOF 404 | # rewrite feature. 405 | 406 | auto-aof-rewrite-percentage 100 407 | auto-aof-rewrite-min-size 64mb 408 | 409 | ################################ LUA SCRIPTING ############################### 410 | 411 | # Max execution time of a Lua script in milliseconds. 412 | # 413 | # If the maximum execution time is reached Redis will log that a script is 414 | # still in execution after the maximum allowed time and will start to 415 | # reply to queries with an error. 416 | # 417 | # When a long running script exceed the maximum execution time only the 418 | # SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be 419 | # used to stop a script that did not yet called write commands. The second 420 | # is the only way to shut down the server in the case a write commands was 421 | # already issue by the script but the user don't want to wait for the natural 422 | # termination of the script. 423 | # 424 | # Set it to 0 or a negative value for unlimited execution without warnings. 425 | lua-time-limit 5000 426 | 427 | ################################## SLOW LOG ################################### 428 | 429 | # The Redis Slow Log is a system to log queries that exceeded a specified 430 | # execution time. The execution time does not include the I/O operations 431 | # like talking with the client, sending the reply and so forth, 432 | # but just the time needed to actually execute the command (this is the only 433 | # stage of command execution where the thread is blocked and can not serve 434 | # other requests in the meantime). 435 | # 436 | # You can configure the slow log with two parameters: one tells Redis 437 | # what is the execution time, in microseconds, to exceed in order for the 438 | # command to get logged, and the other parameter is the length of the 439 | # slow log. When a new command is logged the oldest one is removed from the 440 | # queue of logged commands. 441 | 442 | # The following time is expressed in microseconds, so 1000000 is equivalent 443 | # to one second. Note that a negative number disables the slow log, while 444 | # a value of zero forces the logging of every command. 445 | slowlog-log-slower-than 10000 446 | 447 | # There is no limit to this length. Just be aware that it will consume memory. 448 | # You can reclaim memory used by the slow log with SLOWLOG RESET. 449 | slowlog-max-len 128 450 | 451 | ############################### ADVANCED CONFIG ############################### 452 | 453 | # Hashes are encoded using a memory efficient data structure when they have a 454 | # small number of entries, and the biggest entry does not exceed a given 455 | # threshold. These thresholds can be configured using the following directives. 456 | hash-max-ziplist-entries 512 457 | hash-max-ziplist-value 64 458 | 459 | # Similarly to hashes, small lists are also encoded in a special way in order 460 | # to save a lot of space. The special representation is only used when 461 | # you are under the following limits: 462 | list-max-ziplist-entries 512 463 | list-max-ziplist-value 64 464 | 465 | # Sets have a special encoding in just one case: when a set is composed 466 | # of just strings that happens to be integers in radix 10 in the range 467 | # of 64 bit signed integers. 468 | # The following configuration setting sets the limit in the size of the 469 | # set in order to use this special memory saving encoding. 470 | set-max-intset-entries 512 471 | 472 | # Similarly to hashes and lists, sorted sets are also specially encoded in 473 | # order to save a lot of space. This encoding is only used when the length and 474 | # elements of a sorted set are below the following limits: 475 | zset-max-ziplist-entries 128 476 | zset-max-ziplist-value 64 477 | 478 | # Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in 479 | # order to help rehashing the main Redis hash table (the one mapping top-level 480 | # keys to values). The hash table implementation Redis uses (see dict.c) 481 | # performs a lazy rehashing: the more operation you run into an hash table 482 | # that is rehashing, the more rehashing "steps" are performed, so if the 483 | # server is idle the rehashing is never complete and some more memory is used 484 | # by the hash table. 485 | # 486 | # The default is to use this millisecond 10 times every second in order to 487 | # active rehashing the main dictionaries, freeing memory when possible. 488 | # 489 | # If unsure: 490 | # use "activerehashing no" if you have hard latency requirements and it is 491 | # not a good thing in your environment that Redis can reply form time to time 492 | # to queries with 2 milliseconds delay. 493 | # 494 | # use "activerehashing yes" if you don't have such hard requirements but 495 | # want to free memory asap when possible. 496 | activerehashing yes 497 | 498 | # The client output buffer limits can be used to force disconnection of clients 499 | # that are not reading data from the server fast enough for some reason (a 500 | # common reason is that a Pub/Sub client can't consume messages as fast as the 501 | # publisher can produce them). 502 | # 503 | # The limit can be set differently for the three different classes of clients: 504 | # 505 | # normal -> normal clients 506 | # slave -> slave clients and MONITOR clients 507 | # pubsub -> clients subcribed to at least one pubsub channel or pattern 508 | # 509 | # The syntax of every client-output-buffer-limit directive is the following: 510 | # 511 | # client-output-buffer-limit 512 | # 513 | # A client is immediately disconnected once the hard limit is reached, or if 514 | # the soft limit is reached and remains reached for the specified number of 515 | # seconds (continuously). 516 | # So for instance if the hard limit is 32 megabytes and the soft limit is 517 | # 16 megabytes / 10 seconds, the client will get disconnected immediately 518 | # if the size of the output buffers reach 32 megabytes, but will also get 519 | # disconnected if the client reaches 16 megabytes and continuously overcomes 520 | # the limit for 10 seconds. 521 | # 522 | # By default normal clients are not limited because they don't receive data 523 | # without asking (in a push way), but just after a request, so only 524 | # asynchronous clients may create a scenario where data is requested faster 525 | # than it can read. 526 | # 527 | # Instead there is a default limit for pubsub and slave clients, since 528 | # subscribers and slaves receive data in a push fashion. 529 | # 530 | # Both the hard or the soft limit can be disabled just setting it to zero. 531 | client-output-buffer-limit normal 0 0 0 532 | client-output-buffer-limit slave 256mb 64mb 60 533 | client-output-buffer-limit pubsub 32mb 8mb 60 534 | 535 | ################################## INCLUDES ################################### 536 | 537 | # Include one or more other config files here. This is useful if you 538 | # have a standard template that goes to all Redis server but also need 539 | # to customize a few per-server settings. Include files can include 540 | # other files, so use this wisely. 541 | # 542 | # include /path/to/local.conf 543 | # include /path/to/other.conf 544 | -------------------------------------------------------------------------------- /roles/redis/handlers/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | # Handler to handle common notifications. Handlers are called by other plays. 3 | # See http://ansible.cc/docs/playbooks.html for more information about handlers. 4 | 5 | - name: restart redis-server 6 | service: name=redis-server state=restarted 7 | -------------------------------------------------------------------------------- /roles/redis/tasks/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | # Redis installation 3 | - name: Install dependencies for redis (via apt) 4 | apt: update_cache=yes cache_valid_time=86400 name="redis-server" 5 | 6 | - name: Copy configuration file - redis.conf 7 | copy: src=redis.conf dest=/etc/redis/redis.conf 8 | notify: restart redis-server 9 | 10 | - name: Copy init file - redis-server 11 | copy: src=redis-server dest=/etc/init.d/redis-server 12 | notify: restart redis-server 13 | 14 | - name: Setting file permissions for init file - redis-server 15 | file: path=/etc/init.d/redis-server owner=root group=root mode=0755 state=file 16 | notify: restart redis-server 17 | 18 | - name: mkdir -p /var/lib/redis 19 | file: path=/var/lib/redis owner=redis group=redis state=directory 20 | notify: restart redis-server 21 | 22 | - name: mkdir -p /var/log/redis 23 | file: path=/var/log/redis owner=redis group=redis state=directory 24 | notify: restart redis-server 25 | 26 | - name: Enable redis to start on boot 27 | service: name=redis-server runlevel="2345" enabled="yes" state="started" 28 | -------------------------------------------------------------------------------- /vars/centos.yml: -------------------------------------------------------------------------------- 1 | apache: httpd 2 | apacheuser: apache 3 | 4 | -------------------------------------------------------------------------------- /vars/debian.yml: -------------------------------------------------------------------------------- 1 | apache: apache2 2 | apacheuser: www-data 3 | 4 | -------------------------------------------------------------------------------- /vars/ubuntu.yml: -------------------------------------------------------------------------------- 1 | apache: apache2 2 | apacheuser: www-data 3 | 4 | --------------------------------------------------------------------------------