November 23, 2015Cloud Foundry Advisory Board Meeting, November 2015
November 12, 2015More Ideas Than Things at Internet of Things Expo
November 16, 2015BNY Mellon’s NEXEN Drives Digital Transformation with CF
October 6, 2015South Korea Adopts Cloud Foundry as Its PaaS
November 19, 2015Cloud Foundry POC: Tips and Concerns for Your Apps
November 11, 2015Cloud Foundry: Infrastructure Options
May 21, 2015Architect’s Guide to Implementing Cloud Foundry
Dec 1, 2014Microservices vs. Monolithic Architectures: The Pros, Cons, and Cloud Foundry Examples
October 15, 2015Golang Internals, Part 6: Bootstrapping and Memory Allocator Initialization
September 16, 2015Cloud Foundry Containers: Warden, Docker, and Garden
August 14, 2015Porting Cloud Foundry to IBM POWER Processors
All parts: Part 1 | Part 2 | Part 3 | Part 4 | Part 5 | Part 6
This post is the continuation of our Golang Internals series. It explores the bootstrapping process, which is key to understanding the Go runtime, in more detail. In this part, we will run through the second portion of the starting sequence, learn how arguments are initialized, what functions are called, etc.
Warden is a container implementation currently used in Cloud Foundry. Docker is another option to easily and efficiently manage containers. That’s why a lot has been made to enable Docker on CF.
Here, I briefly compare Warden and Docker: their implementation, what makes them alike/different, and how they’ll work together in Garden—the new container back-end that will become available in CF v3.
IBM POWER microprocessors are extensively used to run mission-critical workloads for the world’s largest financial companies, but they are little known inside the Cloud Foundry community. IBM and Altoros are working to change that by bringing CF to the POWER8 architecture. This post sheds some light on the current progress and describes the issues that we had to overcome. It also features a short demo of a CF app running on ppc64le architecture.
Part 1 | Part 2
Until recently, all custom BOSH CPIs were forks of the BOSH project. They were hard to maintain and had to be implemented in Ruby. In August 2014, the BOSH team introduced the new external CPI mechanism that has removed these constraints. The second part of our blog series on adding BOSH support to custom clouds will be dedicated to external BOSH CPIs, how they are used, and what it takes to build one.
Lattice is a light-weight, open source tool for clustering containers. Containers in a Lattice cluster are long-running processes or one-time tasks that are scaled and scheduled dynamically. Apps running in containers have to use external services, such as MySQL, RabbitMQ, etc., but if these services are dynamic, you cannot hardcode their IPs to the client.
The solution is to use a service discovery product, such as Consul, a highly available, distributed tool for discovering and configuring services. In this tutorial, I describe how an app running in Lattice can discover a MySQL service with Consul.
When using Cloud Foundry for deploying apps, one might expect that all the test suites will run painlessly and what works in development/testing/staging will work in production. However, what if it won’t? What if it is impossible to replicate those conditions in a non-production environment? Here, remote debugging comes to the rescue.
In this blog post, I provide guidelines on how to remotely debug Ruby and Java applications deployed with Cloud Foundry.
Support for Docker is one of the main advantages of Cloud Foundry Diego, but how far does this compatibility go? Is it possible to push an arbitrary image from the Docker Hub to Diego and, if not, what are the constraints? What’s going to change in the future? Finally, why should anyone want to use Diego with Docker at all?
In this post, I’ll answer all of these questions, as well as show how to customize and push the official Redis image and demonstrate how to turn it into a simple service to be consumed by other apps.
After having attended Day 1 and Day 2 of this year’s CF Summit, we strongly believe: the momentum looks unstoppable for Cloud Foundry. Ten Fortune 500 companies, seven new CF Foundation members, 120 user groups in 40 countries, and it’s just the beginning.
All these people had a lot to share during the event. Their knowledge, wisdom, and humor were invaluable. Read this selection of quotes collected during the two days—some of these words will go down in history.
All recaps: Day 1 | Day 2 | Top 100 Quotes
According to Diego Lapiduz—who presented at CF Summit on Monday—one of his colleagues recently said: “If you take Cloud Foundry from us, we will hurt you.” Quite convincing to hear this from anyone working within US GSA!
Still, every joke has its share of truth. Those who already implemented Cloud Foundry, became its advocates. Keynotes and sessions delivered on the 2nd day proved that once again. Read on to learn what May 12 brought to 1,500 attendees of the summit.
This year, the Cloud Foundry Summit introduced a stronger focus on community diversity and closer collaboration between its ecosystem members. New partnerships, integrations, support for a broader technology stack, etc. Just like a year ago, I recap what was happening this Monday at the Santa Clara Convention Center, which was themed in the cyberpunk style.
Learn why Altoros joined the Cloud Foundry Foundation