Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

The Cloudcast #116: Managed OpenStack and Cloud Foundry

DZone's Guide to

The Cloudcast #116: Managed OpenStack and Cloud Foundry

· Cloud Zone
Free Resource

See how the beta release of Kubernetes on DC/OS 1.10 delivers the most robust platform for building & operating data-intensive, containerized apps. Register now for tech preview.

The Cloudcast #116 - Managed OpenStack and Cloud Foundry (20:12)

Download the MP3

Date: November 5, 2013

By: Aaron Delp and Brian Gracely

Description: Aaron and Kenneth Hui (@hui_kenneth) speak with Blue Box Founder/CEO Jesse Proudman (@blueboxjesse) about OpenStack deployment issues, managed OpenStack offerings, and Cloud Foundry on top of OpenStack


Topic 1 - Blue Box Group has been around for a while (2003). How did you evolve to be focused on OpenStack and Cloud Foundry?

Topic 2 - Bluebox is a Cloud and Hosting provider, but you provide a set of operations/deployment tools on top of OpenStack. Is a place for providers to differentiate their services, or are they required to fill gaps in OpenStack functionality?

Topic 3 - Recently you’ve been vocal (via your blog) about the role of OpenStack and whether it makes sense for OpenStack to move up the stack into PaaS . Talk about your thinking in this space

Topic 4 - Where do you see the PaaS market vs the IaaS market today and how do you expect that to change in the next couple years? Do you expect to see defined lines or a blurring over time?

Topic 5 - As a Cloud provider, do you see OpenStack’s “openness” as a good thing for your business (customers can come and go), or a competitive threat because of the scale of certain providers?

New Mesosphere DC/OS 1.10: Production-proven reliability, security & scalability for fast-data, modern apps. Register now for a live demo.

Topics:

Published at DZone with permission of Brian Gracely, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}