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

Cabinet Banks - Investigate SPS monitoring and control for AA0.5

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

Details

    • LOW ART
    • Hide

      High-level Cabinet Bank device needed in AA1 to

      • orchestrate power sequencing for banks of 3 cabinets (i.e. 6-station cluster) on the 3 mains phases
      • monitor and control COTS equipment in the cabinets (PDUs, network switches etc.)
      Show
      High-level Cabinet Bank device needed in AA1 to orchestrate power sequencing for banks of 3 cabinets (i.e. 6-station cluster) on the 3 mains phases monitor and control COTS equipment in the cabinets (PDUs, network switches etc.)
    • Hide

      Write a Confluence document outlining the required functionality of the MCCS Cabinet Bank device. Create a stub Cabinet Bank device and "demo" it at a suitable session.

      Show
      Write a Confluence document outlining the required functionality of the MCCS Cabinet Bank device. Create a stub Cabinet Bank device and "demo" it at a suitable session.
    • Inter Program
    • 1
    • 1
    • 0
    • Team_MCCS
    • Sprint 5
    • Hide

      The necessary capabilities of CabinetBank were investigated. Existing devices were identified which could be developed further, if necessary, to manage White Rabbit end points and PDU hardware. A stub CabinetBank device was created. This took a role between Controller and Station devices in powering-on stations.

      We concluded that a more sophisticated architecture (more of a choreographer than a conductor) was a better fit. This is being pursued under SP-4342. The demonstration ticket has been moved there.

      Show
      The necessary capabilities of CabinetBank were investigated. Existing devices were identified which could be developed further, if necessary, to manage White Rabbit end points and PDU hardware. A stub CabinetBank device was created. This took a role between Controller and Station devices in powering-on stations. We concluded that a more sophisticated architecture (more of a choreographer than a conductor) was a better fit. This is being pursued under SP-4342 . The demonstration ticket has been moved there.
    • 23.4
    • Stories Completed, Outcomes Reviewed, Satisfies Acceptance Criteria, Accepted by FO
    • LOW-G5 Team_MCCS Team_WOMBAT mccs_software

    Description

      A spike to investigate the work required to monitor and control SPS for AA0.5, including ways for Wombat to contribute.

      Each SPS cabinet is powered by one of the three mains phases. To be able to sequence power control across mains phases MCCS requires a new device with a corresponding multiplicity (1 per 3 cabinets, i.e. 6 Stations). At RPFs this corresponds to 1 device per 6-Station Cluster. The name for this is TBD; possibly CabinetBank, SPSCabinetGroup or SPSCabinetUnit. It is also TBD whether this device should be at top level or in the spshw repo. Noting also that the CMB will not be used for at least AA0.5 and AA1, and that therefore COTS equipment will be filling its role, MCCS responsibilities for CMB monitoring/control may transfer to monitoring/control of these new devices. Exactly where the boundaries of responsibility fall for this new realization is TBD. Where this requires work with lower level devices there might be a role for the Wombat team. Please see here for updates to PI planning.

      In addition, some review of the Architecture may be needed, and should be investigated and fixes/updates planned to address the following concerns:

      • PaSD control/monitor issues identified by Wombat.
      • Explore how to resolve issues on internal state definition not always being detailed enough - unknown state in particular.
      • Consider integration of existing White Rabbit functionality (the precise SAT.LMC / MCCS boundary is TBD, but a WR switch device already exists)

      Attachments

        Issue Links

          followed 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-4342 Cabinet Banks - Implement power sequencing and investigate COTS control

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

          Structure

            Activity

              People

                Thomas.Franzen Franzen, Thomas
                Thomas.Franzen Franzen, Thomas
                Votes:
                0 Vote for this issue
                Watchers:
                2 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
                  Complete37.0
                  Total37.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel