Over a million developers have joined DZone.

The Cloudcast #159 - Panamax - Docker Simplified

DZone 's Guide to

The Cloudcast #159 - Panamax - Docker Simplified

· Cloud Zone ·
Free Resource

Download the MP3

Date: August 22, 2014

By: Aaron Delp and Brian Gracely

Description: Aaron & Brian talk with Lucas Carlson (@cardmagic, Chief Innovation Officer at CenturyLink Labs) and Jonas Rosland (@virtualswede, OCTO at EMC) about the recently released Panamax system to manage Apps, Docker, Fleet and CoreOS. They discuss application templates and how Panamax is working with Mesos, Kubernetes and the Docker ecosystem. Music Credits: Nine Inch Nails (www.nin.com)

Topic 1 - Lucas, what’s in the water over at CenturyLink? First a PaaS offering, then a Docker offering, and today a big Hybrid Cloud launch. How does a big ISP/MSP deliver all this next-gen stuff?

Topic 2 - Let’s talk about Panamax. I like the description - “Docker requires you to learn tons of stuff - Panamax makes all of that simple.” Was that the original plan, and how did the service evolve to this point?

Topic 3 - Jonas, you were part of the beta. What was your experience, especially when questions came up - how is the community interaction?
Topic 4 - Let’s dive into what Panamax delivers. Very cool GUI to create, drag & drop things together to build apps. Is everything driven through the GUI (to keep it simple), or does the GUI mimic what is available via the APIs? Does it include capabilities to deploy across clouds?

Topic 5
- Panamax is still new, but what are you seeing in terms of common usages, and how far do you think it can be pushed at this point?

Topic 6 - What was the thinking of having a Panamax store for publishing apps vs. just using Docker Hub?

Topic 7 - How do you get a project like Panamax kicked off at CenturyLink, where it supports both open-source and native deployability to other clouds?

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}