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

SDP Integration in an end-to-end software deployment

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

Details

    • Feature
    • Must have
    • PI14
    • COM SDP SW
    • None
    • Data Processing
    • Hide

      Integration is critical for ensuring that SDP can participate in observations together with the other SKA sub-systems. We need to ensure that this exercises all the important interfaces and behaviours that will be relevant to the SDP.

      Show
      Integration is critical for ensuring that SDP can participate in observations together with the other SKA sub-systems. We need to ensure that this exercises all the important interfaces and behaviours that will be relevant to the SDP.
    • Hide
      • Integration test in SKAMPI where TMC controls SDP to perform a scan (i.e. assigns resources, configures + executes scan(s))
      • Especially means providing appropriate configuration strings to TMC for either Mid (SP-2404) or Low (SP-2403)
      • The test should demonstrate the generation of a measurement set file
      • Stretch: Implement or prepare for required changes for SBI->EB change and/or ADR-16 (or even ADR-54 if we manage to decide it)
      Show
      Integration test in SKAMPI where TMC controls SDP to perform a scan (i.e. assigns resources, configures + executes scan(s)) Especially means providing appropriate configuration strings to TMC for either Mid ( SP-2404 ) or Low ( SP-2403 ) The test should demonstrate the generation of a measurement set file Stretch: Implement or prepare for required changes for SBI->EB change and/or ADR-16 (or even ADR-54 if we manage to decide it)
    • Intra Program
    • 5
    • 5
    • 13
    • 2.6

    • Sub-system Version REL-109 SDP 0.10.1

      Sub-system Version REL-93 SDP 0.10.0

      Sub-system Version REL-8 SDP 1.0.x

    • Team_ORCA
    • Sprint 5
    • Hide

      It has not been possible to do end-to-end tests of the SDP with TMC because TMC was not fully refactored and reintegrated until the end of the PI. We offered our support to the NRCA team, but we have not been called upon to provide any.

      As preparation for an end-to-end test of the visibility receive workflow, we decided to implement it as a component test in the Skampi pipeline. We refactored the visibility receive test in the SDP integration pipeline to make creating and deleting persistent volume claims part of the test, and added the test marker so it would be executed as a component test in the Skampi pipeline. We enlisted the help of the System team to create a service account to allow the pod running the component tests in the Skampi pipeline to create and delete PVCs. However, the component tests were removed from the Skampi pipeline this PI, so after discussion with the stakeholders, we decided not to re-enable them.

      The SBI -> EB change will be implemented as part of the Great Renaming which will also rename "workflows" to "processing scripts", among other things.

      Show
      It has not been possible to do end-to-end tests of the SDP with TMC because TMC was not fully refactored and reintegrated until the end of the PI. We offered our support to the NRCA team, but we have not been called upon to provide any. As preparation for an end-to-end test of the visibility receive workflow, we decided to implement it as a component test in the Skampi pipeline. We refactored the visibility receive test in the SDP integration pipeline to make creating and deleting persistent volume claims part of the test, and added the test marker so it would be executed as a component test in the Skampi pipeline. We enlisted the help of the System team to create a service account to allow the pod running the component tests in the Skampi pipeline to create and delete PVCs. However, the component tests were removed from the Skampi pipeline this PI, so after discussion with the stakeholders, we decided not to re-enable them. The SBI -> EB change will be implemented as part of the Great Renaming which will also rename "workflows" to "processing scripts", among other things.
    • 15.1
    • Stories Completed, Integrated, Solution Intent Updated, BDD Testing Passes (no errors), Outcomes Reviewed, NFRS met, Satisfies Acceptance Criteria, Accepted by FO

    • PI24 - UNCOVERED

    • SPO-1590

    Description

      Who?

      For developers of components and other systems that integrate with SDP. 
      For AIV engineers designing and running tests of the SDP system.

      What?

      Improvements to SDP as a well defined, documented, easily deployable product with testable public interfaces.

      Support/collaboration in end-to-end tests (captured in XRay) that verify the behaviour of a configured SKA software deployment that includes the SDP (sub-)system, considering use cases for:

      • Start-up of the telescope
      • Operate and monitor the telescope (possibly considering work being done under SP-2363)
      • (stretch) Access, inspect and analyse telescope data

      The exact nature of end-to-end tests depends somewhat on the code integrated as part of SS-90

      Timeboxed consideration of technical debt carried from SDP reintegration into SKAMPI that would otherwise block running SDP for identified PSI tests (eg https://confluence.skatelescope.org/display/SE/PSI+Mid+System+Integration+Test+1)

       

      Why?

      Support system integration activities and testing at PSI where SDP is deployed.

       

      Other notes:

      • Timeboxed activity to address technical debt remaining from SDP integration
      • Support revised testing from introducing new e2e test resulting from the integration of new products (and new SDP components?) into SKAMPI
      • Timeboxed update to user and developer SDP documentation to capture latest changes and make it easier for additional developers to contribute to this in future.
      • Timeboxed activity to work with AIV engineers to define and develop PSI tests

      Attachments

        Issue Links

          Child Of

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SS-77 Software Deployment configuration in AA0.5 and ITF

          • 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. SS-90 Reintegrate missing components into SKAMPI

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

          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-2403 Observational Scan (including configure) for TMC in Low

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

          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-2404 Observational Scan (including configure) for TMC in Mid

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • Discarded
          Is delivered by

          Sub-system Version - A version of a sub-system, used in the Release Management and Configuration Management process REL-8 SDP 1.0.x

          • Discarded

          Sub-system Version - A version of a sub-system, used in the Release Management and Configuration Management process REL-93 SDP 0.10.0

          • Released

          Sub-system Version - A version of a sub-system, used in the Release Management and Configuration Management process REL-109 SDP 0.10.1

          • Released
          relates to

          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-2593 AA2 visibility receive pipeline

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • 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-2466 CBF-SDP emulator sends correlator data dumps

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • 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-2363 Visibility Receive workflow enhancements

          • 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-2483 Visibility Receive Multiple Scan Support (ADR-54)

          • 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-2262 Integration effort: End-to-End On/Off Command Test: OET → TMC → SDP

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • Discarded
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                p.wortmann Wortmann, Peter
                b.mort Mort, Ben
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 5.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete515.5
                  Total515.5

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel