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

TMC Resilient Assign Resources implementation

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

Details

    • Enabler
    • Must have
    • PI15
    • None
    • None
    • Obs Mgt & Controls
    • Hide

      Having knowledge about failures in completing tasks and subtasks will greatly increase the ability to diagnose and understand root causes of failures triggered by compute infrastructure.

      Show
      Having knowledge about failures in completing tasks and subtasks will greatly increase the ability to diagnose and understand root causes of failures triggered by compute infrastructure.
    • Hide

      A new release in skampi with refactored functionality causing end-to-end tests to pass consistently (eg. > 100 times back to back) or in case of failures indicate clearly what the cause was. 

      Evidence of unhappy path tests in tmc repo must also be given

      Show
      A new release in skampi with refactored functionality causing end-to-end tests to pass consistently (eg. > 100 times back to back) or in case of failures indicate clearly what the cause was.  Evidence of unhappy path tests in tmc repo must also be given
    • 2
    • 0
    • 16.1

    • PI22 - UNCOVERED

    Description

      Refactor current Subarray Assign/Release resources functionality so that it allows for the TMC to handle "compute infrastructure-related" failures on SDP, CSP, and Dishes whilst performing the act of switching on (e.g. after returning OK but before successfully assigned/released).

      Note the handling of this shall be limited to "passive" measures only: E.g appropriate log messages on the client-side to indicate to an investigator when and why something went wrong in the execution of assign/release on one of the servers. Also,  the scope of these messages/notifications will be limited to leaf nodes monitoring their counterpart devices (e.g. CSP Subarray Leaf node monitoring CSP Subarray counterpart)

      Verification shall be done by means of tests on the TMC repo side in which server-side failures can be injected using mocks.

      Also, see below for technical discussion:

      https://docs.google.com/document/d/15LAXGcrQVfUEQp3-1nPpcUaNNxhH8oszA2u8z1nlS3w/edit#

      Attachments

        Structure

          Activity

            People

              Adam.Avison Avison, Adam
              g.leroux Le Roux, Gerhard [X] (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Feature Progress

                Story Point Burn-up: (0%)

                Feature Estimate: 2.0

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

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Structure Helper Panel