Another Drizzle GSoC Success Story

Drizzle has always been a big believer in young talent contributing code to Open Source. Hence, we have been part of the past four editions of Google Summer of Code with a lot of code getting back into trunk. One of the very smart interns that we have had so far is Sharan who worked closely with Patrick Crews on some of the Drizzle automation. Sharan has landed a job as a developer in Thought Works thanks to the effort that he has put into Drizzle. On behalf of the Drizzle team I would like to congratulate Sharan on his job offer and we hope that Drizzle helps nurture many more young minds in their paths to greatness. Here is what Sharan has to say regarding his journey:
http://sharcorner.wordpress.com/2013/08/13/a-wave-of-memories/

Drizzle 7.1.33-stable has been released

The Global Drizzle Development Team is pleased to announce the immediate availability of Drizzle 7.1.33-stable. The first stable release of Drizzle 7.1 and the result of 12 months of hard work from contributors around the world.

Improvements in Drizzle 7.1 compared to 7.0

- Xtrabackup is included (in-tree) by Stewart Smith

- Multi-source replication by David Shrewsbury

- Improved execute parser by Brian Aker and Vijay Samuel
- Servers are identified with UUID in replication by Joe Daly

- HTTP JSON API (experimental) by Stewart Smith

- Percona Innodb patches merged by Laurynas Biveinis

- JS plugin: execute JavaScript code as a Drizzle function by Henrik Ingo

- IPV6 data type by Muhammad Umair

- Improvements to libdrizzle client library by Andrew Hutchings and Brian Aker

- Query log plugin and auth_schema by Daniel Nichter

- ZeroMQ plugin by Markus Eriksson

- Ability to publish transactions to zeromq and rabbitmq by Marcus Eriksson

- Replication Dictionary by Brian Aker

- Log output to syslog is enabled by default by Brian Aker

- Improvements to logging stats plugin

- Removal of drizzleadmin utility (you can now do all administration from drizzle client itself) by Andrew Hutchings

- Improved Regex Plugin by Clint Byrum

- Improvements to pandora build by Monty Taylor

- New version numbering system and support for it in pandora-build by Henrik Ingo

- Updated DEB and RPM packages, by Henrik Ingo

- Revamped testing system Kewpie all-inclusive with suites of randgen, sysbench, sql-bench, and crashme tests by Patrick Crews

- Removal of HailDB engine by Stewart Smith

- Removal of PBMS engine

- Continued code refactoring by Olaf van der Spek, Brian Aker and others

- many bug fixes

Brian Aker ,Mark Atwood- Continuous Integration

Vijay Samuel – Release Manager

Installing Drizzle 7.1.33-stable

The source tar package is available from our Launchpad download area. Please see the manual on how to install Drizzle 7.1.33-stable from source tar package.

The Ubuntu packages are available from the Drizzle PPA. Instructions on how to install from the PPA are in the Drizzle manual.

CentOS 6 packages are available from download.drizzle.org. Instructions on how to install them with yum are in the Drizzle manual.

Note: For Drizzle 7.1.33-stable, only 64-bit packages were built for RedHat/Centos.

Known issues

All of the optional plugins are packaged in their own package. These are named drizzle-plugin-*. If a plugin is installed, it is also configured to load by default. (see /etc/drizzle/conf.d/pluginname.cnf) However, not all plugins actually work without further configuration. These plugins will cause the server startup to fail. The workaround is to either configure the plugin to work, or uninstall it if you don’t want to use it. (Related blueprint) In short, you should only install the plugins you want to use. Don’t install all available plugins. You also need to use “yum erase” and “apt-get purge” to uninstall plugins.

Please post bugs on the Drizzle bug tracker and questions and general feedback to drizzle-discuss mailing list.

Drizzle documentation

Much improved documentation is available at docs.drizzle.org

Planet Drizzle

You can follow our developer blogs, with more information about the features in Drizzle 7.1 at planetdrizzle.org

Percona Live MySQL Conference and Drizzle Day

The Drizzle team will be well represented at next week’s Percona Live MySQL Conference and Expo and the Drizzle Day in the Santa Clara Convention Center. There are a couple talks from Drizzle developers and users in the main conference, and a full day on Friday, Apr 13. Drizzle Day is free to attend (though donations are encouraged). Please join us in Santa Clara and come and say hi!

 

Commercial 24/7 support is available

Several support vendors in the MySQL space provide commercial support and services for Drizzle 7.1. Click here for a list of support vendors that contributed to Drizzle during the 7.1 release cycle.

Info to press

Drizzle core developers are available for email and phone interviews to discuss Drizzle 7.1 and also upcoming Drizzle topics. To arrange an interview, please contact

In Americas: Brian Aker brian@tangent.org,  Mark Atwood me@mark.atwood.name, Kent Bozlinski : kent@bozlinski.com

In EMEA: Henrik Ingo henrik.ingo@avoinelama.fi

In APAC: Stewart Smith stewart.smith@percona.com

 

Drizzle 7.1 Release Candidate 7.1.32-rc has been released

This is the third and hopefully final Release candidate for Drizzle 7.1

Tar ball, Debian package and RPMs available.

Changes since previous release:

* libdrizzle is no longer installed by these packages. To install libdrizzle, see lp:libdrizzle launchpad project. Libdrizzle so-version was bumped to 4.0.0.
* Removed Transaction Log (includes drizzletrx command line utility) and Replication Dictionary (Brian Aker)

Bugs and other minor fixes:

* Bug fixed: The Regex Policy plugin could consume unbounded amounts of memory, which could be used for denial of service attacks. (Clint Byrum.)
* Bug fixed: Drizzled could crash when filesystem permissions cause writing a pid file to fail. (Brian Aker)
* Bug fixed: An undocumented ipv6_function was enabled and could crash drizzled if called – the function was disabled. (Fixed by Henrik Ingo.)
* Bug fixed: In master master setup, slave plugin would try to apply transactions originating from itself. (Joe Daly)
* Bug fixed: Fix performance regression introduced with catalog being added to key. (Brian Aker)
* Bug fixed: actually return the next exception in Exception::getNextException() & Fix for execute parser to recognize escaped semicolons. (David Shrewsbury)
* Bug fixed:  A typo in assertion causing false positive failure with log > 4GB. (Laurynas Biveinis)
* Updated docs. Check out comprehensive replication documentation! (Daniel Nichter, Henrik Ingo, Muhammad Umair, Brian Aker, et.al.)
* Cleanups to drizzle and drizzled –help output and error messages. Standardize plugin names. (Daniel Nichter, Mohit Srivastava)
* Updates and cleanups to the Kewpie testing suite. Enable more automated CI process. (Patrick Crews, Olaf van der Spek)

Changes in Drizzle 7.1 series since Drizzle 7 include:

- Multi-master replication
- Servers are identified with UUID in replication
- HTTP JSON interface available (experimental)
- Percona Innodb patches merged
- Xtrabackup in-tree
- IPV6 data type available
- Query log plugin
- Log output to syslog is enabled by default
- Ability to publish transactions to zeromq and rabbitmq
- Improvements to logging stats plugin
- Native multi-tenancy (database virtualization) support (catalogs)
- Removal of drizzleadmin utility (you can now do all administration from drizzle client itself)
- Removal of HailDB engine
- Revamped testing system Kewpie all-inclusive with suites of randgen, sysbench, sql-bench, and crashme tests
- Continued code refactoring & various bug fixes

Installing Drizzle 7.1.32-rc

The source tar package is available from our Launchpad download area. Please see the manual on how to install Drizzle 7.1.32-rc from source tar package.

The Ubuntu packages are available from the Drizzle PPA. Instructions on how to install from the PPA are in the Drizzle manual.

CentOS 6 packages are available from download.drizzle.org. Instructions on how to install them with yum are in the Drizzle manual.

Note: For Drizzle 7.1.32-rc, only 64-bit packages were built for RedHat/Centos. Please let us know if there is demand for 32-bit packages (such as by commenting to this blog post.)

Known issues

All of the optional plugins are packaged in their own package. These are named drizzle-plugin-*. If a plugin is installed, it is also configured to load by default. (see /etc/drizzle/conf.d/pluginname.cnf) However, not all plugins actually work without further configuration. These plugins will cause the server startup to fail. The workaround is to either configure the plugin to work, or uninstall it if you don’t want to use it. (Related blueprint) In short, you should only install the plugins you want to use. Don’t install all available plugins.

Please post bugs on the Drizzle bug tracker and questions and general feedback to drizzle-discuss mailing list.

Drizzle White Paper published: Drizzle and IPv6

Drizzle white papers highlight unique features and designs in Drizzle, and give you examples of how to use them. We are proud to announce that we have today published our first white paper: Drizzle and IPv6.

This white paper will explain how Drizzle supports IPv6. The support for IPv6 networking was added to Drizzle early on and is available already in the first Drizzle 7 release. The Drizzle 7.1 release also adds the support for an IPV6 Data Type, to provide a way of storing IPv6 addresses in the database that is both user friendly and efficient. As an introduction we will also cover the differences between IPv4 and IPv6 network addresses and the reasons for transitioning from IPv4 to IPv6 addresses.

With this white paper we wish to thank the Google Summer of Code program for supporting Drizzle. The IPV6 data type was developed as a GSOC 2011 project by Muhammad Umair, with Mark Atwood mentoring. The IPv6 networking support was developed by Brian Aker and Eric Day, at the time employed by Sun Microsystems.

RPM and DEB packages for 7.1.31-rc has been released

The first Drizzle 7.1 Release Candidate was released 2 weeks ago. It contained a few last minute changes that broke the packaging process (version number and decision to package libdrizzle separately) and hence only a source release was made. However, we are happy to announce that we have now caught up with those changes and binary packages are today available for RHEL/Centos 6 and Ubuntu 11.10 Oneiric.

In addition we are working closely with the Debian project to upload Drizzle 7.1.x into Debian unstable repository in the near future. This will be the primary place to get Drizzle for Debian and we will not be setting up any other Debian repository ourselves. As of today you can already find the stable Drizzle 7 release in Debian unstable. Thanks to Tobias Frost for stepping up as the Drizzle packager for Debian.

Fedora packages were not provided at this time. This is due to Fedora 16 switching to the new systemd, which rendered our standard init script unusable. We will probably look into systemd startup scripts at some point in the future.

Installing Drizzle 7.1.31-rc on Ubuntu.

The Ubuntu packages are available from the Drizzle PPA. Instructions on how to install from the PPA are already in the Drizzle manual.

Installing Drizzle 7.1.31-rc on RedHat / Centos 6.

Note: For Drizzle 7.1.31-rc, only 64-bit packages were built for RedHat/Centos. Please let us know if there is demand for 32-bit packages (such as commenting to this blog post.)

A pre-requisite is to install the EPEL repository:

su -c 'rpm -ivh http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-5.noarch.rpm'

After this, please add the following to /etc/yum.repos.d/drizzle.repo

   [drizzle]
   name=drizzle
   baseurl=http://download.drizzle.org/7.1/redhat/$releasever/$basearch/
   enabled=1
   gpgcheck=0

   [drizzle-src]
   name=drizzle-src
   baseurl=http://download.drizzle.org/7.1/redhat/$releasever/source
   enabled=1
   gpgcheck=0

Note that the baseurl is different from what was used for Drizzle 7.

Known issues

All of the optional plugins are packaged in their own package. These are named drizzle-plugin-*. If a plugin is installed, it is also configured to load by default. (see /etc/drizzle/conf.d/pluginname.cnf) However, not all plugins actually work without further configuration. These plugins will cause the server startup to fail. The workaround is to either configure the plugin to work, or uninstall it if you don’t want to use it. (Related blueprint) In short, you should only install the plugins you want to use. Don’t install all available plugins.

Resources

To know what’s new in this release, you can read the 7.1.31-rc release notes here. Please post bugs on the Drizzle bug tracker and questions and general feedback to drizzle-discuss mailing list.

Drizzle 7.1 Release Candidate 1 (7.1.31-rc) has been released

This is the first Release candidate for Drizzle 7.1
Changes since previous release (2012.01.30) include:

* Various bug fixes from Stewart Smith
* New versioning system from Henrik Hingo
* Updated docs

Changes since Drizzle 7 include:

