{"id":3272,"date":"2015-06-09T20:00:10","date_gmt":"2015-06-09T17:00:10","guid":{"rendered":"http:\/\/www.altoros.com\/blog\/?p=3272"},"modified":"2018-06-22T14:48:41","modified_gmt":"2018-06-22T11:48:41","slug":"cloud-foundry-diego-and-bosh-an-interview-with-james-watters","status":"publish","type":"post","link":"https:\/\/www.altoros.com\/blog\/cloud-foundry-diego-and-bosh-an-interview-with-james-watters\/","title":{"rendered":"James Watters on How Diego and BOSH Changed Cloud Foundry"},"content":{"rendered":"

\n

\n

Table of Contents<\/p>\nToggle<\/span>

The two biggest milestones for Cloud Foundry<\/a><\/li>
Pivotal CF: business growth<\/a><\/li>
Want details? Watch the video!<\/a><\/li>
About the speaker<\/a><\/li><\/ul><\/nav><\/div>\n
<\/span>The two biggest milestones for Cloud Foundry<\/span><\/h3>\n
In a stimulating conversation led by AppFog’s founder (and current CenturyLink’s executive) Lucas Carlson, James Watters of Pivotal went into detail about Diego, BOSH, Pivotal CF, and Docker.<\/p>\n
These are the big, high-level takeaways:<\/p>\n
- BOSH should be thought of as \u201ca declarative cloud-integrated deployment and life-cycle tool. Declare what you want, (then you) need to simply tell it the scale you want to run at and away it goes.\u201d He did not that the complexity with BOSH comes with creating the deployments, i.e., creating your declarative manifest.<\/li>\n<\/ul>\n
  <\/p>\n
  <\/span>Pivotal CF: business growth<\/span><\/h3>\n
  On the less technical side, James refers to the scale of Pivotal’s resources\u2014number of developers and its sales and marketing force\u2014as well as its recent growth. He mentions \u201cdouble-digit number of deals in China this quarter,\u201d thousands of installs, the number of enterprises adopting Pivotal CF as \u201capproaching 100,\u201d and as many as 250,000 people using Pivotal Web Services.<\/p>\n
  On this latter point, he says \u201cwe want the most number of highly active users,\u201d and that Pivotal merely breaks even on this service \u201cto help us burn in the software.\u201d<\/p>\n
  He also provides a distinction between the foundations for CF and OpenStack, noting that companies may \u201conly call (something) Cloud Foundry if using the core bits that we ship together, unlike OpenStack (in which) you can (go) with only a quarter of the APIs.\u201d<\/p>\n
  He calls Pivotal’s implementation \u201cnot a better Cloud Foundry but a supported enterprise distribution with better management tools.\u201d<\/p>\n
  The undercurrent throughout the entire conversation is the apparent confidence James has in Pivotal’s ability to emerge as a foundational technology provider. And he doesn’t see much hope for a new startup to try to enter the PaaS space, but encourages companies to solve specific, discrete problems within the cloud\/PaaS ecosystem.<\/p>\n
  
  \n
  <\/div>
  Altoros Take<\/div>
  Ahead of the parade?<\/strong><\/p>\n
  From this conversation, it may appear that the major Cloud Foundry players show up at all the same \"usual events.\" One can find that it is not reflective of the enterprise IT world as a whole.<\/p>\n
  The low-level conversations seem to be several steps ahead of an enterprise IT world that is only now grappling seriously with cloud adoption. James himself points out that even the feared public-cloud giant Amazon has reached less than 10% of the market, and on the development front he says he\u2019s not a fan of \"premature optimization.\"<\/p>\n
  One wonders how well this profound, front-edge conversation is understood by mainstream enterprise IT executives, and how long it might be before they are synced up with it.<\/p>\n
  In another session<\/a>, James Watters gives more answers to the questions that are of a particular interest to the executives. In adition, describing real-life use cases of CF adoption<\/a> is still the best way to speak the same language with enterprises.<\/span><\/div><\/div><\/div><\/div><\/div><\/div>\n
  <\/p>\n
  <\/span>Want details? Watch the video!<\/span><\/h3>\n\n\n
  \n
  \nTable of contents<\/strong><\/p>\n
  \n
  How has CF changed over the last four years? (3:18)<\/li>\n
  What is Diego for a developer? (7:53)<\/li>\n
  Can you run Diego on multiple servers out-of-the-box? What is a micro-PaaS? (9:46)<\/li>\n
  What is Pivotal’s current relationship with Docker? (12:04)<\/li>\n
  What are Pivotal Web Services designed for? (15:41)<\/li>\n
  How Pivotal and OSS CF differ? (18:07)<\/li>\n
  What is BOSH and what is it similar to? (21:20)<\/li>\n
  The declarative format used by BOSH (22:46)<\/li>\n
  Can you install Diego without BOSH? (24:19)<\/li>\n
  An overview of the upcoming Diego CPI for BOSH. (26:14)<\/li>\n
  Is geard by Red Hat similar to Diego? (28:24)<\/li>\n
  Where is the biggest growth opportunity for CF? (29:00)<\/li>\n
  Advice to people who want to create PaaS start-ups (31:17)<\/li>\n
  The future of CF and Pivotal (33:37)<\/li>\n<\/ol>\n<\/div>\n
  https:\/\/www.youtube.com\/watch?v=g80ioBe8gSg\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
  <\/div>\n
  <\/span>About the speaker<\/span><\/h3>\n
  \n
  \r\n