Convert build process to autotools

Replaced the use of a manual Makefile with the use of autotools to
automatically verify and generate the necessary build files. Follow the
steps outlined within th

Convert build process to autotools

Replaced the use of a manual Makefile with the use of autotools to
automatically verify and generate the necessary build files. Follow the
steps outlined within the README.md file to build the package.

Change-Id: I75a0cc5029a63f448866cf38f3edc6d9be363c7e
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>

show more ...

Ensure all tools are building with -Wall and -Werror

Added -Wall & -Werror to CFLAGS. Added -Werror to CPPFLAGS.
Also corrected resulting compiler errors.

Change-Id: I1777c3c122edd4b6382a565caf2967

Ensure all tools are building with -Wall and -Werror

Added -Wall & -Werror to CFLAGS. Added -Werror to CPPFLAGS.
Also corrected resulting compiler errors.

Change-Id: I1777c3c122edd4b6382a565caf2967bb9b8afd14
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>

show more ...

phosphor-event: Add dbus method acceptBMCMessage

Add dbus method to accept event log from BMC.
This patch partially resolves issue: openbmc/skeleton#64

Change-Id: Icd19e02a1497a1139f7ba76226a3c16be

phosphor-event: Add dbus method acceptBMCMessage

Add dbus method to accept event log from BMC.
This patch partially resolves issue: openbmc/skeleton#64

Change-Id: Icd19e02a1497a1139f7ba76226a3c16bef6e85f0
Signed-off-by: Yi Li <adamliyi@msn.com>

show more ...

Merge pull request #14 from causten/associate

Add association interface to each event log

Add association interface capabilities for event logs

When a new event log is created it may create an interface
with a name of org.openbmc.association. If there are associations
between the log an

Add association interface capabilities for event logs

When a new event log is created it may create an interface
with a name of org.openbmc.association. If there are associations
between the log and other entites it will have a single property
named "association" which will be an a(sss).
That will be enough information for the rest server to present
it.

Note if the log does not have FRU call outs no association interface will exist

Lets say you want to run the acceptTestMessage method. It
will create an association between the event log and 2 dimms.

So
/org/openbmc/inventory/system/chassis/motherboard/dimm2
/org/openbmc/inventory/system/chassis/motherboard/dimm3

/org/openbmc/records/events/1/fru
should return
data : {/org/openbmc/inventory/system/chassis/motherboard/dimm2 , /org/openbmc/inventory/system/chassis/motherboard/dimm3}

You should also be able to go to the dimm and get the association in reverse

/org/openbmc/inventory/system/chassis/motherboard/dimm2/event
should return
data : {/org/openbmc/records/events/1/}

show more ...

Merge pull request #7 from causten/persist

Removing linked list requirements

Tabs, spaces and columns

you wanted it you got it. Indentation set to tabs, shrunk some
lines to adhere to 80 columns. All in one commit.

Remove dependency on linked lists

I was using a linked list to keep track of each dbus object.
It was because during a "Clear All Logs" I had to run through
all existing events and delete them. Tha

Remove dependency on linked lists

I was using a linked list to keep track of each dbus object.
It was because during a "Clear All Logs" I had to run through
all existing events and delete them. That meant I had to
record the slotid's for each interface. I have since
discovered the sd_bus_call_method_async sdbus call. It will
call the individual delete methods per log. So with that
along with the fact that all events are file based I simply
had to swap my linked list traverser with a directory listing
of all valid event logs.

show more ...

Merge pull request #6 from causten/broadcastdelete

Event Logs to survive a reboot

Event Logs to survive a reboot

The event service stores the events from the host. Before this commit all the code was in memory. That meant once a reboot occured you lost the logs. With this comm

Event Logs to survive a reboot

The event service stores the events from the host. Before this commit all the code was in memory. That meant once a reboot occured you lost the logs. With this commit I am storing all logs to the file system. This refactoring also enables a test suite. The suite can be invoked by 'make test; ./test'.

1) /var/sys/obmc/events/x
2) logs are stored in binary and saved
3) Each log now has a timestamp of when the log reached the service
4) I added a caching mechanism to reduce the io traffic if the the method is simply being called to capture the next parameter
5) You will notice a mixture of c/c++. This is because I want the test infrastructure to take advantage of c++ features

Useful REST calls
~~~~~~~~~~~~~~~~~
Note, dont forget to login first

List all events
curl -k https://bmc/org/openbmc/records/events/

Create an event log for testing purposes
curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST -d "{\"data\": []}" https://bmc/org/openbmc/records/events/action/acceptTestMessage

Delete an event
curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST -d "{\"data\": []}" https://bmc/org/openbmc/records/events/1/action/delete

Delete all events
curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST -d "{\"data\": []}" https://bmc/org/openbmc/records/events/action/clear

show more ...