Q&A: Junjie Cai
We’re closing in on the opening keynote of Cloud Foundry Summit 2015 (May 11-12 in Santa Clara…you registered already, right?). Continuing our series of Q&As with speakers you’ll see at the Summit is IBM Bluemix runtime architect, Junjie Cai, who’s talk on “10 common errors when pushing applications to Cloud Foundry” is sure to draw a crowd.
Tell us a little bit about yourself and your career history.
I’m currently the architect for the runtime offerings in IBM’s cloud application platform called Bluemix. Previously I worked on several cloud related incubation projects inside IBM including the multi-tenancy tech-preview feature in IBM JDK. Before that I worked on Apache Geronimo and Apache Harmony.
EMC Stages the First Cloud Foundry Dojo
(Earlier this morning, EMC announced the first Cloud Foundry Dojo in Cambridge, Massachusetts. Brian Gallagher, President, Cloud Management Division at EMC, gives us a look inside.)
Having reached the rank of second-degree black belt in ShukoKai Karate, I’m acutely aware that martial arts excellence requires an all-in commitment by students to master strength, flexibility, discipline and harmony across both body and mind. Like any worthwhile training, students benefit greatly from a teacher, a sensei, to impart experience, skill and wisdom. The same holds true in software and application development. Pupils learn from masters and advance to create new innovations through the art of code writing.
Growing CF Foundation – Swapping over the Atlantic
In the last few weeks, we saw a fast adaption and commitment from the Cloud Foundry Open Source Foundation members and just during the Cloud Foundry Platform conference two weeks ago; Swisscom joined the group as the 34th member of the Foundation (Checkout the panel discussion with Piston, Pivotal and Swisscom on stage).
Snapshot from the CF Platform Conference, 6.9.14, San Francisco
Swisscom is the biggest Service Provider of Switzerland, an early adopter of Cloud Technologies and was involved as one of the first few Service Providers in the Cloud Foundry Community in 2013.
Using AWS spot instances to cut the cost of your BOSH deployments
AWS, Google and Azure are in a price war; and seem committed to matching on-demand prices. That is good, but not the whole story.
The under reported price is that of the AWS spot market; which can be up to 10 x cheaper than on-demand prices.
On-demand / month
Spot / month
There are only 2 differences between AWS spot and on-demand instances.
1. Spot instances take longer to start (5 min vs 1 min)
2. Spot instances “fail” more frequently; when spot prices move above your bid price your instance gets terminated.
You might think that ( 2 ) would prevent you from using spot to host “always on” services like Cloud Foundry.
New Performance Testing Tool added to the Cloud Foundry Incubator
At the April Cloud Foundry Advisory Board meeting the Performance Acceptance Test (PAT) project, contributed by IBM, was accepted as a new Cloud Foundry incubator project. The idea behind PAT is that there should be a super easy way to test performance of Cloud Foundry installations so that any intended improvements can be proven, and regressions can be caught before the new code goes live.
High level overview of the PAT tool
PAT was originally created at the start of 2014 when it was noticed that a previous load testing tool project called Stac2 had gone stale, leaving an important gap in the Cloud Foundry CI/CD story that needed filling.
New Fellow Travelers Join the Cloud Foundry Foundation Mission
Pivotal CEO Paul Maritz wrote about Cloud Foundry back in February when we announced our intention to form the non-profit Cloud Foundry Foundation. The Foundation aims to formalize Pivotal’s commitment to the open governance of a new platform that serves businesses in a multi-cloud world, anchored around Cloud Foundry.
I’m delighted with Pivotal’s announcement of the eight new Gold level members who have stated their intention to join the Cloud Foundry Foundation when it launches this Fall. They include Accenture, BNY Mellon, Capgemini, Ericsson, GE, Intel, NTT and Verizon, bringing the total level of Platinum and Gold members to 17.
Software continues to disrupt every aspect of the consumer and enterprise experience.
Packaged and Offline Buildpacks
With the recent addition of the cf create-buildpack and cf update-buildpack commands, we’ve been looking into changes to how the Java Buildpack is deployed on Cloud Foundry. There is a move afoot to remove the buildpacks from the DEAs in favor of using those commands (with an automated initial install to preserve user-experience) and an outcome of this was the need to more easily create ‘packaged’ buildpacks. In the process of delivering these packages we also realized that we could also deliver “offline” buildpacks. To understand why “offline” buildpacks are interesting, it helps to understand why the buildpack is designed to look for dependencies on the Internet in the first place.
Cloud Foundry Eclipse 1.6.0: Spring Boot Support and Self-Signed Certificates
Cloud Foundry Eclipse integrates Cloud Foundry server and application management into Eclipse and Spring Tool Suite (STS). You can push applications to a Cloud Foundry server via drag and drop from the Eclipse Project Explorer much in the same way as deploying to a local tomcat server. Application memory and instances can be scaled easily, and services created and bound to an application through drag and drop. A comprehensive description of the plug-in is available at:
Since 1.5.0, we have been busy making CF Eclipse ready to better support new features in Cloud Foundry public and private servers.
Version 1.6.0 introduces additional enhancements:
Support for Spring Boot applications.
Working with the Cloud Controller API in Ruby: Beyond CFoundry.
Cloud Controller is the primary API through which third parties interact with Runtime; it encapsulates the myriad internal services that take a user from ‘cf push’ to a running application. Both the Pivotal Developer Console (the web application that ships with Pivotal CF and backs console.run.pivotal.io) and the CloudFoundry CLI interact directly with the Cloud Controller API. The two applications were originally written in Ruby and shared a common Ruby code base for talking to Cloud Controller called CFoundry.
CFoundry provides a friendly interface to the Cloud Controller API.
Diego Phase 1: Staging in a multiplatform world
The first phase of Diego’s development has focused on offloading the staging workflow – the task of converting uploaded app bits to compiled droplets ready for running in Cloud Foundry – from the existing DEAs to Diego. From the outset one of Diego’s mandates has been to make it relatively easy to support multiple platforms (e.g. linux + heroku buildpacks/linux + docker/windows) on one Cloud Foundry installation.
This blog post outlines what has emerged out of this first phase of development, and describes Diego’s architecture with an emphasis on how multiplatform support is envisioned to work.
To wrap your head around Diego you need to wrap your head around the components that make Cloud Foundry tick.