Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-4228

Define the test campaigns

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • SRCnet
    • Hide

      BH: Data lifecycle tests are the closest tests to the behaviour expected by the operations group, so they will provide good metrics of the behaviour of the SRCNet and, also, support the identification of bottlenecks. We will want to run these tests during SRCNet0.1 testing campaigns (2025) so need to build out these tests in PI23 and PI24.

      Show
      BH: Data lifecycle tests are the closest tests to the behaviour expected by the operations group, so they will provide good metrics of the behaviour of the SRCNet and, also, support the identification of bottlenecks. We will want to run these tests during SRCNet0.1 testing campaigns (2025) so need to build out these tests in PI23 and PI24.
    • Hide

      AC1: List provided of data lifecycle tests with links to test in rucio task manager repisitory.

      AC2: For every test, documentation that should allow the execution at any SRC and information to ensure a proper analysis of the results

      AC3: All of the information needed to put into test yaml is captured (somewhere, writing the actual test yaml isn't required)

      AC4: Define the Dashboard View to be used for verification of successful tests

      AC5: Feedback gathered from the ART and sites to identify gaps in definition of the test framework and dashboard

      Stretch: Implementation of the dashboard

      Show
      AC1: List provided of data lifecycle tests with links to test in rucio task manager repisitory. AC2: For every test, documentation that should allow the execution at any SRC and information to ensure a proper analysis of the results AC3: All of the information needed to put into test yaml is captured (somewhere, writing the actual test yaml isn't required) AC4: Define the Dashboard View to be used for verification of successful tests AC5: Feedback gathered from the ART and sites to identify gaps in definition of the test framework and dashboard Stretch: Implementation of the dashboard
    • 2
    • 2
    • 0
    • Team_CORAL, Team_SPT

    • PI23 - UNCOVERED

    • SRC23-PB SRCNet0.1 data-lifecycle tests-compilation

    Description

      These will be one category of tests driving the test Campaigns for SRCNetv0.1

      These will be end-to-end data lifecycle tests:

      • Starting from data ingestion
      • Data replication to multiple sites
      • Data processing e.g. via Jupyter notebooks (or data visualisation)
      • Uploading of new data products

      Data lifecycles to be identified that focus on capturing the operational interaction of multiple components like ingestion, DDM and compute across v0.1 sites (as opposed to prioritised user science workflows)

      These data lifecycle tests should be documented (e.g. confluence) and software elements should be provided in a portable format (mainly notebooks with the proper documented environment or containers if this implies the use of a certain batch processing library or similar)

      Result expected:

      Documented set of ‘live’ tests conducted during the identified high-availability window describing the data lifecycle being demonstrated, sites participating, data used (type/volume), workflow chosen, and description of any new data ingested. The Operations team will likely be consolidating this information in preparation for the test campaigns. Where applicable demos of the tests conducted, and dashboard views showing data ingestion, and replication.

       

       

      Attachments

        Issue Links

          relates to

          Spike - A time limited investigation to get some knowledge SP-4251 Investigate use of WLCG DC inject tool for (task manager) V0.1 Data moving campaign scenarios

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Implementing

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4257 Development of sufficient functionality for v0.1 Data Challenge tests

          • Not Assigned - Priority is not assigned yet.
          • Funnel

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4229 Establish a simulated-test-data generation pipeline for v0.1 (using Karabo)

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Implementing
          mentioned in

          Page Loading...

          Structure

            Activity

              People

                Jesus.Salgado Salgado, Jesus
                Jesus.Salgado Salgado, Jesus
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do13.0
                  In Progress   00.0
                  Complete00.0
                  Total13.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel