targetd_lsmplugin(1)

💖 targetd_lsmplugin — the libStorageMgmt targetd plugin 💖

okay bestie, welcome to targetd_lsmplugin(1), the manual page for the libStorageMgmt targetd plugin. yes it's section 1. yes it's a whole vibe. let's get into it 🫶

---

✨ NAME ✨

targetd_lsmplugin — the libStorageMgmt targetd plugin, periodt.

---

🌸 DESCRIPTION 🌸

So the libStorageMgmt targetd plugin lets you manage storage using the targetd storage API [1]. That's the whole point, no cap.

And the targetd_lsmplugin executable file? It's literally there for the libStorageMgmt daemon to execute when a client user specifies the targetd plugin in the URI. That's its job. It's giving backstage crew energy — you never see it, but nothing works without it. 👑

---

🦋 URI 🦋

To use this plugin, bestie, you set your URI to one of these formats. Choose your fighter:

# HTTP connection
targetd://<username>@<targetd_server>:<port number>

# HTTPS connection
targetd+ssl://<username>@<targetd_server>:<port number>

# HTTPS connection with certificate file
targetd+ssl://<username>@<targetd_server>:<port number>?ca_cert_file=<full path and filename>

# HTTPS connection disabling all certificate checks (not recommended for production)
targetd+ssl://<username>@<targetd_server>:<port number>?no_ssl_verify=yes

now let's break down every single piece, because I refuse to let you guess 🙈

• username — this is the user account configured in the targetd configuration file. that's it, that's the whole thing.
• targetd_server — the IP address or DNS name of the server that's running the targetd daemon. where your storage lives, basically.
• port number — the listening port of the targetd daemon. and here's the tea: if you don't supply one on the URI, the default port 18700 is used. it's got your back like that 💅
• URI parameters — these are the URI parameters this plugin supports:
  • ca_cert_file=<certificate file> — this URI parameter is for SSL connections only, okay? For those users who are out here utilizing a self signed certificate, you can pass the path and file to the certificate that should be used to verify the server certificate. it's the "trust but verify" of it all ✨
  • no_ssl_verify=yes — also SSL connections only. With this URI parameter, the targetd plugin will not validate the server's SSL certificate. It's often used for self-signed CA environments, but — and I'm saying this with my whole chest — it is strongly suggested to remove this URI parameter and install a self-signed CA properly, or use the cert_file parameter instead.

🚨 bestie listen: no_ssl_verify=yes turns off certificate validation. great for a quick test, absolutely not it for production. the manpage literally says "not recommended for production." believe it. 😭

---

🔥 SUPPORTED SOFTWARE 🔥

Linux targetd 0.7.1 or later version. that's the bar, and you must clear it.

Wanna know the detailed support status? You can query it, and you have options, queen:

• lsm.Client.capabilities() — Python API
• lsm_capabilities() — C API
• lsmcli capabilities — the lsmcli command line

pick your language, they all eat 💖

---

🌈 FIREWALL RULES 🌈

By default, this plugin requires access to the targetd server's TCP 18700 port. so like… open the door or nothing's getting through. 🔑

---

👑 SEE ALSO 👑

• lsmcli(1)
• lsmd(1)
• [1] https://github.com/agrover/targetd

go read those too, iykyk 💜

---

💀 BUGS 💀

Please report bugs to <libstoragemgmt-devel@lists.sourceforge.net>. found a gremlin in the code? tell the devs, don't just suffer in silence bestie 🙈

---

🎀 AUTHOR 🎀

• Gris Ge <fge@redhat.com>
• Tony Asleson <tasleson@redhat.com>

the icons who made this happen. we stan. 🫶

---

and that's the whole page, babes! this was targetd_lsmplugin, version 1.10.3, dated July 2017 — so yeah, she's vintage, and she still slays. ✨💅🌸