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

Power control initial implementation

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

      Implementation advanced enough to be able to demonstrate power requests by a lower-level device (e.g. a Subrack, Tile, &c) being responded to. This will include:

      • Mechanism for lower-level devices to request power
      • Policy mechanism to respond to requests
      • Trivial implementation of policy (e.g. immediately grant power on request)
      • Experimental Pdu device (for deployment at a chosen test site) PDU already deploying but we will continue to work, especially on the new Raritan
      • Any new device required for power control
        • CabinetBank has been expunged. We will likely need some high-level power control device
      • Ability to deploy the new mechanism and any new devices
      Show
      Implementation advanced enough to be able to demonstrate power requests by a lower-level device (e.g. a Subrack, Tile, &c) being responded to. This will include: Mechanism for lower-level devices to request power Policy mechanism to respond to requests Trivial implementation of policy (e.g. immediately grant power on request) Experimental Pdu device (for deployment at a chosen test site) PDU already deploying but we will continue to work, especially on the new Raritan Any new device required for power control CabinetBank has been expunged. We will likely need some high-level power control device Ability to deploy the new mechanism and any new devices
    • Inter Program
    • 3
    • 3
    • 0

    • PI24 - UNCOVERED

    • LOW-G3 Team_MCCS mccs_software
    • Low G1 Low G3

    Description

      In SP-4342 we chose to re-evaluate the architecture for MCCS power control, rather than proceeding with power orchestration by the CabinetBank device. The new approach will generalize our existing architecture of having low-level devices request power from an up-stream power provider. In PI24 we deployed a PDU device experimentally. Under this feature we will:

      • Continue exercising deployed PDU device(s)
      • Implement the power control mechanism
        • Abstract machinery to implement the high-level logic
        • Use this within the "client" devices such that they cooperate with power sequencing
        • Link to top level MCCS power state control
        • Make use of this mechanism (or parts of it) for at least 1 of Subrack, Tile or Fndh devices

      The deployment changes should be made such that the new control mechanism is optional, allowing a default "always on" behaviour so as not to obstruct operations.

      Attachments

        Issue Links

          Child Of

          Capability - SAFe program capability SS-167 Initial integration additional monitoring interfaces added for Low AA1

          • Medium - Has the potential to affect progress.
          • Analyzing

          Capability - SAFe program capability SS-156 Low AA0.5/AA1 Control & Monitoring improvements

          • Medium - Has the potential to affect progress.
          • Implementing
          depends on

          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
          mentioned in

          Page Loading...

          Structure

            Activity

              People

                Thomas.Franzen Franzen, Thomas
                Thomas.Franzen Franzen, Thomas
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete00.0
                  Total00.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel