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

MID TMC provides API for the DISH to VCC Mapping Table and correctly handles initalisation and updates

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

Details

    • Obs Mgt & Controls
    • Hide

      TMC provides interface to allow Operations to command Mid.CBF to load a particular version of the DISH to VCC Mapping Table, and to obtain the currently used version (TMC can obtain that from Mid.CBF via CSP.LMC).
      Without DISH to VCC Mapping Table the MID telescope cannot be functional.

      Show
      TMC provides interface to allow Operations to command Mid.CBF to load a particular version of the DISH to VCC Mapping Table, and to obtain the currently used version (TMC can obtain that from Mid.CBF via CSP.LMC). Without DISH to VCC Mapping Table the MID telescope cannot be functional.
    • Hide

      TMC provides DISH ID to VCC Mapping Table for the Telescope and for each facility (including CI/CD pipelines).
      The content of the mapping table may be different for different deployments (and facilities).

      • The proposal for the format and content of the DISH to VCC Mapping Table, defined by CIPA team, reviewed and agreed.
      • The content of the DISH to VCC Mapping Table may be different for different deployments (and facilities).
      • The location of the DISH to VCC Mapping Table agreed. Mid.CBF team takes lead on design and implementation, TMC team reviews and provides comments.
      • The location / naming for deployment in different locations (Telescope, ITF, PSI, CICD pipeline) agreed.
      • TMC user documentation clearly describes how the DISH to VCC Mapping Table can be accessed and updated.
      • TMC is integrated with CSP.LMC.
      • TMC provides API that enables Operations to obtain the version of the DISH to VCC Mapping Table currently used by the Telescope (TMC and MID.CBF).
      • TMC provides API that enables Operations to instruct the Telescope to load specific version of the DISH to VCC Mapping Table.
      • The version of the DISH to VCC Mapping Table is specified as a part of the TMC configuration and loaded during TMC initialization.
      • When TMC completes initialization (after deployment and restart) the TMC verifies that MID CBF uses the same version of the DISH to VCC Mapping Table. If not TMC raises a warning and instructs Mid.CBF to load the correct table. The telescope is not ready to be used until the DISH ID is correctly configured in the dishes and in CSP.
      • TMC takes in consideration the DISH to VCC Mapping Table status when reporting the status of the Telescope, Subarrays and resources.
      • TMC raises warning and alarms as appropriate to bring issues to the Operator attention.

      The demo is provided to show:
      a) How a new version of the DISH to VCC Mapping Table can be created (for a new facility).
      b) How the table for an existing facility can be updated. Execute test for the initial version, update the mapping table and execute test again to show the steps to modify the mapping table. Is the version automatically updated for every change/modification?
      c) How Operations define which version of the table will be loaded during TMC initialization. Does TMC, when it completes initialization verify that Mid.CBf uses the correct version of the DISH to VCC Mapping Table. What is Mid.CBF uses a different version from the one defined in the TMC default configuration?
      d) How Operations instruct the Telescope to load a different version of the DISH to VCC Mapping Table.
      e) How Operations check which version of the table is used, and how the content of the table can be viewed.

      Show
      TMC provides DISH ID to VCC Mapping Table for the Telescope and for each facility (including CI/CD pipelines). The content of the mapping table may be different for different deployments (and facilities). The proposal for the format and content of the DISH to VCC Mapping Table, defined by CIPA team, reviewed and agreed. The content of the DISH to VCC Mapping Table may be different for different deployments (and facilities). The location of the DISH to VCC Mapping Table agreed. Mid.CBF team takes lead on design and implementation, TMC team reviews and provides comments. The location / naming for deployment in different locations (Telescope, ITF, PSI, CICD pipeline) agreed. TMC user documentation clearly describes how the DISH to VCC Mapping Table can be accessed and updated. TMC is integrated with CSP.LMC. TMC provides API that enables Operations to obtain the version of the DISH to VCC Mapping Table currently used by the Telescope (TMC and MID.CBF). TMC provides API that enables Operations to instruct the Telescope to load specific version of the DISH to VCC Mapping Table. The version of the DISH to VCC Mapping Table is specified as a part of the TMC configuration and loaded during TMC initialization. When TMC completes initialization (after deployment and restart) the TMC verifies that MID CBF uses the same version of the DISH to VCC Mapping Table. If not TMC raises a warning and instructs Mid.CBF to load the correct table. The telescope is not ready to be used until the DISH ID is correctly configured in the dishes and in CSP. TMC takes in consideration the DISH to VCC Mapping Table status when reporting the status of the Telescope, Subarrays and resources. TMC raises warning and alarms as appropriate to bring issues to the Operator attention. The demo is provided to show: a) How a new version of the DISH to VCC Mapping Table can be created (for a new facility). b) How the table for an existing facility can be updated. Execute test for the initial version, update the mapping table and execute test again to show the steps to modify the mapping table. Is the version automatically updated for every change/modification? c) How Operations define which version of the table will be loaded during TMC initialization. Does TMC, when it completes initialization verify that Mid.CBf uses the correct version of the DISH to VCC Mapping Table. What is Mid.CBF uses a different version from the one defined in the TMC default configuration? d) How Operations instruct the Telescope to load a different version of the DISH to VCC Mapping Table. e) How Operations check which version of the table is used, and how the content of the table can be viewed.
    • 2
    • 2
    • 10
    • 5

    • Sub-system Version REL-684 TMC 0.15.0: Mid version available for Mid ITF integration, with details on mapping between VCC to DISH ID

    • Team_HIMALAYA
    • Sprint 2
    • Hide
      • The proposal for the format and content of the DISH to VCC Mapping Table, defined by CIPA team, has been reviewed and agreed.
        Done.
      • The content of the DISH to VCC Mapping Table may be different for different deployments (and facilities).
        It can, but it is not loaded during initalisation.
        The mechanism for loading the table during initalisation not provided.
      • The location of the DISH to VCC Mapping Table agreed. Mid.CBF team takes lead on design and implementation, TMC team reviews and provides comments.
        For testing TMC is using table stored on GitLab.
        Reason: CIPA team did not provide the Telescope Model interface by the end of Sprint 4.
      • The location / naming for deployment in different locations (Telescope, ITF, PSI, CICD pipeline) agreed.
        Outstanding.
      • TMC user documentation clearly describes how the DISH to VCC Mapping Table can be accessed and updated.
        https://confluence.skatelescope.org/display/UD/Load+Dish+Configuration+in+TMC.
      • TMC is integrated with CSP.LMC.
        Outstanding. CSP.LMC does not support this functionality.
      • TMC provides API that enables Operations to obtain the version of the DISH to VCC Mapping Table currently used by the Telescope (TMC and MID.CBF).
        attribute:
        sourceSysParam = URI + filePath
        sysParam - content of the file identified by URI (JSON String).
        Both are read-only attributes
      • TMC provides API to enable Operations to instruct the Telescope to load specific version of the DISH to VCC Mapping Table.
        CN command loadDishCfg(). It takes as parameter sourceSysParam.
      • The version of the DISH to VCC Mapping Table is specified as a part of the TMC configuration and loaded during TMC initialization.
        Outstanding - Telescope Model access to be implemented by CIPA Team.
      • When TMC completes initialization (after deployment and restart) the TMC verifies that MID CBF uses the same version of the DISH to VCC Mapping Table. If not, TMC raises a warning -and instructs Mid.CBF to load the correct table.
        Outstanding.
      • The telescope is not ready to be used until the DISH ID is correctly configured in the dishes and in CSP.
        Outstanding
      • TMC takes in consideration the DISH to VCC Mapping Table status when reporting the status of the Telescope, Subarrays and resources.
        Outstanding
      • TMC raises warning and alarms as appropriate to bring issues to the Operator attention.
        Outstanding. Need to agree on details.

      The demo is provided to show:
      a) How a new version of the DISH to VCC Mapping Table can be created (for a new facility).
      Cipa Team will show this.
      b) How the table for an existing facility can be updated. Execute test for the initial version, update the mapping table and execute test again to show the steps to modify the mapping table. Is the version automatically updated for every change/modification?
      Not possible in this PI.
      c) How Operations define which version of the table will be loaded during TMC initialization. Does TMC, when it completes initialization verify that Mid.CBf uses the correct version of the DISH to VCC Mapping Table. What if Mid.CBF uses a different version from the one defined in the TMC default configuration?
      Demo not possible in this PI
      d) How Operations instruct the Telescope to load a different version of the DISH to VCC Mapping Table.
      The command could be demoed to FO during IP Sprint
      e) How Operations check which version of the table is used, and how the content of the table can be viewed.
      Could be demoed during IP Sprint.

      Show
      The proposal for the format and content of the DISH to VCC Mapping Table, defined by CIPA team, has been reviewed and agreed. Done . The content of the DISH to VCC Mapping Table may be different for different deployments (and facilities). It can, but it is not loaded during initalisation. The mechanism for loading the table during initalisation not provided. The location of the DISH to VCC Mapping Table agreed. Mid.CBF team takes lead on design and implementation, TMC team reviews and provides comments. For testing TMC is using table stored on GitLab. Reason: CIPA team did not provide the Telescope Model interface by the end of Sprint 4. The location / naming for deployment in different locations (Telescope, ITF, PSI, CICD pipeline) agreed. Outstanding . TMC user documentation clearly describes how the DISH to VCC Mapping Table can be accessed and updated. https://confluence.skatelescope.org/display/UD/Load+Dish+Configuration+in+TMC . TMC is integrated with CSP.LMC. Outstanding. CSP.LMC does not support this functionality. TMC provides API that enables Operations to obtain the version of the DISH to VCC Mapping Table currently used by the Telescope (TMC and MID.CBF). attribute: sourceSysParam = URI + filePath sysParam - content of the file identified by URI (JSON String). Both are read-only attributes TMC provides API to enable Operations to instruct the Telescope to load specific version of the DISH to VCC Mapping Table. CN command loadDishCfg(). It takes as parameter sourceSysParam. The version of the DISH to VCC Mapping Table is specified as a part of the TMC configuration and loaded during TMC initialization. Outstanding - Telescope Model access to be implemented by CIPA Team. When TMC completes initialization (after deployment and restart) the TMC verifies that MID CBF uses the same version of the DISH to VCC Mapping Table. If not, TMC raises a warning -and instructs Mid.CBF to load the correct table. Outstanding . The telescope is not ready to be used until the DISH ID is correctly configured in the dishes and in CSP. Outstanding TMC takes in consideration the DISH to VCC Mapping Table status when reporting the status of the Telescope, Subarrays and resources. Outstanding TMC raises warning and alarms as appropriate to bring issues to the Operator attention. Outstanding. Need to agree on details . The demo is provided to show: a) How a new version of the DISH to VCC Mapping Table can be created (for a new facility). Cipa Team will show this. b) How the table for an existing facility can be updated. Execute test for the initial version, update the mapping table and execute test again to show the steps to modify the mapping table. Is the version automatically updated for every change/modification? Not possible in this PI. c) How Operations define which version of the table will be loaded during TMC initialization. Does TMC, when it completes initialization verify that Mid.CBf uses the correct version of the DISH to VCC Mapping Table. What if Mid.CBF uses a different version from the one defined in the TMC default configuration? Demo not possible in this PI d) How Operations instruct the Telescope to load a different version of the DISH to VCC Mapping Table. The command could be demoed to FO during IP Sprint e) How Operations check which version of the table is used, and how the content of the table can be viewed. Could be demoed during IP Sprint.
    • 20.6
    • Stories Completed, Solution Intent Updated, Outcomes Reviewed, Demonstrated, Accepted by FO

    Description

      DISH ID is inserted into data flowing from the DISH to MID.CBF. Each Mid.CBF VCC (Very Coarse Channelizer) handles digitized and packetized data from one dish, and is able to retrieve DISH ID from the received packets. In addition, to ensure that the connections are as expected, MID.CBF receives (or obtains) DISH to VCC Mapping Table via Monitor and Control path. When deployed, during initialization Mid.CBF loads the DISH to VCC Mapping Table via Telescope Model.
      TMC provides interface to allow Operations to command Mid.CBF to load a particular version of the DISH to VCC Mapping Table, and to obtain the currently used version (TMC can obtain that from Mid.CBF via CSP.LMC).
      Without DISH to VCC Mapping Table the MID telescope cannot be functional.

      The design work to determine the format of the DISH to VCC Mappint Table, the location where the table is stored, the file names and the development work required to enable that the table can be accessed via the Telescope Model is responsibility ot the MID.CBF team. See https://jira.skatelescope.org/browse/SP-3611.

      TMC only provides API to enable Operations to specify which version should be used, and to instuct the Telescope to load a different version when needed. TMC also ensures that CSP uses the correct version (as specified by Operations).

      It has been agreed that TMC, in the same manner as Mid.CBF, will load the "DISH to VCC Mapping Table" during initialization, from a file via Telescope Model.
      In addition, Mid.CBF should be able to receive an instruction (command) to load a particular version of the "DISH to VCC Mapping Table" (it could be the same of different version), and may allow user to specify DISH ID for an individual VCC (via an engineering interface).

      Context:
      The purpose of "DISH to VCC Mapping Table" is to tell Mid.CBF which dish is connected to which VCC (Very Coarse Channelizer). Mid.CBF will compare the DISH ID received from the dish with this table and raise ALARM if the actual setup is not as expected. This table will eventually have 197 entries and should be stored under version control, so that we keep historical data, and can, for each observation (SB/scan, establish what was the telescope setup.

      Requirements:

      • The "DISH to VCC Mapping Table" shall be under version control to allow operations to tell TMC and Mid.CBF which version to use.
      • Operations/users shall be able to define different version of the table for different deployments (telescope, ITF, PSI, CI/CD pipelines).
      • Operations shall be able to specify the version to be used for each deployment. The table shall be loaded during the telescope (TMC) initialization.
      • TMC shall provide interface so that the Operations can instruct the Telescope (TMC and Mid.CBF) to load a different version of the "DISH to VCC mapping table" without a need to re-deploy software.
      • It has been agreed that the Telescope Model is the best place to place this table. More precisely, the file containg the table will be stored on CAR, and the access will be via the Telescope Model.

      Similar requirements apply for the dish coordinates. It is to expect that the "DISH to VCC mapping table" will change more often than the dish coordinates, in particular in ITF and PSI, but we should be able to update the dish coordinates without redeploying software.

      Attachments

        Issue Links

          clones

          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-2909 TMC implements the correct DISH ID format (ADR-32)

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done
          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-3611 Dish ID-VCC Map

          • 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-3852 TMC handles initialization scenarios of setting and verifying Dish ID - VCC map

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

          Sub-system Version - A version of a sub-system, used in the Release Management and Configuration Management process REL-684 TMC 0.15.0: Mid version available for Mid ITF integration, with details on mapping between VCC to DISH ID

          • 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-3034 DISH.LMC implements the correct DISH ID format (ADR-32)

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

          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-1795 Mid.CBF and SPFRx Implement ADR-32 DISH ID

          • 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

          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-3233 CSP.LMC implements the correct DISH ID format (ADR-32)

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • 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-3777 MID CSP.LMC provides API for the DISH to VCC Mapping Table and correctly handles initalisation and updates

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

          Architectural Decision - Software Architectural Decision ADR-32 SKA MID Telescope: DISH ID

          • decided
          mentioned in

          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: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete513.0
                  Total513.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel