f3ew

###########################################################
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

f3ew

# 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

f3ew

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...

f3ew

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.