local_lsmplugin(1)

πŸ“¦
version 1.10.3 Β· 3 versions
, in fedora 43, fedora 44

✨ NAME ✨

local_lsmplugin β€” the LibstorageMgmt Local Pseudo plugin, aka the friend who knows everybody and handles the intros πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so picture this: you wanna manage your local storage system but you do NOT wanna deal with figuring out which real plugin is supposed to handle it. That's literally the whole point of the LibStorageMgmt local plugin, bestie. It does the matchmaking for you.

The local_lsmplugin executable file is the thing the libStorageMgmt daemon runs when a client user specifies the local plugin in the URI. It's giving backstage pass energy.

Right now, the local plugin wraps these plugins:

Heads up: a specific binary tool may be required for some of these! πŸ‘€ Please check the error message or the manpage of the plugins listed above.

Also, to load the NFS plugin, the kernel module nfsd should be loaded. Not optional, no cap. 🌸


🌈 URI 🌈

To use this plugin, you set your URI to this format:

local://

or

local://?parameter_name=<value>

πŸ’– URI parameters πŸ’–

These URI parameters are supported by this plugin:

  • ignore_init_error=true β€” this one tells the plugin to ignore errors when initializing real plugins. But listen: if no valid system is found, an error will still be raised. So it's not a free pass, it's a "let's keep going anyway" pass. By default, all errors will be raised.
  • only=<plugin_name> β€” this forces the local plugin to load only one specific real plugin. Very main character, very "I only work with these people." By default, all plugins will be loaded if supported hardware has been found.
  • <plugin_name>_<uri_parameter_name>=<value> β€” this format is how you pass URI parameters down to a real plugin. For example, to pass the storcli=/usr/bin/storcli URI parameter to the MegaRAID plugin, you would use megaraid_storcli=/usr/bin/storcli. See how the plugin name gets glued onto the front? 🫢 That's the whole trick.

πŸ‘‘ ROOT PRIVILEGE πŸ‘‘

This plugin requires both the lsmd daemon and the API client running as root user. Both. Not one. Both. 😭

Please check manpage lsmd.conf(5) for details.


⭐ SUPPORTED HARDWARES ⭐

Please refer to these manpages for the hardware support status:

Wanna get the detailed support status? Query it like this, bestie:

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

πŸ”₯ FIREWALL RULES πŸ”₯

This plugin only executes tools on localhost. No network connection required. Zero. None. Your firewall can stay unbothered, it's not that kind of party. πŸ’œ


πŸŽ€ SEE ALSO πŸŽ€

lsmcli(1), lsmd(1)


πŸ™ˆ BUGS πŸ™ˆ

Please report bugs to <libstoragemgmt-devel@lists.fedorahosted.org>

(Yes, actually email them. They're nice, I promise.)


🌸 AUTHOR 🌸

Gris Ge <fge@redhat.com>


And that's the whole page, babe β€” local_lsmplugin version 1.10.3, from way back in July 2017, still iconic, still doing the most so you don't have to. 🧚✨

πŸ“¦ where this page comes from