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

SDP 0.16.0

    XporterXMLWordPrintable

Details

    • Sub-system Version
    • Resolution: Resolved
    • PI19
    • COM SDP SW

    Description

      Summary

      The SDP version is available to integrate in Mid and Low ITFs as part of solution goals SPO-2490 and SPO-2493.

      Added

      • Add new "Using the SDP" section in the documentation.
      • Add queue connector Tango devices to exchange data between Tango and the SDP data queues.

      Changed

      • Change behaviour of subarray Configure command to wait for processing resources to be ready before entering READY observing state.
      • Update ska-sdp-qa chart dependency to 0.18.0.
      • Update ska-tango-base chart dependency to 0.4.6.

      Removed

      • Remove old QA metrics Tango device. This functionality will be exposed via the new queue connector Tango devices.
      • Remove operator web interface. This was developed as a proof-of-concept way to monitor the configuration DB, but it had not been updated for some time and was not exposed to users outside the cluster.
      • Remove data product dashboard. This was available as an optional dependency of the SDP, but it will now be deployed as a separate product.

      Fixed

      • Add checks on processing namespace / Helm release prefix to avoid problems if the SDP is deployed in a single namespace (not recommended).

      Testing

      SDP Integration test plan: XTP-25468
      Test execution for this release: XTP-26348

      Attachments

        Issue Links

          Delivers

          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-3185 Wait for underlying resources to be ready on Subarray Configure

          • 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-3466 Improve documentation of SDP releases

          • 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-2981 Resolve SDP signal display SKAMPI integration issues and add functionality for multiple baselines

          • 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-3216 Prepare for integration of Tango devices for visibility receive (QA) metrics

          • 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-3229 Integrate Tango devices for real-time data exchange

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

          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          mentioned on

          GitLab Commit - REL-670: bumped version to 0.16.0

          Features

          Structure

            Activity

              People

                m.ashdown Ashdown, Mark
                m.ashdown Ashdown, Mark
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Structure Helper Panel