Uploaded image for project: 'Request For Comments'
  1. Request For Comments
  2. RFC-456

Adopt LDM-148 with terminology and product/component rationalization

    Details

    • Type: RFC
    • Status: Implemented
    • Resolution: Done
    • Component/s: DM, TCT
    • Labels:

      Description

      I propose to adopt new versions of the LDM-148 system design. These versions primarily synchronize terminology and descriptions with the Ops Concepts in LDM-230 and the infrastructure in LDM-129, as well as adding a couple of products/components that are new to the design.

      The new version is visible at https://ldm-148.lsst.io/ and is in DocuShare.

      Changes include:

      • Replace "domain" terminology with "enclave"
      • Add Observatory Operations Data Service
      • Describe Header Generator as part of Image and EFD Archiving
      • Move Qserv from DBB to LSP
      • Describe Planned Observation Publishing Service
      • Replace Level 1/2/3 terminology where appropriate
      • Unify Batch Processing services and Batch Production (formerly various Production Execution) services and mention Special Programs processing
      • Combine Alert Distribution/Filtering
      • Expand infrastructure service list and descriptions in accordance with LDM-230
      • Incorporate the latest product tree, traceability, and diagrams
      • Update descriptions of the OODS and DBB
      • Generate some diagrams from MagicDraw instead of OmniGraffle

        Attachments

          Issue Links

            Activity

            Hide
            spietrowicz Steve Pietrowicz added a comment -

            I'm reading through this and found a minor typo - "dataabases" should be "databases".

            Show
            spietrowicz Steve Pietrowicz added a comment - I'm reading through this and found a minor typo - "dataabases" should be "databases".
            Hide
            ktl Kian-Tat Lim added a comment -

            Steve Pietrowicz If that's the worst error in the document, I'll be quite happy! (Not yet committing that fix in anticipation of others to come.)

            Show
            ktl Kian-Tat Lim added a comment - Steve Pietrowicz If that's the worst error in the document, I'll be quite happy! (Not yet committing that fix in anticipation of others to come.)
            Hide
            womullan Wil O'Mullane added a comment -

            Enclave just appears first on page 4 "The Data Backbone links all of the enclaves" with no idea what that is. That may be ok but I would expect in Section 4 some line on enclaves in the first paragraph  where the relation of services and components is described - perhaps include enclaves there ? ..

             

            Should we include in figure 5 title or near it a link to pipelines.lsst.io ?

            Though mentioned before rementioning the middle ware documents near figure 6 would seem appropriate - that figure has super task and Butler in it , butler is mentioned on page 13 and a task framework but not super task.

             

            5.1.2 there is now a IVOA paper on publishing planned observations .. but I guess we do not need to mention that here yet.

            5.1.3 Should Level 1 Domain be Prompt NCSA Enclave  - Domain is not mentioned elsewhere  (and should it have a forward ref to that section ?)

             

            10.1 should we mention LDM-635 for DBB?  Or does that mean we should mention all the requirements docs somewhere  .. so perhaps not in this version but next time.   I see all the design docs are mentioned - so perhaps that is more correct for LDM-148.

             

             

            This reads pretty well and gives a good overview.

             

            Show
            womullan Wil O'Mullane added a comment - Enclave just appears first on page 4 "The Data Backbone links all of the enclaves" with no idea what that is. That may be ok but I would expect in Section 4 some line on enclaves in the first paragraph  where the relation of services and components is described - perhaps include enclaves there ? ..   Should we include in figure 5 title or near it a link to pipelines.lsst.io ? Though mentioned before rementioning the middle ware documents near figure 6 would seem appropriate - that figure has super task and Butler in it , butler is mentioned on page 13 and a task framework but not super task.   5.1.2 there is now a IVOA paper on publishing planned observations .. but I guess we do not need to mention that here yet. 5.1.3 Should Level 1 Domain be Prompt NCSA Enclave  - Domain is not mentioned elsewhere  (and should it have a forward ref to that section ?)   10.1 should we mention LDM-635 for DBB?  Or does that mean we should mention all the requirements docs somewhere  .. so perhaps not in this version but next time.   I see all the design docs are mentioned - so perhaps that is more correct for LDM-148.     This reads pretty well and gives a good overview.  
            Hide
            womullan Wil O'Mullane added a comment -

            with PR#10 this looks good to go

            Show
            womullan Wil O'Mullane added a comment - with PR#10 this looks good to go
            Hide
            ktl Kian-Tat Lim added a comment -

            "dataabases": fixed.

            "Enclave": I removed the early appearance under DBB and added a definition before the list of enclaves and facilities.

            Link to pipelines.lsst.io: added at the end of the Pipelines section.

            SuperTask: added pipe_supertask to the package list for Middleware.  Didn't remention the middleware design document, as then they'd all have to be.

             

            IVOA paper: not mentioned yet.

            Level 1 Domain: fixed (missed this before since it was split over a line boundary).

            Requirements docs: not mentioned yet.

            Show
            ktl Kian-Tat Lim added a comment - "dataabases": fixed. "Enclave": I removed the early appearance under DBB and added a definition before the list of enclaves and facilities. Link to pipelines.lsst.io: added at the end of the Pipelines section. SuperTask: added pipe_supertask to the package list for Middleware.  Didn't remention the middleware design document, as then they'd all have to be.   IVOA paper: not mentioned yet. Level 1 Domain: fixed (missed this before since it was split over a line boundary). Requirements docs: not mentioned yet.

              People

              • Assignee:
                ktl Kian-Tat Lim
                Reporter:
                ktl Kian-Tat Lim
                Watchers:
                Gabriele Comoretto, Gregory Dubois-Felsmann, Jeff Kantor, John Swinbank, Kian-Tat Lim, Steve Pietrowicz, Tim Jenness, Wil O'Mullane
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Planned End:

                  Summary Panel