BCDA-APS / use_bluesky

Tools to help APS use the Bluesky Framework (https://blueskyproject.io/)
8 stars 3 forks source link

use intake-style catalog #76

Closed prjemian closed 3 years ago

prjemian commented 3 years ago

Following this advice, switch use_bluesky/admin/make_catalog.py to use intake-style catalogs and store them per recommendations here.

@danielballan : Thanks for the tip!

[Bluesky] made an intentional choice to adopt intake-style configuration (both the format and the config directory location) and relegate databroker ones to backward-compatible legacy.

prjemian commented 3 years ago

Example Broker-style configuration file:

assets:
  class: Registry
  config:
    database: test1-file_refs
    host: poof
    port: 27017
  module: databroker.assets.mongo
description: heavyweight shared database
metadatastore:
  class: MDS
  config:
    database: test1-run_data
    host: poof
    port: 27017
    timezone: US/Central
  module: databroker.headersource.mongo
prjemian commented 3 years ago

Example intake-style configuration file, using mongodb:

sources:
  intake_test1:
    driver: bluesky-mongo-normalized-catalog
    args:
      metadatastore_db: mongodb://poof:27017/test1-run_data
      asset_registry_db: mongodb://poof:27017/test1-file_refs
prjemian commented 3 years ago

Q: Where do configuration files go? A:

style location
Broker ~/.config/databroker
intake see databroker.catalog_search_path() (first location is typical: ~/.local/share/intake)
prjemian commented 3 years ago

Working: ./make_catalog.py poof quokka_intake -o ~/.local/share/intake