Authored by Ryan Kelly, Staff Systems Engineer, Cloud Management


In no particular order, here are the top 10 labs that I want to take this year at VMworld

  • Cloud Operations With Photon Platform [SPL-1730-USE-2]– This lab will provide an introduction into the new operational models for cloud native applications. Users will set up a Private Cloud on the Photon Platform control plane and will deploy Cloud Applications using multiple application framework technologies, including Docker and Kubernetes.
  • DevOps-Ready IT with vRealize Code Stream [SPL-1706-SDC-2]– This lab will introduce you to vRealize Code Stream which provides release pipeline automation and continuous delivery for DevOps-ready IT. You will learn how to install and configure vRCS and execute a pipeline on a live application.
  • Introduction to vRealize Orchestrator [SPL-1721-SDC-5] – Learn how to use vRealize Orchestrator to simplify the automation of IT tasks. Explore the vRealize Orchestrator development environment and learn important development concepts by building and testing basic workflows.
  • vRealize Automation Extensibility [SPL-1721-USE-3]– his advanced lab explores how vRealize Automation leverages the new Event Broker to extend functionality with existing toolsets and workflows. Common extensibility scenarios include IP Address Management with Infoblox, ITSM tools, DNS and many more.
  • vCloud Network Functions Virtualization [SPL-1786-USE-1]– VMware vCloud NFV is a Network Functions Virtualization (NFV) services delivery, operations and management platform, developed for Communications Service Providers (CSPs). For this lab we have partnered with Cloudify and Athonet. We will demonstrate the end-to-end lifecycle of VNF management and orchestration  from installation and deployment through post-deployment, or in the telco industry terminolo
  • vSphere Automation API and SDK: Tech Preview [SPL-1710-SDC-5]– This Lab introduces you to vSphere Automation APIs and SDKs, which are new developer friendly, simplified interfaces that allow for Virtual Machine creation, modification and deletion via a consistent set of developer and automation tooling.
  • vRealize Operations Advanced Use Cases [SPL-1706-USE-4]– This Lab introduces some advanced vRealize Operations topics such as crafting your Policies, working with Super Metrics and Custom Dashboards, using the Alerting framework, and creating custom Views and Reports. We will also introduce the user to End Point Operations and the vRealize Operations API.
  • vRealize Automation 7 Basics [SPL-1721-USE-1]– This introductory lab demonstrates the features of vRealize Automation and is a great place to start to begin learning about the powerful capabilities and features of the solution.
  • vSphere Integrated Containers from A to Z [SPL-1730-USE-1]– This lab explores vSphere Integrated Containers (VIC) and it’s ability to combine the agility and application portability of Docker Linux containers with VMware’s industry-leading virtual infrastructure platform – a solution that provides unique isolation advantages along with improved container manageability.
  • vRealize Automation 7 Advanced [SPL-1721-USE-2]– This advanced lab covers the more complex service authoring capabilities of vRealize Automation including XaaS and Puppet, NSX integration and Application Authoring.

There you have it, maybe I will see you in a Lab next to me!

NOTE: These labs are delivered on a first-come, first-served basis and do not need to be scheduled in advance.


Sun., Aug. 28: 9am-7pm
Mon., Aug. 29: 10:30am-6pm
Tue., Aug. 30: 10:30am -6pm
Wed., Aug. 31: 8am-5pm
Thur., Sept. 1: 8am-3pm



Get Ready for Another Cloud-Native Packed VMworld!

CNA_cloud logo

VMworld is less than a week away.  And like last year, we’ve got a lot happening on the Cloud-Native front!  We’ll be providing updates and deep dives into vSphere Integrated Containers and Photon Platform, talking about what our other technologies are doing in this space (e.g. NSX, VSAN, vRealize), in addition to going deeper on DevOps, containers, CI/CD, and more.

