Portability and cross-platform compatibility are the fundamental principles and also key advantages of the Cloud Foundry PaaS. Despite that, until now, its architecture supported a limited number of cloud platforms: OpenStack, AWS, vSphere, vCloud, and Warden. However, thanks to the efforts of the community some new names have been added to the list of available IaaS vendors. At the end of May, Pivotal released its Google Compute Engine CF-BOSH CPI. Developers are currently discussing ways to create a CPI for Microsoft Azure in the BOSH Developers Google group. Finally, the BOSH team have released an experimental version of the external CPI that can serve as a new way for creating CPIs.
In this post, I will share my experience with developing a custom CPI for Cloud Foundry using the standard CPI mechanism. Read on to learn about the issues I have encountered and get some tips on how to address them. (more…)
Up until recently, BOSH has been pretty much the only tool chain for deployment of Cloud Foundry. We love BOSH for its visionary approach towards managing life cycle of clustered systems, flexibility and a distro-agnostic approach to Linux. Yet, it could be quite difficult to deploy BOSH/with BOSH. Yes, despite all its beauty, BOSH has a learning curve, and you certainly need to know its key concepts and internals to be productive. Bottom line, it takes quite a few manual steps to bring all Cloud Foundry components into a single working deployment using BOSH.
To grow the Cloud Foundry community, Altoros, Canonical, and Pivotal joined their efforts to deliver an alternative deployment tool, which would reduce complexity of Cloud Foundry deployment and decrease the number of steps. This solution is based on Juju, a service orchestration tool by Canonical.
PaaS has revolutionized the way applications are developed and deployed. With reduced delivery cycles and full automation, PaaS users can reach the market faster, significantly improving ROI and time-to-revenue. Cloud Foundry is one of the most popular open-source solutions for enterprises.
Until recently, .NET developers—who constitute a large part of software delivery folks—had rather limited access to Cloud Foundry’s services. The Iron Foundry project has corrected this imbalance by providing support for .NET on Cloud Foundry. It is not merely an extension, but an entire collection of tools and services .NET developers are used to working with, e.g. MS SQL and Message Bus-as-a-service. Services can be bound to applications, so you do not have to worry about infrastructure and maintenance.
This post starts a series that will explore the capabilities of Iron Foundry. To show you how this platform works and try its services in action, I am going to create a validation prototype using a mixture of .NET and Node.js. I will rely on the Cloud-First approach in my investigation on how application interaction, management, and deployment are implemented in this platform. By the end of the series, you will have learned everything you need to know about creating .NET apps on Iron Foundry.
HP Moonshot is a new-generaition low-power server built specifically for distributed computing and big data processing. It is perfect for deploying Cloud Foundry, an open source platform for delivering cloud apps. To help you reap all the benefits of Cloud Foundry deployed on top of Moonshot, we have created a 12-page guide with a reference architecture and a tested configuration. It includes detailed instructions on how to install MaaS, assign roles to servers, deploy OpenStack, configure a new environment, set up routing, provide high availability of apps on Cloud Foundry, and much more.
Download your copy to get:
- a tested Moonshot configuration and reference architecture
- a step-by-step guide on installing OpenStack
- instructions on how to configure MaaS and Juju
- a tutorial on creating a highly available Cloud Foundry deployment
Ever wondered how Hadoop distros differ from each other? In a recent article for NetworkWorld, I overview how Hadoop became what it is today and explore the differences between the standard edition vs. Hortonworks, Cloudera, and MapR. I also provided insights into 5 major trends that are shaping their evolution—in terms of features, ecosystem, enterprise adoption, etc.
Read the article to learn about:
- The top 5 trends currently affecting the evolution of Hadoop distributions
- Why enterprises need Hadoop distros and how they differ
- How YARN has solved the issues present in Hadoop 1.0
- What will become of Hadoop in the foreseeable future
Continue to the article at NetworkWorld: “Comparing the Top Hadoop Distributions.”
One of the most interesting presentations at this year’s CF Summit was comparison of Cloud Foundry with other PaaS systems. It was delivered by Michael Maximilien of IBM and James Bayer of Pivotal. The overview featured Microsoft Azure, Google App Engine, AWS Beanstalk, Heroku, OpenShift, and Cloud Foundry. My blog post highlights the main points of this presentation.
The amazing session, “Diego: Re-envisioning the Elastic Runtime,” was one of the highlights at this year’s CF Summit. Onsi Fakhouri, Engineering Manager at Pivotal, shared some technical details on Project Diego, including why it is important for Cloud Foundry developers and how it will evolve in the future.
Diego, a large-scale project on which Pivotal is working right now, will introduce a number of significant changes to the Cloud Foundry architecture. Read on to learn about the reasons for this kind of revision, why we should care about Diego, and what impact it will have on Cloud Foundry and PaaS.
Continuous integration (CI) allows for pushing regular enhancements and bug fixes to your application in an easy, fast, and safe way. When using this practice, every time a developer commits a change, the software has to pass a number of tests. This guarantees that every new release is safe and bug-free. Ultimately, continuous integration can help to automate the entire software delivery process.
Figure 1. Software delivery process based on the continuous integration strategy
In this blog post, I will explain in detail how to set up continuous delivery for your Ruby on Rails application running on the Cloud Foundry PaaS with Jenkins CI, a popular continuous integration tool.
In a recent blog post on how to deploy Helios MBaaS to Cloud Foundry, I promised another tutorial for an alternative mobile back-end powered by Node.js. So, today I will walk you through the steps for installing LoopBack.
Despite the overlap with DockerCon and other events, the Cloud Foundry Summit gathered around 1,000 attendees this year. 60+ speakers had a lot to share and delivered insightful sessions on CF, Docker, microservices, Diego, Go, etc. (See our recaps of Day 1, Day 2, and Day 3 for details and photos.)
In this post, we’ve gathered some of the most interesting remarks by the CF Summit presenters. Please note that the quotes are listed at random and their grouping is very rough!
James Watters (Pivotal) with David Lewis and Swamy Kocherlakota (BNY Mellon)
Open movement / CF mission
- “Open source has become a very effective approach to enable people to come together and build a standard platform.” —Paul Maritz, CEO @ Pivotal