SDxCentral Inside the Linux Container Ecosystem Report A

7/25/2019 SDxCentral Inside the Linux Container Ecosystem Report A

http://slidepdf.com/reader/full/sdxcentral-inside-the-linux-container-ecosystem-report-a 1/44



© 2016 SDNCentral LLC. All Rights Reserved. Page i

Market Report | Inside the Linux Container Ecosystem

contents

Table of Contents

Introduction -- What’s in a Linux Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Chapter 1: Container Wars -- LXCs vs. Docker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Chapter 2: Comparing Containers and VMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixChapter 3: Container Security, Networking, and Management . . . . . . . . . . . . . . . . . . . . . . . xi

Chapter 4: What Users Want: Survey Container Survey Results . . . . . . . . . . . . . . . . . . . . . .xiv

Chapter 5: Container NFV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii

Addressing NFV with Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii

Containers in NFV – challenges, best fit use-cases. . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv

Virtual CPE and Linux Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv

Vendor Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv

Companies [Featured]

Juniper Networks, Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Nuage Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Red Hat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Companies

Amazon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Ansible (a Red Hat Company) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Apcera . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

AppDynamics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

BlueData Software, Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Canonical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Chef Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Cisco Systems, Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

ClusterHQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

CoreOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Docker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Google . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

HashiCorp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Hewlett Packard Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Kismatic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Mesosphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Microsoft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

New Relic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Portworx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Puppet Labs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Rancher Labs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

SaltStack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Shippable, Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15



© 2016 SDNCentral LLC. All Rights Reserved. Page ii

market summary


SignalFX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Sysdig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Twistlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

VMware, Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Weaveworks Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18



http://www.opencontrail.org/

http://www.juniper.net/us/en/



© 2016 SDNCentral LLC. All Rights Reserved. Page v

market summary


Introduction -- What’s in a Linux Container?

Linux container technology: Everybody’s talking about it. Container has become one of those magic buzzwords that

can conjure up billions of dollars in capital and create market-leading companies such as Docker, overnight.

But what are containers used for, exactly, and how do they apply to existing virtualization and networking markets?

That is what we intend to define here in the first SDxCentral report on container infrastructure, which is sure to

become an annual tradition. This includes the development of important niches of the container ecosystem, including

container security, container networking, and Docker networking. Think of the container technology world as

developing parallels to all of the existing tools in the networking market.

The easiest way to think about container technology is it’s a new way to manage, distribute and run applications in a

more flexible and agile way. The concept of container technology uses the paradigm of shipping containers in

inter-modal transport. The idea is that before shipping containers were invented, manufacturers had to be prepared to

ship goods in a wide variety of modes – ships, trains, or trucks – with different sized containers and packaging. By

standardizing the shipping container, goods could be seamlessly transferred among shipping methods without any

additional preparation.

Linux Roots

Container technology emerged from the Linux world, based on key features in the Linux kernel, including cgroups and

namespaces. These features allow lightweight applications processes to be virtualized within the Linux OS. These

features were first exploited most publicly by Google Inc., which built its entire data-center architecture around

container technology and also developed the open source project Kubernetes, for managing containers and container

clusters. It became clear that just having container features in Linux was not enough: management tools would be

needed as well. Docker containers and Linux containers (LXCs) emerged as ways to manage containerized

applications and make them portable across networks.

The key for Linux container technology is that it can run on any compatible Linux operating system (OS), which only

requires a container runtime to execute the code. This means that the OS is “prepped” for the software so that it can

boot up and run fast. Several containers can run simultaneously on the same instance of an OS, which enables

OS-level virtualization – maximizing the resources of a server node. Pieces of compatible code can be distributed

across a data center, network, or even the cloud, so that a container application can be linked via APIs to processes

and applications in many different places. This approach enables the portability of code and allows the applications tobe quickly tested and deployed.

Flexibility & Agility Drive Container Popularity

Because of these characteristics of flexibility and agility, containers are increasingly being looked at to build and test

distributed applications. They are starting to gain interest in large-scale application deployments such as Fortune 500

companies. But as the popularity of container technology grows, it’s also clear that a wide ecosystem of tools need to

be built – tools to help network, orchestrate, manage, and support data for containerized applications. It’s still early in

the cycle as this large container ecosystem is built. We are likely to see containers applied to a wider world of the

cloud technology world over time.

According to SDxCentral’s Container Survey, only 7% of those surveyed have already deployed container technology,

but a whopping 76% are evaluating the technology (56% are looking at different solutions, while 20% are actively

testing/piloting). Less than a fifth (17%) of respondents are not considering container technology for theirenvironment. These are amazing stats, considering containers have really started to come into the limelight in the last

several years.



© 2016 SDNCentral LLC. All Rights Reserved. Page v

market summary


Chapter 1: Container Wars -- LXCs vs. Docker

So, we’ve defined a basic container: It’s a lightweight distributed app that runs on a compatible Linux OS. It’s grown

somewhat more confusing via the emergence of Docker, both as a company and an open-source project, which

provides a management platform as well as a specific runtime and OS system for Linux containers.

But why are containers suddenly hot now? It’s been interesting to watch how a somewhat mysterious and wonky

technology such as containers developed slowly for more than decade, originating in the open source software

community, and then suddenly took off.

From Solaris to Docker

Early versions of the container concept included FreeBSD Jails and Oracle Solaris “Zones.” As mentioned, Google took

major steps with container technology beginning around 2006 and developed Kubernetes. Docker was first

introduced as an open source environment for building containerized microservices in 2013.

Perhaps the table was set for container technology with virtualization and cloud. Now that server virtualization has

penetrated the market and many large companies are comfortable building applications in the cloud, container

technology makes sense. Because containers are another form of virtualization, some IT experts are looking at the

technology in cases in which it is more efficient than VMs – for example, it’s more efficient to run many instances of

software on a single OS.

The container world was transformed by the arrival of Docker, which was started as an open-source project (which stil

exists) and then later became a company, Docker Inc.. Docker helped containers get wider adoption by providing a

standardized set of tools for running container projects. But here’s the thing: Docker is not the only way to run

containers. As we mentioned, containers have deep origins in Linux. The LXC Project maintains many resources for

building LXC applications at linuxcontainers.org.

Container Platform Components

A Linux OS can be ready to run containers, but several elements are needed: You need a compatible OS, a runtime

that is compatible with the containers you want to run, a platform to manage the applications, and many other tools

for container orchestration, management, networking, and security. This report, especially the product listings at the

end, demonstrate how quickly the ecosystem for container technology is evolving.

Some parts of the community see containers in the context of LXCs vs. Docker. Think of it as a little bit like Windows

vs. Apple – there are proponents to each development environment. The differentiation largely comes in the

implementation at the Linux kernel.

The irony of the Docker vs. LXCs debate is that they both emerged from the world of open source world of Linux – the

idea being that organic, open development would drive the community of containers. It all sounds warm and fuzzy

until hundreds of millions of dollars of VC funding gets injected into the market. That’s when things get interesting.

How Docker Got the Containers Rolling

So you might ask: How was Docker so successful? In just a couple of years, it has emerged as the most popular

container platform. It is now supported as the container platform of choice by many software giants, including IBM,

Microsoft, and Red Hat.

Docker has some different ways of handling containers from LXCs, but then again they are both Linux-based projects

so there are also many compatibilities. It comes down to the specific implementations and way the containerized apps

are built. Docker and LXCs also have differences in how they handle things.

One major difference as defined by many experts in the market is that Docker only handles a single process, where as

LXCs are multi-process.1 There are also differences in how LXCs and Docker handle data storage. Docker doesn’t like

1 Rami Rosen, “Linux Containers and the Future Cloud” http://media.wix.com/ugd/295986_d5059f95a78e451db5de3d54f711e45d.pdf

https://linuxcontainers.org/

http://media.wix.com/ugd/295986_d5059f95a78e451db5de3d54f711e45d.pdf

http://media.wix.com/ugd/295986_d5059f95a78e451db5de3d54f711e45d.pdf

https://linuxcontainers.org/



© 2016 SDNCentral LLC. All Rights Reserved. Page vi

market summary


assigning static IP addresses to containers. Docker took this approach to streamline and simplify the way to

implement containers – which is has arguably done successfully.

So why have you probably heard more about Docker than LXCs – or other container technologies for that matter?

One key may be Docker images. These images are installed on the host OS to run a Docker process. Images are stored

on standard private and public Docker repositories for container images. In short, Docker provides many tools to makecontainers more simple to run. It got some momentum, and the image registries grew, attracting more developers. A

large funding round for the namesake company, Docker Inc., did not hurt. Follow that up with hundreds of articles

written in the technology press about “Docker containers” and you have a recipe for marketing success.

The Docker architecture is based on a client/server paradigm. To run Docker applications, a Docker client connects to

a Docker daemon, which is installed on a host system.

The client can be thought of as the user interface that communicates with the daemon, whereby the two nodes

communicate via sockets or through a RESTful API.

There are other key components of a Docker container, or other microservices system. These include:

Images – This is a template than can be pushed to install containerized applications. It may include the operating

system (OS) and applications.

Registry – These are public and private spaces where container images and applications are held.

The following image demonstrates these components as implemented in a Docker system:

Source: Docker



© 2016 SDNCentral LLC. All Rights Reserved. Page vii

market summary


Other container and microservices architectures are similar, even though Docker is on its way to becoming somewhat

of a de facto standard. But because LXCs and Docker are based on open source, many components are compatible.

Many large companies have publicly stated that a container approach has sped up the development of their

applications and platform. These companies include Yelp, AirBNB, and Google, among many others. Google cites wide

usage of open source container technology called IMCTFY.

This doesn’t mean that LXCs are dead, or that Docker has won, or that both can’t exist at the same time. Many

technology startups and developers are building tools to make LXCs more user friendly, just as Docker did. Both

technologies have their place. In same cases, technology companies are hedging their bets. For example, Canonical

(Ubuntu) has developed its own LXD solution over LXC, which provides improved security and manageability all the

while publicly stating support for both LXD and LXC.

For the moment, however, there is no doubt that the Docker community has a marketing edge and significant

momentum. It’s being picked up by many large companies that are building partnerships. For example, Microsoft is

adding features to support Docker containers and VMware has made efforts in integrating support for Docker into

virtual machine technology (VMware Photon). Linux companies have also jumped on the bus, seeing as this as an

opportunity to grow the Linux market. For example, Red Hat has released versions of Linux that are customized for

Docker.

Container War And Peace?

This report includes a listing of popular products in the container ecosystem, showing the LXC and Docker container

world is expanding rapidly with a range of management tools, including those for tracking container development,

monitoring performance, beefing up security, analyzing applications performance, and providing general management

and orchestration platforms.

With an explosion of commercial interests, venture funding, and many new startups it’s clear that container

technology is at risk of splintering into different camps, running the risk of developing incompatibilities. One

interesting area to watch is the competition between Docker and CoreOS.

Two key areas to watch are Container OSes and container runtimes. Runtimes are the small code interfaces that run on

top of the OS that enable the container apps to run. Container-ready OSes are another area to watch. Many container

technology companies have their own lightweight version of the Linux OS developed specifically for containers, aswell as runtimes. This includes CoreOS (CoreOS and Rkt runtime) Docker, Rancher (RancherOS), Red Hat, and

Canonical, among others.

CoreOS and Docker have gained prominence as rivals in the industry, something that may have been started in 2014

when CoreOS CEO Alex Polvi famously called the Docker approach “fundamentally flawed.”2 But recently, the two

companies announced they would unite on the Open Container Project to build standards for container runtimes and

image format.3 This was an important development that showed startups are interested in working together on

container interoperability.

The issue of runtime compatibility will be one of the most closely monitored areas of containerland. The idealistic

version is that the Open Container Project will develop a “universal runtime” that can become the industry’s Type O

blood. Docker contributed runC to the Linux Foundation as the basis of this universal runtime.

2 “Rocket released to challenge ‘fatally flawed’ Docker,”FierceCIO, December 4, 2014. http://www.fiercecio.com/story/rocket-released-chal-lenge-fatally-flawed-docker/2014-12-043 “Docker and CoreOS unite to start the Open Container Project and standardize runtime, image format,” VentureBeat.com, June 22, 2015. http://venturebeat.com/2015/06/22/docker-and-coreos-unite-to-start-the-open-container-project-and-standardize-runtime-image-format/

http://www.fiercecio.com/story/rocket-released-challenge-fatally-flawed-docker/2014-12-04


http://venturebeat.com/2015/06/22/docker-and-coreos-unite-to-start-the-open-container-project-and-standardize-runtime-image-format/








© 2016 SDNCentral LLC. All Rights Reserved. Page ix

market summary


Chapter 2: Comparing Containers and VMs

The competition to watch won’t just come down to who has the best container OS, runtime, or management tools. It

has also turned into a debate between containers and virtual machine (VM) technology.

Both containers and virtual machines (VMs) are forms of virtualization, though they are virtualizing at different levels

of the stack. VMs enable a server to run several guest OSes, virtualizing the hardware using a hypervisor. Containers

do away with a hypervisor and can be run on a single OS on the host machine by adding a lightweight LXC or

Docker-based runtime -- applications can then run in their own container on top of the OS, virtualizing the OS.

OS Virtualization = Efficiency

The advantage of the container approach is that it consumes less resources, because you don’t need to run multiple

OSes (for each VM). This allows the applications to be loaded and updated faster, without the need to install a

hypervisor and OS for each instance. On the downside, the container ecosystem is much less mature than the VM

world. Even though containers have inherent security advantages, there are also specific risks that need to be carefully

addressed. For example, containers are good at isolating applications – allowing them to access resources specific to

that container – but what if containers were used to install malicious code to observe activity in connected containers?

Because containers are relatively new in production environments, it’s unlikely we have seen the full impact of security

The diagram below demonstrates the difference between a container and VM architecture.

Some software experts have pointed out that container technology could be a threat to virtual machines, because it is

a way to virtualize an OS system without adding the additional overhead (and cost) of installing several virtual

machines. Proponents of container technology have pointed out that by sharing an OS and eliminating the need for

VMs, containers consume far less resources than systems using VMs or hypervisors. Virtualization software companies

such as VMware have tried to counter this perception by integrating container technology into their platforms.



© 2016 SDNCentral LLC. All Rights Reserved. Page x

market summary


Google Goes All-In on Containers

Urs Hölzle, senior vice president of technical infrastructure at Google, believes that open source and container

technology will drive the future of cloud infrastructure.4

In a keynote at Interop in Las Vegas in early 2015, Hölzle said that virtualized computing may be displaced by

containers, which Google favors as a technology for cloud.

“We have to go with containers,” Hölzle said. “We need to think about applications instead of machines. The system

manages the placement on machines. You don’t have to think about OS security patches, and configuration. A whole

class of administrative tasks is removed.”

Many container experts we spoke to said that container and microservices architectures are attracting attention from

large enterprises that would like to modernize their architecture.

“This has the potential to revolutionize the way people write applications,” said Mathew Lodge, COO of Weaveworks,

in an interview. “There’s a big shift to the microservices architecture.”

The reason that container and a microservices architecture are appealing for enterprise software development is that

developers can work on a software applications in teams, and push updates quickly and iteratively using container

management platforms, according to Lodge.

David Aronchick, lead product manager for Google’s Kubernetes project, said that Google sees many large enterprises

moving their application development, a trend that is expected to build in 2016.

“What you will see is the next wave of large deployments from Fortune 1000 companies. You are going to start to see

larger companies adopting containerized workloads. When you talk to any large customers, their problems come

down to two things — they want to move faster and they want to do it in a more cost effective way. Containers enable

both of these.”

Summary: Benefits of Containers

In summary, there is momentum building for containers, with a focus on using microservices architecture as a platform

for managing large, distributed applications with agility and flexibility. Below are potential benefits we heard from both

customers (through our survey) and in interviews with experts in the container world.

Potential benefits of container and microservices:

• Speed and agility and source-code: Allow applications to be more quickly tested and deployed

• Allow applications to be separated from the underlying infrastructure, making them more portable

• Enable a standard “one button” update for applications

• Lower overhead than virtual machines.

• Can enable applications to be isolated from the infrastructure, with potential security benefits.

• Helps reduce VM footprint

• Faster and lighter weight than VMs.

4 “Google’s Urs Hölzle: Containers Will Rule the Cloud,” SDxCentral, April 29, 2015https://www.sdxcentral.com/articles/news/googles-urs-holzle-containers-will-rule-cloud/2015/04

https://www.sdxcentral.com/articles/news/googles-urs-holzle-containers-will-rule-cloud/2015/04

https://www.sdxcentral.com/articles/news/googles-urs-holzle-containers-will-rule-cloud/2015/04



© 2016 SDNCentral LLC. All Rights Reserved. Page x

market summary


Chapter 3: Container Security, Networking, and Management

Like many things in technology, the architectural arguments repeat themselves. Almost as soon as containers became

hot, users were clamoring for better container security, networking, and management tools – as also happened when

other areas of technology such as client/server and the Internet arrived on the scene.

The container ecosystem has moved to building out the features necessary to manage, secure, and network the

container infrastructure. This includes tools specifically targeted at Docker networking, security, and management.

Going back to the client/server paradigm described with Docker, think of how a container system functions by using

client interfaces to communicate with daemons installed on top of a Linux OS on data center compute nodes.

Both Docker and LXC applications use APIs and networking resources to communicate. In addition to the compute

resources on the node on which it is installed, the containerized application still needs access to resources such as

storage and networking. You also need to be able to manage and control the orchestration of containerized

applications, as well as secure them.

This provides for a lot of opportunities for new technology. How do you connect containers with a virtual networking

system? How can large applications be managed and orchestrated? Are there specific security needs? These are the

holes in the container ecosystem that are starting to be filled in with dozens of niche startups and more than $300

million in venture capital, according to Docker. The ecosystem diagram below shows how many companies areworking to fill the gaps in the Linux container ecosystem.

https://www.sdxcentral.com/



© 2016 SDNCentral LLC. All Rights Reserved. Page xi

market summary


The way that containerized applications interact with storage, networking and orchestration platforms means that

many tools will be needed. The larger container technology players, such as Amazon, Docker, Google, are racing to

build technology and buy startups to provide their own management solutions.

Below is a summary of what’s going on in each area.

Container Orchestration and Management Platforms

All virtualized networking systems – for example VMs – require an orchestration system that can set up and tear down

instances of the workload. Containers are no different – there needs to be a central brain that keeps track of the

potential container hosts, where to set up workloads, and how to move them around.

Google, one of the pioneers in LXCs and microservices, had to create its own multi-container management system,

the core of which now forms the open source Kubernetes Project. Kubernetes enables customers to build a cluster of

nodes to run containers. An administrator can manage many more containers at once, enabling large applications to

be built. CoreOS has created a modified version of Kubernetes called Tectonic.

In addition to orchestration and clustering functions, there are many other functions that can be covered by various

container management tools. For example, some management tools can monitor and provide intelligence on

container functions, or keep track of a catalog of container apps. ContainerX and Rancher Labs, are among the many

companies starting to bring container management and orchestration products to market.

Docker was the first to popularize the concept of a full Docker platform, although it soon realized that many more

functions would be needed. It later developed Docker Swarm, it’s own tool for managing Docker clusters

– comparable in functionality to Google’s Kubernetes.

Other tools for container cluster management and orchestration include the open-source project Apache Mesos, and

Mesosphere, the company that used Apache Mesos as the foundation of its own container and management platform.

Mesopshere is founded by ex-Twitter and AirBNB engineers who built those software platforms based on container

technology. Microsoft has already been rumored to have made an offer for Mesosphere in the $150M range, though

recently press reports indicate that Mesosphere’s recent private valuation is much higher. 5

It’s clear from the engineers at Google, Twitter, and AirBNB that clustering orchestration and management is a very

important function, so these product areas will continue to be closely watched in the container ecosystem. (See the

product listings at the end of this report for full detail.)

Container Networking and Docker Networking

Once containers are set up, they also need to talk to each other. This is simple if they reside on the same host node,

but what if different container nodes want to talk to each other across the network? This makes container Networking

and Docker networking a very important part of the container ecosystem.

The existing infrastructure may create barriers to communications between containers with the existence of firewalls,

so it’s important that networking technology be adapted to handle containers. The container world has started to

adapt by creating its own network virtualization technology which allows the container network to be portable across

domains. Think of it as a virtual network within a virtual network.

For example, a Docker or CoreOS Rkt container network can be set up as its own software-defined network (SDN).

Docker recognized the significance of this very quickly. In March 2015, it acquired SocketPlane, which had begun avirtual networking system Docker container networks, bypassing the physical network. SocketPlane’s technology has

been integrated into a new Docker element called libnetwork that provides a plug-in framework for multiple other

vendors to insert their own networking solutions into the Docker platform. Vendors announced at its launch include:

Weaveworks’ Weave, Microsoft, VMware, Cisco, Nuage Networks, Midokura and Project Calico (Metaswitch).

Other startups focusing on the networking angle include Weaveworks. In the case of Weaveworks, it’s focused on

5 “Microsoft tried to buy this hot 2-year-old startup but got turned down,” Business Insider, Oct. 28, 2015 http://www.businessinsider.com/meso-sphere-rejects-microsoft-acquisition-offer-2015-10

https://www.sdxcentral.com/articles/news/docker-acquires-networking-startup-socketplane/2015/03/

http://www.businessinsider.com/mesosphere-rejects-microsoft-acquisition-offer-2015-10




https://www.sdxcentral.com/articles/news/docker-acquires-networking-startup-socketplane/2015/03/



© 2016 SDNCentral LLC. All Rights Reserved. Page xii

market summary


using fully encrypted packets that can traverse firewalls. The Calico Project is an open source effort started by

Metaswitch that creates a Layer 3 network that can be used to create a virtual overlay networks for containers. Many

of the debates around container networking focus on the architecture and whether they should emulate layer 2 or

layer 3 networks. The expansion of container networking system has created its own set of debates revolving around

the most efficient way to connect. For example: Should each container node be able to do its own routing? Or should

it use an independent controller, which may create a single point of failure. The networking aspect will be important towatch as different architectures emerge.

All of the major networking providers are adapting their own container SDN strategies. For example, Cisco is

supporting the open-source project Contiv, which is defining infrastructure operational policies for container-based

application deployment.6 And Google is a big supporter of OpenStack, the open-source virtualization platform, where

it is working to integrate better with Kubernetes. Major virtualization players such as Juniper Networks, Nuage

Networks, and VMware are actively involved in developing Container SDN and Container NFV strategies.

Container Storage

Another challenge for containers is being connected to storage resources. The first containers were stateless, meaning

that they were not persistently connected to specific resources, such as a storage volume. But some applications,

especially those that make heavy use of databases, require a more stateful connection.

Container storage solutions can connect containers to storage devices and storage area networks (SANs). Some of

the companies working in this area include ClusterHQ and Portworx. Docker is also expanding its own storage

connection capabilities.

Container Security

Container security has been identified as an area of weakness when compared to VM technologies. This is primarily

because many of the fundamental elements of containers rely on a shared kernel, exposing the OS. The isolation

mechanisms including Linux cgroups and Namespaces, need to be bulked up to provide more firewalling between

containers. Docker’s supposedly broken security model was what drove CoreOS’s to create its rkt container runtime.

Banyan, a container security firm focusing on analyzing container images, recently found that as many as 30% of the

container images found in public repositories had vulnerabilities.7

Further, Intel has come out with Clear Containers, a collection of technology solutions packaged together to provide

security benefits of full virtual machines (VMs) without giving up on the lightweight nature of containers

Areas of active research and development in container security today include:

• Better Isolation

• Better Visibility

• Security Scanning

VMs and network virtualization (NV) have recently become a tool for building more secure networks because of the

capability to segment traffic and applications on secure, virtualized networks. In theory, containers could be used to

make applications more secure, because the technology offers another potential layer of isolation of applications and

code. It’s expected that containers will move in the same direction as virtualization, as startups, networking

companies, and the container platforms alike build in features to secure and microsegment containerized applications.

Some examples of container startups working this area include Yubico, which allows containers to be signed and

verified, and Twistlock, which scans container code for problems or inconsistencies.

6 “Cisco’s Project Contiv Specifies Policy for Containerized Applications,” SDxCentral.com. https://www.sdxcentral.com/articles/featured/con-tiv-cisco-article/2015/11/7 “Over 30% of Official Images in Docker Hub Contain High Priority Security Vulnerabilities,” Banyan. http://www.banyanops.com/blog/analyzing-docker-hub/”

https://www.sdxcentral.com/articles/featured/contiv-cisco-article/2015/11/


http://www.banyanops.com/blog/analyzing-docker-hub/








© 2016 SDNCentral LLC. All Rights Reserved. Page xiv

market summary


CoreOS, which touts the security of its own platform over Dockers, introduced Distributed Trust Computing, in which

containers can be verified with firmware-based keys. Broader security technologies are emerging for use in the

container ecosystem at large. For example, Security Enhanced Linux (SELinux) enables restrictions to be applied to

applications. It can be used to define the context and rules for the processes being run in a container or between

containers. Red Hat uses these features in its technology called SVirt. CoreOS uses SVirt and SELinux in its rkt

product.8

Chapter 4: What Users Want: Survey Container Survey Results

SDxCentral recently ran the 2016 Container Survey, which collected the feedback of 101 users of technology in

enterprises and service providers. As summarized earlier, we found lots of enthusiasm for container technology, with

76% of respondents evaluating the technology, 56% looking at different solutions, and 20% of the respondents actively

testing and piloting. This comes in contrast with the fact that only 7% of those surveyed have

already deployed container technology, indicating that indeed, 2016, may be the year of deployments. Less than a fifth

(17%) of respondents said they are not considering container technology for their environment.

Below is more detailed information we gathered from users, including feedback about where they see containers

working, the challenges, and who they perceive as leaders in the container ecosystem.

8 “Container Security with SELinux and CoreOS,” CoreOS blog. https://coreos.com/blog/container-security-selinux-coreos.html”

https://coreos.com/blog/container-security-selinux-coreos.html

https://coreos.com/blog/container-security-selinux-coreos.html



© 2016 SDNCentral LLC. All Rights Reserved. Page xv

market summary


Where are Containers Being Deployed?

The majority of respondents – 56% – indicated they would consider deploying container technology on-premises, on a

local workstation or in a private cloud or data center, or in their developer environment (51%). 42% were interested in

using containers across their cloud environments, spanning their public, private and hybrid infrastructures, while 32%

were looking at public cloud deployments.



© 2016 SDNCentral LLC. All Rights Reserved. Page xv

market summary


What are organizations looking to do with Container technologies?

Not surprisingly, given the predominance of deployments being targeted for developer environments, 56% of

respondents cited simplifying the developer environment as a primary driver for using container technology.

Respondents could choose two objectives: 37% felt container technology could be best applied to supporting apps

across multiple clouds, while 35% cited isolating apps as a critical reason they are considering containers. Managing

and automating the code pipeline, which is an ancillary objective within the developer environment, was chosen by

27% of respondents, while scaling and consolidating apps was picked by 26% and 20%, respectively.



© 2016 SDNCentral LLC. All Rights Reserved. Page xvi

market summary


Primary Benefits of Container Technology

Containers enable organizations to deploy a high number of computing workloads on a single server, so it makes

sense that 26% of respondents felt “Improved Resource Utilization (less overhead than virtual machines)” was the

biggest benefit of container technology. However, “Cost Savings” which is a subsequent benefit (due to the reduction

of hardware and the amount of space, power and cooling required, thanks to improved resource utilization) was only

identified by 10% of respondents as the top benefit.

“Fast app deployment” and “Continuous integration and deployment” each received 17% of the vote; this is likely due

to a container’s ability to quickly spin up, since it doesn’t have to load an operating system. “App Portability” followed

closely behind, at 16%, while “Flexible App Management” was chosen by 13% of respondents as the primary benefit.



© 2016 SDNCentral LLC. All Rights Reserved. Page xvii

market summary


The Largest Barriers to Adopting Container Technology

For a technology that appears to be rocketing to the top of everyone’s ‘must have’ list, we wanted to know if there was

anything that could slow these solutions down. It turns out the newness of the technology is the biggest thing working

against it. Forty-six percent of respondents, who could pick up to two potential issues, identified the “Lack of

Expertise” in their organization as the biggest barrier to the adoption of Container technology. 40% identified

“Security Risks” as a potential hindrance, which again points to the immaturity of the market, as organizations try to

figure out how Containers truly fit into their security strategy. 30% of respondents cited “Interoperability Issues”, 20%

identified “Data Management Challenges”, 18% chose “Compliance Risks”, 17% picked “Networking Issues”, 16% cited

“Cultural Acceptance”, 15% noted “Costs” could be an issue.



© 2016 SDNCentral LLC. All Rights Reserved. Page xix

market summary


Standards Are Important

Given the newness of the market, standards have yet to be established and adopted industry-wide. Open Container

Initiative (OCI) was announced at DockerCon in June of 2015 to create an open standard for container runtimes

supporting technology based on Docker’s container format.

OCI includes many leading cloud technology companies and is run by the Linux Foundation. Members includeAmazon, Google, Mesosphere, Pivotal, Cisco, IBM, Microsoft, Intel, RedHat, Oracle, Verizon, and others.

When asked whether these efforts were of value, an overwhelming 56% of respondents said standards are “very

important” to help them deploy container technology. Thirty-four percent said they were “somewhat Important,”

indicating they are not going to wait for standards to adopt (which is what we have seen in the market). Only 10% said

standards were “Not that Important”, and no one indicated that standards were not important at all.



© 2016 SDNCentral LLC. All Rights Reserved. Page xx

market summary


Critical Container Technology Capabilities

When asked to identify what they classed as the three most important container technology capabilities, close to 50%

of respondents indicated they wanted “orchestration.” Surprisingly, given the worries they had about security (see

barriers to adoption section), only 25% of respondents said “security” was critical and only 11% choose “access

controls” as a key feature they look for in a container solution. Also of note, “Container OS”, “simple management”, and

“infrastructure services (networking, storage)” were all identified as critical by 33% of respondents, while a third of the

survey’s participants chose “developer tools.”



© 2016 SDNCentral LLC. All Rights Reserved. Page xx

market summary


Leaders in the Container Space – Beyond Docker

When asked who they would consider a leader(s) in the container space (up to three), Docker was the overwhelming

favorite with respondents, at 72%. Google/Kubernetes was identified by 51% of survey participants as a company that

was leading the space, followed by Amazon, which was chosen by 36%. After those three companies, however, the

market is up for grabs. Only a few companies were named by more than 10% of respondents: Canonical/Ubuntu (13%)

CoreOS/Tectonic/Quay (13%), Microsoft (13%), Puppet (13%) and VMware (16%).



© 2016 SDNCentral LLC. All Rights Reserved. Page xxi

market summary


Chapter 5: Container NFV

Containers have started to surface in the telecommunications market, most notably in the area of network functions

virtualization (NFV), and its counterpart, SDN (software-defined networking). Yes, it’s time to introduce container NFV

and container SDN.

SDxCentral analysts believe that the combined SDN & NFV market will grow to nearly $105B by 2020, with a CAGR of

44% over the 5 years from 2015 to 2020, eight times the growth rate of the broader total available market. The portion

of network purchases influenced by virtualization is anticipated to increase from 16% in 2015 to almost 80% by 2020.

The concept for NFV originated from service providers who were looking to accelerate the deployment of new

network services to support their revenue and growth objectives. The constraints of hardware-based appliances and

the need to control operational expenses (OpEx) drove several service providers to form the NFV ISG (industry

specification group) under European Telecommunications Standards Institute (ETSI) to help develop the concepts,

architecture and standards necessary to make NFV successful. NFV is a new approach to designing, delivering and

managing network services that decouples the network functions proprietary hardware appliances so they can run in

software on COTS (commercial off-the-shelf servers).

Key benefits of container NFV include:

• Reducing CapEx: Reducing the need to purchase purpose-built hardware and supporting pay-as-you-grow

models to eliminate wasteful overprovisioning.

• Reducing OpEX: Reducing space, power and cooling requirements of equipment and simplifying the roll out and

management of network services.

• Accelerating Time-to-Market: Reducing the time to deploy new networking services to support changing

business requirements, seize new market opportunities and improve return on investment of new services. Also

lowers the risks associated with rolling out new services, allowing providers to easily trial and evolve services to

determine what best meets the needs of customers.

• Delivering Agility and Flexibility: Quickly scale up or down services to address changing demands; support

innovation by enabling services to be delivered via software on any industry-standard server hardware.

https://www.sdxcentral.com/articles/editorial/telecom-opens-up-to-containers/2015/10/

https://www.sdxcentral.com/articles/announcements/nfv-sdn-market-sizing-forecast-report-2015-download/2015/05/




https://www.sdxcentral.com/resources/nfv/who-is-etsi-network-functions-virtualization-nfv/

https://www.sdxcentral.com/resources/nfv/whats-network-functions-virtualization-nfv/

https://www.sdxcentral.com/resources/nfv/whats-network-functions-virtualization-nfv/

https://www.sdxcentral.com/resources/nfv/who-is-etsi-network-functions-virtualization-nfv/




https://www.sdxcentral.com/articles/editorial/telecom-opens-up-to-containers/2015/10/



© 2016 SDNCentral LLC. All Rights Reserved. Page xxii

market summary


Addressing NFV with Containers

Most of initial NFV architecture has focused on using OpenStack as the virtualized infrastructure management (VIM)

system, and using virtual machines (VMs) with hypervisors like KVM and VMware ESXi to run the virtual network

functions (VNFs). This was primarily due to the maturity of VM technology and the familiarity of many service-pro-

vider IT departments with its use for their own internal IT infrastructure (in contrast with the operational infrastructure

required to deliver subscriber services for wireless or wireline).

NFV Management andOrchestration

OrchestratorOSS/BSS

Service, VNF and

Infrastructure Description

VNFManager(s)

Virtualised

Infrastructure

Manager(s)

Or-Vnfm

Vi-Vnfm

Nf-Vi

Ve-Vnfm

Se-Ma

Or-Vi

Execution reference points Other reference points Main NFV reference points

Os-Ma

NFV Infrastructure (NFVI)

Virtual

Computing

Virtual

Storage

Virtual

Network

Virtualization Layer

Computing

Hardware

Storage

Hardware

Network

Hardware

Hardware Resources

VI-HaVI-Ha

Virtual

Computing

VNF 1

EMS 1

VNF 2

EMS 2

VNF 3

EMS 3

Vn-Nf

A virtualized infrastructure using VM technology provides numerous advantages over proprietary hardware-based

network functions, providing greater flexibility in how services are provisioned and run, in scaling up and down

services, as well as handling high-availability and disaster recovery. Recent techniques that help improve network I/O,

providing improved throughput with lower latency and jitter have made NFV viable as a replacement for hardware

appliances. These techniques include PCI-passthrough (binding physical NICs to VMs directly) and SR-IOV (single root

I/O virtualization). Intel also developed and shipped its DPDK (Data Plane Development Kit) to accelerate packet

handling on x86 platforms.

As a result, service-providers are seeing success with their early NFV POCs using VMs. At the same time, cutting-edge

service-providers like DT have already started looking into using Linux container technology to gain further agility and