But I may be getting a bit ahead of myself.  Some of you have a good understanding of what the “cloud native” space consists of, but many of you probably don’t.  So before getting into specifics, it’s important to understand why you should care about this space.  When we talk about “cloud native”, we’re really talking about the tools, technologies, and processes that enable a faster, more responsive organization that achieves a higher software delivery velocity.  As software becomes a bigger differentiator for businesses, those businesses that are quickest to release high quality software and react to users’ preferences will have a huge business advantage.  The latest State of DevOps Report 2016 clearly shows the impact of higher performing organizations:

  • Top performing IT organizations deploy 200 times more frequently than lower performing ones
  • They have three times lower change failure rates and when they do have failures, they recover 24 times faster
  • They spend 22 percent less time on unplanned work or rework

As you can see, these numbers are stunning and it should be clear that the sort of advantage a high performing IT organization can deliver really makes a difference between a successful and an unsuccessful business.  Achieving this high performance organization is everyone’s responsibility.  You shouldn’t assume that someone else will do it.  You should think about how you can drive this sort of change in your org!


And that’s what we’re here to help with.  We have a ton of content on all aspects of cloud-native at VMworld.  Let me walk you through what we have in store for VMworld:

  • Keynotes: Cloud-native will be featured throughout the first two days of keynotes at VMworld, but we’ll have a specific section on cloud-native during the day 2 keynote – Tuesday, Aug 30.  We will have some exciting updates on vSphere Integrated Containers and Photon Platform.
  • Breakout sessions: These are deeper dive sessions into a wide variety of topics.  VMworld has hundreds of breakout sessions over a course of four days throughout the conference and there are a few dozen of these sessions dedicated to cloud-native.  There are two specific tracks we’d like to call out:
    • Cloud-Native: the CNA track covers vSphere Integrated Containers, Photon Platform, Pivotal-VMware Cloud-Native Stack, DevOps, CI/CD, Open source, and much more!
    • DevOps : the DevOps track covers all aspects of DevOps, from basic 101 level overviews to deeper dives into specific use cases.  It also covers a broad range of technologies, allowing you to see how VMware’s technologies fit into a DevOps environment.
  • Hands-on labs (HOL): HOLs are where you can get very hands on (as the name suggests… :)) experience with a particular technology or product.  We have two HOLs specifically on cloud-native: one on vSphere Integrated Containers and one on Photon Platform.
  • Expo booths at Solutions Exchange: The expo booth is a great place to get a high level overview of our products as well as a forum to ask specific questions you may have.  We’ll have expo booths for vSphere Integrated Containers, Photon Platform, and the Pivotal-VMware Cloud-Native Stack (bundle of Pivotal Cloud Foundry and Photon Platform) at the VMware booth in the Solutions Exchange.
  • VMware {code} hackathon: A fun way to put what you’ve learned into practice is the hackathon from VMware {code}.  It’s not all cloud-native, but if you adapt cloud-native and DevOps practices, you could have an advantage!!

Finally, if you want everything CNA happening at VMworld in one convenient place, check out our field guide and connect with us @cloudnativeappsSo as you can see, there’s a tremendous amount to do at VMworld this year.  We’re really excited to share these updates with you next week in Vegas and have been working hard to pull everything together.  We look forward to seeing you there!


Authored by Ryan Kelly, Staff Systems Engineer, Cloud Management

     Many organizations are on a journey to adopt containers in some form or another. There are many options available on the market today and even VMware has multiple options for running containers. While containers are similar to virtual machines they come with their own obstacles and challenges to support them in production.

Graphic based on the original Tweet of @mfdii as seen here

In this session I will present the technical features of each solution and give some background on the goals of each of both stacks. I will also compare and contrast the features of both Photon Platform and vSphere Integrated containers and list the use cases that each one addresses. There will also be time to ask any questions that are on the top of your mind. Click here to sign up for this session or any other of my sessions.

Containers for the vSphere Admin


Updated Aug 24, 2016, added graphic attribution.


Authored by Emad Benjamin, Principal Architect, Global Services Advanced Architecture

Cloud-Native Apps_State of the Union

