-

Containers are often intended to solve a single, narrowly defined problem, such as a microservice, but in the real world, problems require multiple containers for a complete solution.

-

We thought we’d give you our traditional 53 things to look for in advance of our What’s New in OpenStack Pike webinar, which is scheduled for September 7.

-

Instead of large integrated releases after every OpenStack Foundation release, MCP DriveTrain enables you to consume some or all of the latest innovation without downtime.

-

Cloud and agile are tools used to build a technology business.

-

Jenkins is crucial for CI/CD. But how do you get it to build the app when changes are pushed to your GitHub repo? Here’s a simple explanation.

-

Earlier this year, we here at Mirantis found ourselves in a situation where we needed to upgrade across two OpenStack releases.

-

NFV makes it possible to do most of what the telcos were doing using specialized hardware, but with disaggregated network functions that can be adapted for new situations on COTS hardware.

-

There are a lot of differences between OpenStack and Kubernetes, but one thing they both share is that setting them up is far from trivial.

-

Virtlet is a Kubernetes CRI (Container Runtime Interface) implementation for running VM-based pods on Kubernetes clusters.

-

We talked to Mariela Gagnon of Cre8Hires and consultant Jens Soldners about one of your greatest advantages: technical certifications.

-

Telcos, multiple-system operators (MSOs i.e. cable & satellite providers), and network providers are under pressure on several fronts.

-

Kubernetes 1.7 is out, focusing on production features such as security, extensibility, and stateful applications. Do you need it? Well, let’s look at what it does for you.

-

If you’re not in the telecom business, you probably haven’t given much thought to the upcoming 5G standard, except perhaps to wonder when your phone will have faster data.

-

Last week we spoke to Ryan Day about using Continuous Integration/Continuous Deployment (CI/CD) to keep not just your own software, but also externally produced software, up to date.

-

The entire OPNFV stack, ultimately, serves one purpose: to run virtual network functions (VNFs) that in turn constitute network services.

Subscribe to Our Newsletter

Latest Tweets

Suggested Content

LIVE DEMO
Mirantis Cloud Platform
WEBINAR
Top Sysadmin Tasks and How to Do Them with OpenStack
WEBINAR
ONAP Overview