Simple Dashing widget (and associated job) to display Pingdom checks.
##Dependencies
Add it to dashing's gemfile:
There are loads of tools out there built around the AWS APIs. In response to that, some software comes with an AWS compatibility layer. One of them is EMC Atmos.
There's a surprising lack of documentation on how to actually use this compatibility. The best I could find is the "EMC® Atmos™ Version 2.1 Programmer’s Guide P/N 300-013-493 REV 01". However, all it does it tell you that the S3 compatibility is hosted on a different port, and which operations are supported. It doesn't give any hints on how to get any tools working.
The main gotcha seems to be that the S3 API has both a path and DNS based way of accessing buckets. It's important to use the path based mechanism.
JetS3t
#!/bin/bash | |
BRIDGE="br-int" | |
ovs-vsctl --may-exist add-br $BRIDGE | |
ovs-vsctl --if-exists del-port $BRIDGE $5 | |
ovs-vsctl --may-exist add-port $BRIDGE $5 |
# Update, upgrade and install development tools: | |
apt-get update | |
apt-get -y upgrade | |
apt-get -y install build-essential | |
apt-get -y install git-core | |
# Install rbenv | |
git clone git://github.com/sstephenson/rbenv.git /usr/local/rbenv | |
# Add rbenv to the path: |
#!/bin/bash | |
CONTENT_TYPE="application/json" | |
DESCRIPTION="bad things™ are happening" | |
URL="https://events.pagerduty.com/generic/2010-04-15/create_event.json" | |
if [ $# -ne 3 ]; then | |
echo "Usage: pd-event.sh [TYPE] [SERVICE KEY] [INCIDENT KEY]" | |
echo " - TYPE: [t]rigger | [a]cknowledge | [r]esolve" | |
echo " - SERVICE KEY: unique identifier for service" |
module Gem | |
class << self | |
## | |
# Returns full path of previous but one directory of dir in path | |
# E.g. for '/usr/share/ruby', 'ruby', it returns '/usr' | |
def previous_but_one_dir_to(path, dir) | |
split_path = path.split(File::SEPARATOR) | |
File.join(split_path.take_while { |one_dir| one_dir !~ /^#{dir}$/ }[0..-2]) |
Problem: Terraform doesn't play nicely with pre-existing infrastructure.
Solution: Officially there isn't one - but here's a work-around that does the trick.
Apply
the plan, thus instantiating the temporary "twinned" resource and building a state file.There are two parts to this:
In general, a CentOS 7 x86_64 box in AWS EC2; in specific, this Packer profile.
Small script to execute a apache benchmark ab
from one host to other.
The scripts are designed for benchmark tsuru routers, and compare between hipache+nginx vs. vulcand.
It will gather metrics of request time and CPU in the target so they can be later plot using gnuplot.
This gist includes some https://concourse.ci job tasks
hello-world.yml
- displays "hello world"display-other-task.yml
- uses this task as a resource itself and displays the hello-world.yml
YAML; assumes that the gist is available in the concourse pipeline as resource-gist
.display-other-task-renamed-resource-input.yml
- is like the task above, but assumes the resource is now named gist
rather than resource-gist