Send Kafka notifications when correction is complete

Description

We're experimenting with the migration system sending Kafka notifications, including when migration has completed and a raw run is available on Maxwell ('event': 'migration_complete'). It would be nice to have similar notifications when a corrected run is available, and the calibration webservice is the obvious place to send those.

This is very minimal at the moment. It would be nice to send more information (migration events also have run directory, instrument & cycle), but this isn't easy without changing the sqlite database, which is a bigger change than I wanted to make at the moment. It could be extended to add events when correction starts, and events for characterisation (e.g. dark processing).

It will also need some work to handle multiple kinds of processing running on the same run. We probably want events when each piece of processing completes (with a robust way to identify which is which), and another event when everything that writes to proc/r0123/ has finished. But we shouldn't let the perfect be the enemy of the good, IMO.

How Has This Been Tested?

Run on max-exfl017, re-corrected a CALLAB run while listening for the event. This is the result I got:

{'event': 'correction_complete',
 'proposal': '900113',
 'run': '9998',
 'detector': 'lpd',
 'success': True}

Types of changes

• New feature (non-breaking change which adds functionality)

Checklist:

• My code follows the code style of this project.

Reviewers

@danilevc @ahmedk

webservice/update_mdc.py

 import argparse
+import os.path as osp
 
 import yaml
 from metadata_client.metadata_client import MetadataClient
@@ -6,8 +7,8 @@ from metadata_client.metadata_client import MetadataClient
 parser = argparse.ArgumentParser(
     description='Update run status at MDC for a given run id.')
 parser.add_argument('--conf-file', type=str, help='Path to webservice config',
-                    default='/home/xcal/calibration_webservice_deployed/webservice/webservice.yaml')  # noqa
-parser.add_argument('--flg', type=str, choices=["NA", "R", "A"],
+                    default=osp.join(osp.dirname(__file__), 'webservice.yaml'))
+parser.add_argument('--flg', type=str, choices=["NA", "R", "A"], required=True,
                     help='Status flag for MDC request: NA - not available, R - running, A - available.')  # noqa
 parser.add_argument('--rid', type=int, help='Run id from MDC')
 parser.add_argument('--msg', type=str, help='Message string to MDC',
@@ -32,6 +33,7 @@ client_conn = MetadataClient(client_id=mdconf['user-id'],
                              scope=mdconf['scope'],
                              base_api_url=mdconf['base-api-url'])
 
+print(f"Updating run {rid} to status {flg} at {mdconf['base-api-url']}")
 response = client_conn.update_run_api(rid, {'flg_cal_data_status': flg,
                                             'cal_pipeline_reply': msg})