lower costs. And AT&T is looking into bringing the concept of micro-services with Containers into NFV solutions.

The most obvious use of container technology is as a host for network functions (VNFs). By running VNFs inside

containers instead of VMs, telcos can reduce the amount of VM tax and overhead. With faster turn-up times and

friendlier CPU and memory footprint, a telco can pack more VNFs into an x86 server, reducing their CapEx while

improving service turn-up times.

ETSI NF V Architecture Framework

Adapted from ETSI publication GS NFV 002: Network Functions Virtualization (NFV); Architectural Framework

http://www.intel.com/content/www/us/en/embedded/technology/packet-processing/dpdk/dpdk-getting-started-guide.html


http://www.businesscloudnews.com/2015/02/09/deutsche-telekom-experimenting-with-nfv-in-docker/


http://www.rcrwireless.com/20150831/software-defined-networking-sdn/att-looks-to-containers-micro-services-in-sdn-and-nfv-push-tag2

https://www.sdxcentral.com/articles/news/can-we-shrink-or-eliminate-vms-to-suit-containers/2015/08/

https://www.sdxcentral.com/articles/news/can-we-shrink-or-eliminate-vms-to-suit-containers/2015/08/

http://www.rcrwireless.com/20150831/software-defined-networking-sdn/att-looks-to-containers-micro-services-in-sdn-and-nfv-push-tag2






© 2016 SDNCentral LLC. All Rights Reserved. Page xxiv

market summary


Containers in NFV – challenges, best fit use-cases

Moving to containers does not make all the problems of VMs in NFV disappear, and it also introduces different

problems. Early analysis of the impact of Containers on NFV are documented in a recent IETF Internet Draft “An

Analysis of Container-based Platforms for NFV” authored by DT, Dell, IBM, BT and Verizon.

Issues with using Containers versus VMs, or in addition to VMs, include:

• Difficulty in maintaining application state: Container architectures are usually ephemeral and solutions built

using micro-services and container technology push state management into external databases, distributed key-

value stores e.t.c.. Network functions may have to be re-architected and modified by their vendors to handle

persistence differently—which will slow down deployment.

• Security and isolation challenges: VMs today provide better security and isolation than containers. And while

solutions like SELinux and AppArmor can improve security, service-providers will have to evaluate the network

functions being run inside each container and determine if compromise of a container can easily spread to other

containers resulting in an expanded breach. Furthermore techniques that improve VNF performance like DPDK

are compatible with containers, but require changing security settings to increase host privilege of containers and

exposing more attack surface to the OS.

• Complexity in orchestrating the mix of containers and VMs: it is unlikely that NFV platforms will be just allcontainers—most will be a hybrid of containers and VMs. The orchestration and management complexity in

managing across containers and VMs will be significant and while management systems for containers exist in the

form of Kubernetes, Mesos, Docker Swarm (to name just a few), a unified system for NFV that can cross VMs and

container will take time to build and mature. There are some early efforts in this space, most notably the Magnum

project in OpenStack that supports container orchestration.

• Inadequate networking support in Containers: Container networking has traditionally been weak. With the

recent acquisition of SocketPlane by Docker, and the roll-out of libnetwork, Docker has laid the groundwork for an

improved networking foundation. We’re also seeing major networking vendors such as Cisco, Ericsson, Juniper,

Nuage Networks improve their network virtualization offerings to support Containers as end-points, but

SDxCentral believes that maturity will only come in the next 12-18 months. (You can see more about networking in

the “Container Networking and Docker Networking” section above.)

Despite the challenges, containers will be a major force in NFV and telco deployments especially for select use cases.

Virtual CPE and Linux Containers

One of the earliest use cases for container use is virtual CPE (customer premises equipment). Telcos are replacing

dated routers and multi-function devices at business and residential customers with virtual equivalents. Till recently,

vCPE deployments have primarily utilized VM technology, with many vCPE deployments running network services

within VMs. Some vCPE solutions utilize a shared multi-tenant VM solution where a single network service running on a

VM can be simultaneously used by multiple subscribers. However, there are numerous other vCPE solutions that use a

VM per network service on a per subscriber basis. This results in VM sprawl and significant overhead and inefficiencies

In a 1,000 subscriber scenario, running just 3 services on average per subscriber results in over 3,000 VMs.

With container technology, vCPE solutions can utilize 4-5 Containers running separate services chained together per

subscriber—many subscribers can be served by a single VM or bare-metal machine. We envision higher-densitydeployments with multiple services per container per subscriber being developed as well. This significantly reduces

the overhead of using VMs and results in dramatic capacity gains on x86 servers.

SDxCentral projects significantly more containers in networking and at communications service-providers in 2016, and

we’re looking forward to seeing more innovation as the industry overcomes the challenges of using container

technology within NFV.

https://tools.ietf.org/html/draft-natarajan-nfvrg-containers-for-nfv-01


https://www.sdxcentral.com/articles/news/google-unleashes-containers-on-openstack/2015/07/


https://www.sdxcentral.com/articles/news/docker-plugs-containers-into-sdn/2015/06/









© 2016 SDNCentral LLC. All Rights Reserved. Page xxv

market summary


Vendor Profiles

The following sections profile many of the vendors in the container market. The individual Profiles were created

through a collaborative effort between SDNCentral’s Research Team and the Vendor’s product experts. SDNCentral

worked under the assumption the information provided by the vendors was factual, auditing the submissions only to

remove unverifiable claims and hyperbole. Extended profiles can be viewed online.

While every attempt has been made to validate the capabilities listed in the Profiles, SDNCentral advises end users to

verify the veracity of each claim for themselves in their actual deployment environments. SDNCentral cannot be held

liable for unexpected operations, damages or incorrect operation due to any inaccuracies listed here. SDNCentral

welcomes feedback and additional information from end users based on their real-world experiences with the

products and technologies listed. The SDNCentral research team can be reached at [email protected].

https://www.sdxcentral.com/reports/linux-container-ecosystem/

mailto:research%40sdxcentral.com?subject=

mailto:research%40sdxcentral.com?subject=

https://www.sdxcentral.com/reports/linux-container-ecosystem/



© 2016 SDNCentral LLC. All Rights Reserved. Page

FEATURED


Description of Company: We strive for solutions that give our customers true advantage over their competition,whether that’s bringing new, revenue-generating services to market in minutes instead of months, reducing network

costs, enabling smarter, more efficient business processes, providing security and protection for their most valuable

assets, or delivering a richer end-user experience. Whatever the challenge, each and every day our customers set out

to build the best possible networks for their businesses. Juniper Networks helps them do just that.

Juniper Networks, Inc. (Click for online version)

http://www.juniper.net/

1133 Innovation Way

Sunnyvale, California 94089 USA

[email protected]

RELEVANT SOLUTION CATEGORIES

Security, Infrastructure Services

SECURITY

Product: Contrail Networking

Product URL: http://www.juniper.net/us/en/products-

services/sdn/contrail/

Open source repository: https://github.com/Juniper/contrail-controller

Date of Initial Release: September 2013

Product Description: Juniper Networks’ Contrail is

a simple, open and agile Cloud Network Automation

platform that implements secure multitenancy and

enables dynamic service chaining in private, public and

hybrid clouds. The Contrail solution is composed of

two products: Contrail Networking and Contrail Cloud

Platform.

SECRUITY REQUIREMENTS

Whether it is private or public cloud, the pooled

infrastructure shared by multiple customers/tenantsmust be able to follow workloads and securely isolate

tenants from one another.

SECURITY BENEFITS & FEATURES

1. Contrail Networking implements secure multitenancy

for tenants utilizing containers and/or groups of

containers, ensuring clear segmentation between

tenants sharing the pooled infrastructure.

2. Contrail Networking implements a fully distributed

firewall in the vRouter that enforces security policies at

every server host where containers are running.

LICENSING/PRICINGPlease contact Juniper Networks at contrail-info@

juniper.net for pricing information.

PRODUCT ARCHITECTURE

http://www.opencontrail.org/opencontrail-architecture-

documentation/#section2

CUSTOMERS

www.juniper.net/us/en/products-services/sdn/contrail/#/

INFRASTRUCTURE SERVICES

Product: Contrail Networking

Product URL: See Security section

Open source repository: See Security section

Date of Initial Release: See Security section

Product Description: See Security section

INFRASTRUCTURE SERVICES REQUIREMENTS

Due to the very nature of containers, their number and

density are greater than traditional virtual machines (VMs).

Not only are containers typically short lived, they can be

created and moved more efficiently than VMs and can also

be managed as groups of logically related elements rather

than individual containers. These advantages of containers

demand that the container networking solution be agile

and scalable. Since the transition from VMs to containers

will not happen overnight, VMs, containers and bare

metal servers will all have to co-exist in the same cloud

environment. The networking solution, therefore, must be

seamless across multiple deployment modes/schemes.

It must also be agnostic in order to work with whatever

compute vehicle is used to deploy applications.

INFRASTRUCTURE SERVICES BENEFITS & FEATURES

1. Contrail Networking provides the ability to weave

virtual overlay networks with heterogeneous

environments that straddle public and private clouds,

orchestration tools and compute workload vehicles.

2. Contrail Networking allows tenants to specify traffic

selection criteria and the network function sequencesthat selected traffic will be subjected to—in other words,

Service Function Chaining.

https://www.sdxcentral.com/reports/linux-container-ecosystem/featured-companies/juniper-networks/



mailto:Contrail-Info%40juniper.net?subject=

http://www.juniper.net/us/en/products-services/sdn/contrail/


https://github.com/Juniper/contrail-controller


mailto:contrail-info%40juniper.net?subject=


http://www.opencontrail.org/opencontrail-architecture-documentation/#section2


http://www.juniper.net/us/en/products-services/sdn/contrail/#/

http://www.juniper.net/us/en/products-services/sdn/contrail/#/









mailto:Contrail-Info%40juniper.net?subject=





© 2016 SDNCentral LLC. All Rights Reserved. Page 2

FEATURED


Description of Company: Nu-âhj: From French, meaning ‘cloud’. Nuage Networks brings a combination of technol-ogies and networking expertise to the enterprise and telecommunications industries. The Silicon Valley-based start up

has applied new thinking to the problem of delivering massively scalable and highly programmable SDN solutions.

Nuage Networks, now part of Nokia, one of the largest technology providers to the telecom and communications

industry, has the pedigree to serve the needs of the world’s biggest clouds.

Nuage Networks (Click for online version)

www.nuagenetworks.net

755 Ravendale D

Mountain View, CA 94043

www.nuagenetworks.net/about-our-company/contact-us/

650-623-3300


Infrastructure Services


Product: Virtual Services Platform (VSP)

Product URL: http://www.nuagenetworks.net/

products/virtualized-services-platform/

Date of Initial Release: March 2014

Product Description: The Nuage Networks Virtualized

Services Platform (VSP) provides SDN virtual

networking capabilities for clouds of all sizes – from

small private clouds to large public clouds. Nuage

Networks VSP is implemented as a non-disruptive

overlay for all existing virtualized and non-virtualized

server and network resources. VSP provides virtual

networking and IT automation for Docker containers and

DevOps environments with the most open, platform-

neutral solution available to avoid vendor lock-in.

INFRASTRUCTURE SERVICES DIFFERENTIATION

Via robust interfaces, existing legacy infrastructurecan be managed along with leading-edge software

and hardware, such as Docker containers and network

accelerators. The platform integrates with a broad range

of tools and environments – from Cloud Platforms such

as CloudStack and OpenStack through custom self-

service interfaces. The result is the most flexible virtual

networking and SDN platform for container-based

deployments and DevOps environments in the industry.

KEY PARTNERS

The Nuage Networks Ecosystem represents a growing

number of industry leaders who share our vision of

instantaneous and boundary-less networking fordatacenters in the cloud era. These leaders come

from open source community projects, ecosystem

partners, systems integration partners, developers, and

customers for Development and Operations (DevOps)

