- Notes:
- No containers required for this version.
- Samples in this project are not designed for
playground
, they are realclusters
but consume minimal resources.
- AWS or GCP accounts at hands.
- Labs:
general-lab
requires one instance.tidb-lab
requires one instance.tikv-lab-aws
andtikv-lab-gcp
require two instances.
- In case of AWS, tag them with key
Name
, set value tobastion
anddemo
respectively. - In case of GCP, nodes naming scripts are provided.
ssh
into (any) VM by using-A
option (for simple handling the-i
and-u
options withtiup
tool).- Make sure current user has passwordless
sudo
permission (Cloud providers should already did this for you).
- Stores common scripts for all labs.
general-lab
will deploy an all-in-one cluster on single EC2 instance.- No replication for any components.
- N/A
- Simple setup scripts:
00
,01
,02
- Start/Stop scripts:
03
,04
- Simple check:
check-cluster.sh
- Simple connection for MySQL interface:
connect.sh
- Tier down caution:
destroy-all.sh
tikv-lab
will deploy an all-in-one cluster on single EC2 instance.- 2 tidb servers will be deployed.
- N/A
- Simple setup scripts:
00
,01
,02
- Start/Stop scripts:
03
,04
- Simple check:
check-cluster.sh
- Simple connection for MySQL interface:
connect-4000.sh
orconnect-4001.sh
- Tier down caution:
destroy-all.sh
- Scripts in this folder are designed for AWS
tikv-lab
will deploy a hybrid cluster across two EC2 instances.- 3 tikv servers will be deployed.
- Spin up two EC2 instances, tag:Name them with
bastion
anddemo
respectively. - Assign read EC2 service role to above EC2 instances.
- Smooth the network traffics between them.
- Simple setup scripts:
00
,01
,02
- Start/Stop scripts:
03
,04
- Simple check:
check-cluster.sh
- Simple connection to TiDB instances with MySQL interface:
connect-demo.sh
andconnect-bastion.sh
- Tier down caution:
destroy-all.sh
- Scripts in this folder are designed for GCP.
tikv-lab
will deploy a hybrid cluster across two VMs.- 3 tikv servers will be deployed.
- Put required account related information into
create-instance.sh
, then runcreate-instance.sh
. - Smooth the network traffics between them.
- Simple setup scripts:
00
,01
,02
- Start/Stop scripts:
03
,04
- Simple check:
check-cluster.sh
- Simple connection to TiDB instances with MySQL interface:
connect-demo.sh
andconnect-bastion.sh
- Tier down caution:
destroy-all.sh