inthecloud247

lang en_US
langsupport en_US
keyboard us
timezone Etc/UTC
text
install
skipx
halt

# Ridiculous URL... I know...

inthecloud247

#!/bin/sh
echo Install all AppStore Apps at first!
# no solution to automate AppStore installs
read -p "Press any key to continue... " -n1 -s
echo  '\n'

# install wallpaper cli
sudo gem install desktop
echo Install Homebrew, Postgres, wget and cask
ruby -e "$(curl -fsSL https://raw.github.com/Homebrew/homebrew/go/install)"

inthecloud247

#/bin/bash

archive=$1

if [ -z "$archive" ]; then
  echo "No archive provided."
  echo "Usage: $0 archive.tar"
  exit
fi

inthecloud247

# Setup the application's runit directory
/etc/sv/application:
  file.directory:
    - mode: 0755
    - user: someuser
    - group: someuser
    - recurse:
      - user
      - group
      - mode

inthecloud247

    

Docker Governance Advisory Board First Meeting
Notes 28 October 2014

Interim Chair: Van Lindberg (VL)



Attendees/Acronyms table:

inthecloud247

Zero downtime deploys with gunicorn

Below are the actual files we use in one of our latest applications at Agora Games to achieve zero downtime deploys with gunicorn. I hope these files and notes help. I am happy to update these files or these notes if there are comments/questions. YMMV (of course).

Salient points for each file:

• gunicorn.py: The pre_fork function looks for gunicorn's old PID file in the proper file and sends the proper QUIT signal to the old process once the new process is running.
• sv-gunicorn-run.jinja: This is the runit template we use in our Salt-managed infrastructure for handling the application process management. You could just as easily convert this to a non-templatized version.

inthecloud247

#!/bin/bash
#
# This file is managed by Chef, using the <%= node.name %> cookbook.
# Editing this file by hand is highly discouraged!
#

# Copyright (c) 2014 Jean Mertz <jean@mertz.fm>
# 
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal

inthecloud247

Zero downtime deploys with gunicorn

Below are the actual files we use in one of our latest applications at Agora Games to achieve zero downtime deploys with gunicorn. I hope these files and notes help. I am happy to update these files or these notes if there are comments/questions. YMMV (of course).

Salient points for each file:

• gunicorn.py: The pre_fork function looks for gunicorn's old PID file in the proper file and sends the proper QUIT signal to the old process once the new process is running.
• sv-gunicorn-run.jinja: This is the runit template we use in our Salt-managed infrastructure for handling the application process management. You could just as easily convert this to a non-templatized version.

inthecloud247

Go here for the latest + some code.

numbat

An alerting engine for a metrics & monitoring system.

This is the same approach I wanted in my initial spike, only instead of writing a custom collector & using an existing alerting engine (riemann), I'm proposing using an existing collector (hekad) and writing the alerting engine.

The system

inthecloud247

supervisor:
  pkg.latest:
    - skip_suggestions: True
    - refresh: False
  service.running:
    - enable: True
    - reload: True
    - watch: [ file: supervisor ]
  file.managed:
    - name: /etc/supervisord.conf