clouds based on OpenStack.

http://www.nuagenetworks.net/partners/

CUSTOMERS

http://www.nuagenetworks.net/resources/customer-

stories/

INFRASTRUCTURE SERVICES BENEFITS & FEATURES

1. Virtualized Services Controller (VSC) serves as

the robust control plane of the datacenter network,

maintaining a full per-tenant view of network andservice topologies. Through network APIs using

interfaces such as Openflow, the VSC programs the

datacenter network independent of network hardware.

2. Virtualized Services Directory (VSD) serves as a

policy, business logic and analytics engine for the

abstract definition of network services. Through RESTful

APIs to the VSD, administrators can define and refine

service designs and incorporate enterprise policies.

3. Virtual Routing and Switching (VRS) is a module

that serves as a virtual layer-3 network switch. Through

the VRS, changes in the compute environment are

immediately detected, triggering instantaneous policy-based responses in network connectivity to ensure that

the needs of app containers are met.

LICENSING/PRICING

Contact Nuage Networks for detailed licensing

information: http://www.nuagenetworks.net/about-our-

company/contact-us/

https://www.sdxcentral.com/reports/linux-container-ecosystem/featured-companies/nuage-networks/


http://www.nuagenetworks.net/

http://www.nuagenetworks.net/about-our-company/contact-us/

http://www.nuagenetworks.net/products/virtualized-services-platform/



http://www.nuagenetworks.net/resources/customer-stories/












http://www.nuagenetworks.net/





FEATURED


Description of Company: Red Hat is working to advance both container technology and the supporting ecosystem tomake containers enterprise-ready, much as it did with Linux. Red Hat delivers reliable and high-performing cloud,

Linux, Linux container, middleware, storage and virtualization solutions.

Red Hat (Click for online version)

www.redhat.com

100 E. Davie Street

Raleigh, NC 2760

http://www.redhat.com/en/about/contac

1-888-RED-HAT1

CONTAINER OS/RUNTIMES

Product: Red Hat Enterprise Linux Atomic Host

Product URL: https://access.redhat.com/products/red -

hat-enterprise-linux/

Open source repository: https://github.com/

projectatomic; https://github.com/GNOME/ostree


Product Description: Red Hat Enterprise Linux

Atomic Host is a secure, lightweight and minimized

footprint operating system that is optimized to run

Linux containers. It couples the flexible, lightweight

and modular capabilities of Linux Containers with the

reliability and security of Red Hat Enterprise Linux in a

reduced image size.

DEVELOPER TOOLS

Product: OpenShift by Red Hat

Product URL: https://www.openshift.com/features /

Open source repository: https://github.com/openshift /

Date of Initial Release: November 2012

Product Description: OpenShift is an application

delivery platform designed for traditional and cloudnative applications. It enables customers to develop,

deploy, and manage traditional and modern, container-

based applications across physical, virtual and public

cloud infrastructures. It also enables DevOps processes

by providing integrated self-service workflows,

automated deployment tools, and pre-packaged

middleware services.

APPLICATION PLATFORMS/HOSTING

Product: OpenShift Online by Red Hat

Product URL: https://www.openshift.com/features /


Date of Initial Release: June 2011

CONFIGURATION MANGEMENT

Product: Red Hat Ansible Tower and Red Hat Satellite

Product URL: http://www.ansible.com/tower ; http://

www.redhat.com/en/technologies/linux-platforms/

satellite

Open source repository: https://github.com/ansible

CUSTOMERS

https://enterprise.openshift.com/customers /

ORCHESTRATION, MANGEMENT, MONIITORING

Product: Red Hat CloudForms

Product URL: https://www.redhat.com/en/

technologies/cloud-computing/cloudforms

Open source repository: https://github.com/ManageIQ

Date of Initial Release: April 2013

Product Description: Red Hat CloudForms offersunified management for hybrid environments, providing

a consistent experience and functionality across

container-based infrastructures, virtualization, private

and public cloud platforms. Red Hat CloudForms

enables enterprises to accelerate service delivery, gain

greater operational visibility, and ensure compliance and

governance, all while reducing operational costs.

IMAGE REGISTRY

Product: Red Hat Atomic Registry

Product URL: https://docs.openshift.com/

enterprise/3.0/architecture /infrastructure_

components/image_registry.html Open source repository: https://github.com/openshift /


SECURITY

Product: Red Hat Atomic Platform and OpenShift

Product URL: https://access.redhat.com/products/red -

hat-atomic-enterprise-platform




Product: OpenShift Enterprise by Red Hat

Product URL: https://www.openshift.com/features / Open source repository: https://github.com/openshift /


STORAGE

Product: Red Hat Storage, including Red Hat Gluster

Storage

Product URL: http://redhat.com/storage

Open source repository: https://github.com/gluster /

https://www.sdxcentral.com/reports/linux-container-ecosystem/featured-companies/red-hat/


http://www.redhat.com/

http://www.redhat.com/en/about/contact

https://access.redhat.com/products/red

https://access.redhat.com/products/red-hat-enterprise-linux/

https://github.com/projectatomic


https://github.com/GNOME/ostree

https://www.openshift.com/features

https://github.com/openshift




http://www.ansible.com/tower

http://www.redhat.com/en/technologies/linux-platforms/satellite



https://github.com/ansible

https://enterprise.openshift.com/customers

https://www.redhat.com/en/technologies/cloud-computing/cloudforms


https://github.com/ManageIQ

https://docs.openshift.com/enterprise/3.0/architecture/infrastructure_components/image_registry.html





https://access.redhat.com/products/red-hat-atomic-enterprise-platform




http://redhat.com/storage

https://github.com/gluster

https://github.com/gluster

http://redhat.com/storage




https://access.redhat.com/products/red-hat-atomic-enterprise-platform






https://github.com/ManageIQ



https://enterprise.openshift.com/customers

https://github.com/ansible




http://www.ansible.com/tower






https://github.com/GNOME/ostree



https://access.redhat.com/products/red-hat-enterprise-linux/


http://www.redhat.com/en/about/contact

http://www.redhat.com/







Amazon (Click for online version) https://aws.amazon.com

Description of Company: Amazon Web Services (AWS) is a cloud services platform offering a multitude of services

starting with compute power, database and file storage and more that enables businesses to scale and grow easily,

flexibly, scalable and reliably.

Ansible (a Red Hat Company) (Click for online version)

http://ansible.com /

Description of Company: Ansible was founded to provide a new way to think about managing systems and

applications. Ansible was designed from the ground up to be a single framework that can automate today’s modern

enterprise and cloud-native apps, from configuration to deployment to zero-downtime rolling upgrades. Ansible was

