Authored by Ryan Kelly, Staff Systems Engineer, Cloud Management

We are just weeks away from VMworld’s 2016 Europe Conference in beautiful Barcelona Spain. This year will be my 5th year attending the Europe conference in Barcelona and I have learned a few things I want to share with all of you. I have actually been lucky enough to attend 3 VMworld’s in Europe, one in Nice, France and 2 in Copenhagen. I enjoyed them all as they are all special places to visit but there is just something about Barcelona that keeps me signing up to go year after year. Here are my tips and tricks to get the most out of your conference and visit. If this is your first time or 5th time I am sure there is something in here for everyone.

Before you go:

  • Register for the event, sounds obvious but some folks arrive and are not registered and the per-registration saves you money.
  • 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.)
  • Make a photo copy of your Passport or documentation and store it in a bag or separate from your passport, in the rare case your passport is stolen you will have a back up.
  • Logon to twitter to see what sessions are trending so you know before you go.
  • Weather in Barcelona can vary this time of year, pack some summer clothes, cotton t-shirts, shorts and a Swimsuit but also pack a rain coat and a sweater or sweat shirts as it can get cold at night or in the mountains if you plan to do some site seeing.
  • Pack extra room in your bag or bring an extra one, you will receive a VMworld bag and you get tons of goodies from VMware and partners in solutions exchange that you will want to bring home for your office mates and family.

Travel Tips:

  • Go to sleep now until the morning you travel to VMworld Europe, no seriously you are gonna need all the sleep you can get!
  • For Hotels you have a couple options depending on your preference or if traveling with family:
  • Be sure your credit card or bank card has a chip and that you know the pin number. Most everywhere in Barcelona requires the chip and the pin. This is common now in most countries but just a reminder.
  • Call your cell phone provider and verify you will have roaming service in Barcelona Spain. You can also buy SIM cards for your phone but you won’t be able to use your phone number for calls.
  • There are taxis at the Airport, some take credit cards and some only cash, be sure to ask first. Also be sure to have a print out of your hotel name and address, there are many similar hotel names in Barcelona but they are not close together. (NOTE: Most taxis in Barcelona prefer cash and will let you know)
  • Sign up for the Hailo App to request and pay for rides from your mobile device. I found this service hit and miss but it worked most of the time.

During the Convention:

  • Use Wifi when ever possible, most hotels have free WiFi and VMworld will also have free Wifi, this will save you a bundle on roaming fees. Also  you may want to disable data roaming on your phone for extra savings.
  • Wear comfortable shoes (Europeans know this already), you walk a lot in and around the city, also many hotels are walking distance but the convention center alone is huge and you will walk a lot.
  • Attend the keynotes, you get all the good information first and the opening visuals are always sexy and stunning. At least attend the Technical Keynote if there is only one you plan to attend!
  • Drink a lot of water, it is very hot and humid in Barcelona 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

Tues, 18 Oct 17.30 – 19.30 #VMworld Welcome Reception Gran Fira, Solutions Exchange Open to all attendees Official kickoff to VMworld 2016 Europe. Enjoy appetizers & drinks in the Solutions Exchange. Network with exhibitors & attendees.
Wed, 19 Oct 17.00 – 19.00 #VMworld Hall Crawl Gran Fira, Solutions Exchange Open to all attendees Enjoy networking with appetizers & drinks in the Solutions Exchange where you can see the latest products and services from exhibitors.
Wed, 19 Oct 19.00 – 22.00 #VMworld Party Gran Fira Open to full conference attendees VMworld 2016 Europe Party! Relax w/ excellent food, music and entertainment. Guest passes available.

Food and sight seeing recommends:

  • Lunch or Dinner on the water at Restaurant Barceloneta
  • Late night Pizza Wine and Beer and occasionally open for lunch Amazing! Pizza del Sortidor
  • Dinner at Calpep – No reservations but if you get in line by 7:30PM or 14:30 you will be in the first seating group. Otherwise order a bottle of wine and enjoy in line while you wait for a seat.
  • Dinner at Tapas 24 – No reservations so get here early for the first seating or a short wait but well worth it.
  • Ride on the Montjuic Cable car. Ride up to Montjuic Castle in a sightseeing gondola.
  • Day trip trip to Montserrat a mountain Monastery

