{\rtf1\ansi\ansicpg1252\cocoartf1504\cocoasubrtf830
{\fonttbl\f0\fnil\fcharset0 AndaleMono;}
{\colortbl;\red255\green255\blue255;\red47\green255\blue18;\red0\green0\blue0;}
{\*\expandedcolortbl;;\cssrgb\c15686\c99608\c7843;\csgray\c0\c90000;}
\margl1440\margr1440\vieww18900\viewh20680\viewkind0
\pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\tx6160\tx6720\pardirnatural\partightenfactor0

\f0\fs24 \cf2 \cb3 \CocoaLigature0 root@mariaDB-PM1:/usr/local/mariadb/columnstore/bin# ./postConfigure -n\
\
This is the MariaDB ColumnStore System Configuration and Installation tool.\
It will Configure the MariaDB ColumnStore System and will perform a Package\
Installation of all of the Servers within the System that is being configured.\
\
IMPORTANT: This tool should only be run on the Parent OAM Module\
           which is a Performance Module, preferred Module #1\
\
Prompting instructions:\
\
	Press 'enter' to accept a value in (), if available or\
	Enter one of the options within [], if available, or\
	Enter a new value\
\
\
===== Setup System Server Type Configuration =====\
\
There are 2 options when configuring the System Server Type: single and multi\
\
  'single'  - Single-Server install is used when there will only be 1 server configured\
              on the system. It can also be used for production systems, if the plan is\
              to stay single-server.\
\
  'multi'   - Multi-Server install is used when you want to configure multiple servers now or\
              in the future. With Multi-Server install, you can still configure just 1 server\
              now and add on addition servers/modules in the future.\
\
Select the type of System Server install [1=single, 2=multi] (2) > 2\
\
\
===== Setup System Module Type Configuration =====\
\
There are 2 options when configuring the System Module Type: separate and combined\
\
  'separate' - User and Performance functionality on separate servers.\
\
  'combined' - User and Performance functionality on the same server\
\
Select the type of System Module Install [1=separate, 2=combined] (2) > 1\
\
Seperate Server Installation will be performed.\
\
NOTE: Local Query Feature allows the ability to query data from a single Performance\
      Module. Check MariaDB ColumnStore Admin Guide for additional information.\
\
Enable Local Query feature? [y,n] (n) > \
\
NOTE: The MariaDB ColumnStore Schema Sync feature will replicate all of the\
      schemas and InnoDB tables across the User Module nodes. This feature can be enabled\
      or disabled, for example, if you wish to configure your own replication post installation.\
\
MariaDB ColumnStore Schema Sync feature, do you want to enable? [y,n] (y) > \
\
\
NOTE: MariaDB ColumnStore Replication Feature is enabled\
\
NOTE: MariaDB ColumnStore Non-Distributed Install Feature is enabled\
\
Enter System Name (columnstore-1) > mariaDB-PM1\
\
\
===== Setup Storage Configuration =====\
\
\
----- Setup Performance Module DBRoot Data Storage Mount Configuration -----\
\
There are 3 options when configuring the storage: internal, external, or DataRedundancy\
\
  'internal' -    This is specified when a local disk is used for the DBRoot storage.\
                  High Availability Server Failover is not Supported in this mode\
\
  'external' -    This is specified when the DBRoot directories are mounted.\
                  High Availability Server Failover is Supported in this mode.\
\
  'DataRedundancy' - This is specified when gluster is installed and you want\
                  the DBRoot directories to be controlled by ColumnStore Data Redundancy.\
                  High Availability Server Failover is Supported in this mode.\
                  NOTE: glusterd service must be running and enabled on all PMs.\
\
Select the type of Data Storage [1=internal, 2=external, 3=DataRedundancy] (1) > 3\
\
===== Setup Memory Configuration =====\
\
NOTE: Setting 'NumBlocksPct' to 70%\
      Setting 'TotalUmMemory' to 50%\
\
===== Setup the Module Configuration =====\
\
\
----- User Module Configuration -----\
\
Enter number of User Modules [1,1024] (1) > \
\
*** User Module #1 Configuration ***\
\
Enter Nic Interface #1 Host Name (unassigned) > mariaDB-UM\
Enter Nic Interface #1 IP Address of mariaDB-UM (0.0.0.0) > 192.168.42.1\
Enter Nic Interface #2 Host Name (unassigned) > \
\
----- Performance Module Configuration -----\
\
Enter number of Performance Modules [1,1024] (1) > 2\
\
*** Parent OAM Module Performance Module #1 Configuration ***\
\
Enter Nic Interface #1 Host Name (mariaDB-PM1) > \
Enter Nic Interface #1 IP Address of mariaDB-PM1 (127.0.1.1) > 192.168.42.11\
Enter Nic Interface #2 Host Name (unassigned) > \
Enter the list (Nx,Ny,Nz) or range (Nx-Nz) of DBRoot IDs assigned to module 'pm1' (1) > \
\
*** Performance Module #2 Configuration ***\
\
Enter Nic Interface #1 Host Name (unassigned) > mariaDB-PM2\
Enter Nic Interface #1 IP Address of mariaDB-PM2 (0.0.0.0) > 192.168.42.12\
Enter Nic Interface #2 Host Name (unassigned) > \
Enter the list (Nx,Ny,Nz) or range (Nx-Nz) of DBRoot IDs assigned to module 'pm2' () > 1\
Invalid Entry, DBRoot ID 1 already assigned to 'pm1', please re-enter\
Enter the list (Nx,Ny,Nz) or range (Nx-Nz) of DBRoot IDs assigned to module 'pm2' () > 2\
\
\
===== Configuring MariaDB ColumnStore Data Redundancy Functionality =====\
\
\
Only 2 PMs configured. Setting number of copies at 2.\
\
----- Setup Data Redundancy Network Configuration -----\
\
  'existing'  -   This is specified when using previously configured network devices. (NIC Interface #1)\
                  No additional network configuration is required with this option.\
\
  'dedicated' -   This is specified when it is desired for Data Redundancy traffic to use\
                  a separate network than one previously configured for ColumnStore.\
                  You will be prompted to provide Hostname and IP information for each PM.\
\
\
Select the data redundancy network [1=existing, 2=dedicated] (1) > \
\
----- Performing Data Redundancy Configuration -----\
\
ERROR: failed to make directory(192.168.42.11): '/usr/local/mariadb/columnstore/bin/remote_command.sh 192.168.42.11  'mkdir -p /usr/local/mariadb/columnstore/gluster/brick1''}