kennwhite

Kenn's Chicken/King Prawn Coconut Curry (Korma)

Ingredients

• 2 cups red or yellow onions, well peeled, loosely chopped
• 6 cloves peeled garlic, finely grated
• 2" peeled ginger root, finely grated
• Optional: 1 medium serrano green pepper, seeded & cored, finely minced (leave out for no heat, use half pepper for medium, full for spicy)
• 14 oz plain greek yogurt (2% or whole milk, eg FAGE 5%)
• large can (~14 oz) unsweetened coconut milk (ideally containing no guar gum; well blended if it does)
• 3 TB cashew butter

eshelman

Latency Comparison Numbers
--------------------------
L1 cache reference/hit                       1.5 ns                      4 cycles
Floating-point add/mult/FMA operation        1.5 ns                      4 cycles
L2 cache reference/hit                       5   ns                      12 ~ 17 cycles
Branch mispredict                            6   ns                      15 ~ 20 cycles
L3 cache hit (unshared cache line)          16   ns                      42 cycles
L3 cache hit (shared line in another core)  25   ns                      65 cycles
Mutex lock/unlock                           25   ns
L3 cache hit (modified in another core)     29   ns                      75 cycles

leonardofed

A curated list of AWS resources to prepare for the AWS Certifications

A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.

---

kennwhite

UPDATE 10-31-2015: I finally got Cent6.x working, skip to bottom.

These are my notes from getting the LetsEncrypt beta client running on Debian and CentOS using Google Compute Engine (GCE) and AWS.

Preface

botchagalupe

#My Presentations

2009

[Devopsdays Ghent - Open Spaces - Chef Overview] (no video)

[NOSQL East - Keynote - Cambrian Explosion] (http://uggedal.com/journal/nosql-east-2009---summary-of-day-1/) (lost video)

acolyer

Internet Scale Services Checklist

A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."

• http://mvdirona.com/jrh/talksandpapers/jamesrh_lisa.pdf

Basic tenets

• Does the design expect failures to happen regularly and handle them gracefully?
• Have we kept things as simple as possible?

tristanfisher

Working with ansible-vault

---

I've been using a lot of Ansible lately and while almost everything has been great, finding a clean way to implement ansible-vault wasn't immediately apparent.

What I decided on was the following: put your secret information into a vars file, reference that vars file from your task, and encrypt the whole vars file using ansible-vault encrypt.

Let's use an example: You're writing an Ansible role and want to encrypt the spoiler for the movie Aliens.

botchagalupe

#Devops and Networking

Proposal: Native Docker Multi-Host Networking #8951 Proposal: Native Docker Multi-Host Networking #8951

DevOps Road Blocks DOES14 - John Willis - DevOps Road Blocks

Managing Open vSwitch across a large heterogenous fleet Managing Open vSwitch across a large heterogenous fleet - Rackspace Openstack Summit Paris

chitchcock

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real