Do’s and Dont’s:

  • Do not keep your wallet or valuables in your back pocket, pick pockets are active in the city and on public transit.
  • 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 or your hotel if it is provided, save some hits on your expense report for dinners and drinks later.
  • Do not leave your laptop or personal belongings unattended or out of your control, while the conference is secure you never know who will walk away with your stuff.
  • Do not trust taxi drivers that don’t take credit cards and want to take you to an ATM machine to get money, it is almost always a scam to copy your card, when in doubt call the police.
  • Do use common sense especially late at night, in my experience Barcelona is very safe but it is a big city like anywhere else in the world and stuff happens.

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


Authored by Ryan Kelly, Staff Systems Engineer, Cloud Management

In this guide I will walk you through a simple setup of Admiral using Photon OS as the container host. Admiral™ is a highly scalable and very lightweight Container Management platform for deploying and managing container based applications. It is designed to have a small footprint and boot extremely quickly. Admiral™ is intended to provide automated deployment and lifecycle management of containers.

Key Features:

  • Rule-based resource management – Setup your deployment preferences to let Admiral™ manage container placement.
  • Live state updates – Provides a live view of your system.
  • Efficient multi-container template management – Enables logical multi-container application deployments.


  • One Photon OS VM to install Admiral Container Service
  • Two Photon OS VM’s with Docker Remote API enabled to use as Container Hosts : See my Guide here
  • Internet Access from all the above Photon OS VM’s
  • A quiet place where you will not be interrupted. See my guide here.

Login to one of your Photon OS VM’s and type the following and press enter

docker run -d -p 8282:8282 --name admiral vmware/admiral

After a few minutes you should see the following:

Open a browser to the ip address of your Photon OS and port 8282 http://ipaddress:8282 then click on add host

Enter the IP and host name of one of your other Photon OS VM’s

Note: The Photon OS host you’re adding needs the Docker Remote API enabled, see my guide here.

Next, click login credentials, New Credentials and enter the following information

Next, select the default-resource-pool

Now click verify to make sure it connected correctly

Now click Add

You should now see this screen with your new host, now click on Templates

In the search box enter vmtocloud and press enter, then click to provision the vmtocloud/myblog template

Watch the progress screen on the right, after several minutes it should show finished. Now clock the Containers tab.

Notice that all the templates are being pulled from Docker Hub. In a later post I will show you how to use VMware Harbor Registry locally.

Click the My Blog Container

Notice all the information you get about the running container. Now click the second port link to go to the WordPress Site

Notice you now have a container running WordPress

Now let’s add a second host. Back in the container service screen click on the hosts tab

Now click add host

Enter the same information as before and click verify

Remember the Photon Host needs to have Docker Remote API enabled of the verify will fail with a connection error. See my guide here.

Now click add

You should now see two hosts available for Container provisioning

You should now be well on your way to using Admiral, see the user guide here to explore more features.


Authored by Ryan Kelly, Staff Systems Engineer, Cloud Management

So you want to connect to the Docker instance on Photon OS remotly from another Docker client? In this guide I will walk you through a few short steps to configure Photon OS to enable the remote docker API. NOTE: This is not considered the secure method. If you want to use encryption and secure connections I will have a follow up post on that soon.

Login to your Photon OS using SSH or open the console and type the following and press enter

systemctl stop docker
vi /etc/default/docker

Press i on the keyboard then enter the following, when done press the ESC key then hold Shift and press the Z key twice

DOCKER_OPTS="-H tcp:// -H unix:///var/run/docker.sock"

Since Photon OS uses IP tables we need to open that port, type the following and press enter

iptables -A INPUT -p tcp --dport 2375 -j ACCEPT

Now start docker with the following command and press enter

systemctl start docker

To test that it worked, open a web browser to the Photon OS at http://ipaddress:2375/info and you should see the following.



Authored by Ryan Kelly, Staff Systems Engineer, Cloud Management

We are back from another successful VMworld and a lot of folks are asking for the slides from this session. While the official slides are being posted on, I want to follow up with a blog post on this for anyone that was unable to attend in person. As you may or may not know, VMware recently announced Photon Platform. In my initial conversations with customers, I came to the conclusion that there is some confusion between vSphere and what Photon Platform is designed for. That was the basis for my session at VMworld this year.

So, what is Photon Platform?

Purpose built, multi-tenant, scale-out infrastructure for running containers on proven VMware technology you can trust!

