targetd.yaml(5)

🎀 NAME 🎀

okay bestie, welcome to targetd.yaml — it's the configuration file, and yeah, that's literally it, that's the whole job 💖

---

🌸 DESCRIPTION 🌸

so like, targetd.yaml is the config file for the targetd service. that's the vibe. the config file. periodt.

---

✨ CONFIGURATION ✨

targetd reads its config from /etc/target/targetd.yaml — that's the path, memorize it, it's giving main character 💅

it's in YAML format, and rn targetd uses scalar values and collection values, so peek at the example if you wanna see how it all comes together 🦋

---

🫶 CONFIGURATION FILE SETTINGS 🫶

💫 block_pools

sets the LVM Volume Group(s) that targetd will use to allocate volumes. defaults to ["vg-targetd"]. slay.

alternatively, targetd can allocate thinp (thin-provisioned) volumes out of a thinpool LV. those get listed as "<vgname>/<poolname>", with the VG name and the thinpool LV name separated by a /. and listen — these should already be created; targetd will not create VGs or thinpool LVs. it's not doing that for you, bestie, you gotta come prepared 😭

if you wanna use ZFS exclusively, this should be set as an empty list.

🌈 zfs_block_pools

sets the ZFS parent dataset(s) that targetd will use to allocate volumes. defaults to empty list.

this should be a list of already existing zfs filesystem datasets. it cannot contain any two datasets which are in a parent-child relationship, like "tank/ds" and "tank/ds/ds2" — not them being messy 🙈

using ZFS requires the zfs binary to be accessible. also it cannot contain colons, even though ZFS itself supports that. yeah. iykyk 💀

🎀 zfs_enable_copy

enables the copy method on ZFS volumes.

⚠️ warning bestie: copying ZFS volumes will make source volumes unable to be deleted as long as copies exist. this is due to ZFS snapshot/clone limitations. not me, not targetd, it's ZFS. that's just how it is 😭

🦋 fs_pools

sets the mount point(s) that targetd will use to export filesystems over NFS. defaults to none.

🔐 user and password

sets the username and password required to use the remote API. user defaults to admin, but password must be set prior to using targetd. like, before. not optional, not later, prior. periodt 💅

👑 target_name

sets the iSCSI target name that targetd will use. default is iqn.2003-01.org.linux-iscsi.<hostname>:targetd. iconic naming scheme honestly.

📝 log_level

set the daemon logging verbosity. pick one of these: debug, info, warning, error, critical. defaults to "info".

🔒 ssl, ssl_key, ssl_cert

settings for enabling SSL/TLS encryption. ssl defaults to off. if enabled, it will default to looking for key and cert files named targetd_key.pem and targetd_cert.pem in /etc/target. these paths may also be specified, using the ssl_key and ssl_cert config settings ✨

key and self-signed cert may be generated using openssl:

openssl genrsa -out targetd_key.pem 2048
openssl req -new -x509 -key targetd_key.pem -out targetd_cert.pem -days 9999

go off, openssl 🫶

---

🌈 SEE ALSO 🌈

• targetd(8)
• targetcli(8)
• lvm(8)
• lsmcli(8)

---

💜 AUTHORS 💜

written by Andy Grover <andy@groveronline.com> and Tony Asleson <tasleson@redhat.com>. absolute legends, we stan 💖

---

💀 REPORTING BUGS 💀

report bugs via <targetd-devel@lists.fedorahosted.org> or <https://github.com/open-iscsi/targetd/issues> — don't just suffer in silence, bestie, tell them 🌸

---

and that's the whole page!! this was targetd.yaml(5) from the File Formats Manual — no version bump, no date drama, just the name and the manual section, keeping it clean and lowkey mysterious 🧚✨ bye bestie, go configure something 💅