About two and a half years ago I wrote about how the MariaDB project moved bug reporting from Launchpad to JIRA. Every now and then I get contacted about how it was done and whether I would be willing to share the tools used for doing it and of course I’ve done that. Especially in one occasion the scripts were even further developed by one company that was in the process of doing exactly the same, i.e. moving bugs from Launchpad to JIRA. Thanks for the enhancements Philip Colmer from Linaro!

In Launchpad there isn’t a readymade tool for exporting bugs and I didn’t find any 3rd party tools for doing it. Launchpad however has an API through which most (if not all) information in Launchpad can be retrieved. Launchpad has made a library available in Python making use of this API.

By using the Launchpad Python API, I wrote a Python script LaunchpadBugs.py that pulls out bug information from Launchpad and creates an XML document for each bug. If the bug includes attachments these are also downloaded and named in a way that they can be connected to the XML.

It would, of course, be nice if the bunch of XML files and attachments that you end up with after running the Python script could be uploaded directly into a JIRA instance. Unfortunately this is not possible, unless it has been added recently, and instead a separate format is needed. According to my investigations, JIRA supports importing information best if it’s in CSV (comma separated values) format. That leads to converting a bunch of XML files to a CSV file. The CSV file can include links to the attachments.

I’ve done quite a lot of C# programming in the past and still had the way of dealing with XML in C# in my head, so I chose to do the XML to CSV conversion in C# in a Windows command line application. You’ll find the application named JiraCSV in the Github repository mentioned below.

The scripts described above have been useful for those that have reached out explicitly asking for a copy of them, but maybe the interest is broader. To initially get to the point where migration was successful it took a lot of trials to correct the data, add missing data, change the XML or CSV structure, and so on to get everything accepted by JIRA. I hope that by now sharing these scripts people will save a significant amount of time. That’s why I’ve decided to put them up on Github so that anyone interested in them can pick them up and make use of them or even improve them further. You can find them at https://github.com/rasmushoj/LP2JIRA.

Year 2014 was an important year for the MariaDB project with the release of MariaDB 10.0. Adoption continued to grow both organically and by MariaDB being included both in the Red Hat Enterprise Linux and Suse Linux Enterprise Server distributions as the default database option. Ubuntu started providing MariaDB as an option since their release 14.04. MariaDB also came available in many cloud services, e.g. DBaaS in the Rackspace Cloud and Cloud Foundry. Those are just a few highlights. There is of course a lot of other news from last year which has already been covered earlier.

If you’re interested in what the MariaDB Foundation worked on last year, Monty wrote a wrap-up on it. You can find it here.

In this article I want to focus on a few recent changes related to the MariaDB Foundation. On Monday this week, the MariaDB Foundation had its first board meeting of the year. In addition to all the general things on a board meeting agenda there were the following topics:

  • New memberships
  • Approval of new board member
  • Approval of new CEO

A Norwegian company called Visma has become a member of the MariaDB Foundation. Visma is a 6,000 person software company focused on finance and accounting software and services.

As part of Visma becoming a member it was also suggested that Visma gets a representative on the board. It would be hard to find a more suitable person for the job than Espen Håkonsen, CIO of Visma and Managing Director of Visma IT & Communications.

The MariaDB Foundation has been looking for a new CEO since Simon Phipps left last fall. Late last year discussions started with Otto Kekäläinen and he got interested. Otto is an entrepreneur in the open source business in Finland. He is the CEO of the open source consulting company Seravo. In addition he has several important open source roles in Finland and Europe. Otto is Finland’s representative in the Free Software Foundation Europe and in the steering group of COSS, the Finnish Centre for Open Systems and Solutions, the umbrella open source association in Finland. Otto will also serve as the Secretary of the board.

These changes in the board and management of the MariaDB Foundation were approved in the board meeting. I’m delighted to have Espen and Otto to join the MariaDB Foundation. They bring a lot of new experience and ideas to the foundation. Welcome!

Chairman of the board
Rasmus Johansson

 

MariaDB Roadshow Helsinki
MariaDB Roadshow Helsinki

One could say that MariaDB originates from Finland’s capital Helsinki. In fact so does MySQL. It was in the Helsinki area that MySQL saw daylight. It was here that Monty Widenius laid the ground for MySQL already in the 80’s, maybe even 1979, when he created UNIREG from which parts were reused when he together with the other 2 founders of MySQL released the first version of MySQL in 1995.

Last week, 19 years later, a MariaDB event was held in Helsinki. It was SkySQL that arranged the first in a row of this year’s MariaDB Roadshow events. The agenda included a walkthrough of MariaDB 10.0, some roadmap and MariaDB high availability options, which consisted of MariaDB Galera Cluster and MaxScale, the pluggable load balancer for MariaDB and MySQL. In addition Vinay from Severalnines visited to give a talk about automation and management of MariaDB Galera Cluster.

I gave the talk on MariaDB 10.0 and it was very interesting to learn that half of the audience was already using MariaDB. Also the amount of input at the end of my presentation on features the audience would like to see in MariaDB was impressive. Some of them were pretty specific, like usage of the same temporary table multiple times in the same query. Others more generic, like using the Connect storage engine, https://mariadb.com/kb/en/introduction-to-the-connect-engine/ as a central integration point for all interoperability with other databases, especially Redis and MongoDB.

Another very clear outcome from the event is that there is definitely a need for a good database load balancer and people enjoyed talking about MaxScale and how it could help them in their specific solutions.

In case you didn’t have a chance to join the MariaDB event in Helsinki, SkySQL has lined up a few of these events throughout the summer:

Join one of them if you are nearby. You might learn a thing or two and you’ll be able to give feedback directly to people that work on MariaDB.