It has been expressed as a concern that 'ipmi' is too generic a name.
Additionally, it is also the case that non-ipmi capability is likely
to be incorporated as it goes along (e.g. Enclosure management and
virtual media are frequently not IPMI based).
Move existing content under the 'pyghmi' namespace. pyghmi stands for
'python general hardware management infrastructure' and is pronounced
'pygmy'
Change-Id: Ib549a9f5b7dd549c7dc5ddbab251a2e06c572e41
After some contemplation, I realized that given the underlying behavior of 'wait_for_rsp', that
synchronous and asynchronous calls play well with each other. The pattern of considering an 'onlogon'
function as running in a sort of greenthread works well and leads to much more comprehensible code
for the average person. While removing those arguments, the module contents were reorganized to
serve as an example of how more straightforward code written in this fashion may be.
Change-Id: I9c83660e4d3c68ad8ae0c016a3377b2a0e7ee6ec
Previously the ipmi session was using time.time(). This means
that retries and keepalives could be thrown off by things like ntp
or manual time corrections.
Ideally, we'd use the baked in time.monotonic(), but that doesn't exist
aside from python 3.3
Change-Id: Ia00026cef6df214f9463909309de44767c3752b5
Ran autopep8 on the four .py files in this module.
Manully fixed many additional pep8 errors as well,
Turned some long-line-comments into proper NOTE lines,
but there are more to do...
Change-Id: I657ba037863860ec3956150931c2c0e41085bd63
