I had to buy some switches recently and needed to gather a second quote from another vendor. I went to the Dell website and was pleasantly surprised to quickly find a clear price and a buy-now button for each device on their website. Normally … Continue reading
The post Clear Pricing for Network Services appeared first on The Network Sherpa.
It's a post-PC world.
Note: This article was originally published here.
One of the purposes when we designed the build system in OpenSwitch, was to make it possible to develop on as many environments as possible. If you have some background with developing networking firmware, the typical developer love to have this VM where everything works perfectly, but makes it impossible to work in your laptop at 30000 feet. This is not really a sin (as long as you can have the VM hosted in your machine), but the problem is that usually is some IT team on charge of the VMs setup, and the deployment is not handled by some automated/version-controlled code.
So for OpenSwitch, we aimed to at least document the requirements and steps for manual setup of your environment. You can read this page to get your Linux machine to ready it for OpenSwitch development.
So, why to write an article about my particular setup? Well, I’m a Mac user, so in this article I’m going to detail my setup using a OS X host with a Linux VM. This provides some nice tricks that makes your workflow easier if you are using a similar setup. I will also explain Continue reading
Mesosphere leads the charge with Microsoft, HPE, Cisco, and EMC support.
Making OpenStack easier, box by box.
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