#### 23.3.8.2 Using the NDB Cluster Auto-Installer

[]()

 The NDB Cluster Auto-Installer interface is made up of several pages, each corresponding to a step in the process used to configure and deploy an NDB Cluster. These pages are listed here, in order:

* **[Welcome](mysql-cluster-installer-using.html#mysql-cluster-installer-using-welcome)**: Begin using the Auto-Installer by choosing either to configure a new NDB Cluster, or to continue configuring an existing one.

* **[Define Cluster](mysql-cluster-installer-using.html#mysql-cluster-installer-using-define-cluster)**: Set basic information about the cluster as a whole, such as name, hosts, and load type. Here you can also set the SSH authentication type for accessing remote hosts, if needed.

* **[Define Hosts](mysql-cluster-installer-using.html#mysql-cluster-installer-using-define-hosts)**: Identify the hosts where you intend to run NDB Cluster processes.

* **[Define Processes](mysql-cluster-installer-using.html#mysql-cluster-installer-using-define-processes)**: Assign one or more processes of a given type or types to each cluster host.

* **[Define Parameters](mysql-cluster-installer-using.html#mysql-cluster-installer-using-define-parameters)**: Set configuration attributes for processes or types of processes.

* **[Deploy Configuration](mysql-cluster-installer-using.html#mysql-cluster-installer-using-deploy-configuration)**: Deploy the cluster with the configuration set previously; start and stop the deployed cluster.

##### NDB Cluster Installer Settings and Help Menus

 These menus are shown on all screens except for the **Welcome** screen. They provide access to installer settings and information. The Settings menu is shown here in more detail:

[]()

**Figure 23.6 NDB Cluster Auto-Installer Settings menu**

<img alt="Content is described in the surrounding text." src="images/settings-menu.png" height="300" width="400" />

 The Settings menu has the following entries:

* Automatically save configuration as cookies: Save your configuration information—such as host names, process data, and parameter values—as a cookie in the browser. When this option is chosen, all information except any SSH password is saved. This means that you can quit and restart the browser, and continue working on the same configuration from where you left off at the end of the previous session. This option is enabled by default.

   The SSH password is never saved; if you use one, you must supply it at the beginning of each new session.

* Show advanced configuration options: Shows by default advanced configuration parameters where available.

   Once set, the advanced parameters continue to be used in the configuration file until they are explicitly changed or reset. This is regardless of whether the advanced parameters are currently visible in the installer; in other words, disabling the menu item does not reset the values of any of these parameters.

   You can also toggle the display of advanced parameters for individual processes on the [**Define Parameters** screen](mysql-cluster-installer-using.html#mysql-cluster-installer-using-define-parameters).

   This option is disabled by default.

* Automatically get resource information for new hosts: Query new hosts automatically for hardware resource information to pre-populate a number of configuration options and values. In this case, the suggested values are not mandatory, but they are used unless explicitly changed using the appropriate editing options in the installer.

   This option is enabled by default.

 The installer Help menu is shown here:

[]()

**Figure 23.7 NDB Cluster Auto-Installer Help menu**

<img alt="Content is described in the surrounding text." src="images/help-menu.png" height="300" width="400" />

 The Help menu provides several options, described in the following list:

* Contents: Show the built-in user guide. This is opened in a separate browser window, so that it can be used simultaneously with the installer without interrupting workflow.

* Current page: Open the built-in user guide to the section describing the page currently displayed in the installer.

* About: open a dialog displaying the installer name and the version number of the NDB Cluster distribution with which it was supplied.

 The Auto-Installer also provides context-sensitive help in the form of tooltips for most input widgets.

 In addition, the names of most NDB configuration parameters are linked to their descriptions in the online documentation. The documentation is displayed in a separate browser window.

 The next section discusses starting the Auto-Installer. The sections immediately following it describe in greater detail the purpose and function of each of these pages in the order listed previously.

##### Starting the NDB Cluster Auto-Installer

[]()

 The Auto-Installer is provided together with the NDB Cluster software. Separate RPM and `.deb` packages containing only the Auto-Installer are also available for many Linux distributions. (See [Section 23.3, “NDB Cluster Installation”](mysql-cluster-installation.html).)

 The present section explains how to start the installer. You can do by invoking the [**ndb\_setup.py**](mysql-cluster-programs-ndb-setup-py.html) executable.

User and privileges

 You should run the [**ndb\_setup.py**](mysql-cluster-programs-ndb-setup-py.html) as a normal user; no special privileges are needed to do so. You should *not* run this program as the `mysql` user, or using the system `root` or Administrator account; doing so may cause the installation to fail.

[**ndb\_setup.py**](mysql-cluster-programs-ndb-setup-py.html) is found in the `bin` within the NDB Cluster installation directory; a typical location might be `/usr/local/mysql/bin` on a Linux system or `C:\Program Files\MySQL\MySQL Server 8.0\bin` on a Windows system. This can vary according to where the NDB Cluster software is installed on your system, and the installation method.

 On Windows, you can also start the installer by running **setup.bat** in the NDB Cluster installation directory. When invoked from the command line, this batch file accepts the same options as [**ndb\_setup.py**](mysql-cluster-programs-ndb-setup-py.html).

[]()[]()

[**ndb\_setup.py**](mysql-cluster-programs-ndb-setup-py.html) can be started with any of several options that affect its operation, but it is usually sufficient to allow the default settings be used, in which case you can start [**ndb\_setup.py**](mysql-cluster-programs-ndb-setup-py.html) by either of the following two methods:

1. Navigate to the NDB Cluster `bin` directory in a terminal and invoke it from the command line, without any additional arguments or options, like this:

   ```
   $> ndb_setup.py
   Running out of install dir: /usr/local/mysql/bin
   Starting web server on port 8081
   URL is https://localhost:8081/welcome.html
   deathkey=627876
   Press CTRL+C to stop web server.
   The application should now be running in your browser.
   (Alternatively you can navigate to https://localhost:8081/welcome.html to start it)
   ```

    This works regardless of operating platform.

2. Navigate to the NDB Cluster `bin` directory in a file browser (such as Windows Explorer on Windows, or Konqueror, Dolphin, or Nautilus on Linux) and activate (usually by double-clicking) the ndb\_setup.py file icon. This works on Windows, and should work with most common Linux desktops as well.

    On Windows, you can also navigate to the NDB Cluster installation directory and activate the setup.bat file icon.

 In either case, once [**ndb\_setup.py**](mysql-cluster-programs-ndb-setup-py.html) is invoked, the Auto-Installer's [**Welcome** screen](mysql-cluster-installer-using.html#mysql-cluster-installer-using-welcome) should open in the system's default web browser. If not, you should be able to open the page `http://localhost:8081/welcome.html` or `https://localhost:8081/welcome.html` manually in the browser.

 In some cases, you may wish to use non-default settings for the installer, such as specifying HTTPS for connections, or a different port for the Auto-Installer's included web server to run on, in which case you must invoke [**ndb\_setup.py**](mysql-cluster-programs-ndb-setup-py.html) with one or more startup options with values overriding the necessary defaults. The same startup options can be used on Windows systems with the **setup.bat** file supplied for such platforms in the NDB Cluster software distribution. This can be done using the command line, but if you want or need to start the installer from a desktop or file browser while employing one or more of these options, it is also possible to create a script or batch file containing the proper invocation, then to double-click its file icon in the file browser to start the installer. (On Linux systems, you might also need to make the script file executable first.) If you plan to use the Auto-Installer from a remote host, you should start using the `-S` option. For information about this and other advanced startup options for the NDB Cluster Auto-Installer, see [Section 23.5.26, “ndb\_setup.py — Start browser-based Auto-Installer for NDB Cluster (DEPRECATED)”](mysql-cluster-programs-ndb-setup-py.html).

##### NDB Cluster Auto-Installer Welcome Screen

[]()

 The **Welcome** screen is loaded in the default browser when [**ndb\_setup.py**](mysql-cluster-programs-ndb-setup-py.html) is invoked. The first time the Auto-Installer is run (or if for some other reason there are no existing configurations), this screen appears as shown here:

[]()

**Figure 23.8 The NDB Cluster Auto-Installer Welcome screen, first run**

<img alt="Content is described in the surrounding text." src="images/welcome-first-run.png" height="600" width="800" />

 In this case, the only choice of cluster listed is for configuration of a new cluster, and both the View Cfg and Continue buttons are inactive.

 To create a new configuration, enter and confirm a passphrase in the text boxes provided. When this has been done, you can click Continue to proceed to the **Define Cluster** screen where you can assign a name to the new cluster.

 If you have previously created one or more clusters with the Auto-Installer, they are listed by name. This example shows an existing cluster named `mycluster-1`:

[]()

**Figure 23.9 The NDB Cluster Auto-Installer Welcome screen, with previously created
cluster mycluster-1**

<img alt="Content is described in the surrounding text." src="images/welcome-previous-run.png" height="600" width="800" />

 To view the configuration for and work with a given cluster, select the radiobutton next to its name in the list, then enter and confirm the passphrase that was used to create it. When you have done this correctly, you can click View Cfg to view and edit this cluster's configuration.

##### NDB Cluster Auto-Installer Define Cluster Screen

[]()

 The **Define Cluster** screen is appears following the [**Welcome** screen](mysql-cluster-installer-using.html#mysql-cluster-installer-using-welcome), and is used for setting general properties of the cluster. The layout of the **Define Cluster** screen is shown here:

[]()

**Figure 23.10 The NDB Cluster Auto-Installer Define Cluster screen**

<img alt="Content is described in the surrounding text." src="images/define-cluster-start.png" height="600" width="800" />

 This screen and subsequent screens also include Settings and Help menus which are described later in this section; see [NDB Cluster Installer Settings and Help Menus](mysql-cluster-installer-using.html#mysql-install-auto-settings-help-menus).

 The **Define Cluster** screen allows you to set three sorts of properties for the cluster: cluster properties, SSH properties, and installation properties.

 Cluster properties that can be set on this screen are listed here:

* Cluster name: A name that identifies the cluster; in this example, this is `mycluster-1`. The name is set on the previous screen and cannot be changed here.

* Host list: A comma-delimited list of one or more hosts where cluster processes should run. By default, this is `127.0.0.1`. If you add remote hosts to the list, you must be able to connect to them using the credentials supplied as SSH properties.

* Application type: Choose one of the following:

  1. Simple testing: Minimal resource usage for small-scale testing. This the default. *Not intended for production environments*.

  2. Web: Maximize performance for the given hardware.

  3. Real-time: Maximize performance while maximizing sensitivity to timeouts in order to minimize the time needed to detect failed cluster processes.

* Write load: Choose a level for the anticipated number of writes for the cluster as a whole. You can choose any one of the following levels:

  1. Low: The expected load includes fewer than 100 write transactions for second.

  2. Medium: The expected load includes 100 to 1000 write transactions per second; this is the default.

  3. High: The expected load includes more than 1000 write transactions per second.

 SSH properties are described in the following list:

* Key-Based SSH: Check this box to use key-enabled login to the remote host. If checked, the key user and passphrase must also be supplied; otherwise, a user and password for a remote login account are needed.

* User: Name of user with remote login access.

* Password: Password for remote user.

* Key user: Name of the user for whom the key is valid, if not the same as the operating system user.

* Key passphrase: Passphrase for the key, if required.

* Key file: Path to the key file. The default is `~/.ssh/id_rsa`.

 The SSH properties set on this page apply to all hosts in the cluster. They can be overridden for a given host by editing that hosts's properties on the **Define Hosts** screen.

 Two installation properties can also be set on this screen:

* Install MySQL Cluster: This setting determines the source from which the Auto-Installer installs NDB Cluster software, if any, on the cluster hosts. Possible values and their effects are listed here:

  1. `DOCKER`: Try to install the MySQL Cluster Docker image from `https://hub.docker.com/r/mysql/mysql-cluster/` on each host

  2. `REPO`: Try to install the NDB Cluster software from the [MySQL Repositories](https://repo.mysql.com/) on each host

  3. `BOTH`: Try to install either the Docker image or the software from the repository on each host, giving preference to the repository

  4. `NONE`: Do not install the NDB Cluster software on the hosts; this is the default

* Open FW Ports: Check this check box to have the installer attempt to open ports required by NDB CLuster processes on all hosts.

 The next figure shows the **Define Cluster** page with settings for a small test cluster with all nodes running on `localhost`:

[]()

**Figure 23.11 The NDB Cluster Auto-Installer Define Cluster screen, with settings for
a test cluster**

<img alt="Content is described in the surrounding text." src="images/define-cluster-local-setup.png" height="800" width="800" />

 After making the desired settings, you can save them to the configuration file and proceed to the **Define Hosts** screen by clicking the Save & Next button.

 If you exit the installer without saving, no changes are made to the configuration file.

##### NDB Cluster Auto-Installer Define Hosts Screen

[]()

 The **Define Hosts** screen, shown here, provides a means of viewing and specifying several key properties of each cluster host:

[]()

**Figure 23.12 NDB Cluster Define Hosts screen, start**

<img alt="Content is described in the surrounding text." src="images/define-hosts-start.png" height="600" width="1000" />

 Properties shown include the following:

* Host: Name or IP address of this host

* Res.info: Shows `OK` if the installer was able to retrieve requested resource information from this host

* Platform: Operating system or platform

* Memory (MB): Amount of RAM on this host

* Cores: Number of CPU cores available on this host

* MySQL Cluster install directory: Path to directory where the NDB Cluster software is installed on this host; defaults to `/usr/local/bin`

* MySQL Cluster data directory: Path to directory used for data by NDB Cluster processes on this host; defaults to `/var/lib/mysql-cluster`.

* DiskFree: Free disk space in bytes

   For hosts with multiple disks, only the space available on the disk used for the data directory is shown.

 This screen also provides an extended view for each host that includes the following properties:

* FDQN: This host's fully qualified domain name, used by the installer to connect with it, distribute configuration information to it, and start and stop cluster processes on it.

* Internal IP: The IP address used for communication with cluster processes running on this host by processes running elsewhere.

* OS Details: Detailed operating system name and version information.

* Open FW: If this check box is enabled, the installer attempts to open ports in the host's firewall needed by cluster processes.

* REPO URL: URL for MySQL NDB Cluster repository

* DOCKER URL: URL for MySQL NDB CLuster Docker images; for NDB 8.0, this is `mysql/mysql-cluster:8.0`.

* Install: If this check box is enabled, the Auto-Installer attempts to install the NDB Cluster software on this host

 The extended view is shown here:

[]()

**Figure 23.13 NDB Cluster Define Hosts screen, extended host info view**

<img alt="Content is described in the surrounding text." src="images/define-hosts-extended.png" height="600" width="1000" />

 All cells in the display are editable, with the exceptions of those in the Host, Res.info, and FQDN columns.

 Be aware that it may take some time for information to be retrieved from remote hosts. Fields for which no value could be retrieved are indicated with an ellipsis (`…`). You can retry the fetching of resource information from one or more hosts by selecting the hosts in the list and then clicking the Refresh selected host(s) button.

[]()

###### Adding and Removing Hosts

 You can add one or more hosts by clicking the Add Host button and entering the required properties where indicated in the Add new host dialog, shown here:

[]()

**Figure 23.14 NDB Cluster Add Host dialog**

<img alt="Content is described in the surrounding text." src="images/add-host-widget.png" height="405" width="250" />

 This dialog includes the following fields:

* Host name: A comma-separated list of one or more host names, IP addresses, or both. These must be accessible from the host where the Auto-Installer is running.

* Host internal IP (VPN): If you are setting up the cluster to run on a VPN or other internal network, enter the IP address or addresses used for contact by cluster nodes on other hosts.

* Key-based auth: If checked, enables key-based authentication. You can enter any additional needed information in the User, Passphrase, and Key file fields.

* Ordinary login: If accessing this host using a password-based login, enter the appropriate information in the User and Password fields.

* Open FW ports: Selecting this check box allows the installer try opening any ports needed by cluster processes in this host's firewall.

* Configure installation: Checking this allows the Auto-Install to attempt to set up the NDB Cluster software on this host.

 To save the new host and its properties, click Add. If you wish to cancel without saving any changes, click Cancel instead.

 Similarly, you can remove one or more hosts using the button labelled Remove selected host(s). *When you remove a host, any process which was configured for that host is also removed*.

Warning

Remove selected host(s) acts immediately. There is no confirmation dialog. If you remove a host in error, you must re-enter its name and properties manually using Add host.

 If the SSH user credentials on the [*Define Cluster* screen](mysql-cluster-installer-using.html#mysql-cluster-installer-using-define-cluster) are changed, the Auto-Installer attempts to refresh the resource information from any hosts for which information is missing.

 You can edit the host's platform name, hardware resource information, installation directory, and data directory by clicking the corresponding cell in the grid, by selecting one or more hosts and clicking the button labelled Edit selected host(s). This causes a dialog box to appear, in which these fields can be edited, as shown here:

[]()

**Figure 23.15 NDB Cluster Auto-Installer Edit Hosts dialog**

<img alt="Content is described in the surrounding text." src="images/edit-host-widget.png" height="525" width="650" />

 When more than one host is selected, any edited values are applied to all selected hosts.

 Once you have entered all desired host information, you can use the Save & Next button to save the information to the cluster's configuration file and proceed to the [**Define Processes** screen](mysql-cluster-installer-using.html#fig-mysql-cluster-installer-define-processes), where you can set up NDB Cluster processes on one or more hosts.

##### NDB Cluster Auto-Installer Define Processes Screen

[]()

 The **Define Processes** screen, shown here, provides a way to assign NDB Cluster processes (nodes) to cluster hosts:

[]()

**Figure 23.16 NDB Cluster Auto-Installer Define Processes dialog**

<img alt="Content is described in the surrounding text. The example process tree topology includes "Any host" and "localhost", as defined earlier. The localhost tree includes the following processes: Management mode 1, API node 1, API node 2, API node 3, SQL node 1, SQL node 2, Multi threaded data node 1, and Multi threaded data node 2. This panel also includes "Add process" and "Del[ete] process" buttons." src="images/define-processes-start.png" height="435" width="600" />

 This screen contains a process tree showing cluster hosts and processes set up to run on each one, as well as a panel which displays information about the item currently selected in the tree.

 When this screen is accessed for the first time for a given cluster, a default set of processes is defined for you, based on the number of hosts. If you later return to the [**Define Hosts** screen](mysql-cluster-installer-using.html#mysql-cluster-installer-using-define-hosts), remove all hosts, and add new hosts, this also causes a new default set of processes to be defined.

 NDB Cluster processes are of the types described in this list:

* **Management node.**  Performs administrative tasks such as stopping individual data nodes, querying node and cluster status, and making backups. Executable: [**ndb\_mgmd**](mysql-cluster-programs-ndb-mgmd.html).

* **Single-threaded data node.**  Stores data and executes queries. Executable: [**ndbd**](mysql-cluster-programs-ndbd.html).

* **Multi threaded data node.**  Stores data and executes queries with multiple worker threads executing in parallel. Executable: [**ndbmtd**](mysql-cluster-programs-ndbmtd.html).

* **SQL node.**  MySQL server for executing SQL queries against [`NDB`](mysql-cluster.html). Executable: [**mysqld**](mysqld.html).

* **API node.**  A client accessing data in [`NDB`](mysql-cluster.html) by means of the NDB API or other low-level client API, rather than by using SQL. See [MySQL NDB Cluster API Developer Guide](https://dev.mysql.com/doc/ndbapi/en/), for more information.

 For more information about process (node) types, see [Section 23.2.1, “NDB Cluster Core Concepts”](mysql-cluster-basics.html).

 Processes shown in the tree are numbered sequentially by type, for each host—for example, `SQL node 1`, `SQL node 2`, and so on—to simplify identification.

 Each management node, data node, or SQL process must be assigned to a specific host, and is not allowed to run on any other host. An API node *may* be assigned to a single host, but this is not required. Instead, you can assign it to the special Any host entry which the tree also contains in addition to any other hosts, and which acts as a placeholder for processes that are allowed to run on any host. *Only API processes may use this Any host entry*.

**Adding processes.**  []() To add a new process to a given host, either right-click that host's entry in the tree, then select the Add process popup when it appears, or select a host in the process tree, and press the Add process button below the process tree. Performing either of these actions opens the add process dialog, as shown here:

[]()

**Figure 23.17 NDB Cluster Auto-Installer Add Process Dialog**

<img alt="Most content is described in the surrounding text. Shows a window titled "Add new process" with two options: "Select process type:" that shows a select box with "API node" selected, and "Enter process name:" with "API node 4" entered as plain text. Action buttons include "Cancel" and "Add"." src="images/add-process-widget.png" height="300" width="600" />

 Here you can select from among the available process types described earlier this section; you can also enter an arbitrary process name to take the place of the suggested value, if desired.

**Removing processes.**  []() To delete a process, select that process in the tree and use the Del process button.

 When you select a process in the process tree, information about that process is displayed in the information panel, where you can change the process name and possibly its type. You can change a multi-threaded data node ([**ndbmtd**](mysql-cluster-programs-ndbmtd.html)) to a single-threaded data node ([**ndbd**](mysql-cluster-programs-ndbd.html)), or the reverse, only; no other process type changes are allowed. *If you want to make a change between any other process types, you must delete the original process first, then add a new process of the desired type*.

##### NDB Cluster Auto-Installer Define Parameters Screen

[]()

 Like the [**Define Processes** screen](mysql-cluster-installer-using.html#mysql-cluster-installer-using-define-processes), this screen includes a process tree; the **Define Parameters** process tree is organized by process or node type, in groups labelled Management Layer, Data Layer, SQL Layer, and API Layer. An information panel displays information regarding the item currently selected. The **Define Attributes** screen is shown here:

[]()

**Figure 23.18 NDB Cluster Auto-Installer Define Parameters screen**

<img alt="Content is described in the surrounding text." src="images/define-parameters-start.png" height="600" width="800" />

 The check box labelled Show advanced configuration, when checked, makes advanced options for data node and SQL node processes visible in the information pane. These options are set and used whether or not they are visible. You can also enable this behavior globally by checking Show advanced configuration options under Settings (see [NDB Cluster Installer Settings and Help Menus](mysql-cluster-installer-using.html#mysql-install-auto-settings-help-menus)).

 You can edit attributes for a single process by selecting that process from the tree, or for all processes of the same type in the cluster by selecting one of the Layer folders. A per-process value set for a given attribute overrides any per-group setting for that attribute that would otherwise apply to the process in question. An example of such an information panel (for an SQL process) is shown here:

[]()

**Figure 23.19 Define Parameters—Process Attributes**

<img alt="Content is described in the surrounding text." src="images/define-parameters-process.png" height="675" width="800" />

 Attributes whose values can be overridden are shown in the information panel with a button bearing a plus sign. This + button activates an input widget for the attribute, enabling you to change its value. When the value has been overridden, this button changes into a button showing an X. The X button undoes any changes made to a given attribute, which immediately reverts to the predefined value.

 All configuration attributes have predefined values calculated by the installer, based such factors as host name, node ID, node type, and so on. In most cases, these values may be left as they are. If you are not familiar with it already, it is highly recommended that you read the applicable documentation before making changes to any of the attribute values. To make finding this information easier, each attribute name shown in the information panel is linked to its description in the online NDB Cluster documentation.

##### NDB Cluster Auto-Installer Deploy Configuration Screen

[]()

 This screen allows you to perform the following tasks:

* Review process startup commands and configuration files to be applied

* Distribute configuration files by creating any necessary files and directories on all cluster hosts—that is, *deploy* the cluster as presently configured

* Start and stop the cluster

 The **Deploy Configuration** screen is shown here:

[]()

**Figure 23.20 NDB Cluster Auto-Installer Deploy Configuration screen**

<img alt="Content is described in the surrounding text." src="images/deploy-configuration-start.png" height="675" width="800" />

 Like the [**Define Parameters** screen](mysql-cluster-installer-using.html#mysql-cluster-installer-using-define-parameters), this screen features a process tree which is organized by process type. Next to each process in the tree is a status icon indicating the current status of the process: connected (`CONNECTED`), starting (`STARTING`), running (`STARTED`), stopping (`STOPPING`), or disconnected (`NO_CONTACT`). The icon shows green if the process is connected or running; yellow if it is starting or stopping; red if the process is stopped or cannot be contacted by the management server.

 This screen also contains two information panels, one showing the startup command or commands needed to start the selected process. (For some processes, more than one command may be required—for example, if initialization is necessary.) The other panel shows the contents of the configuration file, if any, for the given process.

 This screen also contains four buttons, labelled as and performing the functions described in the following list:

* Install cluster: Nonfunctional in this release; implementation intended for a future release.

* Deploy cluster: Verify that the configuration is valid. Create any directories required on the cluster hosts, and distribute the configuration files onto the hosts. A progress bar shows how far the deployment has proceeded, as shown here, and a dialog is pisplayed when the deployment has completed, as shown here:

  []()

  **Figure 23.21 Cluster Deployment Process**

  <img alt="Content is described in the surrounding text." src="images/deploy-configuration-deploy-cluster.png" height="675" width="800" />

* Start cluster: The cluster is deployed as with Deploy cluster, after which all cluster processes are started in the correct order.

   Starting these processes may take some time. If the estimated time to completion is too large, the installer provides an opportunity to cancel or to continue of the startup procedure. A progress bar indicates the current status of the startup procedure, as shown here:

  []()

  **Figure 23.22 Cluster Startup Process with Progress Bar**

  <img alt="Content is described in the surrounding text." src="images/deploy-configuration-start-cluster.png" height="675" width="800" />

   The process status icons next to the items shown in the process tree also update with the status of each process.

   A confirmation dialog is shown when the startup process has completed, as shown here:

  []()

  **Figure 23.23 Cluster Startup, Process Completed Dialog**

  <img alt="Content is described in the surrounding text." src="images/deploy-configuration-start-cluster-started.png" height="675" width="800" />

* Stop cluster: After the cluster has been started, you can stop it using this. As with starting the cluster, cluster shutdown is not instantaneous, and may require some time complete. A progress bar, similar to that displayed during cluster startup, shows the approximate current status of the cluster shutdown procedure, as do the process status icons adjoining the process tree. The progress bar is shown here:

  []()

  **Figure 23.24 Cluster Shutdown Process, with Progress Bar**

  <img alt="Content is described in the surrounding text." src="images/deploy-configuration-stop-cluster.png" height="675" width="800" />

   A confirmation dialog indicates when the shutdown process is complete:

  []()

  **Figure 23.25 Cluster Shutdown, Process Completed Dialog**

  <img alt="Content is described in the surrounding text." src="images/deploy-configuration-stop-cluster-stopped.png" height="675" width="800" />

 The Auto-Installer generates a `config.ini` file containing NDB node parameters for each management node, as well as a `my.cnf` file containing the appropriate options for each [**mysqld**](mysqld.html) process in the cluster. No configuration files are created for data nodes or API nodes.

