Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The server-side code (which receives http requests on the database server) is here:  https://github.com/slac-lcls/psdm_configdb.  The client-side code (which forms the http requests) is here:  https://github.com/slac-lcls/lcls2/tree/master/psdaq/psdaq/configdb.


Configuration history management

Two scripts are available for configuration history management:

  • configdb_key_history: this script can be used to explore configuration history. It takes hutch, alias and device as arguments (plus authentication information):
    python configdb_key_history.py --user tmoopr --password pcds --hutch tmo --alias NOBEAM --device hsd_0

    And returns a list of configurations for the specific hutch/alias/device with date and key. The key can be used to retrieve the specific configuration using the configdb_rollback.py script.

  • configdb_rollback.py: this script can be used to retrieve a specific device configuration, and, optionally, to make it the current configuration for the device. It takes hutch, alias and device (and authentication information) as arguments, plus a key defining a device configuration (see the configdb_key_history.py script above):
    python configdb_rollback.py --user tmoopr --password pcds --hutch tmo --alias NOBEAM --device hsd_0 --key 266

    By default, the script just shows the configuration. However, when the --write-to-database option is used, the scripts write the retrieved configuration as the current configuration of the same hutch/alias/device.