http://www.smartbrief.com/original/2017/04/fallacy-lessons-learned?utm_source=brief
#!/bin/bash -e | |
# $Id: dm-cache-status,v 1.1 2014/08/19 09:02:46 oernii Exp $ | |
# Status | |
# ------ | |
# | |
# <metadata block size> <#used metadata blocks>/<#total metadata blocks> | |
# <cache block size> <#used cache blocks>/<#total cache blocks> | |
# <#read hits> <#read misses> <#write hits> <#write misses> | |
# <#demotions> <#promotions> <#dirty> <#features> <features>* |
#cloud-config | |
# Set up the package repository to get Rudder. | |
# We use the "latest" pseudo-version name to always get an up-to-date agent. | |
write_files: | |
- content: | | |
[Rudder_4.1] | |
name=Rudder 4.1 EL repository | |
baseurl=http://www.rudder-project.org/rpm-4.1/RHEL_7/ |
#cloud-config | |
# Set up the package repository to get Rudder. | |
# We use the "latest" pseudo-version name to always get an up-to-date agent. | |
write_files: | |
- content: | | |
[Rudder_4.1] | |
name=Rudder 4.1 EL repository | |
baseurl=http://www.rudder-project.org/rpm-4.1/RHEL_7/ |
#cloud-config | |
# I'm very unhappy to end up with this scriptlike solution but there was some bugs (i.e. things not being run) | |
# that seem to be in their cloud-config version | |
runcmd: | |
- apt-get -y install wget --force-yes | |
- wget --quiet -O- "https://www.rudder-project.org/apt-repos/rudder_apt_key.pub" | apt-key add - | |
- echo "deb http://www.rudder-project.org/apt-4.1/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/rudder.list | |
- apt-get update | |
- DEBIAN_FRONTEND=noninteractive apt-get -y install rudder-agent --force-yes |
https://confluence.oceanobservatories.org/download/attachments/21205028/2110-00001_CMP_CI.pdf
http://www.cisco.com/c/en/us/support/docs/availability/high-availability/15111-configmgmt.html
http://itsm.certification.info/config2.html
https://www.cmcrossroads.com/question/what-numbering-scheme-use-naming-cm-items
-------------------------------------- | |
||| Test return to stable state | |
-------------------------------------- | |
||| External Fault injection tests | |
-------------------------------------- | |
||| System health | |
-------------------------------------- | |
\========/ | |
Below: \ / | |
"insufficient tests for OS code |
Install a mixed update for Leap42.1
consisted of 106 packages including kernel update and a very slow samba update script
Try prefetching the updates (i.e. an hour before the downtime)
Try disabling deltaRPM
Caches NOT dropped, all packages likely to stay in cache on today's servers.
VM size:
It happens I had read the database troubleshooting part of Gitlab's Ops manual (https://gitlab.com/gitlab-com/runbooks/blob/master/troubleshooting/postgresql_replication.md) just a month ago, looking for monitoring info. I found many sound instructions on how to deal with database replication issues. I was very happy when I read they're also using Check_MK, but ...
It also made me decide pg_basebackup is too dangerous w/o dedicated DBA staff for two reasons:
- reason 1: lack of stability / fault tolerance
- reason 2: destructive resume on issue