Skip to content
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

Digging Design, Storage with Kubernetes #27

Open
AmitKumarDas opened this issue Jan 13, 2018 · 1 comment
Open

Digging Design, Storage with Kubernetes #27

AmitKumarDas opened this issue Jan 13, 2018 · 1 comment

Comments

@AmitKumarDas
Copy link
Owner

AmitKumarDas commented Jan 13, 2018

Design

  • Anything that does not record changes in version control is harmful

Storage

  • Partition & format storage devices

    • To partition a drive, you may use parted utility
    • parted can list the partition layout of our disks
    • Any disk that don't have a valid partition will result in error
    • This can be used to identify new disk
    • lsblk can also be used to look for a disk of a particular size with no partitions
    • Other Notes:
      • Remember to check lsblk in every session before making changes. The /dev/sd* and /dev/hd* disk identifiers will not necessarily be consistent between boots, which means there is some danger of partitioning or formatting the wrong disk if you do not verify the disk identifier correctly. Consider using more persistent disk identifiers like /dev/disk/by-uuid, /dev/disk/by-label, or /dev/disk/by-id
  • Partitioning Standard

    • GPT is modern while MBR is supported widely
    • One the standard (otherwise known as format) is selected you can partition
    • You can partition the entire drive or part of it
    • Check the partition(s) using lsblk
  • Create a FileSystem on New Partition

    • Once partitioned you can format it e.g. as ext4 filesystem
    • For above you use mkfs.ext4 utility
  • Mount this FileSystem now

    • create a mount directory i.e. /mnt/data
    • then mount the filesystem on above mount directory
    • mounting everytime the server boots, use /etc/fstab
    • If you had not mount the filesystem previously, you can use sudo mount -a
  • Test you mount

    • Check the availability of disk via df command

Kubernetes

  • pull 306
    • support random access storage devices e.g. hard disks & SSDs
    • non goals - support for I/O isolation using CFS & blkio cgroups
    • Distributed systems often use replication to provide fault tolerance, and can therefore tolerate node failures. However, data gravity is preferred for reducing replication traffic and cold startup latencies.
@AmitKumarDas AmitKumarDas changed the title Digging Storage Digging Storage with Kubernetes Jan 13, 2018
@AmitKumarDas AmitKumarDas changed the title Digging Storage with Kubernetes Digging Design, Storage, etc. with Kubernetes Jan 18, 2018
@AmitKumarDas AmitKumarDas changed the title Digging Design, Storage, etc. with Kubernetes Digging Design, Storage with Kubernetes Jan 23, 2018
@AmitKumarDas
Copy link
Owner Author

AmitKumarDas commented Jan 23, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant