Verizon Data Center Sale Still Up in the Air
Telco will decide in next three months whether or not to move ahead.
Docker and HPE: Accelerating modern app architectures in enterprise datacenters
Docker has evolved tremendously over the last 3 years to empower developers and IT operations teams to maintain greater control over their own environments without sacrificing agility. From an ops tool used by the original dotCloud team, to Docker’s commercially supported Containers-as-a-Service (CaaS) platform, Docker Datacenter (DDC), Docker has been at the forefront of this evolution.
Today we are excited to announce the next evolution in the Docker story providing enterprises with infrastructure optimized for the Docker platform with the leading provider of cloud infrastructure – Hewlett Packard Enterprise (HPE). Together, Docker and HPE will deliver integrated and fully supported Docker ready HPE x86 servers, bundled with Docker’s commercially supported Engine (CS Engine) right out of the box.
TCP/IP Is Lossy Protocol
The foundation of TCP/IP design is that the network is unreliable and packets will be lost.
The post TCP/IP Is Lossy Protocol appeared first on EtherealMind.
What’s Fueling the Move to a Converged Data Platform?
The datacenter is going through tremendous change, and many long-held assumptions are now being called into question. Even the basic process of separating data onto a separate storage area network, growing it, and pulling it across the network and processing it, is no longer necessarily the best way to handle data. The separation between production and analytics, which has evolved into an art form, is also breaking down because it takes a day or longer to get operational data into analytic systems.
As a backdrop to all of these technology changes, organizations say they need more agility. The ability to …
What’s Fueling the Move to a Converged Data Platform? was written by Nicole Hemsoth at The Next Platform.
Verizon Uses Radisys & Mojatatu for SDN & NFV
Mojatatu Who?
Worth Reading: IPv6 Link Local Addresses
The post Worth Reading: IPv6 Link Local Addresses appeared first on 'net work.
Supporting the transition to IPv6-only networking services for iOS
Early last month Apple announced that all apps submitted to the Apple Store June 1 forward would need to support IPv6-only networking as they transition to IPv6-only network services in iOS 9. Apple reports that “Most apps will not require any changes”, as these existing apps support IPv6 through Apple's NSURLSession and CFNetwork APIs.
Our goal with IPv6, and any other emerging networking technology, is to make it ridiculously easy for our customers to make the transition. Over 2 years ago, we published Eliminating the last reasons to not enable IPv6 in celebration of World IPv6 Day. CloudFlare has been offering full IPv6 support as well as our IPv6-to-IPv4 gateway to all of our customers since 2012.
Why is the transition happening?
IPv4 represents a technical limitation, a hard stop to the number of devices that can access the Internet. When the Internet Protocol (IP) was first introduced by Vint Cerf and Bob Kahn in the late 1970s, Internet Protocol Version 4 (IPv4) used a 32-bit (four-byte) number, allowing about 4 billion unique addresses. At the time, IPv4 seemed more than sufficient to power the World Wide Web. On January 31, 2011, the top-level pool of Internet Assigned Numbers Authority Continue reading
Netronome Supports P4 On Server Adapters For NFV
Netronome has announced server adapter support for P4, a language for programming packet-forwarding devices, to make x86 servers better suited for virtual networking.
The post Netronome Supports P4 On Server Adapters For NFV appeared first on Packet Pushers.
Building a “Network” Network
Over my years as a network engineer, I’ve notice that the engineering job tends to be somewhat isolated (or isolating). Part of the reason is probably that there tend to be one or two network engineers at a single company, munged in with a lot of other IT folks who share some common ground (but not entirely), so there’s little chance to interact with others who are working on the same sorts of problem sets on a day to day basis. This tends to produce network engineers who are more attached to their vendor than they are to their “day job.” In fact, this tends to make the entire network engineering world, to the average network engineer, appear to be “not much more” than the vendors who show up on our doorsteps, the vendor specific trade shows we can attend, and what we read online. This is—how can I say this gently—??
This is an unhealthy situation for your career as a network engineer—and as a person.
What you need to do is build a network of other network engineers—a network network—so you can broaden your scope, keep your ear to the ground for changes, prepare for changes, have Continue reading