tree e7432406a6600d2c0858955eca3d21c8c78bfbdd
parent dfc4bbf2a227b2251ef8d69e7c88c8fbb2debaea
author Patrick Venture <venture@google.com> 1558372601 -0700
committer Patrick Venture <venture@google.com> 1560874208 -0700

firmware_update_via_blobs: new design notes about updating

During implementation, it was observed that the exact moment of update
wasn't sufficiently defined.  This patchset defines that the moment the
update is allowed upon closing of the verification blob once the
verification state is "complete" and without "error."  The exact
implementation of update is specific to the type of image.

There'll be a default implementation that simply
starts a systemd unit "update-bmc.service".
However, this is only one approach and the exact mechanism is up to the
implementer.  The default implementation will call the service.  The
service name will be configurable and the entire mechanism can be
specified by providing another implementation of the interface.
Similarly, to the verification mechanism.

Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: I7bdc705c9a2589db3fe19ab19c764c6795fcc7be