psu code mgmt

From: Patrick Venture <venture@google.com>
To: Lei YU <mine260309@gmail.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Benjamin Fair <benjaminfair@google.com>
Subject: psu code mgmt
Date: Wed, 21 Aug 2019 15:47:28 -0700	[thread overview]
Message-ID: <CAO=notwjUWqOjBt7oRQpr7F95yANHT_SicGz-XVSXDPYNywKfw@mail.gmail.com> (raw)

Lei Yu;

I wanted to ask about the psu-code-mgmt, will it be exposing dbus
interfaces similarly to bmc-code-mgmt (I think I see that it is).  I
wanted to confirm that we could write a simple handler or type for
talking to psu-code-mgmt from phosphor-ipmi-flash.  Today I wrote a
guide on how to do part of that --
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-ipmi-flash/+/24606

We'd add something like:

[{
    "blob": "/flash/psu",
    "handler": { "type": "file", "path": "/tmp/psu-firmware" },
    "actions": {
        "preparation": {
            "type": "systemd",
            "unit": "phosphor-ipmi-flash-psu-prepare.target"
        },
        "verification": { "type": "psuSystemdVerification" },
        "update": { "type": "psuSystemdActivation" }
    }
}]

So then if we implement a psuSystemdVerification and
psuSystemdActivation, those can all the things you expect and stage
the file where you expect, etc.

Patrick