Skip to content

Latest commit

 

History

History
499 lines (361 loc) · 12.3 KB

fake-devicegraphs-yaml-format.md

File metadata and controls

499 lines (361 loc) · 12.3 KB

YAML File Format For Fake Device Graphs

This document describes the file format used to set up fake (mockup) device trees for testing some of the functionality of YaST storage, in particular the storage proposal.

Please notice that those fake device trees have limitations. They are meant for creating unit tests, not for actually creating partitions etc. on a real hard disk.

There are two ways to look at this: (1) what FakeDeviceFactory accepts when reading the file and creating a device tree and (2) what YamlWriter puts into the YAML file when dumping a device tree.

FakeDeviceFactory accepts anything YamlWriter has written and tries to build exactly the same device tree. But YamlWriter does also include a bit more data than strictly necessary for informational purposes like free spaces it encounters.

FakeDeviceFactory on the other hand can fill in missing parts like partition starts and partition sizes which makes it easier for humans to specify a device tree.

File Structure

The device tree is specified in one YAML file. This YAML file might have multiple documents, separated with "---" as specified by the YAML standard:

---
disk:
  name: /dev/sda
  size: 1 TiB
---
disk:
  name: /dev/sdb
  size: 800 GiB

Even if there is just one document in the file, the first "---" is still required:

---
disk:
  name: /dev/sda
  size: 1 TiB

There might be one or more toplevel items. If there is just one, the leading dash "-" may be omitted for the toplevel item (see examples above). If there are multiple toplevel items, they have to be specified as an array, i.e. with leading "-":

---
- disk:
    name: /dev/sda
    size: 1 TiB
- disk:
    name: /dev/sdb
    size: 800 GiB

Remember to indent the next level (the parameters for each disk in this example) one level. 2 spaces (no tabs!) are recommended for each indentation level.

Tree Structure

Currently Implemented

- disk:
    partition_table: <type>
    partitions:
      - partition:
          file_system: <type>
      - partition
      - free
      - partition

or

- disk:
    file_system: <type>
    encryption

- lvm_vg:
    lvm_lvs:
- lvm_lv:
lvm_pvs:
- lvm_pv:

or

- dasd

Very much like "disk" with some additional parameters.

For Future Use

- raid

Parameters

disk

Example:

- disk:
    name: /dev/sda
    size: 1 TiB
    partition_table:  ms-dos
    partitions:
    - partition:
        ...
    - partition:
        ...

  • name: Kernel device name of the disk, typically something like /dev/sda, /dev/sdb etc.

  • size: Size of the disk specified as something the DiskSize class can parse:

    • nn
    • nn B (same as nn)
    • nn KiB
    • nn MiB
    • nn GiB
    • nn TiB
    • ... i.e. binary-based sizes, but not kB, MB, GB or shortcuts (k, M, G, ...).

  • partition_table: Type of the partition table to create. Omit if no partition table should be created. Permitted values (case-insensitive):

    • msdos, ms-dos
    • gpt
    • dasd
    • mac

  • partitions: Specifies an array of partitions to create. Omit if no partitions should be created.

  • mount_point: mount point for a filesystem directly on the disk. Notice that partition_table and mount_point (filesystem) are mutually exclusive; a disk can only have either of them, never both.

dasd

"dasd" is very similar to "disk", but S/390 specific. In addition to the parameters that "disk" offers, it can also have:

  • type: Type of the DASD to create. Permitted values (case-insensitive):

    • eckd
    • fba

  • format: Format of the DASD to create. Permitted values (case-insensitive):

    • ldl
    • cdl

partition

Example:

- partition:
    size:         60 GiB
    start:        100 GiB
    align:        keep_size
    name:         /dev/sda3
    type:         primary
    id:           Linux
    file_system:  btrfs
    mount_point:  /
    label:        root
    encryption:
        type:     "luks"
        name:     "/dev/mapper/cr_root"
        password: "s3cr3t"
    btrfs:
        default_subvolume: @
        subvolumes:
            - subvolume
                  path: var/log
              ...
            - subvolume
                  path:  var/lib/mysql
                  nocow: true

  • size: Similar to disk.size: Size of the partition specified as something the DiskSize class can parse, including "unlimited". "unlimited" means "Use all the rest of the available space". This makes sense only for the last partition on a disk or for an extended partition on a disk with an MS-DOS partition table. Notice that subsequent logical partitions start at the beginning of that extended partition, so the last one of those logical partitions might have size "unlimited" again.

    size may be missing and defaults to 'unlimited'.

    Note: all size values are exact. So, for example, on a 1000 MiB disk you can't create a 1000 MiB partition but only one with 999 MiB as the partition table takes up some space on its own.

  • start: The value is optional and, if given, specifies the partition start. When missing, the next free space is used taking into account any preceding free space spec and aligned according to the align policy if one is given.

  • name: Kernel device name of the partition, typically something like /dev/sda1, /dev/sda2, ...; as usual, the first logical partition in an extended partition is always /dev/sda5, no matter if /dev/sda4 and /dev/sda3 actually exist.

  • align: Alignment policy. If missing, no specific alignment is done.

    Permitted values:

    • align_end
    • keep_end
    • keep_size

  • type: Partition type. Default if not specified: "primary".

    Permitted values (case insensitive):

    • primary
    • extended
    • logical

    "extended" and "logical" are supported only for MS-DOS partition tables.

  • id: Partition ID, specified either numerical (0x82, 0x83) or as string. Default if not specified: linux (0x83)

    Permitted values (case insensitive):

    • linux
    • swap
    • extended
    • lvm
    • raid
    • prep
    • ntfs
    • dos12
    • dos16
    • dos32
    • unknown
    • bios_boot
    • windows_basic_data
    • microsoft_reserved

  • file_system: This is really a separate tree level, but it would be awkward to write it in the YAML file as such. "mount_point" and "label" really belong to the file system, too. As used here, "file_system" specifies the type of file system to create. Omit this parameter if no file system should be created.

    Permitted values (case insensitive):

    • ext2
    • ext3
    • ext4
    • btrfs
    • vfat
    • xfs
    • jfs
    • hfs
    • ntfs
    • swap
    • hfsplus
    • nfs
    • tmpfs
    • iso9660
    • reiserfs
    • udf

  • mount_point: The mount point of the file system of this partition. Omit if the file system should not be mounted. Permitted values: Any valid Linux path (case sensitive)

  • label: The label of the file system of this partition. Omit if there should be no label.

  • encryption: This is a separate tree level. Omit if there should be no encryption.

  • btrfs: Some Btrfs-specific attributes. Omit if the filesystem on this partition is not a Btrfs or if no specific attributes are desired.

encryption

Example:

encryption:
    name:     "/dev/mapper/cr_root"
    type:     "luks"
    password: "s3cr3t"

This is permitted under "partition" or "lvm_lv". For LVM PVs, add this to the corresponding partition.

  • name: Required parameter. This is the name (with the complete path) of the crypto device that appears in /etc/crypttab and in /dev/mapper. Starting this with "cr_" is a convention, but not mandatory.

  • type: Right now, only "luks" is supported. This is the default and optional, so it can be omitted.

  • password: The encryption password. In the context of fake device graphs, this is not really used (but it is set in libstorage).

free

Example:

- free:
    size: 300 GiB
    start: 100 GiB # (optional)

This indicates a slot of free space (space that does not belong to any partition) on the disk between partitions.

Note that free slots are not part of the device tree and added by YamlWriter for purely informational purposes.

FakeDeviceFactory ignores start and uses size when creating a partition.

  • size: Size of the free slot (DiskSize compatible).
  • start: Start of the free slot (DiskSize compatible).

lvm_vg

Example:

- disk:
    vg_name: system
    extent_size: 4 MiB

  • vg_name: name of volume group.

  • extent_size: Similar to disk.size: Size of the physical extent as something the DiskSize class can parse, excluding unlimited.

lvm_lv

- lvm_lv:
    lv_name: root
    size: 16 GiB
stripes: 2
stripe_size: 8 MiB

  • lv_name: name of logical volume, different from kernel device name.

  • size: Similar to disk.size: Size of the logical volume as something the DiskSize class can parse, excluding unlimited.

  • stripes: Number of stripes.

  • stripe_size: Similar to disk.size: Size of the stripes as something the DiskSize class can parse, excluding unlimited.

  • in addition the filesystem parameters are allowed

lvm_pv

- lvm_pv:
  blk_device: /dev/sda
  • blk_device: The block device used by the physical volume. The block device must be defined before the physical volume in the file.

btrfs

btrfs:
    default_subvolume: @
    subvolumes:
        - subvolume
            path: var/log
        ...
        ...
        - subvolume
            path:  var/lib/mysql
            nocow: true

  • default_subvolume: If present, contains the name for the default subvolume (typically "@").

  • subvolumes: A list of subvolumes

  • path: The path of the subvolume (without leading "@" and without leading "/")

  • nocow: "no copy on write" attribute for this subvolume. Default: false.

Complete Example

This setup will create 3 disks (/dev/sda, /dev/sdb/, /dev/sdc) with partitions on the first one (/dev/sda). On /dev/sda, there will be 4 primary partitions, the last one of which is an extended partition with 2 logical partitions in it that have a slot of free space between them.

Note the two missing size specs denoting 'to the end' in both cases.

(4 spaces indented to conform with markdown formatting standards)

---
- disk:
    name: /dev/sda
    size: 1 TiB
    partition_table:  ms-dos
    partitions:

    - partition:
        size:         2 GiB
        name:         /dev/sda1
        type:         primary
        id:           0x82
        file_system:  swap
        mount_point:  swap
        label:        swap

    - partition:
        size:         100 GiB
        name:         /dev/sda2
        type:         primary
        id:           0x7
        file_system:  ntfs
        label:        windows

    - partition:
        size:         60 GiB
        name:         /dev/sda3
        type:         primary
        id:           Linux
        file_system:  ext4
        mount_point:  /
        label:        root

    - partition:
        name:         /dev/sda4
        type:         extended

    - partition:
        size:         200 GiB
        name:         /dev/sda5
        type:         logical
        id:           0x83
        file_system:  xfs
        mount_point:  /home
        label:        home

    - free:
        size:         300 GiB

    - partition:
        name:         /dev/sda6
        type:         logical
        id:           0x83
        file_system:  xfs
        mount_point:  /data
        label:        data

- disk:
    name: /dev/sdb
    size: 160 GiB
---
disk:
  name: /dev/sdc
  size: 500 GiB

Shortcomings

The file format is overly simplistic in several ways:

  • It treats the device graph as a tree. For some objects, e.g. filesystems using several block devices, it is not obvious how to extend the tree.

  • The filesystem parameters are intermixed with the block device data (partition, logical volume). This will fail to work if e.g. the UUID of a logical volume should be specified as it conflicts with the UUID of the filesystem. It also makes moving or removing a filesystem more difficult since every single line has to be reviewed instead of a big block.