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

Deploy aavs-system in Kubernetes at JBO / Oxford

    XporterXMLWordPrintable

Details

    • Obs Mgt & Controls
    • Hide

      aavs-system in Kubernetes will make the Hardware tests available to be executed on AAVS3 hardware. 

      Show
      aavs-system in Kubernetes will make the Hardware tests available to be executed on AAVS3 hardware. 
    • Hide

      aavs-system is deployed in Kubernetes at JBO and/or Oxford and hardware tests pass on TPMs. 

      Show
      aavs-system is deployed in Kubernetes at JBO and/or Oxford and hardware tests pass on TPMs. 
    • 2
    • 2
    • 0
    • Team_MCCS
    • Sprint 3
    • Hide

      A new rack setup for Oxford (RAL) has been built up (finalization of a server order is pending RAL IT approval). Containerization of the AAVS system software has been developed and deployed at JBO. This was used to run the subrack tests, verifying that the JBO subrack is synchronizing correctly to its timing signals.

      Show
      A new rack setup for Oxford (RAL) has been built up (finalization of a server order is pending RAL IT approval). Containerization of the AAVS system software has been developed and deployed at JBO. This was used to run the subrack tests, verifying that the JBO subrack is synchronizing correctly to its timing signals.
    • 21.4
    • Stories Completed, Integrated, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI22 - UNCOVERED

    • Team_MCCS mccs_firmware solution-goal-3

    Description

      During PI19 the MCCS team pursued SP-3367 as far as they could. However due to issues outside of our control were not able to access representative hardware as we conclude PI19. They aim to continue to monitor the hardware access situation coupled with the demand for this work to be achieved and re-evaluate the remaining work of this feature as we proceed through PI20 & PI21 in order to fulfil the intent of the aforementioned PI19 feature. Taking this forward the scope of hardware will be broadened to not necessarily be the Oxford facility, but rather any alternative appropriate system

      **Original PI19 SP-3367 feature intent**
      As a firmware developer I want to deploy aavs-system software in Kubernetes and be able to run the Hardware tests. Currently these are run on "bare metal" only. Deploying the tests to Kubernetes in Oxford will then facilitate deployment to the Kubernetes system at AAVS3 to be able to run the tests there.

      Attachments

        Issue Links

          clones

          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-3367 Deploy aavs-system in Kubernetes in Oxford

          • 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

          Structure

            Activity

              People

                v.mohile Mohile, Vivek
                r.chiello Riccardo Chiello
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete523.0
                  Total523.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel