MaxScale binaries are now available

UPDATE: Short story: ignore the next update and read the post. Long story: the original post was a mistake, as explained in the next update. But then, MariaDB released free MaxScale binaries and everything I wrote in the post is now correct.

UPDATE 2016-04-14: It seems that I was mistaken. MaxScale download page is a bit different from MariaDB Enterprise page, and does not explicitly require us to accept terms of use before download. But we accept those terms while creating an account.

So, MaxScale binaries cannot be used in production without paying for MariaDB enterprise. Thanks to the persons who commented this post and pointed my mistake. My apologies to my readers.

I won’t delete this post because I don’t want the comments to disappear, as they express opinions of some community members.

My jestarday’s post Comments on MaxScale binaries followed up a post from Percona’s blog. It had much more visits than any other post I wrote before. It was linked by Peter Zaitsev and Oli Senhauser on social networks. No, this is not a self-advertisement, I’m just saying that the problem I’ve talked about is considered important by the community.

Today, MaxScale binaries are available! Not because of me (obviously), but because MariaDB must have found out that the community badly wants those binaries.

MaxScale 1.4.1 was released today, and it is available from the Database Downloads page on MariaDB.com. You can click on MaxScale and then you can select the version (1.4.1, 1.3.0, 1.2.1) and the system (Debian, Ubuntu, RHEL/CentOS, SLES, both available as deb/rpm or tarball). Registration is required for download, but this is acceptable, as long as the binaries are freely available.

There are no restrictive terms of use. Here is how the copyright note starts:

This source code is distributed as part of MariaDB Corporation MaxScale. It is free
software: you can redistribute it and/or modify it under the terms of the
GNU General Public License as published by the Free Software Foundation,
version 2.

The only problem is the lack for a repository – but now that the binaries are freely available, I expect most Linux distros to provide their packages.

I downloaded the Ubuntu 14.04 version on my Mint machine, and everything worked as expected:

fede-mint-0 ~ # dpkg -i /home/federico/Downloads/maxscale-1.4.1-1.ubuntu_trusty.x86_64.deb 
Selecting previously unselected package maxscale.
(Reading database ... 184280 files and directories currently installed.)
Preparing to unpack .../maxscale-1.4.1-1.ubuntu_trusty.x86_64.deb ...
Unpacking maxscale (1.4.1) ...
Setting up maxscale (1.4.1) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Processing triggers for libc-bin (2.19-0ubuntu6.7) ...
fede-mint-0 ~ # maxadmin -uadmin -pmariadb
MaxScale> show servers
Server 0x1b7a310 (server1)
	Server:                              127.0.0.1
	Status:                              Auth Error, Down
	Protocol:                    MySQLBackend
	Port:                                3306
	Node Id:                     -1
	Master Id:                   -1
	Slave Ids:                   
	Repl Depth:                  -1
	Number of connections:               0
	Current no. of conns:                0
	Current no. of operations:   0

So, thanks MariaDB! I love software projects that listen to their community needs. This should be a lesson for another company – we all know who I am talking about.

Federico

Advertisements

17 thoughts on “MaxScale binaries are now available

  1. I’m sticking to my (non-lawyer) assertion that the Evaluation License cannot trump the GPL license of the MaxScale product itself, and restrictions against using such software in production are not enforceable. Regardless, that either of us are confused on the matter is problematic, and until MariaDB publicly clarifies this, I have to guess that this confusion is the desired result – any doubt can be eliminated by paying MariaDB.

    • Yes, I agree that the GPL appliance here is problematic. Let’s say that I accept the terms of use and download a copy. Let’s say that there is no contradiction between the terms of use and GPL. But then, I can give my copy to you, because the GPL says so. And you didn’t accept MariaDB’s terms, so why should you pay?

      But in the real world, companies need to be sure they are not breaking any contract.

  2. Pingback: Requests for MariaDB | Todd's MySQL Blog

  3. If you need to register and accept “Evaluation Agreement” and “MariaDB Enterprise Terms and Conditions” – it does not mean that binaries are freely available. Your usage of binaries are restricted by these agreements.

      • Alas it looks like you still have to agree on account creation, this holds true for all account types:

        “To continue to use this site please read the Terms & Conditions below, and complete the form to confirm your acceptance.

        Yes, I have read and agree to the terms of the Evaluation Agreement. By clicking and accepting this Agreement, I represent and warrant that I have authority to bind the entity named on this form to these terms and conditions *”

        • Really, I can’t find that string. I suspect we are following different paths. In which case, there is clearly a problem on mariadb.com – one should always or never see that message. Would you show me that message?

          • It’s a condition you’re required to agree to during the account creation process. Unless the process has changed, I suspect it’s something you already agreed to when you created the account you have. Maybe try setting up another account using one of the other authentication types (Google, Github or email), all have the same requirement on sign up.

            • I did not create an account. I just logged in via LinkedIn, and I can’t see any clause like that. But it’s possible that this is a mariadb.com mistake that will be fixed, in which case, MaxScale binaries are still not free. It would be great if someone from MariaDB commented on this.

              • So I think we are talking about two different things here.

                If I navigate to https://mariadb.com/resources/downloads, and choose to “Download MariaDB MaxScale Binaries”, it takes me to https://mariadb.com/user/login?destination=my_portal/download/maxscale, without an account here I need to “Please log in or register to access this resource”.

                At this point, I have to create an account to access the binaries thereafter, the point I was trying to make above, is when registering an account, be it using an email, or linked to the LinkedIn, Google, or GitHub SSO options, before I’m able to sign in for the first time, I have to first agree to the terms of the Evaluation Agreement. This has the implication this applies to all content downloaded thereafter, regardless of whether I’m prompted on each download or not.

                It’s entirely possible it’s just an oversight, I’m just pointing out the behaviour as it is now 🙂

  4. First things first: Yay for MariaDB! This is a significant improvement to access to GPL-licensed MaxScale binaries. Thanks to MariaDB for listening to the community.

    But I wonder: Are we celebrating a bit prematurely? The MariaDB Enterprise Server binaries remain shackled by the same onerous Evaluation agreement:

    “Please note that your use of any product download for which you do not have an active subscription is subject to the terms of our Evaluation Agreement.”

    https://mariadb.com/my_portal/download/mariadb-enterprise

    I’m no lawyer, so I have no idea how enforceable such restrictions are against GPL-licensed product, but that’s a bit beside the point, isn’t it? Shouldn’t we expect that unconstrained access to GPL product downloads apply to MariaDB Enterprise Server as much as MaxScale?

    Beyond that, is the community satisfied with a differentiation strategy which says the community gets “cutting-edge”, “experimental” builds while paying Enterprise customers get “stable”, “optimized”, “certified” binaries? Nobody in the community wants the latter? Not even Linux distros?

    I’ll also admit I’m a bit disappointed there’s a need for the community to raise these issues again. MariaDB talks frequently about many of their staff having been part of the original MySQL team – a team that tried – and failed – to implement virtually identical policies while part of Sun. This isn’t new, and the fact that the same people keep trying the same policies might be justification for alarm.

    If the community’s only concern is unfettered access to MaxScale binaries, this is clearly a win. If the community cares about the underlying differentiation strategy and artificial access limitation to all GPL-licensed MariaDB products, it seems there’s still work to be done.

    • Hi Todd. My concern was about MaxScale because it’s a software I use and like. You are right about MariaDB Enterprise. But, as far as I can’t tell, it does not include unique software – I mean, it is an enterprise-oriented distribution of software projects that can also be installed separately. Again: I’m not saying you are wrong. But still, it is not a real problem for me.

Leave a comment

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s