Re: Release v1.99.4

[Patrick Williams <patrick@stwcx.xyz>]

[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]

On Fri, Apr 07, 2017 at 09:10:01AM +0930, Andrew Jeffery wrote:
> A few points and queries:
> 
> >     * Elimination of "debug mode" in favor of systemd targets:
> >         - External FSI control for Cronus is done by systemd targets.
> >         - Automatic reboot of the host can be disabled independently
> >           by systemd targets.  This leaves the system in quiesce state
> >           when the host-watchdog fail or checkstop detection occurs.
> 
> Patrick: Do you have a link to documentation of these targets? Ideally
> these announcements would also provide these pointers.

This was posted to the mailing list recently.

https://lists.ozlabs.org/pipermail/openbmc/2017-March/007103.html

Matt Spinler, can you put a commit into openbmc/docs to permanently
document?

> 
> >     * LED management is refactored out of 'skeleton' and old
> >       /org/openbmc interfaces are removed.
> >     * Soft power-off should be supported.
> >         - This allows the host OS to gracefully shutdown on a power-off
> >           request.
> 
> Again, is there documentation?

https://github.com/openbmc/phosphor-dbus-interfaces is the starting
point for all dbus interfaces now. State-management is pretty well
documented: https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/xyz/openbmc_project/State

Your specific question about soft power-off, this is the default now for
the host object.  If you want to simply pull power (hard power-off) you
operate on the chassis object.

-- 
Patrick Williams

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]