acquired by Red Hat, Inc in late 2015. (http://red.ht/1k9tUAi)


Orchestration, Management, Monitoring

ORCHESTRATION, MANAGEMENT, MONITORING

Product: Amazon EC2 Container Service

Product URL: https://aws.amazon.com/ecs /

Open source repository


Description: A Docker container management service

that leverages AWS's scalability and performance and

provides simple manageability across EC2 instances.It’s goal is to help eliminate the need for a separate

cluster management service. Simple API cals can be

used to launch, query status, schedule, place and

stop a company's Docker containers. In addition,

already existing Amazon services such as Elastic Load

Balancing, EBS, and IAM roles are available.

CUSTOMERS

Coursera, Meteor, Segment, Remind, Linden Lab

PARTNERS

https://aws.amazon.com/containers/partners /


FEATURE/BENEFIT

Easily manage clusters at any scale. Eliminates the

burden of having to maintain a separate cluster

management architecture. Allows the customer to focus

on building Dockerized applications.

LICENSING/PRICING

AWS Container Service is free with the EC2 Cloud

Computing service and charges are based on the

standard EC2 pricing structures.


Developer Tools; Configuration Management;


DEVELOPER TOOLS

Product: Ansible

Product URL: http://ansible.com /

Open source repository: http://github.com/ansible/

ansible


CONFIGURATION MANAGEMENT

Product: Ansible and Ansible Tower


Open source repository: http://github.com/ansible/

ansible

Date of Initial Release: February 2013

CUSTOMERS

http://ansible.com / (See 'Success Stories')


Product: Ansible and Ansible Tower


Open source repository: http://github.com/ansible/ansible


LICENSING/PRICING

Ansible is open source software, available under the GNU

GPL version 3. Ansible Tower is commercial software

available in three editions that are differentiated by

support and features. Tower is priced based on the

number of nodes (systems, hosts, instances, VMs,

containers or devices) that you are managing.

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/amazon/


https://aws.amazon.com/

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/ansible/


http://ansible.com/

http://red.ht/1k9tUAi

https://aws.amazon.com/ecs

https://aws.amazon.com/containers/partners

http://ansible.com/

http://github.com/ansible/ansible


http://ansible.com/



http://ansible.com/

http://ansible.com/





http://ansible.com/

http://ansible.com/



http://ansible.com/



http://ansible.com/

https://aws.amazon.com/containers/partners

https://aws.amazon.com/ecs

http://red.ht/1k9tUAi

http://ansible.com/


https://aws.amazon.com/






AppDynamics (Click for online version) https://www.appdynamics.com

Description of Company: AppDynamics develops application performance management (APM) solutions for

problem resolution in distributed applications. The company focuses on managing the performance and availability of

applications across cloud computing environments as well as inside the data center.

Apcera (Click for online version) https://www.apcera.com /

Description of Company: Apcera builds a platform as a service (Paas) cloud platform for cloud-native applications,

containers, microservices, and legacy applications. Apcera provides an environment spanning both developers and

DevOps teams IT and Operations teams.


Developer Tools; Orchestration, Management,

Monitoring

DEVELOPER TOOLS

Product: Apcera Platform

Product URL: https://www.apcera.com/why-apcera

Open source repository: https://github.com/apcera


Description: Apcera uses container technologies

(native as well as Docker) to support microservices-

based application development. Apcera supports abroad array of infrastructure providers and workload

types. Infrastructure support includes Amazon Web

Services, Google Compute Engine, Microsoft Azure, IBM

SoftLayer, VMware vSphere and OpenStack. Apcera

supports all common web application languages and

runtimes including Java, Node.js, Ruby, Python, PHP, Go

and .NET.

CUSTOMERS

https://www.apcera.com/customers


Product: Apcera Platform

Product URL: https://www.apcera.com/why -apcera

Open source repository: https://github.com/apcera


Description: Apcera’s Platform supports the

orchestration of microservices, connections to

legacy systems, the establishment connections and

dependencies between applications and services(databases, users, service requests) on both hybrid and

heterogeneous systems.



ORCHESTRATION, MANAGEMENT, MONITORIN

Product: AppDynamics Application Intelligence

Platform

Product URL: https://www.appdynamics.com/product /



Description: The AppDynamics application intelligence

platform enables you to monitor, respond, and analyze

data from within your business critical applications.

AppDynamics delivers real time data to the user within

context of business & operational transactions.

CUSTOMERS

Cisco, eHarmony, Hallmark, The Container Store, Sony

PARTNERS

https://www.appdynamics.com/partners/technology /


FEATURE/BENEFIT

AppDynamics automatically discovers application

topology and interdependencies and traces key

business transactions based on production application

behavior.

LICENSING/PRICING

Pricing is based on the number of units and is billed on

a yearly subscription. Pricing starts at $3,600/unit/

year for up to 10 units, and gets discounted for larger

numbers of units. Free trials are available.

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/appdynamics



https://www.appdynamics.com/

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/apcera/



https://www.apcera.com/

https://www.apcera.com/why-apcera

https://github.com/apcera




https://www.appdynamics.com/product

https://www.appdynamics.com/partners/technology

https://www.appdynamics.com/partners/technology

https://www.appdynamics.com/product






https://www.apcera.com/


https://www.appdynamics.com/






Canonical (Click for online version) http://www.canonical.com/

Description of Company: Canonical is a computer software company that markets commercial support and related

services for Ubuntu and related projects.

BlueData Software, Inc. (Click for online version) www.bluedata.com

Description of Company: BlueData develops the The BlueData EPIC software platform which uses virtualization

technology for big data. BlueData supports Hadoop deployments and can also support Hadoop-as-a-Service in

an on-premises deployment model. BlueData’s supports Spark clusters providing data scientists access to theirapplications, data and infrastructure. Based in Mountain View, CA, BlueData is founded by VMWare veterans and

multiple well-known VC firms.


Orchestration, Management, Monitoring; Infrastructure

Services


Product: BlueData EPIC 2.0

Product URL: http://www.bluedata.com/product /



Description: BlueData Epic 2.0 is a software platform

utilizing Docker to lifcycle management of big data

applications including provisioning, orchestration, load

balancing, storage, networking (e.g. IP management)

and security (e.g. tenant isolation with VLANs)

complete with a management console for deploying

and monitoring Hadoop and Spark environments.

CUSTOMERS

http://www.bluedata.com/customers /


Product: BlueData EPIC 2.0

Product URL: http://www.bluedata.com/product /



Description: BlueData is an on-premises, multi-tenant

and secure solution for big data environments. It

provides self-service provisioning and policy-based

automation and can be integrated to LDAP and Active

Directory. BlueData supports shared enterprise

storage such as NFS, GlusterFS, CEPH, Swift or HDFS.

BlueData’s policy engine can define service levels based

on priority and automate resource management based

on tenants and applications.


Container OS/Runtimes

ORCHESTRATION, MANAGEMENT, MONITORIN

Product: LXD

Product URL: http://www.ubuntu.com/cloud/lxd

Open source repository: https://github.com/lxc/lxd/

Date of Initial Release: November 2015Description: Canonical’s LXD is a container hypervisor

for Linux. LXD offers all the core features of a

hypervisor, including the ability to start, stop, clone and

live-migrate guests between machines. It is integrated

with OpenStack and will support hardware isolation for

containers in the future. The LXD hypervisor is part of

Linux Containers (LXC) Release 2.0.

CUSTOMERS

Not Provided

PARTNERS

http://www.ubuntu.com/cloud/partners

CONTAINER OS/RUNTIMES FEATURE/BENEFIT

LXD is currently based on top of LXC. It uses the stable

LXC API to do all the container management behindthe scenes and adds the REST API on top to provide a

consistent user experience.

LICENSING/PRICING

http://www.ubuntu.com/cloud/plans-and-pricing

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/Canonical



http://www.canonical.com/

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/bluedata



http://www.bluedata.com/

http://www.bluedata.com/product

http://www.bluedata.com/customers


http://www.ubuntu.com/cloud/lxd

https://github.com/lxc/lxd/





https://github.com/lxc/lxd/

http://www.ubuntu.com/cloud/lxd


http://www.bluedata.com/customers


http://www.bluedata.com/


http://www.canonical.com/






Cisco Systems, Inc. (Click for online version)

http://www.cisco.com

Description of Company: Cisco (NASDAQ: CSCO) is the worldwide leader in IT that helps companies seize the

opportunities of tomorrow by proving that amazing things can happen when you connect the previously unconnected

Cisco infrastructure products provide open APIs to help developers simplify and secure distributed application

development and lifecycle management.

Chef Software (Click for online version) www.chef.io

Description of Company: Chef is the leader in automation for DevOps, empowering customers to become high

velocity organizations. Built on an open source foundation, we have distilled the proven patterns for fast and scalable

software development into our IT automation platform. With hundreds of commercial customers and tens ofthousands of open source community members, we are one of the strongest technology movements today.


Configuration Management


Product: Chef

Product URL: https://www.chef.io/chef /

Open source repository: https://github.com/chef/chef


Description: Chef is a dynamic, policy-based automation

platform that securely distributes intelligence across

the entire network. Chef has a unique ability to scale,from start-ups to Facebook to GE; and a unique ability

to ensure consistency in complex, highly dynamic

environments; Chef is fault tolerant; Chef grows with you.

When it comes to solving configuration and automation

challenges, Chef makes the easy things easy and the

hard things possible.

CUSTOMERS

https://www.chef.io/customers /

PARTNERS

https://www.chef.io/partners /

CONFIGURATION MANAGEMENT FEATURE/BENEFIT

Chef is highly scalable. Chef is constructed so that

most of the computational effort occurs on the nodes

themselves rather than on the Chef server. With Chef,

the intelligence about the desired state of the network isdistributed across the network itself.

LICENSING/PRICING

Chef is sold as either on-premises or hosted subscription.

Pricing is simple and easiest way to review it is via

diagram found here: https://www.chef.io/pricing /


Developer Tools; Application Platforms/Hosting;


Services

DEVELOPER TOOLS

Product: Open NX-OS

Product URL: https://github.com/datacenter/opennxos Open source repository: https://github.com/

datacenter/opennxos



Product: Shipped

Product URL: https://developer.cisco.com/site/shipped


CiscoCloud /

Date of Initial Release: July 2015

PARTNERS

Docker, Basho, Zoomdata, Streamsets, Elastic,

Hortonworks


Product: MANTL Data Platform & Monitoring

Product URL: http://mantl.io /

Open source repository: https://github.com/CiscoCloud/microservices-infrastructure

Date of Initial Release: January 2015


Product: Project Contiv

Product URL: https://github.com/contiv

Open source repository: https://github.com/contiv

Date of Initial Release: December 2014

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/cisco



http://www.cisco.com/

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/chef/



http://www.chef.io/

https://www.chef.io/chef

https://github.com/chef/chef

https://www.chef.io/customers

https://www.chef.io/partners

https://www.chef.io/pricing

https://github.com/datacenter/opennxos



https://developer.cisco.com/site/shipped

https://github.com/CiscoCloud


http://mantl.io/

https://github.com/CiscoCloud/microservices-infrastructure


https://github.com/contiv







http://mantl.io/



https://developer.cisco.com/site/shipped




https://www.chef.io/pricing

https://www.chef.io/partners

https://www.chef.io/customers

https://github.com/chef/chef

https://www.chef.io/chef

http://www.chef.io/


http://www.cisco.com/






CoreOS (Click for online version) https://coreos.com

Description of Company: CoreOS produces, maintains and utilizes open source software for Linux containers and

distributed systems. Projects are designed to be composable and complement each other in order to run

container-ready infrastructure.

ClusterHQ (Click for online version) https://clusterhq.com

Description of Company: Cluster HQ is a software-as-a-service (SaaS) solution to make container virtualization (e.g.

Docker) useful for database-driven services. They offer a full suite of products called Flocker, Volume Hub and dvol

which are tools for testing and managing containerized applications.


Developer Tools

DEVELOPER TOOLS

Product: Flocker

Product URL: https://clusterhq.com/flocker/

introduction /


ClusterHQ/flocker


Description: Flocker is an open source container data

volume manager for your Dockerized applications. It

manages Docker containers and data volumes together.

Unlike a Docker data volume which is tied to a single

server, a Flocker data volume, called a dataset, is

portable and can be used with any container in your

cluster. When you use Flocker to manage your stateful

microservice, your volumes will follow containers when

they move between different hosts in a cluster.

CUSTOMERS

Swisscom

PARTNERS

https://clusterhq.com/partners /

DEVELOPER TOOLS FEATURE/BENEFIT

Flocker allows developers to easily move applicaitons,

including their associated data, between different virtual

machines and can move existing containers between

different hosts.

LICENSING/PRICING

The Flocker app is based on open source so it is free,

but support starts at $1000. ClusterHQ also offers

training, PoC (proof-of-concept) support, and growth

support for additional charges. https://clusterhq.com/

flocker/support /


Container OS/Runtimes, Orchestration, Management,

Monitoring, Image Registry


Product: CoreOS

Product URL: https://coreos.com/docs/Open source repository: https://github.com/coreos

Date of Initial Release: August 2013


Product: Tectonic Enterprise

Product URL: https://tectonic.com/enterprise/

Open source repository: https://github.com/coreos


CUSTOMERS

Viacom, Computer Associates, Verizon, and Salesforce.com

IMAGE REGISTRY

Product: Quay

Product URL: https://quay.io/

Open source repositoryDate of Initial Release: June 2012

LICENSING/PRICING

CoreOS: pricing is not publicly disclosed

Tectonic: pricing is not publicly disclosed

Quay.io pricing: https://quay.io/plans/

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/coreos



https://coreos.com/

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/ClusterHQ



https://clusterhq.com/

https://clusterhq.com/flocker/introduction


https://github.com/ClusterHQ/flocker


https://clusterhq.com/partners

https://clusterhq.com/flocker/support


https://coreos.com/docs/

https://github.com/coreos

https://tectonic.com/enterprise/


https://quay.io/

https://quay.io/plans/

https://quay.io/plans/

https://quay.io/


https://tectonic.com/enterprise/


https://coreos.com/docs/



https://clusterhq.com/partners





https://clusterhq.com/


https://coreos.com/






Google (Click for online version) www.google.com

Description of Company: Google’s mission is to organize the world’s information and make it universally accessible

and useful.

Docker (Click for online version) www.docker.com

Description of Company: Docker is an open platform for developers and sysadmins to build, ship, and run distributed

applications. With Docker, organizations shrink application delivery from months to minutes, frictionlessly move

workloads between data centers and the cloud and achieve 20X greater efficiency in their use of computing resources.


Application Platforms/Hosting; Image Registry


Product: Google Container Engine

Product URL: https://cloud.google.com/container-engine/


kubernetes/kubernetes

Date of Initial Release: July 2015 Description: Google Container Engine is a powerful

cluster manager and orchestration system for running

your Docker containers. Container Engine schedules

containers into the cluster and manages them

automatically based on requirements you define (such

as CPU and memory). It’s built on the open source

Kubernetes system, giving you the flexibility to take

advantage of on-premises, hybrid, or public cloud

infrastructure.

CUSTOMERS

Not Provided

IMAGE REGISTRY

Product: Google Container Registry

Product URL: https://cloud.google.com/container-registry/



Description: Fast, private Docker image storage on

Google Cloud Platform

LICENSING/PRICING

Google Container Engine charges a fee for managing

a Kubernetes master for clusters that are 5 nodes and

over. Clusters that are under 5 nodes have no charge.

Google Container Registry charges for storage of your

images and bandwidth charges. You pay no per image

storage fee.


Container OS/Runtimes; Developer Tools; Application

Platforms; Orchestration, Management, Monitoring;

Image Registry; Security; Infrastructure


Product: Docker Engine

Product URL: https://www.docker.com/products/

docker-engine

Open source repository: https://github.com/docker/

docker



Product: Docker Swarm

Product URL: http://www.docker.com/products/

docker-swarm

Open source repository: github.com/docker/swarm

CUSTOMERS

http://www.docker.com/customers

APPLICATION PLATFORMS

Product: Containers as a Service (CaaS) via the

Universal Control Plane


docker-universal-control-plane



IMAGE REGISTRY

Product: Docker Trusted Registry


docker-trusted-registry



https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/google



http://www.google.com/

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/docker



http://www.docker.com/

https://cloud.google.com/container-engine/


https://github.com/kubernetes/kubernetes


https://cloud.google.com/container-registry/


https://www.docker.com/products/docker-engine


https://github.com/docker/docker


http://www.docker.com/products/docker-swarm


https://github.com/docker/swarm


http://www.docker.com/products/docker-universal-control-plane


http://www.docker.com/products/docker-trusted-registry







https://github.com/docker/swarm













http://www.docker.com/


http://www.google.com/






Hewlett Packard Enterprise (Click for online version) www.hpe.com

Description of Company: Hewlett Packard Enterprise is a leading technology company with a portfolio of services,

software, and hardware spanning the cloud from the data center to workplace applications.

HashiCorp (Click for online version) https://www.hashicorp.com /

Description of Company: HashiCorp, founded in 2012, develops tools for data center management: application

development, delivery, and maintenance. HashiCorp provides open source solutions.


Container OS/Runtimes; Developer Tools; Application

Platforms/Hosting; Orchestration, Management,

Monitoring; Image Registry

DEVELOPER TOOLS

Product: HPE Helion Stackato

Product URL: http://www.stackato.com


cloudfoundry


Description: Whether you use Java, Perl, Python, PHP,Ruby, Node.js, Erlang, Scala, Clojure, Mono, or almost

anything else for your applications, Stackato helps

you deploy them to any private, public or hybrid cloud

faster, in a secure Docker container.




CUSTOMERS

Capital One, Angie’s List, Gemalto, Nelnet, Dirk

Rossmann



Product URL: http://www.stackato.com


cloudfoundry


Description: HPE Helion Stackato is an application

platform or Platform as a Service (PaaS) that enablesdevelopers to rapidly develop, deploy, and scale cloud

applications across a mix of public and private clouds.

We provide support for a wide and growing list of

programming languages and technologies.





Developer Tools

DEVELOPER TOOLS

Product: Vagrant

Product URL: https://www.vagrantup.com /

Open source repository: https://github.com/mitchellh/

vagrant

Date of Initial Release: January 2010

Description: Vagrant creates and configures

lightweight, reproducible, and portable development

environments. Vagrant open source is available Mac OS

X, Windows, or a popular distribution of Linux. Vagrant

stores a single file for your development project.

Vagrant creates identical development environments

for everyone on your team.

CUSTOMERS

Disqus, BBC, Mozilla, Expedia, Yammer

PARTNERS

https://www.vagrantup.com/sponsors.html


Developers: Vagrant isolates dependencies and their

configuration within a single disposable, consistent

environment, and uses the tools you are used to working

with (editors, browsers, debuggers, etc.).

Benefit: Developers and teams have consistent

development environments.

LICENSING/PRICING

https://www.vagrantup.com/vmware/

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/hewlett-packard-enterprise



http://www.hpe.com/

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/hashicorp



https://www.hashicorp.com/

http://www.stackato.com/

https://github.com/cloudfoundry





https://www.vagrantup.com/

https://github.com/mitchellh/vagrant








https://www.vagrantup.com/







https://www.hashicorp.com/


http://www.hpe.com/






Kismatic (Click for online version) https://kismatic.com

Description of Company: Kismatic was founded to be a commercial open source company supporting the Kubernetes

open source project.

IBM (Click for online version) http://www.ibm.com

Description of Company: International Business Machines Corporation provides information technology (IT) products

and services worldwide.


Developer Tools; Application Platforms/Hosting;


DEVELOPER TOOLS

Product: IBM Bluemix

Product URL: http://www.ibm.com/cloud-computing/

bluemix/solutions/open-architecture/?cm_

mc_uid=72787495120514543641617&cm_mc_

sid_50200000=1454373608#containers

Open source repository: https://github.com/IBM-

Bluemix




Product URL: See Product URL Above


Bluemix


CUSTOMERS

http://www.ibm.com/cloud-computing/bluemix/case-

study/



Product URL: http://www.ibm.com/cloud-computing/

bluemix/solutions/open-architecture/?cm_

mc_uid=72787495120514543641617&cm_mc_

sid_50200000=1454373608#containers


Bluemix


LICENSING/PRICING

IBM Bluemix pricing ranges from free for start-ups

to complex pricing offerings for larger enterprises.

IBM provides a pricing calculator to estimated costs

based on the required resources for development,

management and hosting needs.


Enterprise Support and Services

ENTERPRISE SUPPORT AND SERVICES

Product: Enterprise Support

Product URL: https://kismatic.com/product/enterprise -

support/

Open source repository: https://github.com/kismatic


Description: Kismatic provides support and services

to manage open source technologies and tools at

scale. Kismatic enterprise is focused on mission-critical

environments and helps customers build and manage

container-based applications, workloads while keeping

security and governance in mind.

CUSTOMERS

Not Provided

PARTNERS

Not Provided

ENTERPRISE SUPPORT & SERVICES

FEATURE/BENEFIT

“Google-scale” container based computingimplementations and support.

LICENSING/PRICING

Enterprise support is through subscriptions and

professional services can be purchased on an ad-hoc

basis.

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/kismatic



https://kismatic.com/

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/ibm



http://www.ibm.com/

http://www.ibm.com/cloud-computing/bluemix/solutions/open-architecture/?cm_mc_uid=72787495120514543641617&cm_mc_sid_50200000=1454373608#containers




https://github.com/IBM

https://github.com/IBM-Bluemix



http://www.ibm.com/cloud-computing/bluemix/case-study/








https://kismatic.com/product/enterprise

https://kismatic.com/product/enterprise-support/

https://github.com/kismatic

https://github.com/kismatic

https://kismatic.com/product/enterprise-support/

https://kismatic.com/product/enterprise

















http://www.ibm.com/


https://kismatic.com/






Microsoft (Click for online version)

http://www.microsoft.com

Description of Company: Microsoft develops, licenses, and supports a range of software products, services, and

devices.

Mesosphere (Click for online version) https://mesosphere.com

Description of Company: Mesosphere (Twitter: @Mesosphere) is building the datacenter operating system (DCOS)

to help enterprises unlock the next generation of scale, efficiency and automation. The Mesosphere DCOS pools

datacenter and compute resources, gives IT operators a much simpler administration model, and improves developervelocity with more modern abstractions and APIs for writing distributed systems.


Container OS/Runtimes; Developer Tools


Product: Mesosphere Datacenter Operating System

(DCOS)

Product URL: www.mesosphere.com

Open source repository: http://mesos.apache.org /


Description: The Mesosphere DCOS pools datacenter

and compute resources, gives IT operators a much

simpler administration model, and improves developer

velocity with more modern abstractions and APIs for

writing distributed systems. DCOS is optimized for

container and microservices orchestration, and scaling

production Big Data workloads

CUSTOMERS

Verizon, Yelp

DEVELOPER TOOLS

Product: Marathon (on DCOS)

Product URL: https://mesosphere.github.io/marathon /


mesosphere/marathon


Description: Marathon is an application and container

orchestration engine. Marathon is built on top of Apache

Mesos and leverages Mesos’ powerful capabilities to

easily deploy and orchestrate containers and workloads

at very large scale. Marathon simplifies the application

deployment by offering features such as intelligent

workload placement, port allocation, automatic failure

detection and recovery, blue/green deployment, etc.


Container OS/Runtimes; Developer Tools


Product: Windows Containers

Product URL: https://msdn.microsoft.com/en-us/

virtualization/windowscontainers/containers_welcome



Description: Windows offers two types of containers:

Windows Server Containers and Hyper-V Containers.

Windows Containers provide operating system level

virtualization that allows multiple isolated applications

to be run on a single system. Windows Server

Containers achieve isolation through namespace and

process isolation. Hyper-V Containers encapsulates

each container in a lightweight virtual machine

CUSTOMERS

Not Provided

DEVELOPER TOOLS

Product: Windows Nano Server

Product URL: https://technet.microsoft.com/en-us/

library/mt126167.aspx



Description: Microsoft’s Nano Server is a remotely

administered server operating system for private

clouds and datacenters. It is similar to Windows Server

in Server Core mode, but smaller, has no local logon

capability, and only supports 64-bit applications, tools,

and agents. It takes up less disk space, sets up faster,

and requires fewer updates and restarts than Windows

Server.

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/microsoft



http://www.microsoft.com/

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/mesosphere



https://mesosphere.com/

http://www.mesosphere.com/

http://mesos.apache.org/

https://mesosphere.github.io/marathon

https://github.com/mesosphere/marathon


https://msdn.microsoft.com/en-us/virtualization/windowscontainers/containers_welcome


https://technet.microsoft.com/en-us/library/mt126167.aspx








https://mesosphere.github.io/marathon

http://mesos.apache.org/

http://www.mesosphere.com/

https://mesosphere.com/


http://www.microsoft.com/






Portworx (Click for online version) http://portworx.com

Description of Company: Portworx creates software-defined infrastructure for containerized applications.

New Relic (Click for online version)

http://newrelic.com

Description of Company: New Relic is a Software Analytics company that makes sense of billions of metrics across

millions of apps. New Relic’s technology, delivered in a software as a service (SaaS) model monitors Web and mobile

applications in real-time that run in cloud, on-premises, or hybrid environments. New Relic, founded in 2008, is a

public company trading on the NYSE as “NEWR.”


Infrastructure Services


Product: Portworx Container Defined Storage

Product URL: http://portworx.com/products /


libopenstorage/openstorage


Description: Portworx Container-Defined Storage(CDS) is a storage solution for containerization. With

CDS, enterprise IT departments can provide a scalable

and provisioned agile infrastructure.

CUSTOMERS

Not Provided

PARTNERS

Not Provided

INFRASTRUCTURE SERVICES FEATURE/BENEFIT

Keep containers portable by allowing their storage to be

migrated across environments in their entirety.

LICENSING/PRICING

Pricing not available publicly




Product: New Relic, with versions for monitoring

servers, applications, mobile apps, data, and others.

Product URL: http://newrelic.com/products



Description: New Relic’s platform is designed to allowdevelopers to deploy 50+ plug-ins from technology

partners (or build their own) to the New Relic

dashboard. The software provides insight provides

analytics and monitoring statistics from all aspects

of a business, including application performance to

customer experience and your business as a whole.

CUSTOMERS

http://newrelic.com/why-new-relic/customers

PARTNERS

IBM Bluemix, Amazon Web Services, CloudBees, Engine

Yard, Heroku, and Microsoft Azure.


FEATURE/BENEFIT

New Relic’s platform allows organizations to provide

better customer experience management. It canmeasure customer experience across all users, for web

and mobile channels and allow analysts to understand

customer behavior and evolve engagement tactics

accordingly.

LICENSING/PRICING

http://newrelic.com/application-monitoring/pricing

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/portworx



http://portworx.com/

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/new-relic



http://newrelic.com/

http://portworx.com/products

https://github.com/libopenstorage/openstorage


http://newrelic.com/products





http://newrelic.com/products



http://portworx.com/products

http://newrelic.com/


http://portworx.com/






Rancher Labs (Click for online version)

http://rancher.com

Description of Company: Rancher Labs is building software for organizations to run Docker in production. Rancher is

an open source platform for building a private container service. Rancher combines Docker orchestration, scheduling,

networking, storage and application management into an easy to operate platform that can deploy containers on any

cloud or infrastructure.

Puppet Labs (Click for online version) www.puppetlabs.com

Description of Company: Puppet Labs helps organizations automate the configuration and management of machines

and the software running on them. With Puppet, businesses can make rapid, repeatable changes and automatically

enforce the consistency of systems and devices, across physical and virtual machines, on premises or in the cloud.


Container OS/Runtimes; Orchestration, Management,

Monitoring; Infrastructure Services


Product: RancherOS

Product URL: http://rancher.com/rancher-os/

Open source repository: https://releases.rancher.com/

os/latest/rancheros.iso



Product: Rancher

Product URL: http://rancher.com/rancher /

Open source repository: https://github.com/rancher/

cattle


PARTNERS

Docker, Sysdig, Kubernetes


Product: Rancher Networking and Rancher Convoy

Product URL: http://rancher.com/rancher /

Open source repository: https://github.com/rancher/

cattle


LICENSING/PRICING

Rancher and RancherOS are available as Free and Open

Source Software. Rancher Labs provides commercial

versions of our products that include enterprise-grade

support. Pricing is based on the number of LCPUs under

management.


Configuration Management; Orchestration,

Management, Monitoring


Product: Puppet; Puppet Enterprise

Product URL: https://puppetlabs.com/puppet/puppet -

enterprise

Open source repository: http://info.puppetlabs.com/

open-source-puppet-download.html?_ga=1.183193638.14

53335505.1415291517


Description: Automated configuration management

eliminates a lot of manual work, and creates greater

stability and predictability. Puppet Enterprise provides

the operational agility, efficiency and insight needed to

proactively manage dynamic infrastructure. You define

the desired state, and Puppet Enterprise enforces it.

CUSTOMERS

https://puppetlabs.com/about/customers


Product: Puppet Application Orchestration

Product URL: https://puppetlabs.com/puppet/puppet -

application-orchestration-news

Open source repository: http://info.puppetlabs.com/

open-source-puppet-download.html?_ga=1.183193638.1

453335505.1415291517

Description: Puppet Application Orchestration sets

the standard for how to deliver, install, configure

and maintain distributed software applications. This

simplified application orchestration process enables you

to model distributed applications and application stacks

as Puppet code so you can quickly and reliably roll out

new infrastructure and applications.

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/rancher-labs



http://rancher.com/

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/puppet-labs



http://www.puppetlabs.com/

http://rancher.com/rancher-os/

https://releases.rancher.com/os/latest/rancheros.iso


http://rancher.com/rancher

https://github.com/rancher/cattle





https://puppetlabs.com/puppet/puppet-enterprise


http://info.puppetlabs.com/open-source-puppet-download.html?_ga=1.183193638.1453335505.1415291517




https://puppetlabs.com/puppet/puppet-application-orchestration-news
























http://rancher.com/rancher-os/

http://www.puppetlabs.com/


http://rancher.com/






Shippable, Inc. (Click for online version) https://app.shippable.com

Description of Company: Shippable develops a Docker-based continuous integration platform that supports custom

Docker workflows to support developers.

SaltStack (Click for online version) www.saltstack.com

Description of Company: SaltStack is a complete systems management software platform for scalable, data-driven

orchestration and automation of any infrastructure or application stack. SaltStack is used by IT operators, system

administrators and DevOps engineers to automate configuration management, private cloud building, public cloudorchestration and event-driven infrastructure.


Configuration Management, Orchestration;

Management, Monitoring


Product: SaltStack Enterprise

Product URL: http://saltstack.com/saltstack-enterprise-

for-devops/

Open source repository: http://saltstack.com/

saltstack-downloads/

Date of Initial Release: May 2011 Description: SaltStack delivers a scalable, flexible,

and intelligent configuration management solution

using SaltStack data-driven orchestration for both a

declarative or imperative representation of system

configuration. SaltStack config management was built

from the ground up on a very fast remote execution

platform utilizing a master and minion architecture. Salt

SSH is now also available for an agentless approach.

SaltStack manages the most containers, with Docker

support since Feb. 2014.

CUSTOMERS

http://saltstack.com/blog /


Product: SaltStack Enterprise

Product URL: http://saltstack.com/saltstack -enterprise-

cloudops/

Open source repository: http://saltstack.com/

saltstack-downloads/


Description: SaltStack has managed Docker containerssince Feb. 2014. This feature is another piece of the

infrastructure and application stack. As containers have

become part of complex IT environments, SaltStack

provides intelligent, data-driven orchestration and

automation for any public or private infrastructure and

any application, code, virtualization or container, making

holistic data center orchestration an attainable reality


Developer Tools

DEVELOPER TOOLS

Product: Shippable CI/CD and Shippable Formations

Product URL: https://app.shippable.com/products.html



Description: CI/CD integrates into a source control

repository and performs tests on the code as soon

as possible. CI/CD also supports the release process

by uploading code to a cloud provider if successful.

Formations monitors and deploys changes of container

images as well.

CUSTOMERS

Concur, MojoPages

PARTNERS

Not Provided


Push and pull from Docker registries. Push fully tested

containers / custom images from your repo on Docker

Hub, GCR, or Quay. Specify your private registry

credentials and push or pull images from there as well.

LICENSING/PRICING

Free plan allows for one concurrent build at a time and no

support. Paid plans can scale based on needs and load.

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/shippable



https://app.shippable.com/

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/saltstack



http://www.saltstack.com/

http://saltstack.com/saltstack

http://saltstack.com/saltstack-enterprise-for-devops/

http://saltstack.com/saltstack-downloads/


http://saltstack.com/blog


http://saltstack.com/saltstack-enterprise-cloudops/



https://app.shippable.com/products.html

https://app.shippable.com/products.html



http://saltstack.com/saltstack-enterprise-cloudops/


http://saltstack.com/blog



http://saltstack.com/saltstack-enterprise-for-devops/


http://www.saltstack.com/


https://app.shippable.com/






Sysdig (Click for online version) https://sysdig.com

Description of Company: Sysdig is a startup that creates cloud based container native monitoring tools.

SignalFX (Click for online version) https://signalfx.com

Description of Company: SignalFx provides a monitoring platform for applications. Powered by SignalFlow streaming

and historical analytics technology, SignalFx analyzes data collected from thousands or more sources to create

aggregated analytics such as percentiles, moving averages and growth rates within seconds of receiving data.




Product: Sysdig Cloud

Product URL: https://sysdig.com/product /

Open source repository: http://github.com/draios/

sysdig

Date of Initial Release: June 2013 Description: Sysdig Cloud comes with built-

in integrations to several popular applications,

infrastructure, and container technologies. Sysdig

extracts = granular metrics from inside containers

without needing to install any additional agents or

plugins


FEATURE/BENEFIT

Sysdig offers a real-time dashboard that collects,

analyzes, and displays performance metrics at one-

second granularity allowing customers to gain instant

visibility into performance and issues.

LICENSING/PRICING

Sysdig works on a “try-and-buy” model. Anyone cantry Sysdig cloud for 14 days without obligation. This

can be upgraded to a standard plan or enterprise plan.

The standard plan costs $20 a month and provides

for some limited monitoring and restricted support.

The enterprise plan has custom pricing for unlimited

monitoring options and the highest tier of support.




Product: SignalFX

Product URL: https://signalfx.com/technology /

Open source repository: https://github.com/signalfx


Description: SignalFX provides metrics, dashboards,

analytics, and alerts for platforms and applications

to monitor network operations. It also provides open

source and industry-standard libraries like statsd and

DropWizard so developers can create new monitoring

tools. With the data collection capabilities, SignalFX

also adds correlation and analytics tools which allows

administrators to detect problems and profile users.

CUSTOMERS

https://signalfx.com/customers /

PARTNERS

Not Provided


FEATURE/BENEFIT

SignalFX is built for elastic environments. It scales

beyond billions of data points per day. Users can browse

content based on service dimensions and metadata, not

just on hosts, and dynamically generate service-widedashboards with real-time, aggregated metrics.

LICENSING/PRICING

SignalFX employs usage-based pricing model that’s

based on data ingest rates. This provides predictable

pricing and flexibility to burst without penalties when

and where you need more visibility. Pricing starts at

$15/server/month.

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/sysdig



https://sysdig.com/

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/signalfx



https://signalfx.com/

https://sysdig.com/product

http://github.com/draios/sysdig


https://signalfx.com/technology

https://github.com/signalfx

https://signalfx.com/customers

https://signalfx.com/customers

https://github.com/signalfx

https://signalfx.com/technology



https://sysdig.com/product

https://signalfx.com/


https://sysdig.com/






VMware, Inc. (Click for online version) https://www.vmware.com

Description of Company: VMware develops and markets its product and service offerings within three product

groups, which include software-defined data center (SDDC), hybrid cloud computing and end-user computing (EUC).It’s products and services are based on server virtualization and related technologies that have primarily been used for

virtualizing on premise data center servers for private cloud computing.

Twistlock (Click for online version) https://www.twistlock.io

Description of Company: Twistlock is a privately held company that provides an enterprise suite for container

security. Twistlock technologies address risks on the host and the containerized application with consistent security

policies from development to production by monitoring container activities, managing vulnerabilities, detecting andisolating threats targeting production containers.


Container OS/Runtimes; Developer Tools;



Product: vSphere Integrated Containers, Photon

Machines and Photon OS

Product URL: https://www.vmware.com/cloudnative/

technologies

Open source repository: https://vmware.github.io/photon /


DEVELOPER TOOLS

Product: VMware AppCatalyst & VMware Photon OS

Product URL: see Container OS/Runtimes section

Open source repository: see Container OS/Runtimes

section


CUSTOMERS

https://www.vmware.com/company/customers


Product: VMware vSphere, VMware vRealize and third-

party / open-source integrations

Product URL: https://www.vmware.com/products/

vrealize-suite



LICENSING/PRICING

Pricing ranges from free offerings / open source

solutions to enterprise solutions. Pricing for various

components that support containers and virtualized

environments are not published.


Security


Product: Twistlock Container Security Suite

Product URL: https://www.twistlock.com/wp-content/

uploads/2015/11/twistlock-product-sheet-1-final-2.pdf

Open source repository: https://github.com/twistlock


Description: The Twistlock suite ensures security

control and policy compliance. It has 3 maintechnologies: 1) Vulnerability management 2) Access

control 3) Runtime defense

CUSTOMERS

https://www.twistlock.com/customers /

PARTNERS

Amazon Web Services, Docker, Google, Sonatype,

Cloud Native Computing Foundation, and Ishi Systems.

SECURITY FEATURE/BENEFIT

Twistlock provides full stack vulnerabililty management for

the Linux distribution layer, app frameworks, and custom

packages, including images in repositories and on hosts.

LICENSING/PRICING

The Twistlock suite is available for a free trial at https://

www.twistlock.com/demo / Other pricing is not disclosed.

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/vmware



https://www.vmware.com/

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/twistlock



https://www.twistlock.io/

https://www.vmware.com/cloudnative/technologies


https://vmware.github.io/photon



https://www.vmware.com/products/vrealize-suite


https://www.twistlock.com/wp-content/uploads/2015/11/twistlock-product-sheet-1-final-2.pdf


https://github.com/twistlock

https://www.twistlock.com/customers

https://www.twistlock.com/demo




https://www.twistlock.com/customers

https://github.com/twistlock










https://www.twistlock.io/


https://www.vmware.com/






Weaveworks Inc. (Click for online version) http://www.weave.works /

Description of Company: Weaveworks makes it easier to build, deploy and run microservices using containers. Weave

was formed in 2014, shipped its first product, Weave Net in September 2014 and received series A funding from Accel

Partners in December 2014. The company has offices in San Francisco and London, and boasts a strong team withdeep distributed systems, networking, monitoring and cloud services expertise.



Services


Product: Weave Scope

Product URL: http://www.weave.works/products/

weave-scope/


weaveworks/scope


Description: Weave Scope builds a real-time map

of your containerized application. Manage your

docker application in real-time: choose an overview

of your container infrastructure, or focus on a specific

microservice. Easily identify and correct issues

to ensure the stability and performance of your

containerized applications. Docker containers are

automatically color-coded based on patterns and can

be grouped by role, and behavior. Choose the level of

detail, and change it dynamically, without manual config

CUSTOMERS

International Securities Exchange (ISE), Tutum (now

part of Docker), Cloud 66, DCHQ


Product: Weave Net

Product URL: http://www.weave.works/products/

weave-net/


weaveworks/weave


Description: Weave Net is the simplest and easiest way

to build, run and deploy a container network for Docker.

It builds a micro-SDN linking all the containers with built-

in service discovery using DNS. Weave Net is available

as a stand-alone product and as a Docker Networking

plug-in. Unlike standard Docker Networking, there is

no requirement to run an external database (cluster

store). This eliminates a single point of failure, eliminates

database security and maintenance operations, and is

more reliable.

https://www.sdxcentral.com/reports/linux-container-ecosystem/companies/weaveworks



http://www.weave.works/

http://www.weave.works/products/weave-scope/


https://github.com/weaveworks/scope


http://www.weave.works/products/weave-net/


https://github.com/weaveworks/weave










http://www.weave.works/




http://www.sdxcentral.com/

SDxCentral Inside the Linux Container Ecosystem Report A

Documents

Transcript of SDxCentral Inside the Linux Container Ecosystem Report A