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

Implement SKA logging updates in Python LMC base classes

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

Details

    • Enabler
    • PI7
    • None
    • Obs Mgt & Controls
    • Hide

      Reimplementing the logging support in LMC base classes will allow LMC developers to set up logging in a standardized way and remove the limitations in the current Tango logger

      Show
      Reimplementing the logging support in LMC base classes will allow LMC developers to set up logging in a standardized way and remove the limitations in the current Tango logger
    • Hide
      • Existing 3 log level settings replaced by a single log level (includes commands on SKALogger)
      • Demonstrate log messages from TANGO device are output in the SKA compliant logging format
      • dev_logging method can be deprecated, but not removed (unless all usages have been updated)
      Show
      Existing 3 log level settings replaced by a single log level (includes commands on SKALogger) Demonstrate log messages from TANGO device are output in the SKA compliant logging format dev_logging method can be deprecated, but not removed (unless all usages have been updated)
    • 3
    • 6
    • 4.6

    • PI24 - UNCOVERED

    Description

      Update base classes to follow the newly proposed logging architecture and format.  This does not include changing the projects that use the base classes, but avoid "API breaking" changes.

      Changes will affect all of these devices:  SKABaseDevice, SKALogger, SKAMaster, SKAAlarmHandler, SKATelState, SKACapability, SKAObsDevice, SKATestDevice.

      This work was a stretch option for SS-15, but was not started in PI4.

      Attachments

        Issue Links

          Child Of

          Capability - SAFe program capability SS-25 Implement standardised approach to logging for the OMC and DP MVPs

          • 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

          Capability - SAFe program capability SS-26 Continue implementation of standardised approach to logging for the OMC and DP MVPs

          • 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

          Structure

            Activity

              People

                v.mohile Mohile, Vivek
                p.swart Swart, Paul [X] (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                3 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:
                    Resolved:

                    Structure Helper Panel