A closer look under the covers.

Photon Controller is the scheduler and control plane that provides the constructs to combine ESXi, vSAN and NSX into a container cloud.

Ok, but how difficult is it to install?

Easy as..One



Your just a clicks away from access to industry standard API and command line

Photon Platform has Role based access focused on ensuring the Developer retains their preferred tools and workflows.

What are the use cases for Photon Platform?

But we already have vSphere?

As stated, Photon Platform has a heavy focus on containers, that’s not to say that it’s your only option, if you are already running vSphere you have a huge head start to containers. The question we get a lot is..

Also, containers as a service with vRealize Automation

So which one do I choose?

vSphere Integrated Containers:

  • Already invested in and standardized around vSphere
  • You need a quick and easy solution for your developers today
  • Plans to run containers in production
  • Requirement for Policy, governance and metered self service – vRealize Automation
  • Lack of resources or commitment to adopt/learn/train on a new technology

Photon Platform:

  • Lower cost IaaS layer for Pivitol Cloud Foundry – PCF – Photon Bundle!
  • Very mature agile development processes in place that needs to scale beyond vSphere Maximums > 35,000 VM’s
  • Currently or planning to build large distributed micro service architectures.
  • Alternative to other programmable infrastructure stacks
  • Large scale high churn environments (Spin up, tear down thousands of servers/containers per day.

Sometime both:

  • Already using containers on vSphere and need to deploy at a larger scale and faster pace
  • Old hardware laying around and you want to give developers a sandbox environment to relieve some of the resources on vSphere environment
  • Internal mandate to move off of Public Cloud Service
  • Innovation projects:
    • New Mobile App Development
    • Life Science research projects
    • Application Re-Architecture Projects
    • Internet of things projects
    • Distributed computing


Authored by Ryan Kelly, Staff Systems Engineer, Cloud Management

The 1.0 release of Photon Controller is now available on GitHub. Along with some bug fixes In this major release we see a sexy new UI. Photon Platform development is moving fast and this milestone just goes to show the commitment VMware has to deliver this new Container technology to the world.

Photon Controller is the foundation for Photon Platform. It provides a multi-tenant infrastructure for running your favorite cloud native frameworks.

If your not already familiar with Photon Controller packaging it is deployed as part of a downloadable OVA.

Once the OVA is deployed you run through the wizard based install, no changes in the install UI from previous beta, hey if it ain’t broke don’t fix it!

Once deployed you can go to the URL of the Photon Controller Manager and we see a sleek and responsive new UI.

Notice the navigation is now on top.

A look at the tenants view and we can see that the UI is cleaner, more intuative and easier overall to navigate.

Also in the tenant view it is much easier to launch a new VM.

A look at the Image view.

The Flavors view.


Overall I really admire the design and goals of this project, elegantly simple with a laser focus on solving a particular use case. The development and product teams remind me of the early days of vSphere. Looking forward to getting more time with this version and publishing more articles as I get more familiar with some of the use cases.


Authored by Eamon Ryan, Staff Solutions Architect

I wanted to be sure to get my first post out early to promote the session I am co-presenting at VMworld US 2016 this year in Las Vegas – the session details are:

Pivotal and VMware: The Lowdown on the High Up – CNA7806
Thursday, Sep 01, 12:00 p.m. – 1:00 p.m.

You ask, “What have you done for me lately?”
Last year a number of integrations between Pivotal and VMware were showcased, but what indeed have we done for you lately? New products and advancements from VMware, Pivotal, and EMC have brought opportunities for fantastic joint solutions and use cases to be developed, growing capabilities beyond what was possible before, bringing enhanced speed, agility, and simplicity to developers and operations users alike, with unified governance and management.

I will be co-presenting alongside Alka Gupta – Senior Global Technical Alliance Manager at VMware, so come on by and learn about all the ins and outs of what Pivotal and VMware are doing jointly lately!

Learning outcomes:
• The 10,000-foot view of Pivotal and VMware as it stands today
• Pivotal Cloud Foundry and VMware Photon Platform (software bundle and native hybrid cloud)
• Pivotal Cloud Foundry and VMware NSX, vSAN, VMware vRealize Operations, vRealize Automation, and vRealize Code Stream
• Pivotal Cloud Foundry use cases for federation enterprise hybrid cloud
• How you can benefit and where your environment best fits in
• Real-world customer case studies showcasing the learnings and business advantages experienced along the way.

For more deep-dive sessions on specifics, check these two other sessions out:

Éamon Ryan




Introducing the Bigger and Better vSphere Integrated Containers

Last year at VMworld, we announced vSphere Integrated Containers, which allows you to deeply embed a container runtime into vSphere. It enables vSphere admins to provision a container images as a virtual machine, allowing them to extend all the enterprise capabilities of vSphere along with the plugins and products from our partners to work seamlessly with containers.

vSphere Integrated Containers was initially built using Project Bonneville and we used that early prototype to gather feedback from our customers through various early access programs. The learnings from these programs led us to a) update the product architecture to support a broader set of functionality and b) extend the vSphere Integrated Containers feature set by adding an enterprise container registry and a container management portal.

