Past versions were buckling under growing demand.
We’re thrilled to announce that Facebook has partnered with Cumulus Networks to bring you the industry’s first open optical routing platform loaded with Cumulus Linux. That’s right, Cumulus Networks is branching into some exciting new territory (a new voyage… if you will). We couldn’t be more honored and excited to work closely with Facebook to bring scalability and cost-effective hardware and software to the optical space — an industry that is growing rapidly.
Bandwidth for Internet services is becoming a more tangible challenge every single day, but the current proprietary solutions are too expensive and do not scale. As Facebook explained, “the highest-performing ‘bandwidth and reach’ are still fiber-based technologies — in particular, switching, routing, and transport DWDM technologies.” With the popularity of services that require a lot of bandwidth, like VR and video, there has become a critical need for better backhaul infrastructure that is cost-effective and scalable and supports high-performing wireless connectivity. The issue becomes even more critical when considering a variety of geographic conditions. For instance, rural regions need long backhaul pipes, which is cost-prohibitive.
That’s where Voyager comes in. Voyager was designed to bring the Internet to everyone — from dense urban locations to remote Continue reading
The much-touted partnership appears to be flailing.
Nobody likes to talk about the scope and scale of platforms than we do at The Next Platform. Almost all of the interesting frameworks for various kinds of distributed computing are open source projects, but the lack of fit and finish is a common complaint across open source software projects.
As Mark Collier, chief operating officer at the OpenStack Foundation, puts it succinctly: “Open source doesn’t have an innovation problem. It has an integration problem.”
Collier’s chief concern, as well as that of his compatriot, Jonathan Bryce, executive director of the OpenStack Foundation and a former Racker – meaning …
Keeping OpenStack On The Edge, Bleeding And Otherwise was written by Timothy Prickett Morgan at The Next Platform.
Fred Baker joins Network Collective for a second episode, this time sharing the story about how the IETF came to an official policy regarding systemic Internet surveillance and wiretapping in data networking.
Show Notes
Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/
The post History Of Networking – Fred Baker – RAVEN and Internet Surveillance appeared first on Network Collective.
Fred Baker joins Network Collective for a second episode, this time sharing the story about how the IETF came to an official policy regarding systemic Internet surveillance and wiretapping in data networking.
Show Notes
Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/
The post History Of Networking – Fred Baker – RAVEN and Internet Surveillance appeared first on Network Collective.
For several years there has been the ongoing debate about ARM and its future in the datacenter. That debate goes on, but the talk is changing.
At the beginning of the decade, ARM Holdings, the company behind the ARM chip architecture that is now owned by Japanese high-tech conglomerate Softbank, said its low-power system-on-a-chip (SoC) designs were a good alternative to Intel’s dominant Xeon and derivative processors for servers and other hardware at a time when energy efficiency in systems was becoming increasingly important.
Over the years that has been speculation about when ARM-based chips would find a foothold …
Computing Is Bigger Than The Datacenter was written by Jeffrey Burt at The Next Platform.
![]() |
| Fig 1.1- TACACS and TACACS+ Server |
I’ve recently been working on a very simple Flask application that can be used as a demo application in containerized environments (here’s the GitHub repo). It’s nothing special, but it’s been useful for me as a learning exercise—both from a Docker image creation perspective as well as getting some additional Python knowledge. Along the way, I wanted to be able to track versions of the Docker image (and the Dockerfile used to create those images), and link those versions back to specific Git commits in the source repository. In this article, I’ll share a way I’ve found to tag Docker images with Git commit information.
Before I proceed any further, I’ll provide the disclaimer that this information isn’t unique; I’m building on the work of others. Other articles sharing similar information include this one; no doubt there are countless more I haven’t yet seen. I’m presenting this information here simply to show one way (not the only way) of including Git commit information with a Docker image.
Getting the necessary information from Git is actually far easier than one might think. This variation of the git log command will print only the full hash of the last commit Continue reading