tree 183dbf5d41fafb94e958928d5335282a4265d57c
parent 778d1db372561811de43b7954542a4eae1183f04
author Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> 1715918492 -0500
committer Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> 1717089154 -0500

Add Dump Monitoring Support

This commit introduces the DumpMonitor class to monitor DBus signals
for dump creation and manage the collection process. It aims to
abstract the complexities of dump collection from the
phosphor-dump-collector and consolidate system-specific handling
within the openpower-dump-collector.

Rationale:
- By moving dump collection responsibilities to the
  openpower-dump-collector, we ensure that the
  phosphor-dump-collector` remains focused solely on hosting dump
  entries and interacting with external interfaces.
- The openpower-dump-collector now handles all system-specific
  dump collection, reducing potential impacts on the
  phosphor-dump-collector.
- Simplified Management: This change simplifies the overall management
  of dumps by centralizing dump collection logic in one place.

Key Changes:
1. A new DumpMonitor class monitors DBus signals for dump creation.
2. The executeCollectionScript function handles the actual dump
   collection and copies the dump to a specified location for the
   phosphor-dump-manager to pick up.
3. Once the dump is copied to the specific folder, the phosphor dump
   manager will pick up the file and update its status.
3. In the case of collection failure, the monitor updates the progress
   status to indicate that the dump collection failed.

Change-Id: Id5bac5f3fbc8ef7a4bd9e93ac91796206b3cfda9
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>