The intent-based Boulder & Aspen projects are designed to open up networking.
A couple of recent analyst reports tout significant growth in the information security market. But More security spending on products doesn’t necessarily mean better outcomes for customers.
The post Increased Security Spending: Good Money After Bad? appeared first on Packet Pushers.
Citrix is reportedly mulling a selloff of its entire business, or certain assets. Dell is a possible suitor.
Join the Cisco DemoFriday on September 25th and learn how you can benefit from network programmability as you transition from legacy systems to open standard interfaces.
A five-year-old upstart garners investments from Google, Microsoft, Baidu, and Qualcomm and sets its sights on competing with Amazon Web Services.
Datiphy watches how data is being used — a managed service that's being turned into a software product for the U.S. market.

Ethan has an excellent post up on Interoperate or Die. Herewith, a few thoughts in response.
From my perspective, the importance of open standards in the world of network engineering can hardly be overstated. As networks become more complicated (or complex, depending on what word you want to use), having consistent interfaces will become increasingly important. Think of the old IP model — every transport runs on top of IP, and IP runs on top of every physical/link layer. Using IP as a “choke point” built a “wasp waist,” a single API everyone on both sides of the narrow point in the protocol layer could talk to.
in recent years, we’ve forgotten the wasp waist. We’ve built everything over HTTP, and everything over Ethernet over IP, and everything over GRE over IP, and… The entire stack, above IP, is a hornet’s nest of convoluted caverns and side halls pointing, apparently, everywhere at once (like the guy from the forest in The Point, above).
If you think of IP as an API (which is really what it is), the point is to have a single layer API between any two interacting systems. This creates a clean interaction surface that helps you to Continue reading
When I wrote my stretched VSAN post, I thought VSAN uses asynchronous replication across WAN. Duncan Epping quickly pointed out that it uses synchronous replication, and I fixed the blog post.
The “What about latency?” question immediately arose somewhere in my subconscious, but before I could add that thought to the blog post (because travel), Anders Henke wrote a lengthy comment that totally captured what I was thinking, so I’m including it in its entirety:
Read more ...I recently came across IPython while reading some Python development blogs. IPython is an alternative to the standard Python shell that offers some additional features. When I first read about IPython, I was a little confused because many people refer to it as the ‘Python interactive shell’. While IPython is an interactive shell, it is not the Python interactive shell. For instance, we can enter the Python interactive shell just by typing ‘python’ on our Python development box…
So, what we really did here was invoke the Python interpreter in interactive mode. In this mode, commands can be read from the TTY and directly interpreted. So for example, we can do something like this…
The Python code we type is directly interpreted and we get the output we would expect. So instead of using the Python interpreter to run a .py script, we could do it all directly from the interpreter. So the example from our Python up and running post works just as well in interactive mode as it did when run as a script…
![]()
So that’s Python interactive mode. Now, let’s talk about IPython. The first thing we Continue reading