Documentation Home
MySQL 5.7 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 36.5Mb
PDF (A4) - 36.5Mb
Man Pages (TGZ) - 238.1Kb
Man Pages (Zip) - 349.8Kb
Info (Gzip) - 3.4Mb
Info (Zip) - 3.4Mb
Excerpts from this Manual

MySQL 5.7 Reference Manual  /  ...  /  The NDB Cluster Auto-Installer (NDB 7.6) (No longer supported)

21.3.9 The NDB Cluster Auto-Installer (NDB 7.6) (No longer supported)


This feature has been removed from NDB Cluster, and is no longer supported. See Section 21.2.4, “What is New in NDB Cluster”, for more information.

This section describes the web-based graphical configuration installer included as part of the NDB Cluster 7.6 distribution. This version of the installer differs in many respects from that supplied with NDB 7.5 and earlier releases; if you are using NDB 7.5, see Section 21.3.8, “The NDB Cluster Auto-Installer (NDB 7.5) (No longer supported)”, for relevant information. Some of the key improvements are listed here:

  • Persistent storage in an encrypted file as an alternative to cookie-based storage, now used by default

  • Secure (HTTPS) connections by default

  • Upgraded Paramiko security library

  • Ability to use passwords for encrypted private keys, and to use different credentials with different hosts

  • Improved host information retrieval

  • Improved configuration; advanced configuration parameters

See also Section, “What is New in NDB Cluster 7.6”.

Topics discussed in the following sections include an overview of the installer and its parts, software and other requirements for running the installer, navigating the GUI, and using the installer to set up and start or stop an NDB Cluster on one or more host computers.

The NDB Cluster Auto-Installer is made up of two components. The front end is a GUI client implemented as a Web page that loads and runs in a standard Web browser such as Firefox or Microsoft Internet Explorer. The back end is a server process ( that runs on the local machine or on another host to which you have access.

These two components (client and server) communicate with each other using standard HTTP requests and responses. The back end can manage NDB Cluster software programs on any host where the back end user has granted access. If the NDB Cluster software is on a different host, the back end relies on SSH for access, using the Paramiko library for executing commands remotely (see Section, “NDB Cluster Auto-Installer Requirements”).