ONF Debuts Northbound Interfaces for Intent-Based Networking
The intent-based Boulder & Aspen projects are designed to open up networking.
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.
We’re happy to announce the release of Ansible Tower 2.3, our console and service that brings control, security, and delegation to your Ansible deployments.
Historically Tower has been installed with a simple setup playbook that you run with the Ansible you already have to download and install Tower. But not everyone has the luxury of access to the internet at all times.
Starting with Tower 2.3, we now offer a bundled installer for Red Hat Enterprise Linux and CentOS systems. This all-in-one installer contains everything you need to get Tower started in one bundle, including bootstrapping of Ansible for you as needed. All you need is a Red Hat or CentOS machine with access to the vendor OS repositories - no other external access required. The playbook installer is still available as well, and Tower is also still available via Vagrant image or AMI if you’d prefer to try it via that method.
As usual, this release of Tower includes a variety of bug fixes as well, including performance improvements around listing jobs and job templates.
For more information on Tower 2.3, check the release notes at: http://docs.ansible.com/ansible-tower/latest/html/installandreference/release_notes.html
To try Ansible Tower 2.3 Continue reading
Citrix is reportedly mulling a selloff of its entire business, or certain assets. Dell is a possible suitor.
Welcome to Technology Short Take #54! In this episode, I’ve gathered an odd collection of links and articles about key data center technologies. Without further ado, let’s get to the content.
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.
This is a guest post by Yiftach Shoolman, Co-founder & CTO of redislabs. Will 3D XPoint change everything? Not as much as you might hope...
Recently, investors, analysts, partners and customers have asked me how the announcement from Intel and Micron about their new 3D XPoint memory technology will affect the in-memory databases market. In these discussions, a common question was “Who needs an in-memory database if all the non in-memory databases will achieve similar performance with 3D XPoint technology?” Well, I think that's a valid question so I've decided to take a moment to describe how we think this technology will influence our market.
First, a little background...
The motivation of Intel and Micron is clear -- DRAM is expensive and hasn’t changed much during the last few years (as shown below). In addition, there are currently only three major makers of DRAM on the planet (Samsung Electronics, Micron and SK Hynix), which means that the competition between them is not as cutthroat as it used to be between four and five major manufacturers several years ago.
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 ...