The new architecture for vSphere Integrated Containers is as follows:


vSphere Integrated Containers is now comprised of three main components, all of which are available as open source on github (links below):

The vSphere Integrated Containers Engine is a container runtime for vSphere, allowing developers familiar with Docker to develop in containers and deploy them alongside traditional VM-based workloads on vSphere clusters. These workloads can be managed through the vSphere UI in a way familiar to existing vSphere admins.

Harbor, the enterprise container registry, is an enterprise-class registry server that stores and distributes container images. Harbor extends the open source project Docker Distribution by adding the functionalities usually required by an enterprise, such as security, identity and management.

Admiral, the container management portal, provides a UI for developers and app teams to provision and manage containers, including retrieving stats and info about container instances. Cloud administrators will be able to manage container hosts and apply governance to its usage, including capacity quotas and approval workflows. When integrated with vRealize Automation, more advanced capabilities become available, such as deployment blueprints and enterprise-grade Containers-as-a-Service.

With these three capabilities, vSphere Integrated Containers will enable VMware customers to deliver a production-ready container solution to their developers and app teams. By leveraging their existing SDDC, customers will be able to run container-based applications alongside existing virtual machine based workloads in production without having to build out a separate, specialized container infrastructure stack. As an added benefit for customers and partners, vSphere Integrated Containers is modular. So, if your organization already has a container registry in production, you can use that registry with the other components of vSphere Integrated Containers.

We’re really excited about helping customers move containerized applications into production with vSphere Integrated Containers.  If you haven’t already, please check it out and sign up for the beta.  vSphere Integrated Containers is bigger and better than ever! Connect with us @cloudnativeapps on twitter!


Authored by Ryan Kelly, Staff Systems Engineer, Cloud Management

This year VMworld is back in Vegas and it is bigger than ever. While it is going to be a blast to be in Vegas there is a lot more to get excited about. As an employee I can’t register for sessions so that you all have first dibs. I can still attend if there is room. In no particular order here are my top 10 sessions that I want to attend. Notice they are not my own sessions.

If you are interested in any of my sessions here they are:



Authored by Randy Carson, Senior Systems Engineer

vic   PP

Check out  Cloud-Native Applications Hands of Labs that will be released at VMworld 2016, both are listed under HOL-1730.  If you are not attending VMworld, these labs will be available shortly after.  How is VMware offering container focused solutions?  Check them out.  USE-1 is all about VIC (vSphere Integrated Containers). See how easy it is to deploy container VMs in your current VMware infrastructure through the same Docker APIs.  Yes, in VIC we deploy docker images as tiny VMs. Why? Because you can use new developer friendly docker interfaces to manage applications while, at the same time, leveraging your enterprise class infrastructure.  Quickly enable your developers to start creating a container based application.   USE-2 is all about Photon Controller.  Want to create a micoservices based application?  Photon Controller is optimized for pure cloud-native application deployment.  Easily setup different clusters for your developers to run Kubernetes, Mesos, and Docker Swarm each in their own cluster but on the same vSphere hosts.   So come be a geek, bang at the CLI, build a NGINX application and learn how VMware can deliver the environment the developers are asking for.


Authored by Cormac Hogan, Senior Staff Engineer, Storage Product Marketing

