summaryrefslogtreecommitdiff
path: root/meta-phosphor/recipes-phosphor/state/phosphor-state-manager-systemd-links.inc
AgeCommit message (Collapse)AuthorFilesLines
2021-09-20phosphor-state-manager: srcrev bump 2bfb1efc4b..5f8e04a6e1Andrew Geissler1-0/+8
Andrew Geissler (6): lg2: convert bmc state manager bmc-reset: check host boot progress prior to reset bmc-reset: create error if host was running bmc-reset: ensure chassis power on target complete bmc-reset: move to quiesce if host was running bmc-reset: add service to launch new host recovery Add new service to install image Change-Id: I2b3aa0c8c80450295e7884ece74ad9729d3bd66e Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
2021-08-11meta-phosphor: prep for new override syntaxPatrick Williams1-2/+2
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I588025b614416c43aa2d053765ab53bacf890cb5
2021-08-10host-check: check host state on startup of host managerAndrew Geissler1-14/+0
See this commit for more info on function and testing: https://github.com/openbmc/phosphor-state-manager/commit/0d1c3f1f9329c853677f0581287afef83eeea0f0 phosphor-state-manager: srcrev bump 65bfcf5792..0d1c3f1f93 Andrew Geissler (1): host-check: discover host state within state manager Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I04129b1838118efceb1d073539d01d6e1af99eec
2021-01-13remove warm reboot from diagnostic targetAndrew Geissler1-8/+0
Initially the diagnostic target was only tied to one type of system event. This one system event required a warm reboot so it made sense to just put that directly in this recipe. There are now new use cases for the diagnostic target that do not want or need a warm reboot. Remove the warm reboot from the diagnostic target and let other recipes add it if needed for their use cases. Tested: - Verified with all commits in this Topic that the witherspoon system has the same service layout as before and the rainier system has the new layout (crash used for mpipl) (From meta-phosphor rev: 2406ed7d08b4d4c9f2ea7960094aea9aed79f4ac) Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Iea5b791057c74a2be880d842436284fa23bd15bc Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2021-01-12install host state transition servicesAndrew Geissler1-0/+16
See the following for more details: https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-state-manager/+/39359 This will install the services required to get the TransitionToRunning and TransitionToOff support for CurrentHostState. Includes following in bump: Andrew Geissler (1): host state transitioning support Tested: - Verified CurrentHostState changed as expected doing a host on, off, and reboot. (From meta-phosphor rev: 56b7928ea464b89f1f585a92549d9026d1b91a43) Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Iffd6a7b9a71a0df0ee1180797db4253051436edf Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-11-05phosphor-state-manager: srcrev bump 162c7bfb0c..3191be88afAndrew Geissler1-0/+8
Andrew Geissler (5): soft-off: ensure pldm soft svc stopped on hard poweroff autoreboot: clear one time properties on chassis off autoreboot: one-time object support autoreboot: add one-time property to logic autoreboot: add one-time support to obmcutil Install new phosphor-clear-one-time@.service into obmc-chassis-poweroff@.target (From meta-phosphor rev: 948e50a15fd86fb84b9697019cf3ae099fa114fb) Change-Id: I3e883d65ceb403aea09e21dfe1a95bea5f5bffdb Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-09-30phosphor: ensure host state sensors cleared on host quiesceAndrew Geissler1-0/+8
By design, nothing occurs in the obmc-host-quiesce target. The point is to leave everything in its current state so external debug can occur. The host states sensors should be reset though so other BMC software knows the host is in an undefined state. Tested: - Verified sensors were reset when obmc-host-quiesce target was started (From meta-phosphor rev: 1ac5d20b80688027c61b153e8ba46dc1e855b030) Change-Id: Ib99b0261976335bbc0644e5572a131c4f3e25304 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-09-30phosphor: ensure host state sensors cleared on host stopAndrew Geissler1-0/+8
With some of the new targets like obmc-host-diagnostic-mode, the BMC can be a while in these targets before other ones are started which start initializing these sensors again. Need to be sure to reset them to defaults once the host is stopped for any reason. This ensures that other BMC software which is looking at these to know host boot state have the correct information. Tested: - Verified sensors were reset when starting obmc-host-diagnostic-mode target (From meta-phosphor rev: 6f640bd9fcabae0affc0883940e47bdd5a13e752) Change-Id: Iee12327b769ffed03dabb050fd4eed8137f76fe0 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-09-25systemd-units: move state units to own incAndrew Geissler1-0/+118
The openbmc project is moving away from obmc-phosphor-systemd and its SYSTEMD_LINK macros in favor of more explicit package based installation. This commit gets phosphor-state-manager going in the right direction so that future targets and services can build on the new way to do things. The chassis/host action and synchronization targets still need some additional thought and effort. Tested: Booted up image in QEMU and spot checked a few services ensuring they were still in the expected locations. (From meta-phosphor rev: 5059a445b94e70efa7d6c90c1b5e7aa755dfe1d7) Change-Id: I576cddd8ae10edb222d45e5b4903ea7195def4d4 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
generated by cgit v1.2.3 (git 2.39.0) at 2024-09-05 10:53:31 +0300