In this pair of articles I will be dissecting the fundamentals of cooling and refrigeration from an IT engineering perspective, then going over the process of sizing a cooling system. As infrastructure engineers, we likely deal with the topic of cooling on occasion, and those occasions tend to be during a facility buildout/upgrade or outage […]
The post Back to Basics: Cooling – Part 1 appeared first on Packet Pushers.
In this pair of articles I will be dissecting the fundamentals of cooling and refrigeration from an IT engineering perspective, then going over the process of sizing a cooling system. As infrastructure engineers, we likely deal with the topic of cooling on occasion, and those occasions tend to be during a facility buildout/upgrade or outage […]
The post Back to Basics: Cooling – Part 1 appeared first on Packet Pushers.
The post Worth Reading: Datera emerges from stealth appeared first on 'net work.
Some time back a reader sent this question in—
Is there some list of design fundamentals which were “true” or at least “good rules of thumb” in the past (2 months to 20 years and beyond) which are still proclaimed as true and good, which we need to throw out, or at least question closely today?
It’s an interesting question—the problem is, of course, that there are two sorts of answers to this type of question. The first is rather specific, and the second is rather general. Let’s try the more specific answer first, and see if we can get to the more general one.
There are several rules of thumb that are no longer useful today.
OSPF and IS-IS flooding domains should be limited to 50/100/200 routers/intermediate systems. The old “50 in an area rule” is something several of us asked to be removed from Cisco Online something like 10 years ago, as it didn’t even apply then. I’ve heard 200 more recently, but the reality is—there is no right number here. I just did a two post series on dividing up flooding domains that might be useful here (part 1 and part 2).
There are provider Continue reading
The big Red Herring in networking over the past ten years is most things labeled “innovative” when the word that should be used is “iterative.”
The post SDN is NOT an Innovation, its Iteration appeared first on EtherealMind.
Today we're releasing a whole suite of upgrades to page rules: API support, additional settings, pausing a page rule and a mobile-friendly design. Page Rules is the technology that allows you to configure your CloudFlare settings on a per-URL basis. It's often our most powerful feature, enabling CloudFlare domain owners to customize CloudFlare's functionality to exactly match their application's needs.
Page Rules are now fully programmable via API.
$ curl -X POST "https://api.cloudflare.com/client/v4/zones/${ZONE_TAG}/pagerules"
-H "X-Auth-Email: [email protected]"
-H "X-Auth-Key: 000000000000"
-H "Content-Type: application/json"
--data '{
"targets":[{
"target":"url",
"constraint":{
"operator":"matches",
"value":"*example.com/images/*"
}
}],
"actions":[{
"id":"always_online",
"value":"on"
}],
"priority":1,
"status":"active"
}'
Starting today, you can script the creation and modification of page rules. You can integrate page rules into your deployment process to bypass caching on every new API endpoint you ship, or to automatically sync your page rules across your domains on CloudFlare. Check out the page rules API docs and get started today. We can't wait to see what automations you build.
Instead of the short list of settings you could previously toggle, we've added menus with almost every Continue reading
The post Worth Reading: 30 years later, where is the smart home? appeared first on 'net work.