- Requests hitting the same load balancer can't handle HTTP and HTTPS at the same time because of SSL issues
- If you are trying to access an outside resource behind a firewall, you have to tell them every time you get a new webserver so they can whitelist the new IP
- If you know the IPs of your web servers and database servers, you can have requests hit these directly and bypass the load balancers.
- Could buy your own data center, but then you have to buy a load balancing router. Those are fucking expensive (tens or hundreds of thousands of dollars)
http = require('http') | |
Redis = require("redis") | |
c = Redis.createClient(@port, @host) | |
marshal = (req) -> | |
JSON.stringify | |
method: req.method | |
url: req.url | |
headers: req.headers | |
body: req.body | |
Adrian -
I appreciate that you spent time in writing this post. I know I've been up until 2am writing similarly long ones as well. I will take responsibility for having what is likely an irrational response (I blame Twitter for that) to the term "NoOps", but I invite you to investigate why that might be. I'm certainly not the only one who feels this way, apparently, and thus far have decided this issue is easily the largest distraction in my field I've encountered in recent years. I have had the option to simply ignore my opposition to the term, and just let the chips fall where they may with how popular the term "NoOps" may or may not get. I have obviously not taken that option in the past, but I plan to in the future.
You're not an analyst saying "NoOps". Analysts are easy (for me) to ignore, because they're not practitioners. We have expectations of engineering maturity from practitioners in this field of web engineering, especially those we consider leaders. I don't have any expectations from analysts,
Add the following chunk to your existing ISC dhcpd.conf
file.
if exists user-class and ( option user-class = "iPXE" ) {
filename "http://boot.smidsrod.lan/boot.ipxe";
}
else {
filename "undionly.kpxe";
}
(or see https://gist.github.com/4008017 for a more elaborate setup
local Emitter = require('core').Emitter | |
local Error = require('core').Error | |
local table = require('table') | |
local childprocess = require('childprocess') | |
function split(str, pattern) | |
pattern = pattern or '[^%s]+' | |
if pattern:len() == 0 then pattern = '[^%s]+' end | |
local parts = {__index = table.insert} | |
setmetatable(parts, parts) |
# screen like C-a vs C-b | |
unbind-key C-b | |
set-option -g prefix C-a | |
# screen like C-a a vs C-b l | |
bind-key C-a last-window | |
bind a send-prefix | |
# large history | |
set-option -g history-limit 100000 |
[2012-07-12T20:55:25+00:00] INFO: Chef Run complete in 6.78975371 seconds | |
[2012-07-12T20:55:25+00:00] INFO: Running report handlers | |
Run options: -v --seed 16402 | |
# Running tests: | |
recipe::minitest_helper::user_for#test_0003_returns_octal_modes = 0.00 s = . | |
recipe::minitest_helper::user_for#test_0002_returns_the_proper_group = 0.00 s = . | |
recipe::minitest_helper::user_for#test_0001_returns_the_proper_user = 0.00 s = . | |
recipe::openssh-config::ssh_config#test_0004_binds_to_proper_port = 0.00 s = . |
I was inspired by Selena Deckelmann's list of Career Resources for Women (http://www.chesnok.com/daily/career-resources-for-women/), but couldn't think of much to contribute. So I thought maybe those of us already in the field and in a position to mentor could work on creating more. Please fork or comment and add your own!
Also: there is a wealth of info online and elsewhere dating back to the first time it occurred to our species to exchange labor for currency on these topics in general. What I hope we can provide here is our take as individuals. What we would say to someone if we were sitting across from her acting as a mentor. I don't think we should worry about being objectively "right", or about duplicating topics. I add this bit of anti-editorializing in hopes that women will contribute without feeling pressured to be experts, which I worry might prevent them from doing so. TY. :)
- "developer resumes in < 5 minutes" from @garann https://vimeo.com/47550018
- "Cover Letters in 5 m