Uploaded image for project: 'Release Management'
  1. Release Management
  2. REL-191

SDP 0.13.0

    XporterXMLWordPrintable

Details

    • Sub-system Version
    • Resolution: Resolved
    • PI17
    • COM SDP SW
    • None

    Description

      Summary

      Added

      • Add options to use an existing persistent volume claim (PVC) or create a new one for storing data products.

      Changed

      • Update QA sub-chart to 0.13.0
        • QA display is deployed by default.
        • Add QA metrics Tango device (not deployed by default)
      • Visibility receive test downloads telescope layout using ska-telmodel client

      Attachments

        Issue Links

          Delivers

          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-2704 SDP monitoring dashboard of Tango devices

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          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-2705 API for monitoring the visibility receive workflow

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          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-2706 Visibility receive provides health statistics

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          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-2746 Integrated QA displays for updated visibility receive functionality

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          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-2747 Test multi-scan visibility receive in persistent SDP deployment

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-2944 Implement consistent strategy for writing SDP data products

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          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-2703 Configuration of SDP Tango attribute archiving (& alarms)

          • 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.
          • Done

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-3007 SDP can be configured to use specific telescope model version

          • 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.
          • Done
          links to

          Web Link ska-sdp-integration:0.13.0

          mentioned in

          Page Loading...

          mentioned on

          GitLab Commit - REL-191: bumped version to 0.13.0

          GitLab Merge request - DPPT-481: Update SDP to 0.13.0

          Features

          Structure

            Activity

              People

                m.ashdown Ashdown, Mark
                b.mort Mort, Ben
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Structure Helper Panel