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

Publishing SKA/PSS FPGA module library via the CI/CD pipeline

Details

    • Feature
    • Must have
    • PI13
    • COM PSS SW
    • None
    • Data Processing, Services
    • Hide

      Enable and support the execution of FPGA-based modules on the PSS (and more generally the SKA) CI/CD environment. 

      Show
      Enable and support the execution of FPGA-based modules on the PSS (and more generally the SKA) CI/CD environment. 
    • Hide

      Given an existing integration branch in Rabbit
      And the branch has passed all QA and testing in integration
      And the .rpm package has been created with relevant metadata
      And the .rpm package has passed all packaging QA
      When the integration branch is merged into master with a Merge Request
      Then the versioned .rpm package(s) are submitted to the PSS yum repository at the Central Artefact Repository
      And size of each package is not limited to 100MB
      And the branch is tagged with the relevant version number

      Show
      Given an existing integration branch in Rabbit And the branch has passed all QA and testing in integration And the .rpm package has been created with relevant metadata And the .rpm package has passed all packaging QA When the integration branch is merged into master with a Merge Request Then the versioned .rpm package(s) are submitted to the PSS yum repository at the Central Artefact Repository And size of each package is not limited to 100MB And the branch is tagged with the relevant version number
    • Inter Program
    • 1
    • 1
    • 8
    • 8
    • Team_PSS, Team_SYSTEM
    • Sprint 5
    • Hide

      MR for AT4-620: 
      https://gitlab.com/ska-telescope/pss/ska-pss-rabbit/-/merge_requests/9

      MR for AT4-621: 

      https://gitlab.com/ska-telescope/pss/ska-pss-rabbit/-/merge_requests/8

      Because of the long (40 hour) build time, these will only merge later this week, but all the work is finished and captured in the links above. 

      Show
      MR for AT4-620:  https://gitlab.com/ska-telescope/pss/ska-pss-rabbit/-/merge_requests/9 MR for AT4-621:  https://gitlab.com/ska-telescope/pss/ska-pss-rabbit/-/merge_requests/8 Because of the long (40 hour) build time, these will only merge later this week, but all the work is finished and captured in the links above. 
    • 14.1
    • Stories Completed, Outcomes Reviewed, Satisfies Acceptance Criteria, Accepted by FO
    • PI22 - UNCOVERED

    • SPO-1582

    Description

      During work done in SP-1881, the FPGA-based PSS modules within the Rabbit library was successfully built on the Kelvin reference server, but the CI pipeline could not store the artifacts from the build stage to the gitlab artifact repository because of the latters size limitations.
      Currently the full build is disabled and only the much smaller emulator components are currently being built.  This gitlab size limitation needs to be resolved by the Systems team before we can activate the CI pipeline for production 

      To give an examples of the problem. The FPGA device binary image of each module is greater than 150MB which exceeds the defined limit of 100MB Gitlab artifacts. There are currently 3 modules and more are expected to be added over time)

       The pipeline is currently set up to create rpm packages. We need to add an additional stage to publish these packages to a central yum repository dedicated to pss. Systems support is required to set up this repository, and provide the tooling required to QA, sign, and publish these packages to this repository.

       The publishing solution should have the following properties:

      • The publication should be associated with a specific branch. In the first instance this will be master and will be our "production" version. In the future we may, for example, wish to add a "beta" branch to facilitate acceptance testing by the BO before we allow it to go into production.
      • The packaging QA should be performed and passed before the merge into the branch is allowed
      • The version number should be changed as part of the MR
      • The merge shall trigger the publication of the rpm such that at any time the contents of the branch shall have a corresponding package in the yum repository.

      Attachments

        Issue Links

          Structure

            Activity

              People

                j.santander-vela Santander-Vela, Juande
                L.Levin-Preston Levin-Preston, Lina
                Votes:
                0 Vote for this issue
                Watchers:
                4 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
                  Complete411.0
                  Total411.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel