balamurugana

Object Lock Support

Objects can be set to immutable using object lock. Once an object is uploaded, this feature is manageable by below APIs.

• PUT object legal hold
• PUT object retention
• GET object legal hold
• GET Object retention

A bucket can be set to have default object lock configuration using below API.

• PUT Bucket object lock configuration

balamurugana

#!/usr/bin/python

import json
import os
import subprocess

def _read_file(filename):
    try:
        with open(filename) as file:
            return file.read().strip()

balamurugana

As MinIO needs the CN to have the policy name and original mkcert does not support this, download updated mkcert from https://github.com/kanagarajkm/mkcert/releases/download/v1.4.3-1/mkcert

Server certs

1. Generate certificate files

mkcert localhost

2. Copy generated localhost-key.pem and localhost.pem to certs directory of minio server.

cp -avi localhost-key.pem ~/.minio/certs/private.key

balamurugana

Drive states

DriveStatusUnavailable

Drive CRD object is marked as Unavailable, if drive met one of the following condition at startup or added at runtime or dynamic discovery sync.

• device size is less than 16 MiB.
• device is in readonly state.
• device contains partitions.
• device is used as swap space in linux.
• device is used in LVM, linux RAID or LUKS device.
• device is mounted somewhere else i.e. outside of /var/lib/directcsi.

balamurugana

1. Run command $ kubectl edit directpvdrives <NEW-DRIVE-ID> and add directpv.min.io.volume/pvc-12345678 in the finalizer
2. Run command $ kubectl directpv cordon <NEW-DRIVE-ID>
3. Run command $ kubectl edit directpvdrives <NEW-DRIVE-ID> and remove the directpv.min.io.volume/pvc-12345678 finalizer
4. Run command $ ./replace.sh <OLD-DRIVE-ID> <NEW-DRIVE-ID>

balamurugana

Challenges

1. Get drives from each node and identify drives for usability. DirectPV uses sysfs (/sys), udev (/run/udev/data) and procfs (/proc) on each node to collect all necessary information for this and they are stored in directpvnodes CRD.

2. Uniquely identify each drive not by drive name as it may change on node reboots/drive swaps/removal. DirectPV computes a hash using values collected for each drive to make sure it is unique across all nodes. This hash is called ID which is also stored in directpvnodes CRD.

3. Add/Remove of nodes and drives. DirectPV does not monitor addition or deletion of nodes and drives instead it collects information on demand to update directpvnodes CRD.