As OpenStack supporters and tire kickers convene in Mountain View next week at the Unlocked Infrastructure Conference (a.k.a. OpenStack Silicon Valley), it is Unlocked Performance that I will have on my mind. Lately I’ve become a zealous red-flag waver on this issue. In fact, I recently warned of a DevOps train wreck in an article in The New Stack, and I’d like to ring that warning bell again:
Barcelona es Teva! Vote for Our OpenStack Summit Sessions
Wow! 1500+ session proposals! Voting is open for the OpenStack Summit Barcelona, and “Barcelona es Teva” (Barcelona belongs to you!)! Take this opportunity to speak your mind: VOTE HERE
The beauty of Kubernetes is that it essentially frees an application developer from having to worry about the underlying infrastructure upon which the app runs. If only we could give operators the confidence that Kubernetes will run on their platform of choice—from private infrastructure to public providers—and their host operating system of choice. Oh, and while we’re at it, let’s bundle in the additional operational tooling to monitor the health of Kubernetes itself.
Until now, microservice application developers and infrastructure operators have been stuck with old monitoring tools designed for monolithic technologies, where it is common for schedulers to take several minutes to do their work.
When running on software-defined infrastructure, applications share physical hardware resources. Resource contention on a host can lead to reduced and unpredictable performance of an application.TL;DR… It does not matter how much CPU is available if workloads are competing for memory.
UPDATE: Headline changed to reflect proper expression of energy around containers. Super stoked that so many people wrote me to suggest the change!
The barbecue is long gone and house band, Soul Track Mind, that entertained us during the keynotes has packed up their amps. Still, there’s one meal or one song (choose your metaphor) that we Stackers can’t get enough of: Containers.
This spring has been crazy at AppFormix, and I mean that in the best possible sense. So many good things have come to fruition that it’s amazing to think that it was less than a year ago when we announced that AppFormix was exiting stealth mode with our solution for moving slow, sleepy monitoring technology into the service-optimization era.
Last week, I attended the first CNCF technical member meeting in Squaw Valley as part of the Linux Foundation Collaboration Summit 2016. At the meeting, I was pleased to announce AppFormix contributes a nightly CI test job to run an end-to-end test suite on Azure.As part of the effort, we also implemented cloud provider scripts to deploy Kubernetes on Azure. On top of that, I announced the launch of kube-health, a new project in collaboration with contributors from Google that will monitor the health of Kubernetes control plane services.
We’ve all had one at one point or another. Usually, the culprit is a person or a group of people who are misbehaving, acting out, and causing a ruckus in your neighborhood. Well, our development environments aren’t much different. The cloud is a shared environment, much like our neighborhoods. And while a noisy neighbor may inhibit rest, in the cloud it means something completely different. In the cloud workloads compete with each other for resources, it is typical to spin up 100s of containers on a single server. In this environment, contention is inevitable and performance suffers.