| commit | 22b1bb5d9f865cb5a1e3b6e646bd7e9472a131f8 | [log] [tgz] |
|---|---|---|
| author | Justin Thaler <thalerj@us.ibm.com> | Thu Mar 15 13:31:32 2018 -0500 |
| committer | Justin Thaler <thalerj@us.ibm.com> | Tue Apr 10 10:37:42 2018 -0500 |
| tree | b90c571857bfc5f0387b38b4ba9e4be7171c9453 | |
| parent | 8a86fca8c49f978ed47989be873bc8088f47611d [diff] |
FW Update fixes, Policy Table fixes Several improvements were made to the firmware update process for clients. The process added additional automation. It adds a check to see if the FW level is present on the bmc or not. It determines the ID that will be used by the bmc and presents it to the user. It automates the process of uploading, determining the image ID, and activating the new image. When complete the user is prompted to reboot the bmc and/or power on the system, to finish updating the firmware. This update adds system power control and bmc power control restrictions during the activation process, to prevent corrupting the BMC and bricking the system. This is done by adding a check to see if an activation is in progress, before performing the operation. This does not protect users using IPMI or the REST API directly. Some additional policy table changes were made to support problems with some alerts missing, found in several defects. Signed-off-by: Justin Thaler thalerj@us.ibm.com
The goal of this repository is to collect the two-minute hacks you write to automate interactions with OpenBMC systems.
It's highly likely the scripts don't meet your needs - they could be undocumented, dysfunctional, utterly broken, or sometimes casually rm -rf ~. Don't even think about looking for tests.
You have been warned.
Then this repository aims to be the default destination for your otherwise un-homed scripts. As such we are setting the bar for submission pretty low, and we aim to make the process as easy as possible:
However you want to send patches, we will probably cope:
Look, the rm -rf ~ thing was a joke, we will be keeping an eye on all of you for such shenanigans. But so long as your patches look sane with a cursory glance you can expect them to be applied. To be honest, even Perl will be considered moderately sane.
We don't ask for much, but you need to give us at least a Signed-off-by, and put your work under the Apache 2.0 license. Licensing everything under Apache 2.0 will just hurt our heads less. Lets keep the lawyers off our backs. ^
^ Any exceptions must be accompanied by a LICENSE file in the relevant subdirectory, and be compatible with Apache 2.0. You thought you would get away without any fine print?
Probably with difficulty. Don't expect the layout to remain static, or scripts to continue to exist from one commit to the next.