Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc-tools / 4e17811037571bf8e06a45b370b48d4e502058f3
commit4e17811037571bf8e06a45b370b48d4e502058f3[log] [tgz]
authorAsmitha Karunanithi <asmitk01@in.ibm.com>Thu Oct 01 08:18:21 2020 -0500
committerAndrew Geissler <geissonator@yahoo.com>Fri Oct 16 14:23:08 2020 +0000
tree506d2eda5825a52fb5c59ba44b29e2cdcc94dc89
parent54e0c9ae85de24404782b2df8bdbbb6442e2e71a [diff]
Change openbmctool script w.r.t latest redfish dump changes

Oem paths are removed from dump log services and those
changes are incorporated in this commit, while the tool
commands remains the same.

Method to get task are also implemented to keep track of
the creation of dump task completion.

Tested-By:

python3 openbmctool.py -U root -P passwd -H hostname task
get -u /redfish/v1/TaskService/Tasks/<id>

=> Returns the task details

Signed-off-by: Asmitha Karunanithi <asmitk01@in.ibm.com>
Change-Id: Ic2db5b0673dd59e6f5c2d251cbdad88be30e81d4
1 file changed
tree: 506d2eda5825a52fb5c59ba44b29e2cdcc94dc89
  1. adcapp/
  2. altitude/
  3. autojson/
  4. bi2cp/
  5. cla-signers/
  6. dbus-pcap/
  7. dbusView/
  8. ddconvnotrunc/
  9. expectedJsonChecker/
  10. format-yaml/
  11. maintainers/
  12. netboot/
  13. openbmc-autobump/
  14. openbmc-events/
  15. openbmctool/
  16. pretty-journal/
  17. pwmtachtool/
  18. reboot/
  19. reboot-ping-pong/
  20. rootfs_size/
  21. sensor_yaml_config/
  22. tracing/
  23. upload_and_update/
  24. witherspoon-debug/
  25. LICENSE
  26. MAINTAINERS
  27. README.md
README.md

The OpenBMC Tools Collection

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 or utterly broken. Please help us improve!

Repository Rules

  • Always inspect what you will be executing
  • Some hacking on your part is to be expected

If you're still with us

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.

Sending patches

Please use gerrit for all patches to this repository:

Do note that you will need to be party to the OpenBMC CLA before your contributions can be accepted. See Gerrit Setup and CLA for more information.

What we will do once we have your patches

So long as your patches look sane with a cursory glance you can expect them to be applied. We may push back in the event that similar tools already exist or there are egregious issues.

What you must have in your patches

We don't ask for much, but you need to give us at least a Signed-off-by, use SPDX markers in your source files and put your work under an Apache 2.0 compatible license.

How you consume the repository

There's no standard way to install the scripts housed here, and adding parts of the repository to your PATH might be a bit of a dice-roll. We may also move or remove scripts from time to time as part of housekeeping. It's probably best to copy things out if you need stability.