Google Supports Hybrid Cloud with Cloud Dedicated Interconnect
Google can now better compete against AWS and Azure.
Google can now better compete against AWS and Azure.
The company would be the second major cable operator to offer SD-WAN.
The general HPC market might be growing, and the very definition of HPC is expanding thanks to the addition of advanced analytics and machine learning to the HPC toolbox. But it is tough slogging right now in the upper echelons of HPC where supercomputers roam.
There is perhaps no better barometer of the state of supercomputing than Cray, which sells a mix of processing, storage, and interconnect technologies to address the ever-widening scope of modern supercomputing. Because of a general slowdown in supercomputer sales thanks to the fact that organizations are keeping their systems around for longer than they usually …
Cray Looks Forward To Supercomputing Rebound was written by Timothy Prickett Morgan at The Next Platform.
Over the last week or so, I’ve been trying to spend more time with Microsoft Azure; specifically, around some of the interesting things that Azure is doing with containers and Kubernetes. Inspired by articles such as this one, I thought it would be a pretty straightforward process to use the Azure CLI to spin up a Kubernetes cluster and mess around a bit. Simple, right?
Alas, it turned out not to be so simple (if it had been simple, this blog post wouldn’t exist). The first problem I ran into was the upgrading the Azure CLI from version 2.0.13 to version 2.0.20 (which is, to my understanding, the minimum version needed to do what I was trying to do). I’d installed the Azure CLI using this process, so pip install azure-cli --upgrade should take care of it. Unfortunately, on two out of three systems on which I attempted this, the Azure CLI failed to work after the upgrade. I was only able to fix the problem by completely removing the Azure CLI (which I’d installed into a virtualenv), and then re-installing it. First hurdle cleared!
With the Azure CLI upgraded, I proceeded to Continue reading
The internet of things will move more processing to telecom suppliers' facilities.
The internet of things will move more processing to telecom suppliers' facilities.
I love reading well-argued contrarian views, and Geoff Huston’s Opinion in Defense of NAT is definitely worth the time it will take you to read it.
TL&DR: Geoff argues that with all the wastage going on in IPv6 land (most bizarre: let’s give a /48 to every residential subscriber) the number of bits available for IPv6 endpoint addressing gets close to what we can squeeze out of IPv4 NAT.
Containerizing a single legacy application with Docker Enterprise Edition (EE) can be quite simple and immediately makes the application more portable, scalable, and easier to manage and update. Taking this application to production requires additional planning and collaboration with security teams, performance testing and likely requires detailed operations and disaster recovery plans. This part of the process often has little to do with the technology but with the changes to the organization and governance model.
At DockerCon Europe, I presented a talk on the best practices and processes for taking a containerized legacy app or set of apps from a proof of concept (PoC) to production with these changes in mind. You can watch the full talk here:
The Modernize Traditional Apps [MTA] Program is the result of working with hundreds of companies over the years with deploying and using Docker Enterprise Edition [EE]. Those experiences have been transformed into a prescriptive methodology with best practices and considerations to help you get successfully from PoC to production.
After the PoC there is a short assessment phase of the existing organization, tools, and processes and then choosing the pilot application that is representative of the application Continue reading
![]() |
| Fig 1.1- Basic Firewall deployment in the Network |