SAP HANA Service Broker Contributed to the Cloud Foundry Incubator
The quintessential story for platform as a service is that the developer needn’t perform a bunch of administrative functions just to start working on their code. Have a look at the installation instructions for the developer-targeted Spring Trader reference implementation for a pre-PaaS deployment experience. In a PaaS, this lengthy guide is replaced with one command each to provision a database and a messaging service, and then another command that deploys each part of the application with bindings to these services.
Service brokers are what make this provisioning and binding happen with ease, and today we are delighted to report that Cloud Foundry partner, SAP, has open sourced a new Cloud Foundry service broker for their SAP HANA database.
The Platform for Building Great Software
Since the formation of Pivotal as an independent company the Cloud Foundry open source ecosystem has progressed from a promising collection of early movers to the dominant pattern for enterprise PaaS.
Tomorrow, to celebrate the GA launch of Pivotal CF, our enterprise PaaS powered by Cloud Foundry, we are sponsoring a broad swath of Internet and print advertising to spread awareness of the project and the change it will bring to how enterprises build and deliver software. The marquee advertisement will be a full page ad in the Wall Street Journal, supported by some of the leading companies in the world.
Announcing Cloud Foundry cf v6
You can find our new Cloud Foundry CLI, written in Go on github.
A complete rewrite, and yes, we changed things
We hadn’t been happy with the Ruby CLI for a while. We had three big problems: it was hard to test drive, it was hard to understand, it was hard to make changes. It was time for a rewrite. We also wanted to stay sensitive to the feedback we had received from the community and incorporate those learnings into the new CLI. This means that the command names changed as did the arguments and output, but retained all the previous functionality for interacting with your cloud and then some.
We decided to aim for a CLI that was easily scriptable so you can use it as part of your deploy scripts.
Improved Java Tooling for Cloud Foundry
Pivotal has released several new components that enable developers using Java, Groovy, and other JVM languages to deploy applications to Cloud Foundry quickly and easily. This blog post will show the options available to JVM developers with this new tooling.
Maven and Gradle are two popular build tools for Java applications. Maven has been around for many years and enjoys widespread use. Gradle is newer but is gaining mindshare and adoption quickly (Gradle is used to build the core Spring projects and is becoming the recommended build tool for Android applications). Pivotal has released Cloud Foundry plugins for Maven and Gradle that allow developers to deploy and manage applications with the same tools used to build the applications.
Essential Elements of an Enterprise PaaS
When I speak with customer prospects about Cloud Foundry, I don’t start with networks, servers, VMs and build my way up a stack of abstractions, instead I ask them how they will change to compete in an industrial era increasingly defined by software. Refactoring their entire mindset away from IT management to becoming a high performance software factory is job-one of any briefing I give.
Enterprise PaaS delivers a next generation platform to answer this challenge. Leaving the legacy of custom VM, middleware and server orchestration behind can sometimes be uncomfortable for traditional IT buyers, but it is captivating to business oriented leaders looking to transform their organizations.
A Pivotal CF Field Success Story: Installation, User-Provided Services, and Live Capacity Updates
I’ve had the privilege of visiting a few of Pivotal’s early access customers to help them install our Pivotal CF™ PaaS solution, which is powered by Cloud Foundry technology. I’d like to share a recent success story and highlight three benefits from Pivotal CF that were very well received.
This customer, like many we are working with, is in the process of planning a next generation application and data analytics platform focused on PaaS as a strategic centerpiece. We were engaged for a three-day proof of concept (POC) engagement, the focus of which was three-fold:
Install Pivotal CF in a newly created VMware vSphere environment.
Push an application which both ingested and consumed data to/from existing Hadoop and Solr environments.
Monitoring Cloud Foundry Applications with New Relic
A couple of weeks ago, Ben Hale blogged about the new Cloud Foundry Java Buildpack, highlighting some great new features and our design principles – the “it just works” experience.
The new buildpack provides the opportunity for a new level of configuration and setup for popular add-on services, such as application performance and monitoring tools. The Java buildpack now includes automated configuration for the New Relic application monitoring agent. If you create a New Relic service and bind it to an application, the buildpack will set up the New Relic agent automatically when the application is staged.
IBM WebSphere Liberty Buildpack Contributed to Cloud Foundry
IBM is contributing the IBM WebSphere Liberty Buildpack today as further proof of its commitment to make the Cloud Foundry open source project and community even stronger.
A guest blog by Rachel Reinitz, an IBM Distinguished Engineer in IBM Software Services
In late July, I wrote a guest blog here about our development of a preview IBM WebSphere Liberty buildpack. I’m delighted to announce we have contributed the WebSphere Liberty Buildpack to the Cloud Foundry community. It now has its own Cloud Foundry GitHub repo, ibm-webphere-liberty-buildpack.
Importance of Buildpacks
Buildpacks can provide a complete runtime environment for a specific class of applications. They are key to providing portability across clouds and contributing to an open cloud architecture.
Combining Voice with Velocity thru the Cloud Foundry Community Advisory Board
Cloud Foundry is taking a unique approach to community that combines inclusiveness and scale with high velocity development. In this post Christopher Ferris, IBM Distinguished Engineer, shares some thoughts on how to bring this approach to life and invites the community to co-invent the Cloud Foundry Community Advisory Board.
A guest post by Christopher Ferris, an IBM Distinguished Engineer and CTO for Cloud Interoperability in IBM Software Group’s Standards and Open Source organization.
I’m really pleased with the steadily growing interest in Cloud Foundry over the past few months.
Introducing the Cloud Foundry Java Buildpack
Buildpacks are at the core of the Cloud Foundry architecture and we’ve recently made significant improvements to the Cloud Foundry Java Buildpack. As the lead developer of the buildpack, I’d like to give you some insight into the design principles behind it, how to use, configure, and extend it, and what the future holds.
The primary objective of the Java buildpack is to be the easiest way to run a Java application.1 The word easiest can mean a lot of things, but to me it means that a developer can push an application and have an “it just works™” experience. An application developer shouldn’t have to mess about with details like memory settings or configuring the container to work with a bound service.