jwieringa

variable "s3_bucket_id" {
  default = "s3-assets"
}

variable "s3_origin_id" {
  default = "S3-assets"
}

resource "aws_cloudfront_distribution" "main" {
  enabled             = true

jwieringa

Installing Fedora 23 on 4th gen (2016) X1 Carbon

(Last updated Apr 29 2016)

If you attempt to install Fedora 23 (any spin) on the 2016 X1 Carbon you'll receive a black screen just after kernel selection. This is caused by a kernel bug. You will need to add intel_pstate=no_hwp to the kernel boot arguments, which you are able to do from the kernel selection screen. After installation you must do this again to boot into the installed OS. Once booted, I recommend adding intel_pstate=no_hwp to your /etc/default/grub and running sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg, which will then cause any kernel to have this parameter added to it.

Once Fedora ships with the upcoming 4.6 kernel (and perhaps a patch to the 4.4 kernel, but that remains to be seen), you should be able to remove this argument.

~~Update Apr 21: The 4.4.7 kernel was released but still has these issues. It appears that the fix will be shipped in the 4.4.8 kernel: htt

jwieringa

resource "aws_security_group" "gocd_agent_elb" {
    name = "gocd-agent-elb-sg"
    description = "Security group for the gocd agent ELBs"
    vpc_id = "${var.vpc_id}"

    tags {
        Name = "gocd agent (ELB)"
    }

    # HTTP - SSL (SERVER TO AGENT)

jwieringa

source 'https://rubygems.org'

gem 'berkshelf', '~> 3.3.0'
gem 'test-kitchen', '~> 1.4.2'
gem 'kitchen-vagrant', '~> 0.18.0'
gem 'rake', '>= 10.4.2'
gem 'foodcritic', '>= 5.0.0'
gem 'rubocop', '>= 0.34.1'
gem 'chefspec', '~> 4.3'
gem 'serverspec', '~> 2.23.1'

jwieringa

.ONESHELL:
.PHONEY: help set-env init update plan plan-destroy show graph apply output taint

help:
	@grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | sort | awk 'BEGIN {FS = ":.*?## "}; {printf "\033[36m%-30s\033[0m %s\n", $$1, $$2}'

set-env:
	@if [ -z $(ENVIRONMENT) ]; then\
		 echo "ENVIRONMENT was not set"; exit 10;\
	 fi

jwieringa

- What do Etcd, Consul, and Zookeeper do?
  - Service Registration:
    - Host, port number, and sometimes authentication credentials, protocols, versions
      numbers, and/or environment details.
  - Service Discovery:
    - Ability for client application to query the central registry to learn of service location.
  - Consistent and durable general-purpose K/V store across distributed system.
    - Some solutions support this better than others.
    - Based on Paxos or some derivative (i.e. Raft) algorithm to quickly converge to a consistent state.
    - Centralized locking can be based on this K/V store.

jwieringa

FROM alpine:3.3
MAINTAINER Christopher Sexton <[email protected]>

ENV RUBY_VERSION 2.3.0
ENV RUBY_DOWNLOAD_SHA1 96e620e38af351c8da63e40cfe217ec79f912ba1

ENV BASE_PACKAGES bash curl gmp git
ENV BUILD_PACKAGES build-base libc-dev linux-headers openssl-dev postgresql-dev libxml2-dev libxslt-dev

RUN apk update && \

jwieringa

Hey! I saw this has been indexed by the search engines. It is a first draft of a post I ended up publishing on my blog at: Scaling PostgreSQL With Pgpool and PgBouncer

Thanks for stopping by!

PostgreSQL and Pgpool Architecture

jwieringa

#Nodevember Nodes

Yahuda Keynote

• basically a ember 101 walk-thru
• fastboot early 2016 inc client-side re-hydration

Elijah Manor - Code Smells

• switch statement --> strategy pattern
• eslint allows custom plugins
• enable/disabled rules @ file level, or block

jwieringa

variable "cluster-size" {
    description = "Number of CoreOS machines to deploy"
}

variable "region" {
    description = "AWS region in which to deploy"
    default = "us-east-1"
}

variable "coreos-ami" {