Big Data:
Cloudera: Capacity Planning with Big Data and Cloudera Manager
Capacity planning has long been a critical component of successful implementations for production systems. Today, Big Data calls for a particularly deep understanding of capacity management – because resource utilization explodes as business users, analysts, and data scientists jump onboard to analyze and use newly found data. The resource impact can escalate very quickly, causing poor loading and or response times. The result is throwing more hardware at the issue without any understanding of what impact the new hardware will have on the current issue. Better yet, be proactive and know about the problem before the problem even occurs! Read more.

Datadog: Understand how code changes impact system performance with Bitbucket and Datadog
Have you ever had a bad code commit deployed that caused performance issues on a live system? How long did it take to track down the source of the issue? Determining whether a code change is at the root of a performance problem can be a time-consuming task at the worst of moments. Read more.

DevOps:
Datadog: Monitor Docker with Datadog
Docker is an emerging platform to build and deploy software using lightweight, pared-down virtual machines known as containers. By delivering easy-to-provision recipes for developers and bit-for-bit compatibility between environments, Docker is a popular solution to solve continuous delivery in modern infrastructure. Like virtual machines before them, containers require a new monitoring approach. Luckily, if you are a Datadog user, you can now take advantage of our newest integration. Read more.

Datadog: Docker-ize Datadog with agent containers
Many of you who are using Docker are embracing the Docker way and taking a container-only approach. As we release our new Docker integration, we don’t want to force you to break from a container-only strategy because of the traditional Datadog agent architecture. Instead, we’ve also embraced the Docker way and we’re pleased to announce a Docker-ized Datadog agent deployed in a container. Read more.

Docker: It's here: Docker 1.0
On March 20, 2013, we released the first version of Docker. After 15 months, 8,741 commits from more than 460 contributors, 2.75 million downloads, over 14,000 “Dockerized” apps, and feedback from 10s of 1000s of users about their experience with Docker, from a single container on a laptop to 1000s in production in the cloud … we’re excited to announce that it’s here: Docker 1.0. Read more.

OpenStack:
Aaron Rosen: Quick guide to creating a OpenStack bootable image
Usually every time I go to install a VM from scratch I end up having to google around for the exact commands I need… so I figured I’d do a quick post on how to install your own image that’s boot-able via OpenStack. Read more.

Cloudwatt: Introducing Flame: automatic Heat template generation
In this blog-post I will talk about Flame, a tool that generates HOT Heat template from already existing infrastructure. Currently this project is developed by Thomas Herve (Heat core developer) and myself and provides support for Nova (key pairs and servers), Cinder (volumes) and Neutron (router, networks, subnets, security groups and floating IPs) resources. Read more.

Cody Bunch: OpenStack LumberJack – Part 1 rsyslog
Logging for OpenStack has come quite a ways. What I’m going to attempt to do over a few posts, is recreate and expand a bit on what was discussed at this last OpenStack Summit with regard to Log Management and Mining in OpenStack. For now, that means installing rsyslogd and setting it up to accept remote connections. Read more.

Mark McLoughlin: An Ideal OpenStack Developer
In a recent update Jonathan gave to the Board of Directors, we described how OpenStack has had 2,130 contributors to date and 466 of those are active on a monthly basis. That’s an incredible statistic. There’s no doubt OpenStack has managed to attract an unusual number of contributors and, for such a complex project, made it relatively easy for them to contribute. The question then is how to improve the overall quality of our large number of contributors. In order to do that, we need to be able to set expectations. What do we expect and value from our contributors? Read more.

Matt Farina: State of Application Developer Experience with OpenStack
When I first started writing applications that ran in OpenStack clouds or worked against the APIs the experience was painful. To figure out what I could do with the APIs I ended up in the source code for OpenStack or asking those who were in the source or knew the system better. If I'd been using a different, maybe more popular, cloud I could have quickly found my answer in the documentation. As a user I longed for something better. Fast forward to today. OpenStack has come a long way in many regards. Yet, I still find myself poking around in the code and the community to figure out how some things work. Just last week I learned about two undocumented REST API calls that I would be using if I'd known about them. This isn't to say that the documentation team is somehow lacking. There is a lot of documentation and they have a real desire to provide useful documentation. I appreciate their work and drive to get us to something better. Making things better just takes more than a documentation team.Read more.

Mirantis: OpenStack in the gap between PaaS and IaaS
To unpack the problem, let’s work in the other direction: what do developers need to solve to make their apps work and thrive in the IaaS environment? Bridging that gap means that OpenStack needs to offer abstractions that solve real developer problems in a way that makes sense to a developer. To that end, OpenStack has several projects that can provide an opportunity for PaaS developers to help create an environment in which they can flourish. Read more.

Opensource.com: Exploring OpenStack cloud case studies
During the course of the last twelve months, the OpenStack community has advanced as more users of the leading open source cloud technology have been reporting their progress with the help of their partners towards making a meaningful impact on their business goals and objectives. We've also learned how these progressive technology users are pioneering changes in their own organizations—enabling them to become more competitive in the global networked economy.Read more.

Opensource.com: What Docker 1.0 means for OpenStack
At the sold-out DockerCon on Monday and Tuesday of this week, there were plenty of big announcements. But the biggest of which was Docker going 1.0. Whether or not it now meets every need for production workloads is a hotly-debated topic, but there's no doubt that this milestone is an important step in getting Docker into the datacenter. Read more.

Rob Hirschfeld: Understanding OpenStack Designated Code Sections – Three critical questions
After nearly a year of discussion, the OpenStack board launched the DefCore process with 10 principles that set us on path towards a validated interoperability standard. We created the concept of “designated sections” to address concerns that using API tests to determine core would undermine commercial and community investment in a working, shared upstream implementation. Read more.

The OpenStack Blog: Open Mic Spotlight: Mark Vanderwiel
An interview with Mark Vanderwiel, currently working on the OpenStack Chef cookbooks in StackForge as a core contributor. Read more.

Thierry Carez: Analysis of April 2014 TC election
Some people asked me to analyze the results of the recent TC election in the same way I ran the analysis for the previous one. I finally found the time to do it, here are the results. Read more.