Dell EMC, VMware Partner on HCI and Hybrid Cloud Platforms
The systems integrate Dell EMC hardware and VMware software.
The systems integrate Dell EMC hardware and VMware software.
Accenture, Sysco, Adidas, Medtronic, and Moody’s are early-access customers.
Last Friday, 25 August, a routing incident caused large-scale internet disruption. It hit Japanese users the hardest, slowing or blocking access to websites and online services for dozens of Japanese companies.
What happened is that Google accidentally leaked BGP prefixes it learned from peering relationships, essentially becoming a transit provider instead of simply exchanging traffic between two networks and their customers. This also exposed some internal traffic engineering that caused many of these prefixes to get de-aggregated and therefore raised their probability of getting accepted elsewhere.
Initial public cloud support is limited to AWS and Azure environments.
Conversely, Google will take advantage of Marketo's Engagement Platform.
VeloCloud's latest members include Symantec, VMware, and Forcepoint.
Openstack | Amazon AWS | VMware (VSwitch / DVSwitch) | |
---|---|---|---|
Virtual Network Continue reading |
We continue with our second part of the series on the Tsubame supercomputer (first section here) with the next segment of our interview with Professor Satoshi Matsuoka, of the Tokyo Institute of Technology (Tokyo Tech).
Matsuoka researches and designs large scale supercomputers and similar infrastructures. More recently, he has worked on the convergence of Big Data, machine/deep learning, and AI with traditional HPC, as well as investigating the post-Moore technologies towards 2025. He has designed supercomputers for years and has collaborated on projects involving basic elements for the current and more importantly future exascale systems.
TNP: Will you be running …
Heterogeneous Supercomputing on Japan’s Most Powerful System was written by Nicole Hemsoth at The Next Platform.
The post Worth Reading: The rise of info-monopolies appeared first on rule 11 reader.
This is a new 5-part video series in Docker’s Modernize Traditional Apps (MTA) program, aimed at Microsoft IT Pros. The video series shows you how to move a .NET 3.5 app from Windows Server to a Windows Docker container and deploy it to a scalable, highly-available environment in the cloud – without any changes to the app.
Part 1 introduces the series, explaining what is meant by “traditional” apps and the problems they present. Traditional apps are built to run on a server, rather than on a modern application platform. They have common traits, like being complex to manage and difficult to deploy. A portfolio of traditional applications tends to under-utilize its infrastructure, and over-utilize the humans who manage it. Docker Enterprise Edition (EE) fixes that, giving you a consistent way to package, release and manage all your apps, without having to re-write them.
Part 2 shows how easy it is to move traditional apps to Docker EE. I start with an ASP.NET 3.5 WebForms application running on Windows Server 2003, and use Image2Docker to extract the app and package it as a Docker image. Then I run the application in a Docker Windows container on Continue reading
At 03:22 UTC on Friday, 25 August 2017, the internet experienced the effects of another massive BGP routing leak. This time it was Google who leaked over 160,000 prefixes to Verizon, who in turn accepted these routes and passed them on. Despite the fact that the leak took place in Chicago, Illinois, it had devastating consequences for the internet in Japan, half a world away. Two of Japan’s major telecoms (KDDI and NTT’s OCN) were severely affected, posting outage notices (KDDI / OCN pictured below).
Massive routing leaks continue
In recent years, large-scale (100K+ prefix) BGP routing leaks typically fall into one of two buckets: the leaker either 1) announces the global routing table as if it is the origin (or source) of all the routes (see Indosat in 2014), or 2) takes the global routing table as learned from providers and/or peers and mistakenly announced it to another provider (see Telekom Malaysia in 2015).
This case is different because the vast majority of the routes involved in this massive routing leak were not in the global routing table at the time but instead were more-specifics of routes that were. This is an important Continue reading