Added a set of baremetal usage commands

Author: noctarius

docs/usage/baremetal/cloning.md

@@ -3,4 +3,36 @@ title: "Cloning a Logical Volume"
 weight: 30200
 ---
 
-<placeholder>
+Cloning a logical Volume (LV) in simplyblock creates a writable, independent copy-on-write clone of an existing volume.
+This is useful for scenarios such as testing, staging, backups, and development environments, all while preserving the
+original data. Clones can be created quickly and efficiently using the `sbcli` command line interface.
+
+## Prerequisites
+
+- A running simplyblock cluster with an existing logical volume.
+- An existing [snapshot](snapshotting.md) of a logical volume.
+- `sbcli` installed and configured with access to the simplyblock management API.
+
+## Cloning a Logical Volume
+
+To create a clone of an existing Logical Volume:
+
+```bash
+sbcli snapshot clone \
+  <SNAPSHOT_UUID> \
+  <NEW_VOLUME_NAME>
+```
+
+## Verification
+
+After cloning, the new Logical Volume can be listed:
+
+```bash
+sbcli lvol list
+```
+
+Details of the cloned volume can be retrieved using:
+
+```bash
+sbcli lvol get <VOLUME_UUID>
+```

docs/usage/baremetal/expanding.md

@@ -3,4 +3,54 @@ title: "Expanding a Logical Volume"
 weight: 30300
 ---
 
-<placeholder>
+# Resizing (Expanding) a Logical Volume with sbcli
+
+## Overview
+
+Resizing a logical Volume (LV) in simplyblock allows additional capacity to be allocated without downtime, ensuring
+workloads have sufficient storage as demand grows. The `sbcli` command line interface is used to expand the size of an
+existing Logical Volume in a simple and efficient manner.
+
+## Prerequisites
+
+- A running simplyblock cluster with a valid logical volume.
+- `sbcli` installed and configured with access to the simplyblock management API.
+
+## Expanding a Logical Volume
+
+To increase the size of an existing logical volume:
+
+```bash
+sbcli volume resize \
+  <VOLUME_UUID> \
+  <NEW_SIZE>
+```
+
+## Verification
+
+After resizing, confirm the new volume size:
+
+```bash
+sbcli volume get <VOLUME_UUID>
+```
+
+## Resize the Filesystem (If Required)
+
+Certain filesystems, such as ext4, may require growing the filesystem after the underlying volume has been expanded.
+
+### For `ext4` filesystems:
+
+```bash
+resize2fs /dev/nvmeXnY
+```
+
+### For `xfs` filesystems:
+
+```bash
+xfs_growfs /mount/point
+```
+
+## Shrinking a Volume
+
+Theoretically it is possible to shrink a volume. It can, however, create issues with certain filesystems. When a volume
+needs to be shrunk, it is recommended to create a snapshot and restore it onto a new volume.

docs/usage/baremetal/provisioning.md

@@ -3,4 +3,54 @@ title: "Provisioning a Logical Volume"
 weight: 30000
 ---
 
-<placeholder>
+A logical volume (LV) in simplyblock can be provisioned using the `sbcli` command line interface. This allows
+administrators to create virtual NVMe block devices backed by simplyblock’s distributed storage, enabling
+high-performance and fault-tolerant storage for workloads.
+
+## Prerequisites
+
+- A running simplyblock cluster with healthy management and storage nodes.
+- `sbcli` installed and configured with access to the simplyblock management API.
+
+## Provisioning a New Logical Volume
+
+To create a new logical volume:
+
+```bash
+sbcli lvol add \
+  --max-rw-iops <IOPS> \
+  --max-r-mbytes <THROUGHPUT> \
+  --max-w-mbytes <THROUGHPUT> \
+  <VOLUME_NAME> \
+  <VOLUME_SIZE> \
+  <POOL_NAME>
+```
+
+### Available Parameters
+
+| Parameter                     | Description                                         | Default |
+|-------------------------------|-----------------------------------------------------|---------|
+| --snapshot, -s                | Enables snapshot capability on the logical volume.  | false   |
+| --max-size                    | Maximum size of the logical volume.                 | 0       |
+| --ha-type {single,ha,default} | High availability mode of the logical volume.       | ha      |
+| --encrypt                     | Enables in inline encryption on the logical volume. | false   |
+| --crypto-key1 CRYPTO_KEY1     | The hex value of the first encryption key.          |         |
+| --crypto-key2 CRYPTO_KEY2     | The hex value of the second encryption key.         |         |
+| --max-rw-iops MAX_RW_IOPS     | Maximum IO operations per second.                   | 0       |
+| --max-rw-mbytes MAX_RW_MBYTES | Maximum read/write throughput.                      | 0       |
+| --max-r-mbytes MAX_R_MBYTES   | Maximum read throughout.                            | 0       |
+| --max-w-mbytes MAX_W_MBYTES   | Maximum write throughput.                           | 0       |
+
+## Verification
+
+After creation, the Logical Volume can be listed and verified:
+
+```bash
+sbcli volume list
+```
+
+Details of the volume can be retrieved using:
+
+```bash
+sbcli lvol get <VOLUME_UUID>
+```

docs/usage/baremetal/snapshotting.md

@@ -3,4 +3,33 @@ title: "Snapshotting a Logical Volume"
 weight: 30100
 ---
 
-<placeholder>
+# Creating a Snapshot of a Logical Volume with sbcli
+
+## Overview
+
+Snapshots in simplyblock provide point-in-time copies of logical Volumes (LVs), allowing for backup, recovery, or
+cloning operations without impacting the active workload. Snapshots can be created using the `sbcli` command line
+interface to protect critical data or enable development and testing environments based on production data.
+
+## Prerequisites
+
+- A running simplyblock cluster with an existing logical volume.
+- `sbcli` installed and configured with access to the simplyblock management API.
+
+## Creating a Snapshot
+
+To create a snapshot of an existing Logical Volume:
+
+```bash
+sbcli snapshot add \
+  <VOLUME_UUID> \
+  <SNAPSHOT_NAME>
+```
+
+## Verification
+
+After creation, the snapshot can be listed:
+
+```bash
+sbcli snapshot list
+```