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

Dish LMC forwards the logs of TANGO devices to the SKA Logging Service

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

Details

    • Obs Mgt & Controls
    • Hide

      Observability of SPF and SPFRx during integration and operation.

      Show
      Observability of SPF and SPFRx during integration and operation.
    • Hide

      A protocol, for Dish LMC to ingest logs from SPF or& SPFRx devices is:

      • agreed between OMC architects, Cipa and Karoo,
      • documented in the Solution Intent.

      Test results show that:

      • Dish LMC's logger device received logs from a TANGO device that is deployed inside the k8s cluster,
      • Dish LMC's logger receved logs from a TANGO device that is deployed outside the k8s cluster,
      • the SKA Logging service received those logs from Dish LMC's logger device.
      Show
      A protocol, for Dish LMC to ingest logs from SPF or & SPFRx devices is: agreed between OMC architects, Cipa and Karoo, documented in the Solution Intent. Test results show that: Dish LMC's logger device received logs from a TANGO device that is deployed inside the k8s cluster, Dish LMC's logger receved logs from a TANGO device that is deployed  outside  the k8s cluster, the SKA Logging service received those logs from Dish LMC's logger device.
    • 2
    • 2
    • 0
    • Team_KAROO
    • Sprint 4
    • Hide

      A protocol, for Dish LMC to ingest logs from SPF or& SPFRx devices is: agreed between OMC architects, Cipa and Karoo  &  documented in the Solution Intent:

      Test results show that:

      • Dish LMC's logger device received logs from a TANGO device that is deployed inside the k8s cluster,
        • Logs of SPF and SPFRx simulators are triggered by sending a TANGO command to them - see comment on KAR-548
      • Dish LMC's logger received logs from a TANGO device that is deployed outside the k8s cluster,
        • This could not be achieved using a TANGO device that lies outside of k8s cluster because we relied on showing how Dish LMC forwards logs of PSI MID SPFRx to the logging system because integration between SPFRx and Dish LMC could not be achieved in time, and because the MID PSI is not set up to forward logs to STFC Logging System.
        • DishLogger receives logs from a device that has DishLogger as only target target - see comments on KAR-549
      • the SKA Logging service received those logs from Dish LMC's logger device.

      Added commands (SetDishLoggerTarget and RemoveDishLoggerTarget) to DishLogger to add and remove logging target  - https://developer.skao.int/projects/ska-dish-lmc/en/latest/package/DishLogger.html 

      Show
      A protocol, for Dish LMC to ingest logs from SPF  or & SPFRx devices is: agreed between OMC architects, Cipa and Karoo  &  documented in the Solution Intent: The way logs are ingested by Dish LMC from SPFRx is described in Solution Intent: https://confluence.skatelescope.org/display/SWSI/MID+Dish+LMC+logging  (see  Proposed Changes  section) https://confluence.skatelescope.org/display/SWSI/Dish+ID+Dish+LMC+design  (See  Logging  section) Test results show that: Dish LMC's logger device received logs from a TANGO device that is deployed inside the k8s cluster, Logs of SPF and SPFRx simulators are triggered by sending a TANGO command to them - see comment on KAR-548 Dish LMC's logger received logs from a TANGO device that is deployed outside  the k8s cluster, This could not be achieved using a TANGO device that lies outside of k8s cluster because we relied on showing how Dish LMC forwards logs of PSI MID SPFRx to the logging system because integration between SPFRx and Dish LMC could not be achieved in time, and because the MID PSI is not set up to forward logs to STFC Logging System. DishLogger receives logs from a device that has DishLogger as only target target - see comments on KAR-549 the SKA Logging service received those logs from Dish LMC's logger device. See demo in https://confluence.skatelescope.org/display/SE/2023-05-11+Dish+LMC+Weekly+Meeting+notes Added commands (SetDishLoggerTarget and RemoveDishLoggerTarget) to DishLogger to add and remove logging target  - https://developer.skao.int/projects/ska-dish-lmc/en/latest/package/DishLogger.html  
    • 18.6
    • Stories Completed, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO
    • PI22 - NOTRUN

    • Team_KAROO

    Description

      SPF and SPFRx TANGO devices are deployed outside of the k8s cluster. Dish LMC is required to ensure that their logs end up in the SKA Logging System. Dish LMC is also required to locally store the logs of Dish in a 12 hour rolling buffer.

      Agree protocol (for example TANGO Logging Service) for Dish LMC to ingest logs from SPF and SPFRx devices (these are not deployed in k8s cluster).

      Test Dish LMC's logger reception of TLS logs from a TANGO device that is inside k8s and sending of those logs to SKA Logging service.

      Test Dish LMC's logger reception of TLS logs from a TANGO device that is outside k8s and sending of those logs to SKA Logging service.

      Attachments

        Issue Links

          Structure

            Activity

              People

                Adam.Avison Avison, Adam
                p.swart Swart, Paul [X] (Inactive)
                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
                  Complete47.0
                  Total47.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel