The GA binaries for MySQL Cluster 7.0.8a (the “a” is used to indicate that this is an increment on the original 7.0.8 source release) have been released – download them from http://dev.mysql.com/downloads/select.php?id=14
A summary of the changes can be found in the MySQL Cluster 7.0.8a Change Log
OpenLDAP includes a driver that allows it to store and access data held in MySQL Cluster. It uses the NDB-API to access the database and so the performance is extremely good. One of the great things about the solution is that it lets you simultaneously access the same data through both LDAP and SQL (or the NDB-API or any of the MySQL connectors). This article gives an example of how this can be done.
This article assumes that you’ve already installed MySQL Cluster – if that isn’t the case then please first refer to “Creating a simple Cluster on a single LINUX host” or “Deploying MySQL Cluster over multiple hosts“.
Once MySQL Cluster has been installed, you need to build and configure OpenLDAP to use MySQL Cluster (alternatively, you can engage Symas to provide you pre-built binaries); Johan provides a good walkthrough of this in his Blog “OpenLDAP for MySQL Cluster“. One extra note is that slapd must be run as root due to the ports it accesses. That Blog entry also explains how to test that everything is working – do that before proceeding to the next step.
The standard schemas that come with OpenLDAP will be suitable for lots of scenarios that have typically used directories. In this article, we’re interested in other applications where we need to store and access additional attributes.
We create a new schema file “x-clusterdb-hlr.schema” that represents some of the data that would be needed for an HLR application:
attributetype ( 1.3.6.1.4.1.33913.1.0 NAME 'clusterdbsubid'
DESC 'Represents the internal subscriber identifier'
EQUALITY integerMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.27{8})
attributetype ( 1.3.6.1.4.1.33913.1.1 NAME 'clusterdbimsi'
DESC 'Represents the IMSI associated with a subscriber'
EQUALITY numericStringMatch
SUBSTR numericStringSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{15})
attributetype ( 1.3.6.1.4.1.33913.1.2 NAME 'clusterdbmsisdn'
DESC 'Represents the MSISDN associated with a subscriber'
EQUALITY numericStringMatch
SUBSTR numericStringSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{15})
attributetype ( 1.3.6.1.4.1.33913.1.3 NAME 'clusterdbvlrnumber'
DESC 'Represents the visited VLR number associated with a subscriber'
EQUALITY numericStringMatch
SUBSTR numericStringSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{15})
attributetype ( 1.3.6.1.4.1.33913.1.4 NAME 'clusterdbsmscnumber'
DESC 'Represents the SMS SC that handles messages for a subscriber'
EQUALITY numericStringMatch
SUBSTR numericStringSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{15})
attributetype ( 1.3.6.1.4.1.33913.1.5 NAME 'clusterdbsmscount'
DESC 'Represents the number of SMS messages waiting for the subscriber'
EQUALITY integerMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.27{4})
attributetype ( 1.3.6.1.4.1.33913.1.6 NAME 'clusterdbcfu'
DESC 'Represents the Call Forwarding Unconditional number for the sub'
EQUALITY numericStringMatch
SUBSTR numericStringSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{15})
attributetype ( 1.3.6.1.4.1.33913.1.7 NAME 'clusterdbcfnryt'
DESC 'Represents the CFNRY timer'
EQUALITY numericStringMatch
SUBSTR numericStringSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{15})
attributetype ( 1.3.6.1.4.1.33913.1.8 NAME 'clusterdbreleasemin'
DESC 'Represents the software release (minor) of the subscriber data'
EQUALITY numericStringMatch
SUBSTR numericStringSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{15})
attributetype ( 1.3.6.1.4.1.33913.1.9 NAME 'clusterdbreleasemaj'
DESC 'Represents the software release (major) of the subscriber data'
EQUALITY numericStringMatch
SUBSTR numericStringSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{15})
objectclass ( 1.3.6.1.4.1.33913.1 NAME 'clusterdbhlrrecord'
DESC 'The HLR data record for a subscriber'
MUST (clusterdbsubid $ clusterdbimsi)
MAY (clusterdbmsisdn $ clusterdbvlrnumber $ clusterdbsmscnumber $ clusterdbsmscount $ clusterdbcfu $ clusterdbcfnryt))
One thing to note is that the identifier for each objectclass or attributetype has to be globally unique and you should apply for a unique prefix for your organization from the Internet Assigned Numbers Authority – the enterprise ID for clusterdb.com is 33913 and so any identifier starting with 1.3.6.1.4.1.33913 has been defined by clusterdb.com. This article does not attempt to explain exactly how to define your own schema; you can use this example as a starting point and then refer to the OpenLDAP chapter on extending schemas.
To use this schema, you need to copy the schema file to the ‘schema’ directory in the OpenLDAP installation directory – for example “/usr/local/openldap/etc/openldap/schema”. The “slapd.conf” file also needs updating/replacing to include the new schema (and in our case, change the domain and database name to clusterdb):
include /usr/local/openldap/etc/openldap/schema/core.schema include /usr/local/openldap/etc/openldap/schema/cosine.schema include /usr/local/openldap/etc/openldap/schema/inetorgperson.schema include /usr/local/openldap/etc/openldap/schema/x-clusterdb-hlr.schema pidfile /usr/local/openldap/var/run/slapd.pid argsfile /usr/local/openldap/var/run/slapd.args #NDB database defintions database ndb suffix "dc=clusterdb,dc=com" rootdn "cn=Manager,dc=clusterdb,dc=com" rootpw secret directory /usr/local/openldap/var/openldap-data dbconnect localhost:1186 dbhost localhost dbname clusterdb dbuser root dbpass "" dbconnections 2 attrset billy clusterdbreleasemaj,clusterdbreleasemin
For this to take effect, you now need to stop and restart the slapd process.
To test that everything is working as intended, we need some test data covering the new schema – create a file called “add_clusterdb_hlr.txt“:
dn: dc=clusterdb,dc=com dc: clusterdb objectClass: dcObject objectClass: organization description: HLR operator o: GSM PlC dn: clusterdbsubid=12,dc=clusterdb,dc=com objectclass: clusterdbhlrrecord clusterdbsubid: 12 clusterdbimsi: 456123123456789 clusterdbmsisdn: 611231234512345 clusterdbvlrnumber: 611230000000000 clusterdbsmscnumber: 611230000000001 clusterdbsmscount: 2 dn: clusterdbsubid=97,dc=clusterdb,dc=com objectclass: clusterdbhlrrecord clusterdbsubid: 97 clusterdbimsi: 456123123456788 clusterdbmsisdn: 611231234512344 clusterdbvlrnumber: 611230000000000 clusterdbsmscnumber: 611230000000001 clusterdbsmscount: 0
Use the slapadd tool to load the data:
[billy@ws1 OpenLDAP]$ slapadd -l add_clusterdb_hlr.txt 091009 11:49:26 [Note] NDB Binlog: CREATE TABLE Event: REPL$clusterdb/OL_dn2id 091009 11:49:26 [Note] NDB Binlog: CREATE TABLE Event: REPL$clusterdb/OL_nextid 091009 11:49:27 [Note] NDB Binlog: CREATE TABLE Event: REPL$clusterdb/OL_opattrs 091009 11:49:28 [Note] NDB Binlog: CREATE TABLE Event: REPL$clusterdb/billy 091009 11:49:28 [Note] NDB Binlog: CREATE TABLE Event: REPL$clusterdb/dcObject 091009 11:49:29 [Note] NDB Binlog: CREATE TABLE Event: REPL$clusterdb/organization _########### 59.97% eta elapsed spd 258.2 /s 091009 11:49:30 [Note] NDB Binlog: CREATE TABLE Event: REPL$clusterdb/clusterdbhlrrecord -#################### 100.00% eta none elapsed 02s spd 313.5 /s Closing DB...
Behind the scenes, OpenLDAP has now created the “clusterdb” database as well as a number of tables:
mysql> use clusterdb; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A [billy@ws1 OpenLDAP]$ mysql -u root Welcome to the MySQL monitor. Commands end with ; or g. Your MySQL connection id is 13 Server version: 5.1.37-ndb-7.0.8a Source distribution Type 'help;' or 'h' for help. Type 'c' to clear the current input statement. mysql> use clusterdb; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed mysql> show tables; +---------------------+ | Tables_in_clusterdb | +---------------------+ | OL_dn2id | | OL_nextid | | OL_opattrs | | billy | | clusterdbhlrrecord | | dcObject | | organization | +---------------------+ 7 rows in set (0.00 sec)
Again, this article doesn’t attempt to explain all of details around all of these tables but the 2 key ones here are OL_dn2id and clusterdbhlrrecord. The OL_dn2id table is used to map from a distinguished name to an entry-id (eid) which is then used a key into the table that actually holds the data (in our example, clusterdbhlrrecord). A table is created for each objectclass in the LDDAP schema that we’ve added data to (in this example, that means organization and clusterdbhlrrecord:
mysql> select * from OL_dn2id; +-----+-------------------------------+--------+--------------+-------------------+----+----+----+----+----+----+----+-----+-----+-----+-----+-----+-----+ | eid | object_classes | a0 | a1 | a2 | a3 | a4 | a5 | a6 | a7 | a8 | a9 | a10 | a11 | a12 | a13 | a14 | a15 | +-----+-------------------------------+--------+--------------+-------------------+----+----+----+----+----+----+----+-----+-----+-----+-----+-----+-----+ | 1 | dcObject organization @ top | dc=com | dc=clusterdb | | | | | | | | | | | | | | | | 2 | clusterdbhlrrecord @ top | dc=com | dc=clusterdb | clusterdbsubid=12 | | | | | | | | | | | | | | | 3 | clusterdbhlrrecord @ top | dc=com | dc=clusterdb | clusterdbsubid=97 | | | | | | | | | | | | | | +-----+-------------------------------+--------+--------------+-------------------+----+----+----+----+----+----+----+-----+-----+-----+-----+-----+-----+ 3 rows in set (0.00 sec) mysql> select * from clusterdbhlrrecord; +-----+-----+----------------+-----------------+-----------------+--------------------+---------------------+-------------------+--------------+-----------------+ | eid | vid | clusterdbsubid | clusterdbimsi | clusterdbmsisdn | clusterdbvlrnumber | clusterdbsmscnumber | clusterdbsmscount | clusterdbcfu | clusterdbcfnryt | +-----+-----+----------------+-----------------+-----------------+--------------------+---------------------+-------------------+--------------+-----------------+ | 3 | 0 | 97 | 456123123456788 | 611231234512344 | 611230000000000 | 611230000000001 | 0 | NULL | NULL | | 2 | 0 | 12 | 456123123456789 | 611231234512345 | 611230000000000 | 611230000000001 | 2 | NULL | NULL | +-----+-----+----------------+-----------------+-----------------+--------------------+---------------------+-------------------+--------------+-----------------+ 2 rows in set (0.00 sec)
Clearly, the application can now use LDAP or SQL to read and modify these same fields.
There are some restrictions on the schema created in MySQL Cluster by OpenLDAP – for example, all columns are varchars. It could be that your application needs a richer data schema when using SQL to access the data, including data that doesn’t need accessing through LDAP. The simplest way to do this would be to have some tables in the data base that aren’t included in the LDAP schema – OpenLDAP just won’t see them.
Another option is to have OpenLDAP only see a subset of the columns in a table (it only sees those fields that are in the LDAP schema). This is fairly straightforward to acheive as OpenLDAP only creates the database and tables if they don’t already exist and it is happy to ignore any columns that are not included. For simplicity, we assume that you’ve executed Example 1 and then we remove the database and then recreate it by hand (and then you should restart slapd):
mysql> drop database clusterdb; Query OK, 7 rows affected (4.41 sec) mysql> create database clusterdb; Query OK, 1 row affected (0.00 sec) mysql> use clusterdb; Database changed mysql> CREATE TABLE clusterdbhlrrecord ( -> eid bigint(20) unsigned NOT NULL, -> vid int(10) unsigned NOT NULL, -> clusterdbsubid varchar(8) DEFAULT NULL, -> clusterdbimsi varchar(15) DEFAULT NULL, -> clusterdbmsisdn varchar(15) DEFAULT NULL, -> clusterdbvlrnumber varchar(15) DEFAULT NULL, -> clusterdbsmscnumber varchar(15) DEFAULT NULL, -> clusterdbsmscount varchar(4) DEFAULT NULL, -> clusterdbcfu varchar(15) DEFAULT NULL, -> clusterdbcfnryt varchar(15) DEFAULT NULL, -> contractstart date default null, -> PRIMARY KEY (eid,vid)) -> engine=ndb partition by key (eid);
and then add the same data (which doesn’t contain “contractstart”) as in Example 1 and then use LDAP to check that it has been stored correctly and can be retrieved:
[billy@ws1 OpenLDAP]$ slapadd -l add_clusterdb_hlr.txt 091009 12:41:44 [Note] NDB Binlog: CREATE TABLE Event: REPL$clusterdb/OL_dn2id 091009 12:41:45 [Note] NDB Binlog: CREATE TABLE Event: REPL$clusterdb/OL_nextid 091009 12:41:46 [Note] NDB Binlog: CREATE TABLE Event: REPL$clusterdb/OL_opattrs 091009 12:41:46 [Note] NDB Binlog: CREATE TABLE Event: REPL$clusterdb/billy 091009 12:41:47 [Note] NDB Binlog: CREATE TABLE Event: REPL$clusterdb/dcObject 091009 12:41:48 [Note] NDB Binlog: CREATE TABLE Event: REPL$clusterdb/organization .#################### 100.00% eta none elapsed spd 627.0 /s Closing DB... [billy@ws1 OpenLDAP]$ ldapsearch -x -b 'dc=clusterdb,dc=com' # extended LDIF # # LDAPv3 # base <dc=clusterdb,dc=com> with scope subtree # filter: (objectclass=*) # requesting: ALL # # 97, clusterdb.com dn: clusterdbsubid=97,dc=clusterdb,dc=com objectClass: clusterdbhlrrecord clusterdbsubid: 97 clusterdbimsi: 456123123456788 clusterdbmsisdn: 611231234512344 clusterdbvlrnumber: 611230000000000 clusterdbsmscnumber: 611230000000001 clusterdbsmscount: 0 # clusterdb.com dn: dc=clusterdb,dc=com objectClass: dcObject objectClass: organization dc: clusterdb o: GSM PlC description: HLR operator # 12, clusterdb.com dn: clusterdbsubid=12,dc=clusterdb,dc=com objectClass: clusterdbhlrrecord clusterdbsubid: 12 clusterdbimsi: 456123123456789 clusterdbmsisdn: 611231234512345 clusterdbvlrnumber: 611230000000000 clusterdbsmscnumber: 611230000000001 clusterdbsmscount: 2 # search result search: 2 result: 0 Success # numResponses: 4 # numEntries: 3
As you can see, the ‘contractstart’ field is ignored by OpenLDAP but we can work with it through SQL:
[billy@ws1 OpenLDAP]$ mysql -u root; Welcome to the MySQL monitor. Commands end with ; or g. Your MySQL connection id is 24 Server version: 5.1.37-ndb-7.0.8a Source distribution Type 'help;' or 'h' for help. Type 'c' to clear the current input statement. mysql> use clusterdb; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed mysql> update clusterdbhlrrecord set contractstart='2009-01-04' where clusterdbsubid=12; Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 mysql> select * from clusterdbhlrrecord; +-----+-----+----------------+-----------------+-----------------+--------------------+---------------------+-------------------+--------------+-----------------+---------------+ | eid | vid | clusterdbsubid | clusterdbimsi | clusterdbmsisdn | clusterdbvlrnumber | clusterdbsmscnumber | clusterdbsmscount | clusterdbcfu | clusterdbcfnryt | contractstart | +-----+-----+----------------+-----------------+-----------------+--------------------+---------------------+-------------------+--------------+-----------------+---------------+ | 3 | 0 | 97 | 456123123456788 | 611231234512344 | 611230000000000 | 611230000000001 | 0 | NULL | NULL | NULL | | 2 | 0 | 12 | 456123123456789 | 611231234512345 | 611230000000000 | 611230000000001 | 2 | NULL | NULL | 2009-01-04 | +-----+-----+----------------+-----------------+-----------------+--------------------+---------------------+-------------------+--------------+-----------------+---------------+
This example builds upon Example 2 by showing how rows can be added to the clusterdbhlrrecord and then be accessed using LDAP.
The first step is to just add the row:
mysql> insert into clusterdbhlrrecord values (4,0,101,456231234554321,61777777777,611230000000000, -> 611230000000000,0,NULL,NULL,'2008-01-01'); Query OK, 1 row affected (0.00 sec)
When we try to read this entry through LDAP, it can’t be found:
[billy@ws1 OpenLDAP]$ ldapsearch -x -b 'clusterdbsubid=101,dc=clusterdb,dc=com' # extended LDIF # # LDAPv3 # base <clusterdbsubid=101,dc=clusterdb,dc=com> with scope subtree # filter: (objectclass=*) # requesting: ALL # # search result search: 2 result: 32 No such object matchedDN: dc=clusterdb,dc=com # numResponses: 1
The reason for this is that this row doesn’t yet have a corresponding entry in the OL_dn2id table; that can now be fixed:
mysql> insert into OL_dn2id values (4,'clusterdbhlrrecord @ top','dc=com','dc=clusterdb','clusterdbsubid=101','','','','','','','','','','','','',''); Query OK, 1 row affected (0.01 sec) [billy@ws1 OpenLDAP]$ ldapsearch -x -b 'clusterdbsubid=101,dc=clusterdb,dc=com' # extended LDIF # # LDAPv3 # base <clusterdbsubid=101,dc=clusterdb,dc=com> with scope subtree # filter: (objectclass=*) # requesting: ALL # # 101, clusterdb.com dn: clusterdbsubid=101,dc=clusterdb,dc=com objectClass: clusterdbhlrrecord clusterdbsubid: 101 clusterdbimsi: 456231234554321 clusterdbmsisdn: 61777777777 clusterdbvlrnumber: 611230000000000 clusterdbsmscnumber: 611230000000000 clusterdbsmscount: 0 # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1
If you want to hide this extra step from the application then you can of course use stored procedures to automatically add the extra row to OL_dn2id.
6.3.27a source release is now available from ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/
The source version for MySQL Cluster 6.3.27 has now been made available at ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.37-ndb-6.3.27/
You can either wait for the binaries to be released or if you’re in a rush then you can find instructions on building the binaries for yourself in the earlier article: “MySQL Cluster 7.0.7 source released“.
A description of all of the changes (fixes) that have gone into MySQL Cluster 6.3.27 (compared to 6.3.26) can be found in the MySQL Cluster 6.3.27 Change Log.
7.0.8aa source release is now available from ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/
The source version for MySQL Cluster 7.0.8 has now been made available at ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.37-ndb-7.0.8/
You can either wait for the binaries to be released or if you’re in a rush then you can find instructions on building the binaries for yourself in the earlier article: “MySQL Cluster 7.0.7 source released“.
A description of all of the changes (fixes) that have gone into MySQL Cluster 7.0.8 (compared to 7.0.7) can be found in the MySQL Cluster 7.0.8 Change Log.
As network use grows and services become more dynamic, so existing Authentication, Authorization and Accounting (AAA) environments can struggle to keep pace with demand.
Tune into this webinar where you can hear from the Alan Dekok, one of the founders of the FreeRADIUS project and CEO of Network RADIUS, discuss the concepts and implementation of RADIUS services using the FreeRADIUS server and the MySQL Cluster database to deliver highly available and scalable AAA services.
As always, this webinar is free and you can register here. I will be manning the Q&A during the webinar.
In this session, you will learn about:
WHO:
Alan Dekok, Founder of the FreeRADIUS project and CEO of Network RADIUS
Matthew Keep, MySQL Cluster Product Management
WHAT:
FreeRADIUS & MySQL Cluster: Scalable and Highly Available AAA Services web presentation.
WHEN:
Wednesday, September 30, 2009: 09:30 Pacific time (America)
Wed, Sep 30: 06:30 Hawaii time
Wed, Sep 30: 10:30 Mountain time (America)
Wed, Sep 30: 11:30 Central time (America)
Wed, Sep 30: 12:30 Eastern time (America)
Wed, Sep 30: 16:30 UTC
Wed, Sep 30: 17:30 Western European time
Wed, Sep 30: 18:30 Central European time
Wed, Sep 30: 19:30 Eastern European time
The presentation will be approximately 45 minutes long followed by Q&A.
WHERE:
Simply access the web seminar from the comfort of your own office.
WHY:
To learn more about how you can use FreeRADIUS and MySQL Cluster 7.0
Update: You can now download a recording of the webinar and the slides from http://www.mysql.com/news-and-events/on-demand-webinars/display-od-403.html
I’ll be presenting the fourth (and final) session of the MySQL for Online Applications webinar series today (29 September). Today’s High Availability Architectures for Online Applications webinar covers:
This session starts at 10:00 am Pacific Time but will be rerun tomorrow at 10:00 am CET (9:00 am UK) with Ivan Zoratti presenting (I’ll be handling questions).
More details for today’s webinar:
Tuesday, September 29, 2009
Join us for the last of our 4 part webinar series exploring the different aspects of using MySQL as the backend database for online applications. With real life experience gained working with MySQL Customers such as Facebook, Alcatel Lucent and Google, this webinar series will give you the information you need to run scalable, highly available online applications.
In this last installment we look at MySQL high availability technologies and architectures. We will explore the uses cases for implementing:
Also, covered will be the fundamentals of how these technologies work and how they can be combined to create a more scalable and highly available database infrastructure. Several case studies will be presented to show how these technologies have been implemented in the real world.
Whether you are already using MySQL for your online application or considering it for a new project then register today to learn how you can make best use of the world’s most popular database for online applications.
Andrew Morgan, Senior Product Manager, MySQL
High Availability Architectures for Online Applications web presentation.
Tuesday, September 29, 2009: 10:00 Pacific time (America)
| Tue, Sep 29: | 07:00 Hawaii time |
| Tue, Sep 29: | 11:00 Mountain time (America) |
| Tue, Sep 29: | 12:00 Central time (America) |
| Tue, Sep 29: | 13:00 Eastern time (America) |
| Tue, Sep 29: | 17:00 UTC |
| Tue, Sep 29: | 18:00 Western European time |
| Tue, Sep 29: | 19:00 Central European time |
| Tue, Sep 29: | 20:00 Eastern European time |
MySQL/Sun have releases a new white paper…
Do you want to ensure that your Authentication, Authorization and Accounting (AAA) infrastructure will scale to support your business growth?
As network use grows and services become more dynamic, limitations can occur which add administrative overhead, inhibit flexible scaling and impact the timely synchronization of data across the AAA environment.
To address these challenges, Sun has collaborated with the FreeRADIUS server team, the most widely deployed RADIUS server in the world, to integrate the carrier-grade, real-time MySQL Cluster database with the FreeRADIUS Server.
Download our free whitepaper “Delivering Scalable and Highly Available Authentication, Authorization and Accounting Services” now to better understand:
The binaries for MySQL Cluster 7.0.7 have now been released and can be downloaded from http://dev.mysql.com/downloads/cluster/7.0.html
A description of all of the changes (fixes) that have gone into MySQL Cluster 7.0.7 (compared to 7.0.6) can be found in the MySQL Cluster 7.0.7 Change Log.
Update: As explained in “MySQL Cluster 7.0.7 binaries released” you can now download the compiled binaries for your particular platform. I am going to leave this entry in place as it will hopefully be useful for future releases but for 7.0.7 you should refer to that other post.
You’ll need to wait for the pre-built binaries but you can now download the source code and build it for yourself to get started. This article explains where to get it and how to build, install and test the installation.
In this example, I’ve used Ubuntu.
The first step is to download the compressed tar ball containing the source code by pointing your browser to ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.35-ndb-7.0.7/mysql-cluster-gpl-7.0.7.tar.gz
Then you need to extract the code and then build and install the software:
billy@billy-laptop:~/mysql$ tar -xzf mysql-cluster-gpl-7.0.7.tar.gz billy@billy-laptop:~/mysql$ mv mysql-cluster-gpl-7.0.7 7_0_7 billy@billy-laptop:~/mysql$ cd 7_0_7 billy@billy-laptop:~/mysql/7_0_7$ autoreconf --force --install billy@billy-laptop:~/mysql/7_0_7$ ./configure --with-plugins=max --prefix=/usr/local/mysql billy@billy-laptop:~/mysql/7_0_7$ make billy@billy-laptop:~/mysql/7_0_7$ sudo make install billy@billy-laptop:~/mysql/7_0_7$ sudo cp storage/ndb/src/kernel/ndbd /usr/local/mysql/bin billy@billy-laptop:~/mysql/7_0_7$ sudo cp storage/ndb/src/kernel/ndbmtd /usr/local/mysql/bin billy@billy-laptop:~/mysql/7_0_7$ sudo cp storage/ndb/src/mgmsrv/ndb_mgmd /usr/local/mysql/bin billy@billy-laptop:~/mysql/7_0_7$ cd /usr/local/mysql/mysql-test billy@billy-laptop:/usr/local/mysql/mysql-test$ sudo chmod 777 . billy@billy-laptop:/usr/local/mysql/mysql-test$ sudo chmod 777 *
You can then test that the installation has been successful:
billy@billy-laptop:/usr/local/mysql/mysql-test$ ./mtr ndb_basic Logging: ./mtr ndb_basic 090902 18:17:43 [Warning] Forcing shutdown of 2 plugins MySQL Version 5.1.35 Checking supported features... - using ndbcluster when necessary, mysqld supports it - skipping SSL, mysqld not compiled with SSL - multi threaded ndbd, will be used "round robin" Collecting tests... vardir: /usr/local/mysql/mysql-test/var Removing old var directory... Creating var directory '/usr/local/mysql/mysql-test/var'... Installing system database... Using server port 43993 ============================================================================== TEST RESULT TIME (ms) ------------------------------------------------------------ worker[1] Using MTR_BUILD_THREAD 250, with reserved ports 12500..12509 ndb.ndb_basic [ pass ] 73661 ------------------------------------------------------------ The servers were restarted 0 times Spent 73.661 of 143 seconds executing testcases All 1 tests were successful.
Following this you can configure and use the software as normal (refer to Creating a simple Cluster on a single LINUX host).
The annotated header information has already been updated in the NDB API Docs section.
A description of all of the changes (fixes) that have gone into MySQL Cluster 7.0.7 (compared to 7.0.6) can be found in the MySQL Cluster 7.0.7 Change Log.
Following requests received during earlier MySQL Cluster webinars, a new (and as always, free) webinar has been scheduled which focuses on MySQL Cluster Replication. The webinar is scheduled for Thursday 10 September and you can register at http://www.mysql.com/news-and-events/web-seminars/display-415.html
I’ll be on-line during the webinar, answering questions.
Details….
Thursday, September 10, 2009
MySQL Cluster has been deployed into some of the most demanding web, telecoms and enterprise / government workloads, supporting 99.999% availability with real time performance and linear write scalability.
Tune into this webinar where you can hear from the Director of MySQL Server Engineering provide a detailed “deep dive” into one of MySQL Cluster’s key capabilities – Geographic Replication.
In this session, you will learn how using Geographic Replication enables your applications to :
MySQL Cluster: Geographic Replication Deep-Dive web presentation.
Thursday, September 10, 2009: 09:30 Pacific time (America)
| Thu, Sep 10: | 06:30 Hawaii time |
| Thu, Sep 10: | 10:30 Mountain time (America) |
| Thu, Sep 10: | 11:30 Central time (America) |
| Thu, Sep 10: | 12:30 Eastern time (America) |
| Thu, Sep 10: | 16:30 UTC |
| Thu, Sep 10: | 17:30 Western European time |
| Thu, Sep 10: | 18:30 Central European time |
| Thu, Sep 10: | 19:30 Eastern European time |
The presentation will be approximately 45 minutes long followed by Q&A.
Simply access the web seminar from the comfort of your own office.
To learn more about how you can use Geographic Replication in MySQL Cluster 7.0 to build real time, high performance applications delivering continuously available database services.
