Skip to content

Commit b57f0c2

Browse files
committed
Supplemental installation package SHA512 verification
1 parent 7bb2180 commit b57f0c2

File tree

100 files changed

+2019
-320
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

100 files changed

+2019
-320
lines changed
58.1 KB
Loading
62.3 KB
Loading
62.3 KB
Loading
60.9 KB
Loading
60.3 KB
Loading
57.4 KB
Loading
60 KB
Loading

src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md

Lines changed: 31 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,37 @@ Unzip and install the package
5252
| README_ZH.md | file | Explanation of the Chinese version of the markdown format |
5353
| README.md | file | Instructions |
5454

55-
### 2.2 Environmental Preparation
55+
56+
### 2.2 Pre-installation Check
57+
58+
To ensure the AINode installation package you obtained is complete and valid, we recommend performing an SHA512 verification before proceeding with the installation and deployment.
59+
60+
#### Preparation:
61+
62+
- Obtain the officially released SHA512 checksum: Visit the [Release Versions](https://iotdb.apache.org/zh/Download/) page on the IoTDB open-source official website to get it.
63+
64+
#### Verification Steps (Linux as an Example):
65+
66+
1. Open the terminal and navigate to the directory where the installation package is stored (e.g., /data/ainode):
67+
```Bash
68+
cd /data/ainode
69+
```
70+
2. Execute the following command to calculate the hash value:
71+
```Bash
72+
sha512sum timechodb-{version}-ainode-bin.zip
73+
```
74+
3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name):
75+
76+
![img](/img/sha512-06.png)
77+
78+
4. Compare the output result with the official SHA512 checksum. Once confirmed that they match, you can proceed with the installation and deployment of AINode as per the procedures below.
79+
80+
#### Notes:
81+
82+
- If the verification results do not match, please re-obtain the installation package.
83+
- If a "file not found" prompt appears during verification, check whether the file path is correct or if the installation package has been fully downloaded.
84+
85+
### 2.3 Environmental Preparation
5686

5787
1. Recommended operating systems: Ubuntu, MacOS
5888
2. IoTDB version: >= V 2.0.5.1

src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_timecho.md

Lines changed: 30 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,36 @@ Unzip and install the package
5252
| README_ZH.md | file | Explanation of the Chinese version of the markdown format |
5353
| README.md | file | Instructions |
5454

55-
### 2.2 Environmental Preparation
55+
### 2.2 Pre-installation Check
56+
57+
To ensure the AINode installation package you obtained is complete and valid, we recommend performing an SHA512 verification before proceeding with the installation and deployment.
58+
59+
#### Preparation:
60+
61+
- Obtain the officially released SHA512 checksum:please contact Timecho Team to re-obtain the installation package.
62+
63+
#### Verification Steps (Linux as an Example):
64+
65+
1. Open the terminal and navigate to the directory where the installation package is stored (e.g., /data/ainode):
66+
```Bash
67+
cd /data/ainode
68+
```
69+
2. Execute the following command to calculate the hash value:
70+
```Bash
71+
sha512sum timechodb-{version}-ainode-bin.zip
72+
```
73+
3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name):
74+
75+
![img](/img/sha512-06.png)
76+
77+
4. Compare the output result with the official SHA512 checksum. Once confirmed that they match, you can proceed with the installation and deployment of AINode as per the procedures below.
78+
79+
#### Notes:
80+
81+
- If the verification results do not match, please contact Timecho Team to re-obtain the installation package.
82+
- If a "file not found" prompt appears during verification, check whether the file path is correct or if the installation package has been fully downloaded.
83+
84+
### 2.3 Environmental Preparation
5685

5786
1. Recommended operating systems: Ubuntu, MacOS
5887
2. IoTDB version: >= V 2.0.5.1

src/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,38 @@ Use the hostname for `cn_internal_address` and `dn_internal_address` in IoTDB co
5858
2. Configure the operating system environment according to environmental requirements (system environment configuration can be found in:[Environment Requirement](../Deployment-and-Maintenance/Environment-Requirements.md)
5959

6060

61+
### 2.1 Pre-installation Check
62+
63+
To ensure the IoTDB installation package you obtained is complete and valid, we recommend performing an SHA512 verification before proceeding with the installation and deployment.
64+
65+
#### Preparation:
66+
67+
- Obtain the officially released SHA512 checksum: Visit the [Release Versions](https://iotdb.apache.org/zh/Download/) page on the IoTDB open-source official website to get it.
68+
69+
#### Verification Steps (Linux as an Example):
70+
71+
1. Open the terminal and navigate to the directory where the installation package is stored (e.g., /data/iotdb):
72+
```Bash
73+
cd /data/iotdb
74+
```
75+
2. Execute the following command to calculate the hash value:
76+
```Bash
77+
sha512sum apache-iotdb-{version}-all-bin.zip
78+
```
79+
3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name):
80+
81+
82+
![img](/img/sha512-07.png)
83+
84+
4. Compare the output result with the official SHA512 checksum. Once confirmed that they match, you can proceed with the installation and deployment of IoTDB as per the procedures below.
85+
86+
87+
#### Notes:
88+
89+
- If the verification results do not match, please re-obtain the installation package.
90+
- If a "file not found" prompt appears during verification, check whether the file path is correct or if the installation package has been fully downloaded.
91+
92+
6193
## 3. Installation Steps
6294

6395
Taking a cluster with three Linux servers with the following information as example:

0 commit comments

Comments
 (0)