PHOTON_square140As many regular reader will be aware, I’ve been spending a lot of time recently on VMware’s Cloud Native App solutions. This is due to an internal program available to VMware employees called a Take-3. A Take-3 is where employees can take 3 months out of their current role and try a new challenge in another part of the company. Once we launched VSAN 6.2 earlier this year, I thought this would be an opportune time to try something different. Thanks to the support from the management teams in both my Storage and Availability BU (SABU) and the Cloud Native Apps BU (CNABU),  I started my Take-3 at the beginning of May. This is when my CNA articles on VIC (vSphere Integrated Containers) and Photon Controller first started to appear. Only recently I was asked an interesting question – when would I use VIC and when would I use Photon Controller? That is a good question, as both products enable customer to use containers on VMware products and solutions. So let me see if I can provide some guidance, as I asked the same question from some of the guiding lights in the CNABU.

When to use VIC?

Lets talk about VIC first, and why customer might like to deploy container workloads on VIC rather than something like “container in a VM”. Just to recap, VIC allows customers to run “container as a VM” in the vSphere infrastructure, rather than “container in a VM”. It can be deployed directly to a standalone ESXi host, or it can be deployed to vCenter Server. This has some advantages over the “container in a VM” approach.

Reason 1 – Efficiency

Consider an example where you have a VM which runs a docker daemon and launches lots of containers. Customers will now connect to these containers via docker client. Assume that over a period of time, this VM uses up a significant mount (if not all) of its memory for containers and eventually these containers are shutdown. This does not allow the memory consumed by the VM on behalf of the containers go back into a shared pool of memory (on the hypervisor where the VM is run) for other uses. With VIC, since we are deploying containers as VMs and using ESXi/hypervisor memory resource management, we do not have this issue. To think of this another way:- containers are potentially short-lived, whereas the “container host” is long-lived, and as such can end up making very inefficient use of system resources from the perspective of the global pool.

Now there is a big caveat to this, and it is the question of container packing and life-cycle management. If the container host VMs are well-packed with containers, and you also have control over the life-cycle of the container host, then it can still be efficient. If however there is no way to predict container packing on the container host and if over-provisioning is the result, and you also have no control over the life-cycle of the container host, then you typically don’t get very good resource efficiency.

Reason 2 – Muti-tenancy

There is no multi-tenancy in Docker. Therefore if 50 developers all requested a “container” development environment, a vSphere admin would have to deploy 50 Virtual Machines, one per developer. With VIC, we have the concept of a VCH (Virtual Container Host) which controls access to a pool of vSphere resources. A VCH is designed to be single-tenant, just like a Docker endpoint. Both present you with a per-tenant container namespace. However, with VIC, one can create very many VCHs, each with their own pool of resources. These VCH (resource pools), whether built on a single ESX host or vCenter Server, can be assigned to individual developers.

One could consider now that the vSphere admin is doing CAAS – Containers as a Service.

The 50 developers example is as much about efficiency as it is about tenancy – the fact that you can only have one tenant per container host VM will force you down a path of creating a large silo composed of 50 container host VMs. In the case where we’re comparing ESXi with Linux on the same piece of hardware to run container workloads, ESXi has a big advantage in that you can install as many VCHs as you like.

Reason 3 – Reducing friction between vSphere/Infra Admin and developer

On the main goals of VIC was basically not to have the developer worry about networking and security infrastructure with containers. This particular reason is more about how VIC informs and clarifies the boundaries between the vSphere admin and the developer. To put it simply, a container host VM is like a mini-hypervisor. Give that to a developer and they’re then on the hook for patching, network virtualization, storage virtualization, packing etc. within the container host. The container host is then also a “black box” to the infra folks which can lead to mistakes being made. E.g. “Only certain workloads are allowed on this secure network”. The secure network is configured at the VM level. If the VM is a container host, its hard to control or audit the containers that are coming up and down in that VM and which have access to that secure network.

VIC removes any infra concerns from the consumer of a VCH and allows for much more fine-grained control over access to resources. With VIC, each container gets its very own vNIC.A vSphere admin can also monitor resources that are being consumed on a per container basis.

There is one other major differentiator here with regards to the separation of administrator and developer roles which relates to compliance and auditing tools, and a whole list of process and procedures they have to follow as they run their data center. Without VIC developers end up handing over large VMs that are essentially black boxes of “stuff happening” to the infra team. This may include the like of overlay networks between those “black boxes”. It’s likely that most of the existing tools that the infra team use for compliance, auditing, etc will not work.