As per the above picture many have talked about Cloud Native Apps (CNA) but only few have done real implementations, and the time is now for this technology trend to become main-stream.  In this group discussion we will have an interactive session on what is cloud native, what scale it addresses, who are some of the adopters, and which direction this trend is forcing the market over the next few years.  It is an opportunity for you to ask the simplest of questions to the most complex ones, sometimes a simple question as “what is cloud native” can quickly turn into a complicated answer, and hence is the opportunity to discuss the wide variety of opinion that surrounds this.

In this talk we will highlight the elements of this rapidly moving phenomenon through our industry, a phenomenon of building platforms, not just business logic software but infrastructure as software. We humbly believe that the drive towards these platform solutions is due to the following fact: approximately half of new applications fail to meet their performance objectives, and almost all of these have 2.x more cloud capacity provisioned than what is actually needed. As developers/DevOps engineers we live with this fact every day, always chasing performance and feasible scalability, but never actually cementing it into a scientific equation where it is predictable, but rather it has always been trial based, and heavily prone to error. As a result we find ourselves delving with some interesting platforming patterns of this decade, and unfortunately we are lead to believe that such patterns as microservices, 3rd platforms, cloud native, and 12factor are mainly a change in coding patterns.  However, contrary to this popular belief, these patterns represent a major change in “deployment” approach, a change in how we deploy and structure code artifacts within applications runtimes, and how those application runtimes can leverage the underlying cloud capacity. These patterns are not code design patterns, but rather platform engineering patterns, with a drive to using APIs/Software to define application platform policies to manage scalability, availability and performance in a predictable manner.

In this session we give you an opportunity to come ask us any and all of your questions about cloud native and what it is going to mean for you as Ops and DevOps Engineer over the next few years, how the market is changing and how you will have to adapt to meet those challenges.

This session will be presented at VMworld 2016 – Las Vegas. Register here.


Authored by Martijn Baecke, Senior Systems Engineer

Digital Transformation? DevOps? Docker? What is this all about? Well this is exactly what we will discuss during our session “Running Docker on your existing Infrastructure with vSphere Integrated Containers”at VMworld. Over the last couple of years containers have taken the world by storm. Developers have started using them to package their application code. Containers have made their world a lot easier and flexible; but what runs in test / development at some point needs to go into production.

The question that then comes to mind is: How are you going to deploy that and how are we going to manage these new workloads? Should you build a new infrastructure specifically for containers? Do you want another silo to manage, maintain and update or do you run it on something that already works and that you’ve known for years? There is no need for a new infrastructure, you already have an infrastructure that works and that you know how to operate. To stay relevant, containers need to be part of your existing infrastructure; vSphere Integrated Containers is a means to that end.

In this session, we will outline the architecture of vSphere Integrated Containers, explain how it works and how it will help you to stay secure, while keeping control of your infrastructure resources. You can provide developers the containers that they want, but maintain the same way of working without the need to change your infrastructure. The best of both worlds!


Authored by Ryan Kelly, Staff Systems Engineer, Cloud Management

Containers for the vSphere Admin

Following up on the overwhelming response from my blog post from last years observations at VMworld I have been asked to present this in a break out session this year. I spent many years as a vSphere admin at a large corporation and I have come across a lot of technologies. Instead of getting into all the buzzwords, when I explain technology I like to break it down to the basics. Who, what, when and why. In this session you can quickly come up to speed with containers and understand how they fit into your everyday job. Also learn ways that VMware can help you adopt and leverage this new technology using all the tools you have come to love from VMware. Sign up for my sessions here.


Authored by Ryan Kelly, Staff Systems Engineer, Cloud Management

As you probably already know, VMworld is back in Vegas this year and bigger than ever. Whether this is your first time attending or you are a seasoned veteran, I have some tips that I think you all will find valuable. VMworld itself is action packed, from the welcome reception, sponsored parties to the VMworld party, you have plenty to see and do. Add to that is the 24×7 entertainment that Vegas offers, and it can get overwhelming!


