Skip to content

Instantly share code, notes, and snippets.

View gist:5d311d595417b02e2b1dfae67438c27a
###########################################################
Vagrant provisioning script
###########################################################
#!/usr/bin/env bash
PUPPET_BIN=/opt/puppetlabs/bin/puppet
if [ ! -z "${FACTER_vagrant_role}" ]; then
echo "Applying role ${FACTER_vagrant_role}"
else
View gist:a4e36e4b95265e5f6a8d99bb86a82c1a
# Initialise git repo
git clone project.git
cd project
# Current branch is now master
# Make one branch per environment, aka four tags pointing to the same commit
git branch develop
git branch test
git branch acceptance
git branch production
# Switch to develop
View gist:1247b8fd656dd1e3c5b57268079d25c6
CMDB:
I do not have names on specific commentors. These notes have been re-ordered to make a bit more sense.
We have dynamic environments, with information coming from systems and builds.
Systems need configuration from runtime data based on service discovery and build configuration (IP addresses, versions, etc).
CMDB use contexts:
On call users - The sysadmin who has been paged at 4 am needs to determine context for the page.
Deployment systems - To know where to deploy software, what version(s) to deploy, etc.
Maintenance - Downtimes, escalate, software versions, hardware info...
View monitoring-definition.md

Ryan Frantz defined monitoring at http://www.ryanfrantz.com/posts/solving-monitoring/ as

Monitoring is the aggregation of health and performance data, events, and relationships delivered via an interface that provides an holistic view of a system's state to better understand and address failure scenarios.


Here's my alternative definition

  • Monitoring is the detection of variation outside the steady state of the business.
You can’t perform that action at this time.