Yesterday, I created a Launchpad project to be used for tracking bugs and feature requests for the new OpenStack Chef cookbooks house on Stackforge. Please do file bugs as you encounter issue with any of the cookbooks or the example OpenStack Chef Repository.

This blog post is part two in what is now a continuing series on the Star Schema Benchmark.

In my  href="http://www.mysqlperformanceblog.com/2013/03/11/mysql-5-6-vs-5-5-on-the-star-schema-benchmark/" target="_blank">previous blog post I compared MySQL 5.5.30 to MySQL 5.6.10, both with default settings using only the InnoDB storage engine.  In my testing I discovered that innodb_old_blocks_time had an effect on performance of the benchmark.  There was some discussion in the comments and I promised to follow up with more SSB tests at a later date.

href="http://www.mysqlperformanceblog.com/wp-content/uploads/2013/05/data_replication2.jpg"> class="alignleft wp-image-15554" style="margin-left: 9px; margin-right: 9px;" alt="GTID-based replication" src="http://www.mysqlperformanceblog.com/wp-content/uploads/2013/05/data_replication2-300x204.jpg" width="270" height="184" />Global Transactions Identifiers are one of the new features regarding replication in MySQL 5.6. They open up a lot of opportunities to make the life of DBAs much easier when having to maintain servers under a specific replication topology.

For too long, the state of the OpenStack Chef world had been one of duplicative effort, endless forks of Chef cookbooks, and little integration with how many of the OpenStack projects choose to control source code and integration testing. Recently, however, the Chef + OpenStack community has been getting its proverbial act together. Folks from lots of companies have come together and pushed to align efforts to produce a set of well-documented, flexible, but focused Chef cookbooks that install and configure OpenStack services.