Support deploying microservice
What problem does this PR solve?
What is changed and how it works?
Check List
Tests
- Manual test
# # Global variables are applied to all deployments and used as the default value of
# # the deployments if a specific deployment value is missing.
global:
user: "tidb"
ssh_port: 22
deploy_dir: "/tidb-deploy"
data_dir: "/tidb-data"
listen_host: 0.0.0.0
arch: "amd64"
pd_mode: "ms"
monitored:
# # The communication port for reporting system information of each node in the TiDB cluster.
node_exporter_port: 9200
# # Blackbox_exporter communication port, used for TiDB cluster port monitoring.
blackbox_exporter_port: 9215
# # Storage directory for deployment files, startup scripts, and configuration files of monitoring components.
# deploy_dir: "/tidb-deploy/monitored-9100"
# # Data storage directory of monitoring components.
# data_dir: "/tidb-data/monitored-9100"
# # Log storage directory of the monitoring component.
# log_dir: "/tidb-deploy/monitored-9100/log"
# # Server configs are used to specify the configuration of PD Servers.
pd_servers:
# # The ip address of the PD Server.
- host: 10.2.8.101
# # SSH port of the server.
# ssh_port: 22
# # PD Server name
# name: "pd-1"
# # communication port for TiDB Servers to connect.
client_port: 22379
# # Communication port among PD Server nodes.
peer_port: 22380
# # PD Server deployment file, startup script, configuration file storage directory.
# deploy_dir: "/tidb-deploy/pd-2379"
# # PD Server data storage directory.
# data_dir: "/tidb-data/pd-2379"
# # PD Server log file storage directory.
# log_dir: "/tidb-deploy/pd-2379/log"
# # numa node bindings.
# numa_node: "0,1"
# # The following configs are used to overwrite the `server_configs.pd` values.
# config:
# schedule.max-merge-region-size: 20
# schedule.max-merge-region-keys: 200000
# # Server configs are used to specify the configuration of TiDB Servers.
tidb_servers:
# # The ip address of the TiDB Server.
- host: 10.2.8.101
# # SSH port of the server.
# ssh_port: 22
# # The port for clients to access the TiDB cluster.
port: 40000
# # TiDB Server status API port.
status_port: 18000
# # TiDB Server deployment file, startup script, configuration file storage directory.
# deploy_dir: "/tidb-deploy/tidb-4000"
# # TiDB Server log file storage directory.
# log_dir: "/tidb-deploy/tidb-4000/log"
# # Server configs are used to specify the configuration of TiKV Servers.
tikv_servers:
# # The ip address of the TiKV Server.
- host: 10.2.8.101
# # SSH port of the server.
# ssh_port: 22
# # TiKV Server communication port.
port: 22260
# # TiKV Server status API port.
status_port: 22280
# # TiKV Server deployment file, startup script, configuration file storage directory.
# deploy_dir: "/tidb-deploy/tikv-20160"
# # TiKV Server data storage directory.
# data_dir: "/tidb-data/tikv-20160"
# # TiKV Server log file storage directory.
# log_dir: "/tidb-deploy/tikv-20160/log"
# # The following configs are used to overwrite the `server_configs.tikv` values.
# config:
# log.level: warn
tso_servers:
- host: 10.2.8.101
port: 33379
scheduling_servers:
- host: 10.2.8.101
# # Server configs are used to specify the configuration of Prometheus Server.
monitoring_servers:
# # The ip address of the Monitoring Server.
- host: 10.2.8.101
# # SSH port of the server.
# ssh_port: 22
# # Prometheus Service communication port.
port: 9099
# # ng-monitoring servive communication port
ng_port: 22020
# # Prometheus deployment file, startup script, configuration file storage directory.
# deploy_dir: "/tidb-deploy/prometheus-8249"
# # Prometheus data storage directory.
# data_dir: "/tidb-data/prometheus-8249"
# # Prometheus log file storage directory.
# log_dir: "/tidb-deploy/prometheus-8249/log"
# # Server configs are used to specify the configuration of Grafana Servers.
grafana_servers:
# # The ip address of the Grafana Server.
- host: 10.2.8.101
# # Grafana web port (browser access)
port: 3100
# # Grafana deployment file, startup script, configuration file storage directory.
# deploy_dir: /tidb-deploy/grafana-3000
Code changes
- Has exported function/method change
- Has exported variable/fields change
- Has interface methods change
- Has persistent data change
Side effects
- Possible performance regression
- Increased code complexity
- Breaking backward compatibility
Related changes
- Need to cherry-pick to the release branch
- Need to update the documentation
Release notes:
NONE
Codecov Report
Attention: Patch coverage is 9.26573% with 519 lines in your changes are missing coverage. Please review.
Project coverage is 54.89%. Comparing base (
6f01692) to head (6ec0e82). Report is 6 commits behind head on master.
:exclamation: Current head 6ec0e82 differs from pull request most recent head 9218e5b. Consider uploading reports for the commit 9218e5b to get more accurate results
Additional details and impacted files
@@ Coverage Diff @@
## master #2377 +/- ##
==========================================
- Coverage 55.96% 54.89% -1.06%
==========================================
Files 329 333 +4
Lines 35221 35592 +371
==========================================
- Hits 19709 19538 -171
- Misses 13141 13712 +571
+ Partials 2371 2342 -29
| Flag | Coverage Δ | |
|---|---|---|
| cluster | 44.43% <9.27%> (-0.81%) |
:arrow_down: |
| dm | 25.06% <0.18%> (-0.45%) |
:arrow_down: |
| playground | 14.74% <0.00%> (-1.79%) |
:arrow_down: |
| tiup | 33.60% <ø> (-0.04%) |
:arrow_down: |
| unittest | 21.87% <3.71%> (-0.29%) |
:arrow_down: |
Flags with carried forward coverage won't be shown. Click here to find out more.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
[LGTM Timeline notifier]
Timeline:
2024-04-12 09:47:46.515755234 +0000 UTC m=+1214928.043295783: :ballot_box_with_check: agreed by kaaaaaaang.
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: kaaaaaaang
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [kaaaaaaang]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment