Windows Container-as-a-Service Platform

In a previous blog post, we showed you how ContainerX enables you to operate a multi-tenant, enterprise-grade container infrastructure using Elastic Clusters and Container Pools.

ContainerX has pushed the envelope further and now allows you to create, manage and operate both Windows and Linux elastic clusters from within a single pane of glass!  This means deploying apps in Windows containers running on Windows Server 2016 VMs on Azure is going to be a breeze.

Let’s look at how easy this is. Say your company would like to provision the ability to run containers for three different developer teams responsible for different types of applications:

  • Marketing apps
  • Accounting apps
  • Engineering apps

All you have to do is use CX’s quick wizard to create an “Elastic Cluster” and choose Windows Server 2016 (TP4) as the Operating System of your cluster. You can choose any number of Azure VMs to back your elastic cluster. Then, you create “Container Pools” by specifying the maximum resources you would like each team to have access to.

The IT admin chooses these limits based on typical usage patterns and needs of these teams:

  • Engineering apps: CPU and memory limit of 60%
  • Accounting apps: CPU and memory limit of 40%
  • Marketing apps: CPU and memory limit of 40%
Fig 1. Container pools within your Windows Elastic Cluster

After you’ve created the pools you need, the screencast (above) shows you how easy it is to start IIS within a Windows server container in the Marketing apps pool. (Don’t forget to watch it in HD!).

Container Pools

Our container pool technology will ensure that the total workload of any team will not exceed a pool’s max limits (as a percentage of the total available resources in the underlying hosts).  CX continually monitors every container running on this platform. Resource usage metrics are aggregated, analyzed and resource control knobs appropriately tuned to ensure resource isolation.

As CX works its magic to provide resource isolation on shared infrastructure, your teams are now ready to go and create as many containers as they need!

When the resource needs of your teams increase, the number of hosts underlying each cluster can be increased with a single-click. Resource allocations to each container pool will be automatically re-configured on the fly. New containers can continue to be deployed and utilize increased resource capacity.

Windows and Linux Clusters

Well, things look great, but say, you have a new team in your org that needs to run Linux containers. Having ContainerX means that you don’t have to do all the hard work of resolving any of the complexities involved in setting and configuring a new stack from the bottom up! A Linux Elastic Cluster can be setup via the exact same workflow on the UI as a Windows cluster.

Fig 2. Your Windows and Linux Elastic clusters accessible from within the same UI

Let’s say this team needs to isolate its dev, test and staging workloads. The admin simply creates three different pools for each workload type. The figure below illustrates what this setup will look like.

Fig 3. Conceptual overview of your Elastic Clusters and Container pools backed by hosts

If you can’t wait to run Windows and Linux clusters all within one easy-to-use platform, sign up for our Beta access here: ContainerX Beta signup!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s