Ambari (IX) --- use expect to realize no interaction in ambri server setup phase (valid for personal test)

Because of work , Multiple deployments are required ambari

ambari-server setup The frequent interactions between phases affect the experience of automated deployment

So I decided to write an automated script to avoid ambari-server setup Phase interaction , The selected tool is Expect

Used by bloggers Ambari The version is 2.6.0, There may be some differences between different versions ,
The following script contents have been verified by production

List of articles

Expect brief introduction

ambari-server setup Automation script

matters needing attention

One . Expect brief introduction

Expect It's based on tcl A tool based on ,
Expect It is a tool for automatic control and testing . Main solution shell Non interactive problems in scripts .

For specific introduction and use, please refer to this article :

Shell Programming No interaction expect

Two . ambari-server setup Automation script

Script directly , The script has undergone Production Validation ( Be careful : Verification scenario ambari2.6.0 For the first time setup)

Other versions , It may be necessary to make appropriate modifications according to the actual situation

#!/bin/bash
port=$1
password=$2
java_home=$3
hostname=$4

setup_ambari() {
    
  yum -y install expect >/dev/null 2>&1
  expect -c " set timeout -1; spawn ambari-server setup; expect { Customize* {send -- y\r;exp_continue;} daemon* {send -- ambari\r;exp_continue;} change* {send -- y\r;exp_continue;} choice* {send -- 3\r;exp_continue;} JAVA_HOME* {send -- $java_home\r;exp_continue;} configuration* {send -- y\r;exp_continue;} choice* {send -- 3\r;exp_continue;} Hostname* {send -- $hostname\r;exp_continue;} Port* {send -- ${port}\r;exp_continue;} name* {send -- \r;exp_continue;} Username* {send -- \r;exp_continue;} Password* {send -- ${password}\r;exp_continue;} Re-enter* {send -- ${password}\r;exp_continue;} connection* {send -- y\r;exp_continue;} eof {exit 0;} };"
}
setup_ambari

3、 ... and . matters needing attention

1. During scripting , If there is a problem , It is recommended to turn on debugging mode , Easy to locate problems

 Usage mode  expect -d

2. In my way , Keyword matching cannot have spaces , That is, there can only be one keyword , So the key point of writing is to find out the keywords of each interaction stage , otherwise : A matching exception will occur , The script does not execute as expected