GEOSTORE(8)

📦
version 1.2 · 9 versions
, in ubuntu resolute, ubuntu stonking

✨ GEOSTORE(8) ✨

okay bestie, pull up a chair, because this is geostore from the (8) section of the manual — aka the geo cluster attribute manager 💅 and she is lowkey the backbone of your GEO cluster's gossip network.

🌸 NAME 🌸

geostore — geo cluster attribute manager 🫶

🎀 SYNOPSIS 🎀

geostore set [-t ticket] [-s site] [-c config] attribute value

geostore get [-t ticket] [-s site] [-c config] attribute

geostore delete [-t ticket] [-s site] [-c config] attribute

geostore list [-t ticket] [-s site] [-c config]

💖 DESCRIPTION 💖

so like, apps running in GEO cluster environments sometimes need more info than just tickets to make their little decisions. the iconic example? the status of data replication. your app is nosy, it wants tea, and geostore is here to serve it ☕✨

geostore is a helper program that manages site attributes. and here's the key detail, bestie — attributes are defined on a per-ticket basis, meaning every ticket can have one or more attributes. it's giving "everyone gets their own locker" energy 🔐

she can:

  • set an attribute value ✏️
  • retrieve an attribute 🔍
  • delete it 🗑️

the attributes get stored in the CIB status section, which is managed by the pacemaker cib process. and boothd(8) is the one providing transport for attributes to other sites — she's the ✈️ of the operation.

then crm_ticket(8) gets invoked at the target site to actually manage the attributes. teamwork makes the dream work, fr fr 🫶

🌈 SHORT EXAMPLES 🌈

# geostore set -t ticket-A -s other bigdb-repl-status UPTODATE

# geostore get -t ticket-A -s other bigdb-repl-status

# geostore delete -t ticket-A -s 44.0.0.61 bigdb-repl-status

# geostore list -t ticket-A -s other

✨ OPTIONS ✨

  • -t — the ticket scope of the attribute. this one is required if more than one ticket is configured, so don't come in here ticketless bestie 🎟️
  • -s — the site address or name where the attribute is gonna be stored or retrieved 🗺️
    • the special value 'other' can be used to specify the other site. obviously, in that case, the booth configuration must have exactly two sites defined. no cap, two, that's the number 👯
  • -c configfile — which configuration to use 💾
    • this can be either a full path to a configuration file, or just a short name — and if it's a short name, the directory /etc/booth and the suffix .conf get added on for you. per default booth is used, which results in the path /etc/booth/booth.conf. iconic default behaviour, we love a shortcut 🎀
  • -h, --help — gives you a short usage output. when in doubt, ask for help, that's main character energy 🙋‍♀️

👑 COMMANDS 👑

  • set — sets the attribute to the value ✏️
  • get — gets the attribute value and prints it to stdout. but if the attribute doesn't exist? appropriate error message gets printed to stderr. sad girl hours but at least it tells you 😭
  • delete — deletes the attribute. and bestie, if the attribute doesn't exist, an appropriate error message is printed to stderr. same energy 💀
  • list — lists all attributes and their values stored at the site. full inventory, no crumbs left behind 📋

⭐ EXIT STATUS ⭐

  • 0 — success, we ate, no crumbs 🍽️✨
  • 1 — request failed or bad usage. it's giving "oop" 🙈

🦋 RESOURCES 🦋

GitHub: https://github.com/ClusterLabs/booth

💜 COPYING 💜

Copyright © 2015 Dejan Muhamedagic dmuhamedagic@suse.com

Free use of this software is granted under the terms of the GNU General Public License (GPL) as of version 2 (see COPYING file) or later.

🌸 SEE ALSO 🌸

boothd(8), crm_attribute(8)

reminder bestie: -t is required when you've got more than one ticket configured, and 'other' only works if your booth config has exactly two sites. don't say I didn't warn you 💅

and that's the whole page, angel 💖 this was GEOSTORE(8), dated 2026-02-03 — go forth and manage those site attributes, you absolute icon 👑✨

📦 where this page comes from