Deutsche Telekom Expands SD-WAN With VMware VeloCloud
In a big win for VMware, Deutsche Telekom this week announced a new partnership to bring VeloCloud...
In a big win for VMware, Deutsche Telekom this week announced a new partnership to bring VeloCloud...


Today has been a big day for Cloudflare, as we became a public company on the New York Stock Exchange (NYSE: NET). To mark the occasion, we decided to bring our favorite entropy machines to the floor of the NYSE. Footage of these lava lamps is being used as an additional seed to our entropy-generation system LavaRand — bolstering Internet encryption for over 20 million Internet properties worldwide.
(This is mostly for fun. But when’s the last time you saw a lava lamp on the trading floor of the New York Stock Exchange?)

A little context: generating truly random numbers using computers is impossible, because code is inherently deterministic (i.e. predictable). To compensate for this, engineers draw from pools of randomness created by entropy generators, which is a fancy term for "things that are truly unpredictable".
It turns out that lava lamps are fantastic sources of entropy, as was first shown by Silicon Graphics in the 1990s. It’s a torch we’ve been proud to carry forward: today, Cloudflare uses lava lamps to generate entropy that helps make millions of Internet properties more secure.

Housed in our San Francisco headquarters is a wall filled with dozens of lava lamps, Continue reading
The speed bumps with switch ASICs are coming fast and furious these days, and the datacenter is no longer dominated by the big switch incumbents such as Cisco Systems and Juniper Networks, which made their own chips, switches, and operating systems, and the networking divisions of server OEMs like Dell and Hewlett Packard Enterprise, which made some of their own gear – including ASICs – and acquired other companies to help build out their networking businesses – who sometimes also did their own ASICs. …
Everyone Will Want Higher Bandwidth And More Ports – Eventually was written by Timothy Prickett Morgan at The Next Platform.
Today's Heavy Networking welcomes back sponsor Arrcus to discuss the latest advancements in its ArcOS NOS, including support for Jericho2 ASICs, the new ArcIQ Analytics platform, and the vote of confidence from investors in the form of a $30 million funding round. Our guests are Keyur Patel, CTO and founder; and Murali Gandluru, VP of Product Management.
The post Heavy Networking 471: Routing-Centric Transformation With Arrcus’s ArcOS (Sponsored) appeared first on Packet Pushers.
When learning a new technology like Istio, it’s always a good idea to take a look at sample apps. Istio repo has a few sample apps but they fall short in various ways. BookInfo is covered in the docs and it is a good first step. However, it is too verbose with too many services for me and the docs seem to focus on managing the BookInfo app, rather than building it from ground up. There’s a smaller helloworld sample but it’s more about autoscaling than anything else.
In this post, I’d like to get to the basics and show you what it takes to build an Istio enabled ‘HelloWorld’ app from ground up. One thing to keep in mind is that Istio only manages the traffic of your app. The app lifecycle is managed by the underlying platform, Kubernetes in this case. Therefore, you need to understand containers and Kubernetes basics and you need to know about Istio Routing primitives such as Gateway, VirtualService, DestinationRuleupfront. I’m assuming that most people know containers and Kubernetes basics at this point. I will focus on Istio Routing instead in this post.
These are roughly the steps Continue reading
VMware CEO Pat Gelsinger thinks IBM paid too much for Red Hat at $34 billion. Meanwhile VMware paid...
Huawei is desperate to change global perceptions of its business and is willing to license its 5G...
Security-centric SD-WAN vendor Fortinet announced a partnership with Telenor Sweden, while...

We all know by now that I’m not a huge fan of keynotes. While I’ve pulled back in recent years from the all out snark during industry keynotes, it’s nice to see that friends like Justin Warren (@JPWarren) and Corey Quinn (@QuinnyPig) have stepped up their game. Instead, I try to pull nuggets of importance from a speech designed to rally investors instead of the users. However, there is one thing I really have to stand my ground against.
We’ve seen these a hundred times at dozens of events. After the cheers and adulation of the CEO giving a big speech and again after the technical stuff happens with the CTO or product teams, it’s time to talk about…nothing.
Celebrity keynotes break down into two distinct categories. The first is when your celebrity is actually well-spoken and can write a speech that enthralls the audience. This means they get the stage to talk about whatever they want, like their accomplishments in their career or the charity work their pushing this week. I don’t mind these as much because they feel like a real talk that I might want to attend. Generally the celebrity talking Continue reading
Comcast today said it deployed Trellis, the Open Networking Foundation’s (ONF) open source SDN...
At different points in our careers it can be difficult to ask for help. Maybe the expectation is that your customer is paying for expertise and you have to demonstrate it. Maybe it’s just embarrassing to admit when you don’t know something. Nobody can know it all though, so knowing when and how to ask for help will save you trouble and pain in your career. Listen in as Kevin Myers shares his thoughts on when, where, and how to ask for help.
The post Lessons Learned – Asking For Help – Kevin Myers appeared first on Network Collective.
If you thought the gang at Intel were Moore’s Law biggest devotees, you probably haven’t heard Philip Wong expound on the subject. …
TSMC Thinks It Can Uphold Moore’s Law For Decades was written by Michael Feldman at The Next Platform.
It used to be far easier to talk about storage performance, cost, and options. …
Keeping Pace with Rapid Storage Sophistication was written by Nicole Hemsoth at The Next Platform.


To our potential shareholders:
Cloudflare launched on September 27, 2010. Many great startups pivot over time. We have not. We had a plan and have been purposeful in executing it since our earliest days. While we are still in its early innings, that plan remains clear: we are helping to build a better Internet. Understanding the path we’ve taken to date will help you understand how we plan to operate going forward, and to determine whether Cloudflare is the right investment for you.
Cloudflare was formed to take advantage of a paradigm shift: the world was moving from on-premise hardware and software that you buy to services in the cloud that you rent. Paradigm shifts in technology always create significant opportunities, and we built Cloudflare to take advantage of the opportunities that arose as the world shifted to the cloud.
As we watched packaged software turn into SaaS applications, and physical servers migrate to instances in the public cloud, it was clear that it was only a matter of time before the same happened to network appliances. Firewalls, network optimizers, load balancers, and the myriad of other hardware appliances that Continue reading
kustomize is a tool designed to let users “customize raw, template-free YAML files for multiple purposes, leaving the original YAML untouched and usable as is” (wording taken directly from the kustomize GitHub repository). Users can run kustomize directly, or—starting with Kubernetes 1.14—use kubectl -k to access the functionality (although the standalone binary is newer than the functionality built into kubectl as of the Kubernetes 1.15 release). In this post, I’d like to provide an introduction to kustomize.
In its simplest form/usage, kustomize is simply a set of resources (these would be YAML files that define Kubernetes objects like Deployments, Services, etc.) plus a set of instructions on the changes to be made to these resources. Similar to the way make leverages a file named Makefile to define its function or the way Docker uses a Dockerfile to build a container, kustomize uses a file named kustomization.yaml to store the instructions on the changes the user wants made to a set of resources.
Here’s a simple kustomization.yaml file:
resources:
- deployment.yaml
- service.yaml
namePrefix: dev-
namespace: development
commonLabels:
environment: development
This article won’t attempt to explain all the various fields that could be Continue reading