Agreed with Gregory Dubois-Felsmann that LSP design documentation can be baselined (nearly) as is, ie going for RFC within the next couple of weeks (addressing outstanding action item).
Margaret Gelman: Open a Jira ticket to describe the mechanism by which service status information will be propagated to DM staff, with review by Frossie Economou & John Swinbank.
Jeff Kantor: Provide details of the ITRFC or other ITSC documentation which pertains to service catalogues as links on this page.
We almost certainly want to convene a WG for this.
Does the DMLT agree?
If so, let's write the charge now.
We agreed that we would convene a short-term focused “tiger team” to come up with a plan for potentially more than one WG to split up this work.
John Swinbank: Convene a series of calls to come up with a high-level plan for “QA” in the most general sense in the short term, with participation to be agreed between him & Wil O'Mullane.
Initial compute access via NFS mount from the OODS in the AuxTel Archiver box and (manually) selected data preservation in the LDF production filesystem in Jun 2018 is fine. Integration of spectrophotometric algorithms, including calibration generation, with the Batch Production Framework can begin with an initial pipeline using the Gen3 SuperTask in Jan 2019, with production operations targeted for Jun 2019.
The EFD should be active on the summit in Apr-May 2018 but may be late; the EFD Transformation Service cannot go live until the Base EFD is available (expected Jun 2019) and is not absolutely required until ComCam arrives.
Margaret Gelman: Determine with Michael Reuter and Dave Mills whether EFD disaster recovery needs LDF support, especially in the Apr 2018-Jun 2019 single-instance period.
Base data center occupancy is expected in Nov 2018, but we will suggest to Chuck Claver that the Commissioning Cluster not be installed until Jun 2019. He should have access to an equivalent "practice" system in the LDF Kubernetes commons until then.
The move of the one-box Auxiliary Telescope Archiver from the summit to the Base needs to happen in or before Jun 2019 and needs to be coordinated well since it may cause Auxiliary Telescope downtime.
Ensure that we are on track for all LDM-503 milestones over the remainder of this year.
By the time of the next Joint Status Review, we must have test specifications for every milestone we plan to execute. How do we get there? Need to start handing out homework.
Milestones this year
Milestone
Date (March 2018 BL)
Name
Status
LDM-503-01
2017-11-30
Science Platform with WISE data in PDAC
Test spec exists on a branch; will be submitted to CCB ASAP.
Test report is being written, aiming to get it completed quickly.
LDM-503-04
2018-06-01
Aux Tel DAQ integration functionality test
Test spec is close to being submitted.
Test is done.
Test report is not started.
LDM-503-04b
2018-06-01
Aux Tel DAQ interface Verification and Spectrograph Operations Rehearsal
Discussions ongoing on contents of test given available functionality.
Missing functionality can be called out in the test report.
Running this end of March.
LDM-503-05
2018-07-02
Alert distribution validation
Thinking about this in the Alert Production/UW group. We will be writing a test spec over the next ~month.
Needs to run on LDF hardware; will open discussions with the LDF group about how this will happen.
We should consider whether any L1 database tests actually happen in this milestone.
This demonstrates that we can run science payloads on camera test stand data.
No reason we can't address this soon; ~summer 2018 (just after the joint status review).
Goal would be to load and process a full raft; can handle this within the DRP team, and demonstrate access from the science validation instance of the science platform. John Swinbank will coordinate this with Unknown User (xiuqin).
May need a further LDM-503 milestone to demonstrate interfaces.
LDM-503-08
2018-11-30
Spectrograph Data Acquisition
Intent is to show that we're ready for spectrograph operations on the mountain.
Test DM-only systems from archiver box at summit to LDF.
We should regard the end point of this milestone as making the data available for processing.
Milestone is tied to availability of the archiver box on the mountain; likely means this test actually takes place in January 2018.
Will cover both DM services provided to commissioning & pipeline functionality.
Could use AuxTel & data from it for this rehearsal.
LDM-503-10
2018-11-30
DAQ validation
Would be valuable to run a full scale data acquisition test later in the schedule than this (Jeff Kantor suggests November 2019 with no alert latency test).
Wil O'Mullane will make that happen & update PMCS, LDM-503, appropriately.
LDM-503-09 was scheduled for Nov 2018, but has slipped to 2019 during PMCS ingest; it will likely float forward again as we finesse the milestone loading.
Wil O'Mullane: Update the test description (to reflect that it will be run as a full scale data acquisition test) and schedule (to November 2019) of LDM-503-10 in PMCS.