Before you go:

  • Register for the event, sounds obvious but some folks arrive not registered, and the pre-registration is cheaper.
  • Plan your week by visiting the Content catalog and populating your Schedule Builder. The General Sessions are open seating but the break out sessions you need to register for. (There are almost always standing room for additional overflow but registering is a guarantee you get a seat.)
  • Log on to twitter to see what sessions are trending so you know before you go.
  • Vegas is hot and dry in August, pack plenty of summer clothes, cotton t-shirts, shorts and a swimsuit (The pools are amazing here folks!)
  • Pack extra room in your bag or bring an extra one, you will receive a VMworld backpack and get tons of swag from VMware and partners in solutions exchange.

Travel Tips:

  • Go to sleep now until the morning you travel to VMworld Vegas, no seriously you are gonna need all the sleep you can get.
  • Stay at Mandalay Bay or Delano if you can, easy walk to the convention and one of the best pools in Vegas. Next bets in order of distance are Luxor, Excalibur, New York New York (amazing Roller Coaster), MGM Grand and Monte Carlo.
  • Thanks to one of my readers tips there is Uber and Lyft Service now in Vegas. You can also wait in line and take a cab from the airport and around town or share one if you can. Ask about using a credit card before you get in, sadly some still only take cash, about $20 min to pretty much any hotel on the strip, although the limo or black car will save you from waiting in line, it will run you about $50 minimum (but hey you will arrive in style)

During the Convention:

  • Wear comfortable shoes, you walk a lot in Vegas anyway but the convention center alone is huge here.
  • Attend the keynotes, you get all the good information first and the opening visuals are always impressive and inspiring. At least attend the Technical Keynote if there is only one you plan to attend!
  • Drink a lot of water, it is super hot and dry here and it is dangerous to get dehydrated.
  • Visit the solutions exchange during the day, when it is less busy, to get one-on-one sessions with VMware experts or one of our partners experts.
  • Network with other customers and VMware folks, share your success and learn what works for them. All the best in the world will be in one place for a week and that is huge.

Party Time!: Full List here!

  • Welcome Reception, Sunday, Aug 28
, 5:00pm – 7:30pm, Solutions Exchange
  • Hall Crawl, Tuesday Aug 30
, 4:30pm – 6:00pm, Solutions Exchange, Open to attendees
  • VMworld Party, Wednesday Aug 31, 7:30pm – 10:30pm, Las Vegas Motor Speedway, 7000 N Las Vegas Blvd, Open to full conference pass attendees
  • Veeam’s Annual VMworld Party, Tuesday Aug 30, 
8:00pm – 0:00am, The LIGHT Vegas – 3950 South Las Vegas Boulevard, Las Vegas, NV 89119, Register here
, VMworld Badge is required for entrance
  • If you plan to gamble just know that the big fancy casinos didn’t get that way by giving away money, venturing out down the strip will increase your odds. If you do plan to gamble there, sign up for the members rewards card, you would be surprised how many perks and freebies they send you.

Food, Show and Club Recommends:

Do’s and Dont’s:

  • Do get reservations for dinner now, Vegas will be very busy so if there is somewhere you want to eat, especially for large groups, book that reservation now!
  • Do try a hands on lab, there is no better way to learn than trying it yourself. These are first come first served, no need to sign up in advance just plan some time in your schedule.
  • Do eat breakfast and lunch at the conference, save some hits on your expense report for dinners and drinks later.
  • Don’t leave your laptop or personal belongings unattended or out of your control, while the conference is secure you just can’t be too careful.
  • Don’t trust street vendors handing out free limo rides to clubs, there is always a catch!
  • Do use common sense especially late at night, Vegas is a fairly city safe but like any big city, things can happen.

Have fun and be safe everybody! Hope to see you all there!


DockerCon 2016 is now over and it was a great success. The VMware CNA team (along with the VMware cloud management, networking and storage teams) was there, and the traffic at the booth was astonishing.

We noticed booth visitors had plenty of questions around container technologies and their relation to virtual machines, especially around some of the technologies we presented at DockerCon–some of which are meant to blur those boundaries.

In this post, we are going to briefly outline our technologies and brands to help people better understand them. This includes:

If you are curious about any of the above technologies (and what they deliver and how they deliver it), please read on.

Before we get into a brief description of each technology, it is important to understand they fall into two completely different categories.

The first model assumes instantiating “docker images as containers in VMs.” This is the Photon bucket.

The second model assumes instantiating “docker images as VMs.” This is the VIC bucket.

The Photon Model

As we alluded to, this model involves a traditional “containers on top of VMs” model. This is Docker business as usual and what pretty much everyone does today: you instantiate a Linux OS, you install Docker on it and you start containers pulling Docker images from a registry.

In this context, we deliver the following Photon components:

Photon OS: in either model, one thing is clear – the container runtime environment should be smaller and more efficient than traditional OS. Our OS partner ecosystem validates this, as just about every major vendor has created a super-slim version of their OS. But, for VMware, because of our infrastructure platform, there was even greater opportunity. Because we were free to focus on the vSphere market, we could make things even smaller and even more efficient. We’ve been able to strip all sorts of legacy modules from the Photon OS kernel and tune buffers, time accounting and compile flags to eliminate redundancies between the container runtime and hypervisor. We’re seeing lots of interest around the concept of this type of runtime improvement, but we’re not done. There’s an entire layer of operational efficiency that we haven’t even begun to tackle. Beyond these focused optimizations, we’re seeing customers try things we never intended, like using Photon to create their container images (there is a Photon OS image in the Docker hub, check it out!). Others are looking at more traditional Linux application architectures running on Photon OS to take advantage of the optimizations there, as well.

Photon Controller: this is the highly efficient, completely distributed, API oriented and easy to maintain control plane that, by leveraging the ESXi hypervisor, can deliver a lean IaaS stack. The work to integrate Virtual SAN and NSX into this compute stack is underway. In addition to providing core IaaS functionalities, Photon Controller also includes cluster management workflows that will allow users to instantiate Swarm, Kubernetes and Swarm clusters. Cormac Hogan and William Lam have good articles on how to set those up. Go check them out!

Photon Platform: this isn’t a technology per se but rather a brand name to identify the container optimized IaaS platform above. Photon Platform is the brand name that includes ESXi and Photon Controller technologies, similar to how vSphere is the brand name that encompasses ESXi and vCenter technologies.

It is important to understand that Photon Platform isn’t a disruptive model when it comes to “Docker thinking.” The industry have been using this model for 3 years now:

  • you get a hypervisor (Photon Machine)
  • you get a hypervisor control plane (Photon Controller)
  • you instantiate a VM as a Docker host (Photon OS)
  • and you eventually run a container inside said Docker host

Container management and orchestration is out of scope for the Photon technologies. As a matter of fact, the very first supported commercial bundle we have launched is Photon Platform with Pivotal Cloud Foundry.

While you could always download Photon Controller today and instantiate your very own standalone Photon Platform IaaS platform, we are exploring additional out-of-the-box integrations with other container management stacks. For example at DockerCon, we demonstrated a docker-machine integration that you can grab here. Using this driver, you can leverage docker-machine to provision Docker hosts on top of the Photon Platform.

The VIC Model

The VIC model is indeed disruptive when it comes to traditional “Docker thinking” but, at the same time, it is intended to be the least disruptive when it comes to traditional data center operations.

Many have made the observation that containers running in Linux are similar in concept to VMs running on a hypervisor. They main difference is that a VM must run an operating system, whereas a container inherits an operating system. This is one of the reasons why containers are fast and efficient – there’s nothing to boot. As such, when you run containers in a VM, the VM hosting the containers is a little like a nested hypervisor.

But what if your nested hypervisor is far less capable than your actual hypervisor? It doesn’t come with clustering, HA, live migration, hardware virtualization security, etc.

VIC brings the container paradigm directly to the hypervisor, allowing you to deploy containers as first-class citizens, bypassing the pre-requisite for Linux VMs. The net result is that containers inherit all of the benefits of VMs, because they are VMs.

With vSphere Integrated Containers, the Docker image, once instantiated, becomes a VM inside vSphere. This solves security as well as operational concerns (we have learned one thing or two in the last 15 years on how to run applications inside VMs in production) at the same time.

But these are NOT traditional VMs that require 2TB and take 2 minutes to boot. These are usually as big as the Docker image itself and take a few seconds to instantiate.  We call them ContainerVMs to underscore they are not traditional VMs. They boot from a minimal ISO which contains a stripped-out Linux kernel (based on Photon OS), and the container images and volumes are attached as disks.

The ContainerVMs are provisioned into a “Virtual Container Host” which is just like a Swarm cluster, but implemented as logical distributed capacity in a vSphere Resource Pool. You don’t need to add or remove physical nodes to increase or decrease the VCH capacity, you simply re-configure its resource limits and let vSphere clustering and DRS handle the details.

The biggest benefit of VIC is that it helps to draw a clear line between the infrastructure provider (IT admin) and the consumer (developer/ops). The consumer wins because they don’t have deal with managing container hosts, patching, configuring, etc. The provider wins because they can leverage the operational model they are already using today (including NSX and VSAN).

Your developers will continue to “docker run busybox” and your (IT admin) will keep managing VMs. The best of both worlds.

This isn’t to say this is the best model. It’s yet another option. If you think using containers as a run-time for your Docker images is the best route to take for your project, then Photon Platform is the best underlying place to run those Docker Hosts (and containers on top of them).

Note: if you have heard of “Project Bonneville” that is <just> the internal name we gave to the research project, started 2+ years ago, that culminated in VIC as we see it today.

The Third Option

What we have discussed so far are the two main models.

Photon Platform is disruptive when it comes to the operational model you have today (assuming you are running vSphere). But on the other hand it is optimized to run containers at scale and so it’s aligned to the “Docker thinking.”

VIC is disruptive when it comes to the “container model” you usually think of when you think of Docker but on the other hand it is optimized for operations. (Or, in other words, you can keep your operations).

A lot of customers are still using a third option (somewhere in between) that is leveraging vSphere. Think of this model (running Docker images on containers on Docker host VMs running on vSphere) as a way to mitigate the disruption: you are running VMs on a very well operationalized infrastructure and you are running Docker images as traditional containers.

This model doesn’t solve the operational burden of running containers in production nor does it solve the need for having a multi-tenancy IaaS platform that is optimized to run containers at scale.

Nevertheless, this could be a great choice for many customers and we are working to integrate vSphere functionalities with Docker technologies (for example: the new Docker Volume Plugin for vSphere).

We see Photon Platform, VIC and vSphere as a continuum of solutions, possibly radically different to cover the spectrum of all customers’ needs and their very different maturity level when it comes to running Dockerized applications in production.


This post was not intended to go deep into the technologies discussed but to give you greater context of the various technologies and brand names we showcased at DockerCon 2016.

We covered two new models (Photon Platform and VIC) that are being developed to purposely address the Docker wave. Additionally, we are positioning vSphere as a viable platform for Dockerized applications that minimize operational disruption.

The picture below may help visualizing (at a high level) how these three stacks compare with each other:

Overview of Running Containers in VMware Environments

Overview of Running Containers in VMware Environments


Kit Colbert, vice president and general manager, Cloud-Native Applications Business Unit

Enterprises are increasingly embracing digital transformation initiatives today with an eye on accelerating their pace of innovation. Next-generation application architectures leveraging Linux containers and microservices are helping to speed up software development efforts. They have changed how enterprises build, run and update their applications.

As enterprises begin their journey from building to deploying their cloud-native applications into production, they encounter the same IT requirements they are all too familiar with–backup, compliance, disaster recovery, monitoring, security and more. Some enterprises are at a crossroads. Do they take a radical rip-and-replace approach? Is it possible to gracefully adopt containers and microservices relying on existing investments? How can they simultaneously support today’s applications and workloads while also investing for the future?

