2
0
mirror of https://opendev.org/x/pyghmi synced 2025-01-14 03:37:47 +00:00
Jarrod Johnson 120d5f9a82 Passthrough errors when not sent by BMC in MegaRAC
In the 'has_megarac' call, it erroneously was assumed that
any IpmiException reflected the BMC indicating explicitly that
it didn't understand something about the command.  However
IpmiException is frequently used without a code to indicate
some harder error that can't relate to a system return code.
Address this by raising the exception if it didn't have a
BMC error code initialized.  It may be possible to get even
more specific, but somewhat limited because we could be getting
a 'invalid command' or 'invalid command length' or some 0x80
neighborhood error code, some OEM response.  Fortunately
things are limited since this code should only ever fire
against Lenovo equipment, but still keeping things open ended.

Change-Id: Ia84d1474f7d6787d162c6c7ef448f269d826cc2a
2016-04-25 09:28:41 -04:00
2013-08-17 22:29:25 -04:00
2013-06-30 14:21:20 -04:00
2015-10-17 22:36:04 +00:00
2014-05-08 14:06:01 -04:00
2016-03-21 15:04:26 -04:00
2015-12-01 14:30:01 -05:00
2013-09-13 11:28:28 -05:00

pyghmi

Pyghmi is a pure Python (mostly IPMI) server management library.

Building and installing

(These instructions have been tested on CentOS 7)

Clone the repository, generate the RPM and install it:

$ git clone https://github.com/openstack/pyghmi.git
$ cd pyghmi/
$ python setup.py bdist_rpm
$ sudo rpm -ivh dist/pyghmi-*.noarch.rpm

Using

There are a few use examples in the bin folder:

  • fakebmc: simply fakes a BMC that supports a few IPMI commands (useful for testing)
  • pyghmicons: a remote console based on SOL redirection over IPMI
  • pyghmiutil: an IPMI client that supports a few direct uses of pyghmi (also useful for testing and prototyping new features)
  • virshbmc: a BMC emulation wrapper using libvirt

Extending

If you plan on adding support for new features, you'll most likely be interested in adding your methods to pyghmi/ipmi/command.py. See methods such as get_users and set_power for examples of how to use internal mechanisms to implement new features. And please, always document new methods.

Sometimes you may want to implement OEM-specific code. For example, retrieving firmware version information is not a part of standard IPMI, but some servers are known to support it via custom OEM commands. If this is the case, follow these steps:

  • Add your generic retrieval function (stub) to the OEMHandler class in
  • pyghmi/ipmi/oem/generic.py. And please, document its intent, parameters and
  • expected return values.
  • Implement the specific methods that your server supports in subdirectories in
  • the oem folder (consider the lenovo submodule as an example). A OEM folder
  • will contain at least one class inheriting from OEMHandler, and optionally
  • helpers for running and parsing custom OEM commands.
  • Register mapping policies in pyghmi/ipmi/oem/lookup.py so pyghmi knows how
  • to associate a BMC session with the specific OEM code you implemented.

A good way of testing the new feature is using bin/pyghmiutil. Just add an extension for the new feature you just implemented (as a new command) and call it from the command line:

$ IPMIPASSWORD=passw0rd bin/pyghmiutil [BMC IP address] username my_new_feature_command
Description
No description provided
Readme Apache-2.0 13 MiB
Languages
Python 99.9%
Shell 0.1%