Arista’s New CFO Is Some Kid Named Andy Bechtolsheim
Don't worry. He's done this before.
Don't worry. He's done this before.
Chris Miller is the principal architect for AdvizeX in Columbus OH. He runs the NSX program from a technical and marketing perspective, including enterprise pre-sales support and go-to-market strategies.
***
I started my career as a traditional Cisco networking guy. I spent 10 to 15 years as a network architect. But I’d been tracking what was going on in the community, with Open Flow and some of the other technologies. When I saw what VMware was doing, it got me pretty excited. I thought, ’It’s pretty revolutionary what’s going on here.’ I immediately jumped on the opportunity to take part in NSX.
In terms of enterprise customers, we weren’t initially seeing a lot of adoption in the market. Then VMware announced the Nicira acquisition, and Cisco announced what they were going to do with ACI, and heads started turning. I realized, you know, here are two of our largest partners putting their investment dollars behind this technology. And then, when I saw what NSX could do, and the benefits it could bring, it was very clear to me that this was the next wave.
What excites me most about network virtualization is that you essentially don’t have to Continue reading
I’m constantly ranting against large layer-2 domains; recently going as far as saying “we don’t really need all that stuff.” Unfortunately, the IP+Ethernet mentality is so deeply ingrained in every networking engineer’s mind that we rarely ever stop to question its validity.
Let’s fix that and start with the fundamental question: What is Layer-2?
Read more ...In previous posts, we talked about running skyDNS and Heapster on your Kubernetes cluster. In this post, I want to talk about the last of the cluster ‘addons’ available today in the Kubernetes repository. This add on is a combination of Fluentd, Elasticsearch, and Kibana that makes a pretty powerful logging aggregation system on top of your Kubernetes cluster. One of the major struggles with any large deployment is logging. Having a central place to aggregate logs makes troubleshooting and analysis considerably easier to do. That being said, let’s jump right into the configuration.
Note: I have an open PR on this addon to make it a little more flexible from a configuration perspective. Namely, I want to be able to specify the port and protocol used by the API server to access the backend service when using the API server as a service proxy. That being said, some of my pod/controller definitions will be different from what you see on GitHub. I’ll point out the differences below when we come across them.
The first step is to have the Kubernetes nodes collect the logs. This is done with a local Fluentd Continue reading