| #!/bin/bash | |
| # | |
| # Example of how to parse short/long options with 'getopt' | |
| # | |
| OPTS=`getopt -o vhns: --long verbose,dry-run,help,stack-size: -n 'parse-options' -- "$@"` | |
| if [ $? != 0 ] ; then echo "Failed parsing options." >&2 ; exit 1 ; fi | |
| echo "$OPTS" |
| # Use LVM for partitioning | |
| d-i partman-auto/method string lvm | |
| # If one of the disks that are going to be automatically partitioned | |
| # contains an old LVM configuration, the user will normally receive a | |
| # warning. Preseed this away | |
| d-i partman-lvm/device_remove_lvm boolean true | |
| # And the same goes for the confirmation to write the lvm partitions. | |
| d-i partman-lvm/confirm boolean true |
(from http://www.metabrew.com/article/a-million-user-comet-application-with-mochiweb-part-1)
Save yourself some time and tune the kernel tcp settings before testing with lots of connections, or your test will fail and you’ll see lots of Out of socket memory messages (and if you are masquerading, nf_conntrack: table full, dropping packet.)
Here are the sysctl settings I ended up with - YMMV, but these will probably do:
$ cat /etc/sysctl.conf
# General gigabit tuning:
net.core.rmem_max = 16777216
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.
| <contents of normal file> | |
| # Add any additional locations to look for master runners | |
| runner_dirs: [/srv/runners] | |
| # Register a reactor whenever a cloud provider emits 'created' | |
| # the * is the name of the VM, we want any, but you could | |
| # do something like salt/cloud/Webservers-*/created if you only | |
| # wanted your webservers | |
| reactor: |
I've been using a lot of Ansible lately and while almost everything has been great, finding a clean way to implement ansible-vault wasn't immediately apparent.
What I decided on was the following: put your secret information into a vars file, reference that vars file from your task, and encrypt the whole vars file using ansible-vault encrypt.
Let's use an example: You're writing an Ansible role and want to encrypt the spoiler for the movie Aliens.
| #Example usage | |
| id=SASL_003 | |
| HIT_dnsbls >= 2 | |
| sasl_username =~ /^(.+)$/ | |
| client_country_code !~ /^(FR|IL|US|UK|CA|BE|CH|IT)$/ | |
| action = rcpt(sasl_username/3/86400/REJECT your is ip listed as trojaned, only 3 recipient per DAY for $$sasl_username) |
| # Ubuntu Server automated installation | |
| # by Scott Lowe ([email protected]) | |
| d-i debian-installer/locale string en_US | |
| d-i console-setup/ask_detect boolean false | |
| d-i keyboard-configuration/layoutcode string us | |
| d-i netcfg/choose_interface select eth0 | |
| d-i netcfg/get_hostname string hostname | |
| d-i netcfg/get_domain string domain.com | |
| d-i netcfg/wireless_wep string |
| --- | |
| # Copyright 2015, Jean-Philippe Evrard <[email protected]> | |
| # | |
| # Licensed under the Apache License, Version 2.0 (the "License"); | |
| # you may not use this file except in compliance with the License. | |
| # You may obtain a copy of the License at | |
| # | |
| # http://www.apache.org/licenses/LICENSE-2.0 | |
| # | |
| # Unless required by applicable law or agreed to in writing, software |