Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-2050

Integration and test monitoring architecture Part I

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: QA
    • Labels:
      None
    • Epic Name:
      sqre-metrics-infra-capture-one
    • Story Points:
      100
    • WBS:
      02C.01.02
    • Team:
      SQuaRE
    • Cycle:
      Winter 2016

      Description

      [retitled to better capture cycle scope]

      Develop and deploy a layer to capture the outputs, initially numeric,
      of integration testing afterburners such as sdss_demo, hsc_demo, and
      others developed this cycle. Also capture meta-information such as
      execution time and memory footprint. Propose log format to standardise
      production of such informations. Investigate notification system based
      on trending away from expected values. Investigate data provisioning
      of integration tests such as storage of test data in GithubLFS.

      [75% JMP 25% JH]

        Attachments

          Issue Links

          blocks

          Milestone - An overall project milestone DLP-351 Intermediate Performance Metrics routinelly calculated and published

          • Major - Major loss of function.
          • Closed
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. DM-5420 Integration and test monitoring implementation Part I

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-268 Create a safe archive for the astrometry_net_data and other test datasets

          • Done

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. DM-3858 Integration and test monitoring architecture Part II

          • Done

          Stories in Epic (Custom Issue Matrix)

          Key Summary Story Points Assignee Status
           
          		DM-4970

          Investigate logging, monitoring and metrics technologies and architecture

          		 24 J Matt Peterson [X] (Inactive) Done
           
          		DM-4957

          Generate JSON output from validate_drp for inclusion in a test harness

          		 2 Michael Wood-Vasey Done
           
          		DM-4889

          Update git-lfs repositories to point to the git-lfs documentation.

          		 1 J Matt Peterson [X] (Inactive) Done
           
          		DM-4888

          Update git-lfs documentation to work with git-lfs 1.1.0+

          		 2.5 J Matt Peterson [X] (Inactive) Done
           
          		DM-5977

          Create and deploy Beats for Logstash and Elasticsearch.

          		 3 J Matt Peterson [X] (Inactive) Done
           
          		DM-4750

          git push of an LFS didn't show password prompt

          		 J Matt Peterson [X] (Inactive) Done
           
          		DM-4650

          Update sims_dustmaps/sims_maps repository to use git-lfs

          		 1 J Matt Peterson [X] (Inactive) Done
           
          		DM-4649

          Create and rename the sims_dustmaps repository to sims_maps

          		 2 J Matt Peterson [X] (Inactive) Done
           
          		DM-4390

          lfs pull breaks with valid github credentials

          		 J Matt Peterson [X] (Inactive) Done
           
          		DM-4371

          Migrate remaining large gitolite repos to lfs

          		 J Matt Peterson [X] (Inactive) Done
           
          		DM-4370

          Migrate testdata for DECam from disk to git-lfs

          		 0.5 J Matt Peterson [X] (Inactive) Done
           
          		DM-4369

          Migrate lsst/ci_hsc repo to git-lfs.lsst.codes

          		 4 J Matt Peterson [X] (Inactive) Done
           
          		DM-3921

          Create and deploy a git-lfs prototype

          		 64 J Matt Peterson [X] (Inactive) Done
           
          		DM-3685

          Evaluate GitLFS

          		 17 J Matt Peterson [X] (Inactive) Done
           
          		DM-2518

          Add a CFHT-based post-build integration test to the sandbox build

          		 1 Michael Wood-Vasey Done
           
          		DM-4522

          git on lsst-dev is too old for git-lfs

          		 J Matt Peterson [X] (Inactive) Won't Fix

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            wmwood-vasey Michael Wood-Vasey added a comment -

            J Matt Peterson [X] Joshua Hoblitt David Nidever [X] Frossie Economou

            Where does work on designing this test monitoring architecture stand? I don't see an issue related to this Epic that is something like "Design Layer". Should that be added? To whom who it be assigned?

            I'd like to start connecting the validation outputs in `validate_drp` to a test harness.

            What kind of outputs should `validate_drp` produce for this test harness?

            Show
            wmwood-vasey Michael Wood-Vasey added a comment - J Matt Peterson [X] Joshua Hoblitt David Nidever [X] Frossie Economou Where does work on designing this test monitoring architecture stand? I don't see an issue related to this Epic that is something like "Design Layer". Should that be added? To whom who it be assigned? I'd like to start connecting the validation outputs in `validate_drp` to a test harness. What kind of outputs should `validate_drp` produce for this test harness?
            Hide
            Permalink
            frossie Frossie Economou added a comment -

            Hi Michael Wood-Vasey, we're stilll prototyping for this part of the harness, which is intended to capture scalars, the interface is going to be via structured log messages, so if you will just output JSON with your parameters of interest for now, we shouldn't have to make too many changes later.

            Show
            frossie Frossie Economou added a comment - Hi Michael Wood-Vasey , we're stilll prototyping for this part of the harness, which is intended to capture scalars, the interface is going to be via structured log messages, so if you will just output JSON with your parameters of interest for now, we shouldn't have to make too many changes later.
            Hide
            Permalink
            wmwood-vasey Michael Wood-Vasey added a comment -

            Thanks for the clarification and suggestion to output something in JSON.

            Will do as: DM-4957

            Show
            wmwood-vasey Michael Wood-Vasey added a comment - Thanks for the clarification and suggestion to output something in JSON. Will do as: DM-4957
            Hide
            Permalink
            jmatt J Matt Peterson [X] (Inactive) added a comment -

            Completed. Any additional work has been moved to new epics in other cycles.

            Show
            jmatt J Matt Peterson [X] (Inactive) added a comment - Completed. Any additional work has been moved to new epics in other cycles.

              People

              Assignee:
              jmatt J Matt Peterson [X] (Inactive)
              Reporter:
              frossie Frossie Economou
              Watchers:
              Frossie Economou, J Matt Peterson [X] (Inactive), Michael Wood-Vasey
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.