Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

Table of Contents
maxLevel1

asg-protection

description

For scripts with a long runtime, it may happen that the execution server is deleted during execution by our automatic scaling. This script activates or deactivates a protection mechanism for the executing server that prevents this deletion Code. If this is not equal to 0 (number zero), an error occurred and the protection was not activated / deactivated. Possible reasons are:

  • The server is currently down

  • The hardware of the server is currently being modified (enlarged, reduced, restarted, etc.)

  • The script was called too often in a short period of time (> about 1000 views per second)

usage

Enable protection:

Code Block
languagebashlinenumberstrue
if asg-protection on; then
   # Commands if protection could not be activated
   # Ex: exit
fi


Disable protection:

Code Block
languagebashlinenumberstrue
if asg-protection off; then
   # Commands if protection could not be disabled
   # Ex: exit
fi

Get current state:

Code Block
languagebashlinenumberstrue
asg-protection get
  • return code is 0, when ASG protection is enabled

  • return code is 1, when ASG protection is disabled

  • return code is 5, when the server is a single server

check-log-registration  

description

There are cases where the application can not be customized so the log is registered by the application. In these cases, this script can be used. It recursively finds all files in a given path and registers them if they have not been registered yet. It is optimized for use as cronjob. The script has to be run as www-data, which will be done automatically by using the command in the install.sh. If you want to test the script manually you have to add the prefix 'sudo -u www-data'

usage

Log log files in a path:

Code Block
languagebash
linenumberstrue
check-log-registration /full/path/to/log-folder/ [role1 [role2 [roleN]]]

Register logs for specific roles:

Code Block
languagebashlinenumberstrue
check-log-registration /full/path/to/log-folder/ web backend

get-application-env

description

 If the server is used to host an application, the script returns all environment parameters (eg database access credentials, memcache URL, etc.). It supports output in text and json format.

Note

You need to run this script directly on the application instance. The script will not return environment parameters on a natgw because no application runs on a natgw.

This command is not usable on our docker setups.

usage

Return environment parameters for all server roles:

Code Block
languagebash
linenumberstrue
$ sudo get-application-env
Environment for role "rolle1"
  variable                              value
    GIT_SSH                               /usr/local/bin/r3-deploy/custom-git-ssh.sh
    DATABASE_NAME                         db
    REDIS_SESSION_PORT                    6379
    REDIS_SESSION_HOST                    redis.server.0001.euc1.cache.amazonaws.com
    DATABASE_PASSWORD                     password
    DATABASE_HOST                         db.server.eu-central-1.rds.amazonaws.com
    DATABASE_USER                         dbuser
Environment for role "rolle2"
  variable                              value
    GIT_SSH                               /usr/local/bin/r3-deploy/custom-git-ssh.sh
    DATABASE_NAME                         db2
    REDIS_SESSION_PORT                    6379
    REDIS_SESSION_HOST                    redis2.server.0001.euc1.cache.amazonaws.com
    DATABASE_PASSWORD                     password
    DATABASE_HOST                         db2.server.eu-central-1.rds.amazonaws.com
    DATABASE_USER                         dbuser


Return environment parameters only for role "role2":

Code Block
languagebashlinenumberstrue
$ sudo get-application-env rolle2
Environment for role "rolle2"
  variable                              value
    GIT_SSH                               /usr/local/bin/r3-deploy/custom-git-ssh.sh
    DATABASE_NAME                         db2
    REDIS_SESSION_PORT                    6379
    REDIS_SESSION_HOST                    redis2.server.0001.euc1.cache.amazonaws.com
    DATABASE_PASSWORD                     Passwort
    DATABASE_HOST                         db2.server.eu-central-1.rds.amazonaws.com
    DATABASE_USER                         dbuser


Return environment parameters in JSON format:

Code Block
languagebashlinenumberstrue
$ sudo get-application-env --output json
{"rolle1": [["GIT_SSH", "/usr/local/bin/r3-deploy/custom-git-ssh.sh"], ["DATABASE_NAME", "db"], ["REDIS_SESSION_PORT", 6379], ["REDIS_SESSION_HOST", "redis.server.0001.euc1.cache.amazonaws.com"], ["DATABASE_PASSWORD", "Passwort"], ["DATABASE_HOST", "db.server.eu-central-1.rds.amazonaws.com"], ["DATABASE_USER", "dbuser"]], "rolle2": [["GIT_SSH", "/usr/local/bin/r3-deploy/custom-git-ssh.sh"], ["DATABASE_NAME", "db2"], ["REDIS_SESSION_PORT", 6379], ["REDIS_SESSION_HOST", "redis2.server.0001.euc1.cache.amazonaws.com"], ["DATABASE_PASSWORD", "Passwort"], ["DATABASE_HOST", "db2.server.eu-central-1.rds.amazonaws.com"], ["DATABASE_USER", "dbuser"]]}


Return environment parameters in as Bash commands:

Code Block
languagebashlinenumberstrue
$ sudo get-application-env rolle2 --output bash
echo "Environment for role rolle2"

