Generic
Operations
In the last few yers, the number of programmers concerned about writting structured commit messages had dramatically grown. As exposed by Tim Pope in article readable commit messages are easy to follow when looking through the project history. Moreover the AngularJS contributing guides introduced conventions that can be used by automation tools to automatically generate useful documentation, or by developpers during debbuging process.
This document borrow some concepts, conventions and even text mainly from these two sources, extending them in order to provide a sensible guideline for writing commit messages.
(a) Create v1.12.8-gke.10 cluster with one node, two local SSDs. | |
(b) Prior to installing openebs, I logged into the node and did the following to wipeout the ext4 that get pre-formatted. | |
> sudo umount /mnt/disks/ssd0 | |
> sudo umount /mnt/disks/ssd1 | |
> sudo wipefs -af /dev/sdb | |
> sudo wipefs -af /dev/sdc | |
> lsblk -o NAME,TYPE,SIZE,FSTYPE,MOUNTPOINT | |
NAME TYPE SIZE FSTYPE MOUNTPOINT | |
sda disk 100G |
--- | |
apiVersion: extensions/v1beta1 | |
kind: DaemonSet | |
metadata: | |
namespace: kube-system | |
name: node-custom-setup | |
labels: | |
k8s-app: node-custom-setup | |
annotations: | |
command: &cmd apt-get update -qy && apt-get install -qy tgt ceph-fs-common ceph-common xfsprogs |
--- | |
apiVersion: apps/v1 | |
kind: DaemonSet | |
metadata: | |
namespace: kube-system | |
name: node-custom-setup | |
labels: | |
k8s-app: node-custom-setup | |
annotations: | |
command: &cmd apt-get update -qy && apt-get install -qy open-iscsi xfsprogs |