When a new product is announced, the word goes out about its features. If the product sounds like a good thing, then you wonder, "What would it be like to use it?" Our new product how-to series answers that question. Each how-to starts out with the basics -- product and vendor name, price, etc. -- and then gets down to business with a short how-to. This how-to about installation was written by Eero Teerikorpi, CEO of Emic Networks of San Jose, Calif.
What: Emic m/cluster
Type of product A single-image MySQL application cluster
Vendor: Emic Networks provides application clustering solutions for the LAMP (Linux, Apache, MySQL and PHP/Python/PERL) stack, including offer Emic lamp/cluster, Emic lamj/cluster, Emic m/cluster for MySQL and Emic a/cluster for Apache.
Value proposition: Emic m/cluster offers a single-image MySQL cluster which provides high availability, linear scalability and dynamic load balancing between cluster nodes. The core architecture of m/cluster is designed in a way that it allows use of commodity hardware and does not require any special hardware devices like storage area networks or load balancers.
Availability Available now
Pricing: Starts at $1595
How-to: This is an overview of the Emic m/cluster installation process, starting with the four basic steps and then drilling down to more information about each step.
1. Prepare for the installation by checking the hardware and software requirements and defining the m/cluster configuration values. For details, see the section called installation prerequisites below.
2. Install the m/cluster service separately on each node. For details, see the installing the m/cluster service on each node section below.
3. After you have successfully installed the m/cluster service on all nodes of the cluster, you can activate the cluster by bringing the nodes online. For details, see activating the cluster below.
4. After activating the cluster, test that it is operating correctly. For details, see testing the operation of Emic m/cluster below.
Here are the drilldown sections:
Before attempting to install the m/cluster service, make sure you have met the hardware and software requirements. Here's a brief overview of the hardware requirements: X86 or AMD64 compatible computer; 500MHz or higher CPUs; 512MB (minimum) RAM; 4 GB IDE or SCSI disk with at least 30 MB free disk space under /usr/local; TCP/IP-based network; and a minimum of three physical network interface cards (NIC).
You also must define the network configuration values. This helps ensure that the values you use to create the network configuration file are accurate. Check the documentation to define the Emic m/cluster Configuration Values. Information is provided instructing how to define the configuration values for the public network; MySQL configuration; and private network configuration. The parameter definitions in the documentation will help ensure the values you use to create your network configuration file are accurate. Apply the values you define to every node in the cluster.
RUN THE INSTALLATION/CONFIGURATION SCRIPT
The installation program provides detailed instructions for installing the m/cluster MySQL service. The user interface should be intuitive for most system administrators.
Successful completion of the installation results in the following:
- Installation of all binary files, scripts, libraries etc.
- Creation of a configuration file based on the values that you have determined for public network configuration; MySQL configuration; and private network configurations on individual nodes.
Following a successful installation, you should be able to bring one or more nodes online to access MySQL through the cluster.
ACTIVATING THE CLUSTER
After the successful installation of one or more nodes, you can bring the node(s) online using this command on the Cluster Management Console to enable access to MySQL through the m/cluster service. After the nodes have been successfully activated, the Emic m/cluster is ready for use.
TESTING THE OPERATION OF EMIC M/CLUSTER
To confirm that the cluster is operational, perform a simple test example that is provided in the Installation Manual for each node in the cluster, using the Private Network IP Address specific to each node.
For more information: