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

Monitoring and control of PSI-Low hardware using MCCS

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

Details

    • Obs Mgt & Controls
    • Hide

      The most effective way to derisk deployment of MCCS to monitor and control AAVS3 is to achieve successful deployment of MCCS to monitor and control subracks and TPMs in the PSI-Low.

       

      Show
      The most effective way to derisk deployment of MCCS to monitor and control AAVS3 is to achieve successful deployment of MCCS to monitor and control subracks and TPMs in the PSI-Low.  
    • Inter Program
    • 1
    • 1
    • 0
    • Team_MCCS
    • Sprint 5
    • Hide

      Please see SP-3008 (Monitoring and control of PSI-Low hardware using MCCS) for full info.

      Summary of outcomes:

      • New helm chart templates for deploying to hardware
        • Separates facility-specific information
        • Makes it much easier to tailor MCCS deployments to different facilities.
      • ska-low-mccs-spshw deployed to PSI-Low on demand
      • XTP-17871 test plan created
      • Integrated into Gitlab CI pipeline with new optional step
      • Jira Xray integration
        • Reports test results back to Jira
      Show
      Please see SP-3008 (Monitoring and control of PSI-Low hardware using MCCS) for full info. Summary of outcomes: New helm chart templates for deploying to hardware Separates facility-specific information Makes it much easier to tailor MCCS deployments to different facilities. ska-low-mccs-spshw deployed to PSI-Low on demand XTP-17871 test plan created Integrated into Gitlab CI pipeline with new optional step Jira Xray integration Reports test results back to Jira
    • 17.5
    • Stories Completed, Integrated, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO
    • PI24 - UNCOVERED

    • SYSTEM_DEMO_4 Team_MCCS goal_S1 mccs_software
    • SPO-2126

    Description

      Currently MCCS devices cannot reliably monitor and control SPS hardware such as subracks and TPMs. It is essential that MCCS are able to do so on AAVS3. The most effective way to derisk this situation is for MCCS to start routinely deploying and testing against SPS hardware now. The PSI-Low provides a suitable environment for such a derisking activity: a k8s cluster with access to a subrack and two TPMs.

      This feature will put in place a manual CI pipeline step that deploys relevant MCCS devices to the k8s cluster in the PSI-Low, then runs a basic signal-chain test: a TPM will be configured to produce raw / channelised / beamformed data (input from a signal generator), and data acquisition (DAQ) will be configured to acquire data and dump it to file. Test results will be uploaded to Jira Xray.

      Achieving this feature will require:

      • Work on MCCS devices that monitor and control SPS hardware, to add functionality, improve stability, fix bugs and retire technical debt
      • improvements to the MCCS deployment setup (i.e. work on helm charts and templates)
      • Jira and CI pipeline integration

       

      Attachments

        Issue Links

          Structure

            Activity

              People

                Adam.Avison Avison, Adam
                Vani.Naram Naram, Vani
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 1.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete79.0
                  Total79.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel