logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

geostore - geo cluster attribute manager

Commands

set
           Sets the attribute to the value.

       get
           Get the attribute value and print it to stdout. If the attribute doesn’t exist, appropriate error
           message is printed to stderr.

       delete
           Delete the attribute. If the attribute doesn’t exist, appropriate error message is printed to stderr.

       list
           List all attributes and their values stored at the site.

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.

Description

       Applications running in GEO cluster environments may need more information apart from tickets to make
       decisions. One example may be the status of data replication.

       geostore is a helper program to manage site attributes. The attributes are defined on a per-ticket basis,
       that is every ticket may have one or more attributes.

       It can set an attribute value, retrieve an attribute, or delete it. The attributes are stored in the CIB
       status section which is managed by the pacemaker cib process. boothd(8) provides transport for attributes
       to other sites.

       crm_ticket(8) is invoked at the target site to manage the attributes.

Exit Status

0
           Success.

       1
           Request failed or bad usage.

Name

       geostore - geo cluster attribute manager

Options

-t
           Ticket scope of the attribute (required, if more than one ticket is configured).

       -s
           Site address or name where the attribute is to be stored/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.

       -cconfigfile
           Configuration to use.

           Can be a full path to a configuration file, or a short name; in the latter case, the directory
           /etc/booth and suffix .conf are added. Per default booth is used, which results in the path
           /etc/booth/booth.conf.

       -h, --help
           Give a short usage output.

Resources

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

See Also

boothd(8), crm_attribute(8)

                                                   2025-06-03                                        GEOSTORE(8)

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

Synopsis

geostoreset [-t ticket] [-s site] [-c config] attributevaluegeostoreget [-t ticket] [-s site] [-c config] attributegeostoredelete [-t ticket] [-s site] [-c config] attributegeostorelist [-t ticket] [-s site] [-c config]

See Also