-
Notifications
You must be signed in to change notification settings - Fork 688
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tikv, readme: add "Install and Deploy TiKV Using Ansible" #482
Changes from 1 commit
9bd209d
b1e119d
23265c9
c3365c4
f6966b3
79cd7b4
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -15,16 +15,14 @@ This guide describes how to install and deploy TiKV using Ansible. Ansible is an | |
|
||
- 4 or more machines | ||
|
||
A standard TiKV cluster contains 6 machines. You can use 4 machines for test. | ||
A standard TiKV cluster contains 6 machines. You can use 4 machines for testing. | ||
|
||
- CentOS 7.3 or later version of Linux operating system, x86_64 architecture (AMD64), ext4 filesystem | ||
- CentOS 7.3 (64 bit) or later with Python 2.7 installed, x86_64 architecture (AMD64), ext4 filesystem | ||
|
||
Use ext4 filesystem for your data disks. Mount ext4 filesystem with the `nodelalloc` mount option. See [Mount the data disk ext4 filesystem with options](../op-guide/ansible-deployment#mount-the-data-disk-ext4-filesystem-with-options). | ||
|
||
- Network between machines | ||
|
||
Turn off the firewalls and iptables when deploying and turn them on after the deployment. | ||
|
||
|
||
- Same time and time zone for all machines with the NTP service on to synchronize the correct time. | ||
|
||
See [How to check whether the NTP service is normal](../op-guide/ansible-deployment#how-to-check-whether-the-ntp-service-is-normal). | ||
|
@@ -39,9 +37,10 @@ This guide describes how to install and deploy TiKV using Ansible. Ansible is an | |
|
||
> **Note:** The Control Machine can be one of the target machines. | ||
|
||
- CentOS 7.3 or later version of Linux operating system (Python 2.7 involved by default) | ||
- CentOS 7.3 (64 bit) or later with Python 2.7 installed | ||
- Access to the Internet | ||
- Mutual trust of `ssh authorized_key` configured | ||
- Git installed | ||
- SSH Mutual Trust configured | ||
|
||
In the Control Machine, you can log in to the deployment target machine using `tidb` user account without a password. See [How to configure SSH mutual trust and sudo without password](../op-guide/ansible-deployment#how-to-configure-ssh-mutual-trust-and-sudo-without-password). | ||
|
||
|
@@ -63,7 +62,7 @@ This guide describes how to install and deploy TiKV using Ansible. Ansible is an | |
git clone https://github.com/pingcap/tidb-ansible.git | ||
``` | ||
|
||
You can turn to the official team for advice on which version to choose. | ||
You can turn to the official team (info@pingcap.com) for advice on which version to choose. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please change this to: |
||
|
||
## Step 2: Install Ansible and dependencies in the Control Machine | ||
|
||
|
@@ -227,7 +226,7 @@ Edit the parameters in the service configuration file: | |
deploy_dir = /data1/deploy | ||
``` | ||
|
||
**Note:** To separately set the deployment directory for a service, you can configure the host variables while configuring the service host list. It is required to add the first column alias, to avoid confusion in scenarios of mixed services deployment. | ||
**Note:** To separately set the deployment directory for a service, you can configure the host variable while configuring the service host list in the `inventory.ini` file. It is required to add the first column alias, to avoid confusion in scenarios of mixed services deployment. | ||
|
||
```bash | ||
TiKV1-1 ansible_host=172.16.10.4 deploy_dir=/data1/deploy | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe it's a good idea to specify this is done in the inventory file. |
||
|
@@ -267,7 +266,7 @@ The following example uses `tidb` as the user who runs the service. | |
ansible -i inventory.ini all -m shell -a 'whoami' -b | ||
``` | ||
|
||
3. Download the TiDB binary to the Control Machine. | ||
3. Download the TiKV binary to the Control Machine. | ||
|
||
```bash | ||
ansible-playbook local_prepare.yml | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this note is very redundant. Maybe it can be removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's okay to keep it for now just in case the user might ask which machine to be used as the control machine.