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

Install/run hardware-facing k8s deployment

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

Details

    • Obs Mgt & Controls
    • Hide

      Additional integration of hardware into MCCS, enables setting up full beamformer and monitoring. 
      Essential for supporting PSI, AAVS deployments. 

       

      Show
      Additional integration of hardware into MCCS, enables setting up full beamformer and monitoring.  Essential for supporting PSI, AAVS deployments.   
    • Hide

      The k8s deployments launch MCCS
      MCCS communicates successfully with multiple TPMs

      Show
      The k8s deployments launch MCCS MCCS communicates successfully with multiple TPMs
    • 1
    • 1
    • 40
    • 40
    • Sprint 5
    • Hide

      k8s was installed on the system at Oxford. A chart and a dashboard were made and these were then used to perform a demonstration. In this the Oxford tiles were shown to be initializing and being turned ON remotely.

      An AAVS-sized chart was also made, but this could not be tested due to limitations of local machines.

      Remote deployment to AAVS had been planned but this could not be achieved owing to the problems there caused by a network switch failure.

      This last step is now planned for PI16 and the corresponding tickets have be re-linked to new features.

      Show
      k8s was installed on the system at Oxford. A chart and a dashboard were made and these were then used to perform a demonstration. In this the Oxford tiles were shown to be initializing and being turned ON remotely. An AAVS-sized chart was also made, but this could not be tested due to limitations of local machines. Remote deployment to AAVS had been planned but this could not be achieved owing to the problems there caused by a network switch failure. This last step is now planned for PI16 and the corresponding tickets have be re-linked to new features.
    • 16.2
    • Stories Completed, Integrated, Outcomes Reviewed, Satisfies Acceptance Criteria, Accepted by FO

    • PI24 - UNCOVERED

    • goal_O4 mccs_software

    Description

      Kubernetes deployments need to be made to hardware-facing servers - i.e. sites with TPMs - to exercise MCCS. This shall be demonstrated by, for example, turning on and configuring multiple Tiles. This sites envisaged for deployment are Oxford, followed by AAVS.

      Attachments

        Issue Links

          clones

          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-1718 Fully configure/control multiple TPMs from MCCS

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

          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-2626 Configuration of Stations / TPMs

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done
          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-1722 Plan MCCS Deployable on AAVS at site

          • 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-1564 Implement MCCS control of data capture from TPM

          • 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

          Spike - A time limited investigation to get some knowledge SP-1604 MCCS Pointing Control Initial implementation of

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

          Structure

            Activity

              People

                v.mohile Mohile, Vivek
                v.mohile Mohile, Vivek
                Votes:
                0 Vote for this issue
                Watchers:
                3 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
                  Complete59.0
                  Total59.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel