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.
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.
The very first Cloud Foundry conference (PlatformCF) gathered 450+ people in 2013. The year after, this number was already around 1,000. It is expected that the forthcoming CF Summit’15 will get 1,500 attendees. It’s awesome to watch the community grow so quickly! Let’s recall what it was like last year:
As a Gold sponsor of the CF Summit and a speaker, we have a limited number of free passes to give away. Willing to get one? Write back to us and we’ll see if we can help you to attend the summit for free.
Join our sessions on BOSH, Lattice, Docker, and CF metrics
We are happy to sponsor live streaming from the Cloud Foundry & Docker meetup in beautiful San Ramon, California! Tune in, or check out the agenda:
Talk #1: 6:45–7:30 PM Riak and RiakCS on Cloud Foundry
Speaker: Randy Secrist, Director of Professional Services at Basho Technologies
• Introduction to Riak, a distributed Key Value database.
• Introduction to Riak CS, a distributed S3 large object store.
The Cloud Foundry PaaS was designed to provide cross-cloud portability and compatibility. BOSH is the official orchestration and deployment tool for CF that makes these features possible. Currently, there is a set of cloud platforms that are able to work with BOSH, but it can be extended to work with clouds that are not on this list.
In this blog series, we’ll go through all the steps necessary to add BOSH support for a new cloud: from CPI implementation to generating a stemcell.
If you think that implementing integration tests for Juju Charms—Canonical’s orchestration solution—is a trivial task, you’ll be surprised it’s not. Last month, I was involved in testing a collection of 30 mature charms and summarized my experience in recommendations on how to solve the challenges that arise.
In this blog post, I’m sharing my findings: the workflow for Juju Charms integration tests, the tools used, and 7 tips for accelerating these tests.
All parts: Part 1 | Part 2 | Part 3 | Part 4 | Part 5
The bootstrapping process is the key to understanding how the Go runtime works. Learning it is essential, if you want to move forward with Go. So the fifth installment in our Golang Internals series is dedicated to the Go runtime and, specifically, the Go bootstrap process. This time you will learn about:
- Go bootstrapping
- resizable stacks implementation
- internal TLS implementation
Note that this post contains a lot of assembler code and you will need at least some basic knowledge of it to proceed (here is a quick guide to Go’s assembler). So let’s get going!
Today, we’ll take a closer look at the Func structure and discuss a few details on how garbage collection works in Go.
This post is a continuation of “Golang Internals, Part 3: The Linker and Go Object Files” and uses the same sample program. So, if you haven’t read it, I strongly advise that you do this before moving forward.
Today, I will speak about the Go linker, Go object files, and relocations.
Why should we care about these things? Well, if you want to learn the internals of any large project, the first thing you need to do is split it into components or modules. Second, you need to understand what interface these modules provide to each other. In Go, these high-level modules are the compiler, linker, and runtime. The interface that the compiler provides and the linker consumes is an object file and that’s where we will start our investigation today.