While demand for TV services is being disrupted and subscribers are expecting more personalized experiences, operators need to satisfy customer video demands to stay competitive.
12 factors define a cloud-native application. It's also said that Kubernetes is designed for cloud native computing. So how do you create a 12-factor application using Kubernetes?
There's no denying that the last year has seen a great deal of turmoil in the OpenStack world, and here at Mirantis we're not immune to it. In fact, some would say that we're part of that turmoil.
We did tests deploying close to 1000 OpenStack nodes on a pre-installed Kubernetes cluster as a way of finding out what problems you might run into, and fixing them, if at all possible.
You can get an in-depth look at all of the new features in the Kubernetes 1.6 release notes, but let's get a quick overview here.
Managing Kubernetes applications looks difficult compared "apt-get install mysql". Fortunately there's Helm, a Kubernetes-based package installer that manages preconfigured packages of resources.
Kubernetes was designed to orchestrate multiple containers and replication. In this article, we'll look at three options: Replication Controllers, Replica Sets, and Deployments.
With so much going on in the space, which NFV orchestration option is right for you?
Ideally, users should be able to have the same experience (such as the VNC console) to access their nova instances -- even if they're created by Ironic.
You may already have looked at Puppet, Chef or Ansible but today we focus on SaltStack. Simplicity is at its core, without any compromise on speed or scalability.
Availability zones are one of the most frequently misunderstood and misused constructs in OpenStack.