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

TMC Mid Central Node upgrade to Base Classes v0.13

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

Details

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

      Update the TMC Mid Central Node to Base Classes v0.13.

      Rationale: By the end of the PI14 TMC CN and TMC Leaf Nodes for DISH, CSP and SDP will be upgraded to BC v0.11 (which requires re-structuring to introduce the, so called, Component Manager)and  re-integrated in SKAMPI. Operational state machine is implemented (commands STANDBY/ON/OFF) and a part of the Observing state machine, namely commands AssignResources and ReleaseResources.  Implementation of the commands Configure, Scan, EndScan, Abort, ObsReset, Restart is outstanding. A custom monitoring loop (polling) is used to monitor state and state transitions of the subordinate components (a workaround introduced due to a TANGO issue which has been fixed in the mean time).

      Base Classes v0.13 introduce asynchronous communications, which in turn assumes reliance on events instead of polling.  Upgrade to BC v0.13  should include reliance on events instead of custom monitoring loops.

      Instead of implementing the full observing state machine based on BC v0.11.3, it is more economical to upgrade now to BC v0.13, and in the following PI implement the full Observing state machine.

      Rationale:

      • By the end of PI15 the DISH  Master based on BC v0.13 will become available in SKAMPI,  which means that TMC will be able to integrate with DISH.LMC.
      • TMC team gained lot of experience with upgrades to v0.11 and is confident  that  upgrade to v0.13 can be performed successfully. 

       

      Show
      Update the TMC Mid Central Node to Base Classes v0.13. Rationale: By the end of the PI14 TMC CN and TMC Leaf Nodes for DISH, CSP and SDP will be upgraded to BC v0.11 (which requires re-structuring to introduce the, so called, Component Manager)and  re-integrated in SKAMPI. Operational state machine is implemented (commands STANDBY/ON/OFF) and a part of the Observing state machine, namely commands AssignResources and ReleaseResources.  Implementation of the commands Configure, Scan, EndScan, Abort, ObsReset, Restart is outstanding. A custom monitoring loop (polling) is used to monitor state and state transitions of the subordinate components (a workaround introduced due to a TANGO issue which has been fixed in the mean time). Base Classes v0.13 introduce asynchronous communications, which in turn assumes reliance on events instead of polling.  Upgrade to BC v0.13  should include reliance on events instead of custom monitoring loops. Instead of implementing the full observing state machine based on BC v0.11.3, it is more economical to upgrade now to BC v0.13, and in the following PI implement the full Observing state machine. Rationale: By the end of PI15 the DISH  Master based on BC v0.13 will become available in SKAMPI,  which means that TMC will be able to integrate with DISH.LMC. TMC team gained lot of experience with upgrades to v0.11 and is confident  that  upgrade to v0.13 can be performed successfully.   
    • Hide

      TMC CN commands related to the Operational state machine (ON/STANDBY/OFF) aligned with BC v0.13 and implemented as long running commands.

      TMC CN commands assign/release resources aligned with BC v0.13 and implemented as long running comands.

      Custom monitoring loop replaced with event based approach.

      TMC integrated, CN is able to forward commands to the Leaf Nodes which have not been upgraded to BC V0.13. (there is no plan to upgrade CSP and SDP Leaf Nodes in PI15).

      TMC integrated in SKAMPI.

       

      Show
      TMC CN commands related to the Operational state machine (ON/STANDBY/OFF) aligned with BC v0.13 and implemented as long running commands. TMC CN commands assign/release resources aligned with BC v0.13 and implemented as long running comands. Custom monitoring loop replaced with event based approach. TMC integrated, CN is able to forward commands to the Leaf Nodes which have not been upgraded to BC V0.13. (there is no plan to upgrade CSP and SDP Leaf Nodes in PI15). TMC integrated in SKAMPI.  
    • Intra Program
    • 8
    • 8
    • 0

    • Sub-system Version REL-228 TMC Mid v0.5.14

      System Version REL-92 SKA-MID-MVP v0.1.0-experiment

    • Team_SAHYADRI
    • Sprint 5
    • Hide

      TMC Central Node commands related to the Operational state machine (ON/STANDBY/OFF) aligned with BC v0.13 and are implemented as long running commands.
      TMC Central Node commands assign/release resources aligned with BC v0.13 are implemented as long running commands.
      The commands are tested along with the integration of TMC Dish leaf Node (BC v0.13).
      TMC Mid integrated, CN is able to forward commands to the Leaf Nodes (CSP and SDP Leaf Nodes) which have not been upgraded to BC V0.13.
      Merged MR in ska-tmc-integration repo. https://gitlab.com/ska-telescope/ska-tmc/ska-tmc-integration/-/merge_requests/19
      Merged MR on skampi repo, to integrate ska-tmc-mid chart v0.5.14
      link: https://gitlab.com/ska-telescope/ska-skampi/-/merge_requests/670
      The work is demonstrated in System Demo 15.5 and PI 15 demo

      Show
      TMC Central Node commands related to the Operational state machine (ON/STANDBY/OFF) aligned with BC v0.13 and are implemented as long running commands. TMC Central Node commands assign/release resources aligned with BC v0.13 are implemented as long running commands. The commands are tested along with the integration of TMC Dish leaf Node (BC v0.13). TMC Mid integrated, CN is able to forward commands to the Leaf Nodes (CSP and SDP Leaf Nodes) which have not been upgraded to BC V0.13. Merged MR in ska-tmc-integration repo. https://gitlab.com/ska-telescope/ska-tmc/ska-tmc-integration/-/merge_requests/19 Merged MR on skampi repo, to integrate ska-tmc-mid chart v0.5.14 link: https://gitlab.com/ska-telescope/ska-skampi/-/merge_requests/670 The work is demonstrated in System Demo 15.5 and PI 15 demo
    • 15.6
    • Stories Completed, Integrated, Solution Intent Updated, BDD Testing Passes (no errors), Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    Description

      Upgrade TMC Central Node to Base Classes v0.13.

      The upgraded TMC CN node supports the same the same set of commands as the version based on BC v0.11.3  and the comands are implemented as long running comands.

      The API is modified as per BC v0.13 and introduces a breaking change. In order to be integrated with OET, the OET (client) has to be upgraded (which is the plan).

      TMC CN communicates with: DISH, CSP and SDP Leaf Nodes and with TMC Subarray; only DISH Leaf Node will be upgraded to BC v0.13, which means that, by the end of PI15,  CN will be integrated with one TM component upgraded to BC v0.13  and a number of components based on BC v0.11.3; this will be an interesting mix and has to be carefully addressed.

       

      Attachments

        Issue Links

          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-2503 TMC Mid Central Node assign/release resources

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

          System Version - System releases - ie MID, LOW SW. Configured releases of SKAMPI REL-92 SKA-MID-MVP v0.1.0-experiment

          • Discarded

          Sub-system Version - A version of a sub-system, used in the Release Management and Configuration Management process REL-228 TMC Mid v0.5.14

          • Released
          relates to

          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-2601 TMC DISH Leaf Node upgrade to Base Classes v0.13

          • 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

          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-2498 TMC Central Node assign and release resources

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Discarded
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                s.vrcic Vrcic, Sonja
                s.vrcic Vrcic, Sonja
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 8.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete925.0
                  Total925.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel