-
Notifications
You must be signed in to change notification settings - Fork 0
/
ReadME.txt
110 lines (48 loc) · 3.83 KB
/
ReadME.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
# SupportAssistant
SupportAssistant - is used by Dev/Support Engineer to setup the BigSQL for replicating a scenario/customer issues and analyse the BigSQL Logs.
**All the containers are created in a single physical machine so should not use this project for performance/load testing or in Production**
## Internal Architecture
Creates docker container based on the host names mentioned in conf/server & conf/agents. Docker container will have the same name has the host names. The ambari server will be installed in the container that have the name mentioned conf/server and Ambari Agents will be installed on all the container mentioned in conf/agents. After installing, ambari server & agents, installs the ambari bluprints for the dependent components and uses amabri rest API to install BigSQL.
Head node will be installed in the amabri server container and worker node will be installed only in one ambari agent container.
## Usage
**1) bin/setupDocker.sh** - Used to setup the Docker in a fresh Linux Machine.
**2) bin/setupCluster.sh** - Used to setup the container/cluster based on the nodes mentioned in the configuration files. The Amabri server will be created based on the hostname mentioned in conf/server. The Ambari agent containers will be created based on conf/agent. This script will install only the BigSQL and its dependent components.
*bin/setupCluster.sh createBigSQL* - The engineer need to provide the URL for ambari.repo file and BigSQL repository to setup BigSQL.
The path for Ambari repo is available in Hortonworks URL (https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.1.5/bk_ambari-installation/content/ambari_repositories.html )
To test the bigsql, User can login to ssh -p 21 root@localhost
Credentials are root/password or bigsql/passw0rd
Credentials for Ambari UI is admin/passw0rd
*bin/setupCluster.sh stop*
*bin/setupCluster.sh start*
**3) bin/kill_all.sh** - Used to kill the containers created by SupportAssistant.
**4) bin/setupCluster.sh createLogAnalyzer ** - Create the cluster for Log Analysis. If you
#Get the nodes information from Log Collector Script
tar -C . -zxvf <provideTheTarGZFileGotFromCustomerLogCollectorScript> nodes.info
# Update the ambari-Server and ambari-agent nodes
head -n 1 nodes.info > conf/server
tail -n +2 nodes.info > conf/agents
After updating the configuration file conf/server & conf/agents, run the setupCluster.sh createLogAnalyzer to setup the Log Analyzer.
**5) bin/logDistribute.sh** - Used for distributing the customer logs to existing log analyzer cluster. If the engineer uses the bin/setupCluster.sh createLogAnalyzer to setup the cluster, then to distribute the customer logs, support engineer has to run the log distribute script.
**6) bin/logDistribute.sh** - Used for distributing the customer logs to existing cluster. If the engineer uses the bin/setupCluster.sh createBigSQL or bin/setupCluster.sh createLogAnalyzer to setup the cluster, then to distribute the customer logs, support engineer has to run the log distribute script.
## Author
**Nisanth Simon** - [NisanthSimon@LinkedIn]
[NisanthSimon@LinkedIn]: https://au.linkedin.com/in/nisanth-simon-03b2149