-
Notifications
You must be signed in to change notification settings - Fork 109
Provisioning new hosts
Fuhu Xia edited this page Oct 20, 2020
·
9 revisions
Before we can run ansible, we need to install python on the hosts. TODO: include python in the AMI so this step isn't necessary.
$ for host in ...; do ssh $host DEBIAN_FRONTEND=noninteractive apt-get install -y python; done
All hosts are provisioned with a 16G volume for /var/log
. The disk must be manually initialized and mounted. Some instances (solr, jenkins) have additional volumes for data which also must be manually initialized and mounted.
- Run
lsblk
to inspect block devices and make sure the new volume is available. For example, you should see 16GB/dev/xvdf
in the list.
lsblk
- Make an ext4 file system.
mkfs /dev/xvdf -t ext4
- Create
/mnt/log/
and copy over existing log files.
mkdir /mnt/log
mount /dev/xvdf /mnt/log
rsync -avzh /var/log/ /mnt/log/
- Modify
/etc/fstab
to add this line so that the partition is available on boot.
/dev/xvdf /var/log ext4 defaults,discard 0 2
Reboot and verify /var/log is getting new logs.
- Run
lsblk
to inspect block devices and make sure the new volume is available. For example, you should see 100GB/dev/xvdg
in the list.
lsblk
- Make an ext4 file system.
mkfs /dev/xvdg -t ext4
- Create
/data
and mount it.
mkdir /data
mount /dev/xvdg /data
- Modify
/etc/fstab
to add this line so that the partition is available on boot.
/dev/xvdg /data ext4 defaults,discard 0 2
Reboot and verify /var/log is getting new logs.
Note: for newer t3 instances, NVMe virtual devices are used instead of SATA, which look like /dev/nvme0n1p1
, /dev/nvme1n1p1
, etc.