-
Notifications
You must be signed in to change notification settings - Fork 0
/
Makefile
206 lines (179 loc) · 12.6 KB
/
Makefile
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
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
################################################################################################
# This Makefile is intended to make executing, building and testing of edgex services convinient
# This Makefile aims to acheive this using without docker
################################################################################################
# consul agent & executing environment variable export EDGEX_SECURITY_SECRET_STORE to false.
# The configuration is set to false so that current config can run without security.
start-consul-agent:
@nohup consul agent -ui -bootstrap -server -client 127.0.0.1 -bind 127.0.0.1 -advertise 127.0.0.1 -data-dir=tmp/consul -log-level=trace > ~/edgex-foundry/edgex-native-build-3.1-napa/edgex-service-logs/edgex-consul-agent/nohup.out 2>&1 &
@echo "::: EdgeX consul-agent is running... :::"
# This command forcefully kills consul, there is no information in edgex documentation on how to stop consul once we start it
kill-consul-agent:
@ps aux | grep 'consul agent' | grep -v grep | awk '{print $$2}' | xargs kill -15
@echo "::: EdgeX consul-agent has stopped working :::"
######################################################################################################
# The below section of Makefile contains single commands for executing and disabling an edgex service.
# User is allowed to have flexibility in choosing which service to enable and disable
# For fine tuning your configuration please change the directories mentioned in the commands below.
# You need to make sure all your services located in X folder are structured the same as the Makefile.
######################################################################################################
# core-common-config-bootstrapper service
# This service will exit once it has seeded the Configuration Provider with the common config. ( Based on documentation )
start-core-common-config-bootstrapper:
@cd edgex-go-3.1.1/cmd/core-common-config-bootstrapper && nohup ./core-common-config-bootstrapper -cp=consul.http://127.0.0.1:8500 -o > ~/edgex-foundry/edgex-native-build-3.1-napa/edgex-service-logs/core-common-config-bootstrapper/nohup.out 2>&1 &
@echo "::: core-common-config-bootstrapper has pushed configuraitons :::"
# edgex core-metadata service
start-core-metadata:
@cd edgex-go-3.1.1/cmd/core-metadata/ && nohup ./core-metadata -cp=consul.http://127.0.0.1:8500 -registry -o > ~/edgex-foundry/edgex-native-build-3.1-napa/edgex-service-logs/core-metadata/nohup.out 2>&1 &
@echo "::: EdgeX core-metadata is running... :::"
kill-core-metadata:
@ps aux | grep "core-metadata" | grep -v grep | awk '{print $$2}' | xargs kill -15 > /dev/null 2>&1 &
@echo "::: EdgeX core-metadata has stopped working :::"
# It's important to start the services as listed in the order from https://docs.edgexfoundry.org/3.1/getting-started/native/Ch-BuildRunOnLinuxDistro/#run-edgex
# edgex core-data service
start-core-data:
@cd edgex-go-3.1.1/cmd/core-data/ && nohup ./core-data -cp=consul.http://127.0.0.1:8500 -registry -o > ~/edgex-foundry/edgex-native-build-3.1-napa/edgex-service-logs/core-data/nohup.out 2>&1 &
@echo "::: EdgeX core-data is running... :::"
kill-core-data:
@ps aux | grep "core-data" | grep -v grep | awk '{print $$2}' | xargs kill -15 > /dev/null 2>&1 &
@echo "::: EdgeX core-data has stopped working :::"
# edgex core-command service
start-core-command:
@cd edgex-go-3.1.1/cmd/core-command/ && nohup ./core-command -cp=consul.http://127.0.0.1:8500 -registry -o > ~/edgex-foundry/edgex-native-build-3.1-napa/edgex-service-logs/core-command/nohup.out 2>&1 &
@echo "::: EdgeX core-command is running... :::"
kill-core-command:
@ps aux | grep "core-command" | grep -v grep | awk '{print $$2}' | xargs kill -15 > /dev/null 2>&1 &
@echo "::: EdgeX core-command has stopped working :::"
# edgex support-notifications service
start-support-notifications:
@cd edgex-go-3.1.1/cmd/support-notifications/ && nohup ./support-notifications -cp=consul.http://127.0.0.1:8500 -registry -o > ~/edgex-foundry/edgex-native-build-3.1-napa/edgex-service-logs/support-notifications/nohup.out 2>&1 &
@echo "::: EdgeX support-notifications is running... :::"
kill-support-notifications:
@ps aux | grep "support-notifications" | grep -v grep | awk '{print $$2}' | xargs kill -15 > /dev/null 2>&1 &
@echo "::: EdgeX support-notifications has stopped working :::"
# edgex support-scheduler service
start-support-scheduler:
@cd edgex-go-3.1.1/cmd/support-scheduler/ && nohup ./support-scheduler -cp=consul.http://127.0.0.1:8500 -registry -o > ~/edgex-foundry/edgex-native-build-3.1-napa/edgex-service-logs/support-scheduler/nohup.out 2>&1 &
@echo "::: EdgeX support-scheduler is running... :::"
kill-support-scheduler:
@ps aux | grep "support-scheduler" | grep -v grep | awk '{print $$2}' | xargs kill -15 > /dev/null 2>&1 &
@echo "::: EdgeX support-scheduler has stopped working :::"
# edgex app-service-configurable service
start-app-service-configurable:
@cd app-service-configurable-3.1.1/ && nohup ./app-service-configurable -cp=consul.http://127.0.0.1:8500 -registry -p=rules-engine -o > ~/edgex-foundry/edgex-native-build-3.1-napa/edgex-service-logs/app-service-configurable/nohup.out 2>&1 &
@echo "::: EdgeX app-service-configurable is running... :::"
kill-app-service-configurable:
@ps aux | grep "app-service-configurable" | grep -v grep | awk '{print $$2}' | xargs kill -15 > /dev/null 2>&1 &
@echo "::: EdgeX app-service-configurable has stopped working :::"
# edgex device-virtual service
start-device-virtual:
@cd device-virtual-go-3.1.1/cmd && nohup ./device-virtual -cp=consul.http://127.0.0.1:8500 -registry -o > ~/edgex-foundry/edgex-native-build-3.1-napa/edgex-service-logs/device-virtual/nohup.out 2>&1 &
@echo "::: EdgeX device-virtual is running... :::"
kill-device-virtual:
@ps aux | grep "device-virtual" | grep -v grep | awk '{print $$2}' | xargs kill -15 > /dev/null 2>&1 &
@echo "::: EdgeX device-virtual has stopped working :::"
# edgex ui-server service
# The EdgeX graphical user interface (GUI) provides an easy to use visual tool to monitor data passing through EdgeX services.
start-edgex-ui-server:
@cd edgex-ui-go-3.1.0/cmd/edgex-ui-server && nohup ./edgex-ui-server -o > ~/edgex-foundry/edgex-native-build-3.1-napa/edgex-service-logs/edgex-ui-server/nohup.out 2>&1 &
@echo "::: EdgeX ui-server is running... :::"
# the output from executing the command is redirected so it wont print any output
kill-edgex-ui-server:
@ps aux | grep "edgex-ui-server" | grep -v grep | awk '{print $$2}' | xargs kill -15 > /dev/null 2>&1 &
$ @echo "::: EdgeX ui-server has stopped working :::"
# edgex ekuiper service (rules engine)
start-ekuiper:
@export CONNECTION__EDGEX__REDISMSGBUS__PORT=6379
@export CONNECTION__EDGEX__REDISMSGBUS__PROTOCOL=redis
@export CONNECTION__EDGEX__REDISMSGBUS__SERVER=localhost
@export CONNECTION__EDGEX__REDISMSGBUS__TYPE=redis
@export EDGEX__DEFAULT__PORT=6379
@export EDGEX__DEFAULT__PROTOCOL=redis
@export EDGEX__DEFAULT__SERVER=localhost
@export EDGEX__DEFAULT__TOPIC=rules-events
@export EDGEX__DEFAULT__TYPE=redis
@export KUIPER__BASIC__CONSOLELOG="true"
@export KUIPER__BASIC__RESTPORT=59720
@echo ":::All environment variables set :::"
@cd ekuiper-1.14.0/_build/kuiper--linux-amd64/bin && nohup ./kuiperd > ~/edgex-foundry/edgex-native-build-3.1-napa/edgex-service-logs/ekuiper/nohup.out 2>&1 &
@echo "::: EdgeX ekuiper is running... :::"
# Pid is a variable here which will contain pid of the process running at 9081.
# The condition will only be entered when pid will not be empty.
# 1. **`@pid=`**:
# - This part assigns the output of the following command to the variable `pid`.
# 2. **`$$(sudo lsof -t -i :9081)`**:
# - `$$`: In a `Makefile`, `$$` is used to escape the dollar sign, so it gets passed to the shell as a single `$`.
# - `sudo`: Runs the command with superuser privileges.
# - `lsof`: Stands for "list open files". It's a command used to find out which files are open by which processes.
# - `-t`: This option tells `lsof` to output only the process IDs (PIDs) of the processes using the specified files.
# - `-i :9081`: This option tells `lsof` to look for processes using the network port 9081.
# So, the command `sudo lsof -t -i :9081` lists the PIDs of processes using port 9081. The `$$` ensures that the output
# of this command is assigned to the `pid` variable in the `Makefile`.
kill-ekuiper:
@pid=$$(sudo lsof -t -i :9081); \
if [ -n "$$pid" ]; then \
echo "Killing process $$pid using port 9081"; \
sudo kill -15 $$pid; \
else \
echo "No process using port 9081"; \
fi
@echo "::: EdgeX ekuiper has stopped working :::"
###################################################################################################
# The below seciton of Makefile enables user to start and end edgex services using a single command
###################################################################################################
# Implementation of starting all the services.
edgex-services-start:
@$(MAKE) -s start-consul-agent > /dev/null
@$(MAKE) -s start-core-common-config-bootstrapper > /dev/null
@$(MAKE) -s start-core-metadata > /dev/null
@$(MAKE) -s start-core-data > /dev/null
@$(MAKE) -s start-core-command > /dev/null
@$(MAKE) -s start-support-notifications > /dev/null
@$(MAKE) -s start-support-scheduler > /dev/null
@$(MAKE) -s start-app-service-configurable > /dev/null
@$(MAKE) -s start-ekuiper > /dev/null
@$(MAKE) -s start-edgex-ui-server > /dev/null
@$(MAKE) -s start-device-virtual > /dev/null
@echo "\033[32m✔ ::: EdgeX services started! :::\033[0m"
# Implementation of stopping all the services.
edgex-services-stop:
@ps aux | grep 'consul agent' | grep -v grep | awk '{print $$2}' | xargs -r kill -15
@ps aux | grep 'core-metadata' | grep -v grep | awk '{print $$2}' | xargs -r kill -15 > /dev/null 2>&1 &
@ps aux | grep 'core-data' | grep -v grep | awk '{print $$2}' | xargs -r kill -15 > /dev/null 2>&1 &
@ps aux | grep 'core-command' | grep -v grep | awk '{print $$2}' | xargs -r kill -15 > /dev/null 2>&1 &
@ps aux | grep 'support-notifications' | grep -v grep | awk '{print $$2}' | xargs -r kill -15 > /dev/null 2>&1 &
@ps aux | grep 'support-scheduler' | grep -v grep | awk '{print $$2}' | xargs -r kill -15 > /dev/null 2>&1 &
@ps aux | grep 'app-service-configurable' | grep -v grep | awk '{print $$2}' | xargs -r kill -15 > /dev/null 2>&1 &
@ps aux | grep 'device-virtual' | grep -v grep | awk '{print $$2}' | xargs -r kill -15 > /dev/null 2>&1 &
@ps aux | grep 'edgex-ui-server' | grep -v grep | awk '{print $$2}' | xargs -r kill -15 > /dev/null 2>&1 &
@ps aux | grep 'kuiperd' | grep -v grep | awk '{print $$2}' | xargs -r kill -15 > /dev/null 2>&1 &
@echo "\033[32m✔ ::: EdgeX services stopped! :::\033[0m"
####################################################
# The below showcases services status, like PID etc.
# ALl service status is printed out to shell.
####################################################
edgex-services-show-status:
@echo "USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND"
@status=""
@if ps aux | grep -E 'consul.agent|core-metadata|core-data|core-command|support-notifications|support-scheduler|app-service-configurable|device-virtual|edgex-ui-server|kuiperd' | grep -v grep > /dev/null; then \
ps aux | grep consul.agent | grep -v grep || status="$$status\nconsul.agent is not running"; \
ps aux | grep core-metadata | grep -v grep || status="$$status\ncore-metadata is not running"; \
ps aux | grep core-data | grep -v grep || status="$$status\ncore-data is not running"; \
ps aux | grep core-command | grep -v grep || status="$$status\ncore-command is not running"; \
ps aux | grep support-notifications | grep -v grep || status="$$status\nsupport-notifications is not running"; \
ps aux | grep support-scheduler | grep -v grep || status="$$status\nsupport-scheduler is not running"; \
ps aux | grep app-service-configurable | grep -v grep || status="$$status\napp-service-configurable is not running"; \
ps aux | grep edgex-ui-server | grep -v grep || status="$$status\nedgex-ui-server is not running"; \
ps aux | grep kuiperd | grep -v grep || status="$$status\nkuiperd is not running"; \
ps aux | grep device-virtual | grep -v grep || status="$$status\ndevice-virtual is not running"; \
else \
echo "No EdgeX services are currently running."; \
fi; \
echo "$$status"
#####################################################
# The below showcases services status, like PID etc..
# ALl service status is shown with htop filtered view
#####################################################
edgex-services-htop-status:
@echo "::: Filtering EdgeX services and displaying with htop :::"
@./htop-filter.sh