- Multi-master replication
- UUID’s for replication
- JSON interface available
- Percona Innodb patches merged
- Xtrabackup in-tree
- IPV6 data type available
- query login plugin (syslog) is enabled / on by default
- Ability to publish transactions to zeromq
- Improvements to logging stats plugin
- Support for catalogs
- Removal of drizzleadmin utility
- Removal of HailDB engine
- Revamped testing system with suites of randgen, sysbench, sql-bench, and crashme tests
- Continued code refactoring
- Various bug fixes

Announcing Drizzle Day 2012, on Fri 13 Apr in Santa Clara

The Drizzle Team would like to welcome you to our 4th Drizzle Day, to be held on Apr 13 at the Hyatt Regency hotel in Santa Clara.

Admission to Drizzle Day is free, however we recommend that you consider making a voluntary donation between 50 – 150 USD to our SPI account to cover for the costs of this conference: click here to donate. Note that if you are expensing your travel and Percona Live attendance with your employer anyway, you can also expense this payment as a conference fee.

Reflecting the fact that Drizzle 7 has now been out for a year, and Drizzle 7.1 will be released before the conference, the content for this Drizzle Day is geared more towards end users than before. You can learn about unique Drizzle features like true multi-tenancy support, the HTTP JSON interface, and more! Toward the end of the day we also have content that might interest potential contributors and you can end the day by talking to Drizzle developers who are happy to guide you in both using Drizzle as well as becoming an active community member.

Click here for schedule and registration information!

The Drizzle Day follows right after the Percona Live MySQL Conference and Expo where you will also find Drizzle talks, BoFs and a booth in the Exhibition hall dot-org-pavilion. We would like to thank Percona for sponsoring the Drizzle Day by covering a large part of the costs as well as marketing the event as an official side-conference to PLMCE.

Release: Drizzle 2012.01.30 (Fremont beta3) RPM binaries for RHEL / CentOS 6

Hot on the heels of this week’s Drizzle 2012.01.30 source release, we are now also releasing beta quality binary RPMs for your downloading and testing pleasure! While we are revitalizing the Drizzle yum repository, you can download the rpm-bundle from our Launchpad project page: https://launchpad.net/pkg-drizzle/+download

As the Fremont development cycle is ending it’s beta cycle and heading for release candidates, we are starting to publish also binary packages for downloads. Today we are releasing RPM packages for RHEL/CentOS 6.0. Fedora 16 packaging has unfortunately been postponed. We will eventually support also Fedora 16 RPMs, but in the mean time you can possibly spot some Drizzle developers on twitter or irc making snarky comments about systemd …

In the following week(s) we will also publish Debian and Ubuntu packages.

Note that these packages are a first release of their kind and still a bit experimental. What this means is that the underlying Drizzle release itself is stabilizing quite nicely, but the packaging process is currently not completely integrated nor automated.

Please report errors at the main Drizzle bug tracker, and direct your general feedback to the drizzle-discuss mailing list.

Details:

  • These packages were built from the Drizzle bzr trunk at tag 2012.01.30.
  • In addition a branch that supports “make rpm” was merged from lp:~hingo/drizzle/drizzle-integrate-packaging-rpm. This is based on the same RPM spec as was used for Drizzle 7, but the intent is to integrate it with the main Drizzle source code and then Jenkins builds. The current release was however still a manual process.
  • When building this way, an additional bzr tag –force 2012.01.30 was needed to maintain the same version number.
  • Along the RPMs we have uploaded a source tar file fake-drizzle7-2012.01.30.tar.gz. This corresponds to the real Drizzle 2012.01.30 release, plus the above changes.
  • The RPM files are made available as a tar bundle. The process to publish into the Drizzle yum repository is currently broken but will resume in the near future.
  • A related issue is that the packages are not signed.
  • Known issue: If you install the plugin rpms, they will be automatically loaded at startup. However, some of them (in particular, many auth plugins, the policy plugins and possibly the slave plugin) don’t actually work without further configuration and will thus prevent the server from starting. If you encounter this plugin, you should either complete the configuration (in /etc/drizzle/conf.d/[plugin].conf) or, if you don’t want to use it, uninstall the plugin.