PEL: Add PEL Manager class

This class will have the logic for how to handle PELs.  It will
also eventually provide D-Bus interfaces.

This first commit has stubs, plus some basic code to find if a PEL
is being passed in with the OpenBMC event log.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I55a5da4d2239c688fded31c112895c3c92bab56d

1 files changed, 7 insertions, 2 deletions

diff --git a/extensions/openpower-pels/entry_points.cpp b/extensions/openpower-pels/entry_points.cpp
index 1b29ec5..5adeb40 100644
--- a/extensions/openpower-pels/entry_points.cpp
+++ b/extensions/openpower-pels/entry_points.cpp
@@ -1,6 +1,6 @@
 #include "elog_entry.hpp"
 #include "extensions.hpp"
-#include "sdbusplus/bus.hpp"
+#include "manager.hpp"
 
 namespace openpower
 {
@@ -9,10 +9,13 @@ namespace pels
 
 using namespace phosphor::logging;
 
+std::unique_ptr<Manager> manager;
+
 DISABLE_LOG_ENTRY_CAPS();
 
 void pelStartup(internal::Manager& logManager)
 {
+    manager = std::make_unique<Manager>(logManager);
 }
 
 REGISTER_EXTENSION_FUNCTION(pelStartup);
@@ -21,19 +24,21 @@ void pelCreate(const std::string& message, uint32_t id, uint64_t timestamp,
                Entry::Level severity, const AdditionalDataArg& additionalData,
                const AssociationEndpointsArg& assocs)
 {
+    manager->create(message, id, timestamp, severity, additionalData, assocs);
 }
 
 REGISTER_EXTENSION_FUNCTION(pelCreate);
 
 void pelDelete(uint32_t id)
 {
+    return manager->erase(id);
 }
 
 REGISTER_EXTENSION_FUNCTION(pelDelete);
 
 void pelDeleteProhibited(uint32_t id, bool& prohibited)
 {
-    prohibited = false;
+    prohibited = manager->isDeleteProhibited(id);
 }
 
 REGISTER_EXTENSION_FUNCTION(pelDeleteProhibited);