VMware is embracing containers and new models of operating while helping enterprises leverage existing technologies and resources to accelerate their cloud-native journey. Some enterprises are seeking to jumpstart their cloud-native initiatives on top of their current virtual infrastructure. While others seek a cohesive infrastructure stack to solve integration challenges.

Advancing and Expanding Containers-related Projects

This week at DockerCon 2016, VMware will demonstrate its support for Docker containers across compute, networking, storage and management. We have extended our software-defined data center solutions to support Docker to enable IT to easily respond to the cloud-native needs of enterprise developers.

In 2015, we introduced VMware vSphere® Integrated Containers™ and VMware Photon™ Platform to improve the developer experience for building applications using containers while addressing enterprise IT requirements. vSphere Integrated Containers provides IT with an easy on-ramp to containerized and traditional workloads, while Photon Platform promises a new, optimized stack for cloud-native only environments. vSphere Integrated Containers and components of the Photon Platform including the newly available Photon OS 1.0 are downloadable from VMware’s GitHub page.

Solving the challenges of networking and security is a key enabler for production deployments of Docker containers. In a vSphere Integrated Containers environment, enterprises are able to leverage all of the VMware NSX® platform’s rich networking and security features in a Docker environment today. These include per container networking and security services such as micro-segmentation, logical switching and routing and load balancing. Enterprises can also tap NSX’s rich ecosystem of partner integrations to enable advanced services such Next Generation Firewall, IDS/IPS, Advanced Malware Prevention and more. All of the above is available today thanks to the fact that vSphere Integrated Containers instantiate Docker images as virtual machines (as opposed to containers). Additionally, we’ll showcase a cutting-edge demo in our booth (G3) at DockerCon.

Our uniquely capable storage offerings, such as VMware Virtual SAN™, already serve thousands of enterprises running in virtualized environments. With the new Docker Volume Driver for vSphere (available today as a beta release), many of those same key capabilities are natively available to enterprises also running in containerized applications. This is one step on our path to delivering the benefits of our storage platform directly to developers of cloud-native applications.

Thousands of customers rely on VMware vRealize® Automation™ to simplify and accelerate the delivery of integrated multi-tier applications with application-centric networking and security across clouds. At DockerCon 2016, we will introduce Project Bellevue, a technology preview that will enable vRealize Automation to support containers. Project Bellevue capabilities such as modeling containerized applications in vRealize Automation unified service blueprints, provisioning container hosts from the vRealize Automation service catalog and managing container hosts will be demonstrated in the booth.

Foundational Infrastructure to Deploy Cloud-Native Applications with Confidence

In speaking with our customers about their cloud-native efforts, many of them are challenged with how they will move their containerized applications into production. They want to know how best to meet IT requirements across security and isolation, service-level agreements, data persistence, networking services and management. We’re aggressively investing time and resources to deliver a foundational infrastructure that customers can count on to deploy cloud-native applications in production.

VMware is a Gold Sponsor of DockerCon 2016 which runs June 19-21 in the Washington State Convention Center in Seattle. If you are at the show, visit us in booth G3. Additionally, be sure to attend a presentation from Guido Appenzeller, VMware’s Chief Technology Strategy Officer for networking and security, titled “Run Docker Containers. In Production. Today” on Monday, June 20 at 11:45am PT in Room 618.


A year ago, we released AppCatalyst, a desktop hypervisor for developers – as a technology preview. The existing tools at the time were not specifically designed to support developer workflows, and there were many developer use cases where AppCatalyst did much better. The program helped us better understand the use cases and in the process gain valuable insight.

The technology preview for AppCatalyst will end on the 30th of June 2016. While the solution in its current form will not be productized, the learnings from the program will be incorporated into future products and features. We’re constantly evaluating how products are being used and exploring new ways to deliver more value to our customers.

We want to thank you for your participation in the program. If you are already using AppCatalyst and would like to continue using it till the end of 2016, please click here to download the updated version that will expire on the 31st of December 2016. You can also use VMware Fusion to continue running the virtual machines you’ve created with AppCatalyst.