With VIC there is a cleaner line of demarcation. Since all the containers are run as VMs. and the vSphere admin already has tools setup to take care of true operationalizing of VMs, then they inherit this capability with containers.

Reason 4 – Clustering

Up until very recently, Docker Swarm has been very primitive when compared to vSphere HA and DRS clustering techniques as the Docker Swarm placement algorithm was simply using round-robin. I’ll qualify this by saying that Docker just announced a new Swarm mechanism that uses Raft consensus rather than round-robin at DockerCon ’16. However, there is still no consideration given to resource utilization when doing container placement. VCH, through DRS, has intelligent clustering built-in by its very nature. There are also significant considerations in this area when it comes to rolling upgrades/maintenance mode, etc.

Reason  5 – May not be limited to Linux

Since VIC virtualizes at the hardware layer, any x86 compatible operating system is, in theory, eligible for the VIC container treatment, meaning that it’s not limited to Linux. This has yet to be confirmed however, and we will know more closer to GA.

Reason 6 — Manage both VM based apps and CNA apps in the same infra

This is probably the reason that resonates with folks who are already managing vSphere environments. What do you do when a developer asks you to manage this new, container based app? Do you stand up a new silo just to do this? With VIC, you do not need to. Now you can manage both VMs and containers via the same “single pane of glass”.

When to use Photon Controller?

Let’s now talk about when you might use Photon Controller. Photon Controller allows you to pool a bunch of ESXi hosts and use them for the deployment of VMs with the sole purpose of running containers.

Reason 1 – No vCenter Server

This is probably the primary reason. If your proposed “container” deployment will not include the management of VMs but is only focused on managing containers, then you do not need a vCenter Server. Photon Controller does not need a vCenter Server, only ESXi hosts.  And when we position a VMware container solution on “greenfield” sites, we shouldn’t have to be introducing an additional management framework on top of ESXi such as vCenter. The Photon Controller UI will provide the necessary views into this “container” only environment, albeit containers that run on virtual machines.

Reason 2 – ESXi

ESXi is a world-renowned, reliable, best-in-class hypervisor, with a proven track record. If you want to deploy containers in production, and wish to run them in virtual machines, isn’t ESXi the best choice for such as hypervisor? We hear from many developers that they already use the “free” version of ESXi for developing container applications as it allows them to run various container machines/VMs of differing flavours. Plus it also allows them to run different frameworks (Swarm, Kubernetes, Mesos). It would seem to make sense to have a way to manage and consume our flagship hypervisor product for containers at scale.

Reason 3 – Scale

This brings us nicely to our next reason. Photon Controller is not limited by vSphere constructs, such as cluster (which is currently limited to 64 ESXi hosts). There are no such artificial limits with Photon Controller, and you can have as many ESXi hosts as you like providing resources for your container workloads. We are talking about 100s to 1000s of ESXi hosts here.

Reason 4 – Multi-tenancy Resource Management

For those of you familiar with vCloud Director, Photon Controller has some similar constructs for handling multi-tenancy. We have the concept of tenants, and within tenants there is the concept of resource tickets and projects. This facilitates multi-tenancy for containers, and allows resources to be allocated on a per tenant basis, and then on a per-project basis for each tenant. There is also the concept of flavors, for both compute and disk, where resources allocation and sizing of containers can be managed.

Reason 5 – Quick start with cluster/orchestration frameworks

As many of my blog posts on Photon Controller has shown, you can very quickly stand up frameworks such as Kubernetes, Docker Swarm and Mesos using the Photon Controller construct of “Cluster”. This will allow you to get started very quickly on container based projects. On the flip side, if you are more interested in deploying these frameworks using traditional methods such as “docker-machine” or “kube-up”, these are also supported. Either way, deploying these frameworks is very straight forward and quick.


I hope this clarifies the difference between the VIC and Photon Controller projects that VMware is undertaking. There are of course other projects on-going, such as Photon OS. It seems that understanding the difference between VIC and Photon Controller is not quite intuitive, so hopefully this post helps to clarify this in a few ways. One thing that I do want to highlight is that Photon Controller is not a replacement for vCenter Server. It does not have all of the features or services that we associate with vCenter Server, e.g. SRM for DR, VDP for backup, etc.

Many thanks to Ben Corrie and Mike Hall of the VMware CNABU for taking some time out and providing me with some of their thoughts and ideas on the main differentiators between the two products.