[openstack-dev] mysql/mysql-python license "contamination" into openstack?

Chris Friesen chris.friesen at windriver.com
Thu Jun 12 18:13:05 UTC 2014


I'm looking for the community viewpoint on whether there is any chance 
of license contamination between mysql and nova.  I realize that lawyers 
would need to be involved for a proper ruling, but I'm curious about the 
view of the developers on the list.

Suppose someone creates a modified openstack and wishes to sell it to 
others.  They want to keep their changes private.  They also want to use 
the mysql database.

The concern is this:

nova is apache licensed
sqlalchemy is MIT licensed
mysql-python (aka mysqldb1) is GPLv2 licensed
mysql is GPLv2 licensed

The concern is that since nova/sqlalchemy/mysql-python are all 
essentially linked together, an argument could be made that the work as 
a whole is a derivative work of mysql-python, and thus all the source 
code must be made available to anyone using the binary.

Does this argument have any merit?

Has anyone tested any of the mysql DBAPIs with more permissive licenses?


More information about the OpenStack-dev mailing list