export DATABASE_NAME='db2'
export DATABASE_HOST='db2.server.eu-central-1.rds.amazonaws.com'
export DATABASE_PASWORD='xxxxxxxxxxxxxxxx'
export DATABASE_USER='dbuser'
export GIT_SSH='/usr/local/bin/r3-deploy/custom-git-ssh.sh'
export REDIS_SESSION_PORT='6379'
export REDIS_SESSION_HOST='redis2.server.0001.euc1.cache.amazonaws.com'


Can be used to setup test environment variables for install.sh testing, e.g. like this run as www-data:

Code Block
languagebashlinenumberstrue
$ eval "$(sudo get-application-env rolle2 --output bash)"
Environment for role rolle2
$ cd /var/www/rolle2/
$ sudo -Eu www-data bash install.sh


For additional options, see Command Help:

Code Block
linenumbers
languagebashtrue
$ get-application-env -h

get-instance-by-role

description

This script returns a list of all servers in a project that belong to a role. It supports output in text and json format.

usage

Return all servers with the same role, such as:

Code Block
languagebashlinenumberstrue
get-instances-by-role
# output
[{"ip": "10.xxx.xxx.xxx", "name": "host1", "id": "i-yyyyyy"}, {"ip": "10.xxx.xxx.xxx", "name": "host2", "id": "i-yyyyyy"}, {"ip": "10.xxx.xxx.xxx", "name": "host3", "id": "i-yyyyyy"}]


Return all servers of the specified role:

Code Block
linenumbers
languagebashtrue
get-instances-by-role role
# e.g.
get-instances-by-role web


Return all servers of the specified role in the text format:

Code Block
linenumbers
languagebashtrue
get-instances-by-role --output text role
# e.g.
get-instances-by-role --output text web

# output
nameipid
hostname10.xxx.xxx.xxxi-xxxxxxxxxx

Return all servers of the specified role and project:

Code Block
languagebashlinenumberstrue
get-instances-by-role --project project role
# e.g.
get-instances-by-role --project proj2 web

hook-memcache-flush.sh

description

This script can be used as a deploy hook to delete all data from a memcache cluster after a project deployment. It automatically detects all existing memcache clusters. If only one cluster exists, this is deleted. If more clusters exist, the cluster to be cleared is queried via a selection.

usage

Delete based on automatic determination:

Code Block
languagebashlinenumberstrue
hook-memcache-flush.sh -e environment -p project
# Beispiel
hook-memcache-flush.sh -e test -p portal


Deletion under the specification of the cluster:

Code Block
languagebashlinenumberstrue
hook-memcache-flush.sh -u cluster-url
# Beispiel
hook-memcache-flush.sh -u test-r3-45git3.00y7nk.cfg.euc1.cache.amazonaws.com:11211

register-log

description

Upon request, we provide a logging system that collects log files to a central log server and stores them for analysis for a defined period of time. This script can be used to log log files dynamically. This is necessary, for example, for log files with a dynamic path (eg date or partner ID).

Currently up to 6600 log files can be registered.

usage

register logs:

Code Block
languagebashlinenumberstrue
register-log -h
/usr/local/bin/register-log [-h] [-k] [path_to_log] [role]

-h        : show this help
-k        : prevents our cleanup routines to remove the configuration for the logfile when the log file does not exist
[role]    : for instances with multiple roles, please use this option and define a role

...

The option '-k' prevents our cleanup routines to remove the configuration for the logfile when the log file does not exist.

(warning) The script register-log checks if a log file exists to avoid unnecessary configs. This results in the use of register-log during installation, e.g. via install.sh may cause problems, as the paths are not yet fully established. We therefore recommend making a touch on the log file and creating the file.

...

...

usage at install.sh
Code Block
linenumberslanguagetruebash
register-log -k /full/path/to/logfile [role] # you should incorporate pwd

...

This example code in the install.sh run the clear-cache function of 'artisan':

install.sh
Code Block
languagebash
titleinstall.sh
linenumberstrue
#!/bin/bash

[...]

run-once-per-role.sh "${ROLE}" /var/www/web/public/bin/artisan cache:clear

[...]

...

Code Block
* * * * * /usr/local/bin/run-once-per-role.sh 'web' /var/www/web/public/bin/artisan cron:start

varnish-flush.sh

description

This script deletes data from a Varnish cache.

usage

Script using the URL to be deleted on the Jump server.

  • Delete a dedicated URL, eg image or HTML page

Code Block
languagebashlinenumberstrue
varnish-flush.sh http://example.com/test.html http://example.com/foobar.png
  • Delete all elements below a URL, eg foobar / *

Code Block
languagebash
linenumberstrue
varnish-flush.sh http://example.com/foobar/*
  • Delete all elements with unknown URL depth, eg foobar / * / bla / * 

Code Block
languagebashlinenumberstrue
varnish-flush.sh http://example.com/foobar/*/bla/*
  • Dedicated object for all domains

Code Block
languagebash
linenumberstrue
varnish-flush.sh http://.*/test.html http://example.com/foobar.png
  • Delete all elements below a URL, eg foobar/* from a dedicated role, eg varnish01

Code Block
languagebashlinenumberstrue
varnish-flush.sh -r varnish01 http://example.com/foobar/*

...