11. Change log¶
11.1. Version 1.0.0¶
This version contains all fixes up to version 0.32.1.
Dropped support for Python 3.4. Python 3.4 has had its last release as 3.4.10 on March 18, 2019 and has officially reached its end of life as of that date. Current Linux distributions no longer support Python 3.4. (issue #792)
Fixed an install error of lazy-object-proxy on Python 3.5 by no longer installing pylint/astroid/typed-ast/lazy-object-proxy on Python 3.5. It was already not invoked anymore on Python 3.5, but still installed.
Increased minimum version of Pylint to 2.5.2 on Python 3.6 and higher.
Fixed a bug where ‘Console.list_permitted_partitions()’ and ‘Console.list_permitted_lpars()’ when run on HMC/SE version 2.14.0 failed when accessing the ‘se-version’ property of the partition unconditionally. That property was introduced only in HMC/SE version 2.14.1. (issue #816)
Made read and write access to the properties dictionary of zhmcclient resource objects thread-safe by adding a Python threading.RLock on each resource object.
Added support for auto-updating of resources. For details, see the new section ‘Concepts -> Auto-updating of resources’. (issue #762)
Removed old build tools that were needed on Travis and Appveyor (remove_duplicate_setuptools.py and retry.bat) (issue #809)
11.2. Version 0.32.0¶
This version contains all fixes up to version 0.31.1.
Docs: Fixed and added missing authorization requirements for the Partition and Lpar methods.
Examples: Fixed errors in and improved metrics examples.
Fixed issues raised by new Pylint version 2.9.1.
Added support for ‘Console.list_permitted_partitions()’ and ‘Console.list_permitted_lpars()’. These methods require HMC 2.14.0 or later. (issue #793)
The Console object returned by ‘client.consoles.console’ is now a locally built object in order to avoid needless property retrieval.
11.3. Version 0.31.0¶
This version contains all fixes up to version 0.30.2.
Method ‘NotificationReceiver.notifications()’ now raises JMS errors returned by the HMC as a new exception ‘NotificationJMSError’. JSON parse errors are now raised as a new exception ‘NotificationParseError’. Both new exceptions are based on a new base exception ‘NotificationError’. (issue #770)
By default, the zhmcclient now verifies the HMC certificate using the CA certificates in the Python ‘certifi’ package. This can be controlled with a new ‘verify_cert’ init parameter to the ‘zhmcclient.Session’ class. (issue #779)
The ‘properties’ attribute of the resource classes (e.g. ‘Partition’) now is an immutable ‘DictView’ object in order to enforce the stated rule that that callers must not modify the properties dictionary. If your code used to make such modifications nevertheless, it will now get a ‘TypeError’ or ‘AttributeError’ exception, dependent on the nature of the modification.
Fixed a missing argument in ‘NotificationListener.on_message()’ by pinning stomp.py such that 6.1.0 and 6.1.1 are excluded. (issue #763)
Fixed a package dependency issue when setting up the development environment with the “pywinpty” package on Python 2.7 and Windows. (issue #772)
JMS errors returned by the HMC are now handled by raising a new exception ‘NotificationJMSError’ in the ‘NotificationReceiver.notifications()’ method. Previously, an exception was raised in the thread running the notification receiver, rendering it unusable after that had happened. (issue #770)
Fixed a TypeError for concatenating str and bytes. (issue #782)
Added a ‘verify_cert’ init parameter to the ‘zhmcclient.Session’ class to enable verification of the server certificate presented by the HMC during SSL/TLS handshake. By default, the certificate is validated against the CA certificates provided in the Python ‘certifi’ package. (issue #779)
Added catching of OSError/IOError exceptions raised by the ‘requests’ package for certain certificate validation failures, re-raising such exceptions as a pywbem.ConnectionError.
Docs: Added a section “Security” to the documentation that describes security related aspects in the communication between the zhmcclient and the HMC. (related to issue #779)
Docs: Added a section “Troubleshooting” to appendix of the documentation that currently lists two cases of communication related issues. (related to issue #779)
The ‘properties’ attribute of the resource classes (e.g. ‘Partition’) now is an immutable ‘DictView’ object provided by the ‘immutable-views’ package, in order to enforce the stated rule that that callers must not modify the properties dictionary of resource objects.
11.4. Version 0.30.0¶
Docs: Properties of classes are now shown in the Attributes summary table of the class. (issue #726)
Docs: Fixed the incorrect default value documented for the force parameter of Lpar.scsi_load(). The correct default is False. (part of issue #748).
Fixed StatusTimeout when activating an LPAR that goes straight to status “operating”, by adding “operating” as a valid target value for the operational status. (issue #755)
Added an optional parameter secure_boot to Lpar.scsi_load() (issue #748).
Added an optional parameter force to Lpar.scsi_dump() (issue #748).
11.5. Version 0.29.0¶
Mitigated the coveralls HTTP status 422 by pinning coveralls-python to <3.0.0.
Docs: Removed outdated reference to KVM for IBM z Systems Admin book that was used as a second example in the Introduction section.
Docs: Added the missing Methods and Attributes tables to the description of resources related to the storage management feature (e,g. StorageGroup). (issue #708)
Added a new Partition.start_dump_program() method that performs the HMC operation ‘Start Dump Program’. That operation is supported on CPCs in DPM mode that have the DPM storage management feature (i.e. z14 and later) and complements the ‘Dump Partition’ HMC operation that is supported only on CPCs in DPM mode that do not have the DPM storage management feature (i.e. z13 and earlier). Mock support for the ‘Start Dump Program’ operation was also added. (issue #705).
Improved zhmcclient HMC logging in error cases by not truncating the HTTP response content for HTTP status 400 and higher. (issue #717) Also the truncation limit was icreased to 30000 to accomodate most HMC responses.
Improved display of zhmcclient.HTTPError exceptions by adding the ‘stack’ field if present. (issue #716)
Suppressed exceptions that were caught and a new exception was raised in the except clause, by setting __cause__ = None on the new exception. This avoids lengthy and unnecessary tracebacks that contain the message ‘Another exception occurred when handling …’. (issue #715)
Improved the handling of resource not found errors during metrics processing by adding a new zhmcclient.MetricsResourceNotFound exception that may now be raised when accessing the MetricObjectValues.resource property. (zhmc-prometheus-exporter issue #113)
Blanked out value of ‘x-api-session’ field (Session ID) when logging error responses. (zhmccli issue #136)
Added support for Capacity Groups in DPM mode, by adding resource classes zhmcclient.CapacityGroup and zhmcclient.CapacityGroupManager and a property zhmcclient.Cpc.capacity_groups for accessing them. (issue #734)
Docs: Moved change log up one level to avoid Sphinx warning about duplicate labels.
11.6. Version 0.28.0¶
Removed the installed scripts cpcdata and cpcinfo and added them as cpcdata.py and cpcinfo.py to the examples folder.
Test: Increased time tolerance for time-based tests.
Docs: Added z15 to supported environments (issue #684).
Fixed an AttributeError in UserPatternManager.reorder() (related to issue #661).
Test: Fixed an AttributeError in test utilities class HMCDefinition (related to issue #661).
Test: Fixed incorrect assignment in adapter test (related to issue #661).
Migrated from Travis and Appveyor to GitHub Actions. This required several changes in package dependencies for development.
Added support for operations for managing temporary processor capacity: Cpc.add_temporary_capacity() and Cpc.remove_temporary_capacity().
Added support for status timeout in Partition.stop() that waits for partition stop to reach desired status.
Test: Resolved remaining Pylint issues and enforcing no issues from now on (issue #661).
11.7. Version 0.27.0¶
This version contains all fixes up to 0.26.2.
Fixed Travis setup by removing circumventions for old issues that caused problems meanwhile.
Adjusted versions of dependent packages for development environment to fix issues on Python 3.4.
Fixed AttributeError when calling partition.list_attached_storage_groups(). (See issue #629)
Docs: Fixed description to start a new version that was missing updating the version to the new development version. (See issue #639)
Docs: Fixed description of installation from a repo branch. (See issue #638)
Test: Fixed missing ffi.h file on CygWin when testing (See issue #655)
Docs: Fixed links to HMC WS API books that have become invalid. (See issue #665)
Fixed empty port list returned by PortManager.list() for CNA adapters.
Install: Fixed the broken installation from the source distribution archive on Pypi (see issue #651)
Test: Pinned ‘pyrsistent’ package (used by jupyter notebook) to <0.16.0 on Python 2.7 and to <0.15.0 on Python 3.4.
Test: Fixed issue where virtualenv on pypy3 created env one level higher. (see issue #673)
Added an easy way to print debug information for inclusion into issues, via python -m zhmcclient.debuginfo. (See issue #640)
Added discover_fcp() and get_connection_report() methods to the StorageGroup resource. Added an example discover_storage_group.py that uses the two new methods. (See issue #623)
Test: Running coveralls for all Python versions in order to cover Python version-specific code. The coveralls.io web site consolidates these runs properly into a single result.
Docs: Added links to HMC WS APi and Operations books for z15. (Related to issue #665)
Added the z15 machine types 8561 and 8562 for detecting the maximum number of partitions, and started exploiting the new ‘maximum-partitions’ property of the CPC for this purpose.
Docs: Removed link to “KVM for IBM z Systems - System Administration” book, because the product is no longer supported. (Related to issue #665)
Changed the theme of the documentation on RTD from classic to sphinx_rtd_theme (See issue #668)
Test: Added ‘make installtest’ to the Makefile to test installation of the package into an empty virtualenv using all supported installation methods. Added these install tests to the Travis CI tests. (related to issue #651)
11.8. Version 0.26.0¶
This version contains all changes from 0.25.1.
Added the missing os_ipl_token parameter to Lpar.scsi_dump().
Migrated from using the yamlordereddictloader package to using the yamlloader package, because yamlordereddictloader got deprecated. (See issue #605)
Pinned version of PyYAML to <5.3 for Python 3.4 because 5.3 removed support for Python 3.4
Increased minimum version of stomp.py to 4.1.23 to pick up a fix for hangs during NotificationReceiver.close(). (See issue #572)
Promoted the development status of the zhmcclient package on Pypi from 3 - Alpha to 4 - Beta.
Added support for Python 3.8 to the package metadata and to the Travis and Appveyor and Tox environments. (See issue #596)
Dropped the use of the pbr package. The package version is now managed in zhmcclient/_version.py. (See issue #594)
Test: Added support for TESTOPTS env var to Makefile to be able to specify py.test options when invoking make test.
11.9. Version 0.25.0¶
Docs: Fixed incorrect statement about HMC version 2.14.0 supporting both GA generations of z14 machines.
Docs: Added HMC version 2.14.1 in “Bibliography” and “Introduction” sections.
Added support for following LPAR operations:
Lpar.psw_restart() (HMC: “PSW Restart”)
Lpar.scsi_dump() (HMC: “SCSI Dump”)
Added support for Storage Template objects in DPM mode (see issue #589).
11.10. Version 0.24.0¶
Operations that resulted in HTTP status 403, reason 1 (“The user under which the API request was authenticated does not have the required authority to perform the requested action.”) so far raised ServerAuthError. However, that exception does not represent that situation properly, because the login user is actually properly authenticated. The handling of this case was changed to now raise HTTPError instead of ServerAuthError. This change is only incompatible to users of the zhmcclient API who have code handling this exception specifically.
Fixed LookupError on unknown encoding ISO-5589-1 in test_session.py test that occurred with latest requests_mock package.
Increased minimum version of flake8 to 3.7.0 due to difficulties with recognizing certain ‘noqa’ statements. This required explicitly specifying its dependent pycodestyle and pyflakes packages with their minimum versions, because the dependency management did not work with our minimum package versions.
Fixed use of incorrect HTTP method in Console.get_audit_log() and Console.get_security_log(). See issue #580.
Improved end2end test support for zhmcclient and its using projects. The zhmcclient.testutils package already provides some support for end2end tests by users of the zhmcclient package. It is also used by the end2end tests of the zhmcclient package itself. This change improves that support, mainly from a perspective of projects using zhmcclient.
Improved the show_os_messages.py example.
Blanked out the session ID value in the log record for logging off.
Changed import of ‘stomp’ module used for notifications from the HMC, to be lazy, in order to speed up the import of ‘zhmcclient’ for its users. The ‘stomp’ module is now imported when the first zhmcclient.NotificationReceiver object is created. Also, only the class needed is imported now, instead of the entire module.
Added timezone support to the utility function zhmcclient.datetime_from_timestamp(). The desired timezone for the returned object can now be specified as an optional argument, defaulting to UTC for compatibility. This allows displaying HMC timestamps in local time rather than just UTC time.
Added support for specifying multiple notification topics to zhmcclient.NotificationReceiver.
11.11. Version 0.23.0¶
Fixed the list_storage_groups.py example. It used a non-existing property on the Cpc class.
Passwords and session tokens are now correctly blanked out in logs. See issue #560.
Added support for the new “Zeroize Crypto Domain” operation that allows zeroizing a single crypto domain on a crypto adapter. This operation is supported on z14 GA2 and higher, and the corresponding LinuxOne systems.
Changes in logging support:
Removed the notion of module-specific loggers from the description of the logging chapter, because that was not used at all, and is not expected to be used in the future: Errors are supposed to be raised as exceptions and not logged, and warnings are supposed to be issued as Python warnings and not logged.
Escaped newlines to blanks in log messages, so that all log messages are now on a single line.
Changed the syntax for zhmcclient.api log messages, to start with “Called:” and “Return:” instead of “==>” and “<==”.
Changed the syntax for zhmcclient.hmc log messages, to start with “Request:” and “Respons:” instead of “HMC request:” and “HMC response:”, in order to have the URLs column-adjusted.
11.12. Version 0.22.0¶
Added a mitigation for a firmware defect that causes filtering of adapters by adapter-id to return an empty result when the specified adapter-id contains hex digits (‘a’ to ‘f’). See issue #549.
11.13. Version 0.21.0¶
Update Requests package to 2.20.0 to fix following vulnerability of the National Vulnerability Database: https://nvd.nist.gov/vuln/detail/CVE-2018-18074
11.14. Version 0.20.0¶
Docs: Added missing support statements for the LinuxOne Emperor II machine generations to the documentation (The corresponding z14 was already listed).
Docs: Streamlined, improved and fixed the description how to release a version and how to start a new version, in the development section of the documentation.
Added support for Python 3.7. This required increasing the minimum versions of several Python packages in order to pick up their Python 3.7 support:
pyzmq from 16.0.2 to 16.0.4 (While 16.0.4 works for this, only 17.0.0 declares Python 3.6(!) support on Pypi, and Python 3.7 support is not officially declared on Pypi yet for this package).
PyYAML from 3.12 to 3.13 (see PyYAML issue https://github.com/yaml/pyyaml/issues/126).
Docs: Added support statements for the z14-ZR1 and LinuxONE Rockhopper II machine generations to the documentation.
Added support for the z14-ZR1 and LinuxONE Rockhopper II machine generations to the Cpc.maximum_active_partitions() method.
Provided direct access to the (one) Console object, from the ConsoleManager and CpcManager objects, via a new console property. This is for convenience and avoids having to code find() or list() calls. The returned Console object is cached in the manager object.
Also, added a console property to the FakedConsoleManager class in the mock support, for the same purpose.
Added a property client to class CpcManager for navigating from a Cpc object back to the Client object which is the top of the resource tree.
Added support for the new concept of firmware features to Cpcs and Partitions, by adding methods feature_enabled() and feature_info() to classes Cpc and Partition for inspection of firmware features. The firmware feature concept was introduced starting with the z14-ZR1 and LinuxONE Rockhopper II machine generation. The DPM storage management feature is the first of these new firmware features.
Added support for the DPM storage management feature that is available starting with the z14-ZR1 and LinuxONE Rockhopper II machine generation. This includes new resources like Storage Groups, Storage Volumes, and Virtual Storage Resources. It also includes new methods for managing storage group attachment to Partitions. The new items in the documentation are:
In 5.1. CPCs: list_associated_storage_groups(), validate_lun_path().
In 5.5. Partitions: attach_storage_group(), detach_storage_group(), list_attached_storage_groups().
5.12. Storage Groups
5.13. Storage Volumes
5.14. Virtual Storage Resources
In 5.15 Console: storage_groups
Added support for changing the type of storage adapters between FICON and FCP, via a new method Adapter.change_adapter_type(). This capability was introduced with the z14-ZR1 and LinuxONE Rockhopper II machine generation.
11.15. Version 0.19.11¶
Note: The version number of this release jumped from 0.19.0 right to 0.19.11, for tooling reasons.
Docs: Improved the description of installation without Internet access, and considerations on system Python vs. virtual Python environments.
Lowered the minimum version requirements for installing the zhmcclient package, for the packages: requests, pbr, decorator. Added support for tolerating decorator v3.4 in the zhmcclient _logging module.
Adjusted development environment to changes in Appveyor CI environment.
11.16. Version 0.19.0¶
Lpar.deactivate()method is now non-forceful by default, but can be made to behave like previously by specifying the new
forceparameter. In force mode, the deactivation operation is permitted when the LPAR status is “operating”.
Fixed a flawed setup of setuptools in Python 2.7 on the Travis CI, where the metadata directory of setuptools existed twice, by adding a script remove_duplicate_setuptools.py that removes the moot copy of the metadata directory (issue #434).
Fixed a bug where multiple Session objects shared the same set of HTTP header fields, causing confusion in the logon status.
Migrated all remaining test cases from unittest to pytest, and started improving the testcases using pytest specific features such as parametrization.
Added support for a
forceparameter in the
Lpar.load()methods. It controls whether the operation is permitted when the LPAR status is “operating”.
Note that this changes
Lpar.deactivate()to be non-forceful by default (force=True was hard coded before this change).
Added support for an
activation_profile_nameoption in the
Lpar.activate()method, that allows specifying the activation profile to be used. The default is as before: The profile that is specified in the
next-activation-profileproperty of the
Lpar.load()optional in order to support z14. Up to z13, the HMC now returns an error if no load address is specified. Adjusted the zhmcclient mock support accordingly.
Added LPAR status checks in the zhmcclient mock support, so that activate, deactivate and load returns the same errors as the real system when the initial LPAR status is not permitted, or when the activation profile name does not match the LPAR name, or when no load address is specified.
Improved the testcases for the Lpar and LparManager classes.
Added the ability to mock the resulting status of the faked Lpars in the zhmcclient mock support, for the Activate, Deactivate, and Load operations. Added a new chapter “URI handlers” in section “Mock support” of the documentation, to describe this new ability.
Added support for CPC energy management operations:
Cpc.set_power_save()(HMC: “Set CPC Power Save”)
Cpc.set_power_capping()(HMC: “Set CPC Power Capping”)
Cpc.get_energy_management_properties()(HMC: “Get CPC Energy Management Data”)
The zhmcclient package no longer adds a NullHandler to the Python root logger (but still to the zhmcclient.api/.hmc loggers).
Added a function test concept that tests against a real HMC.
11.17. Version 0.18.0¶
Removed the zhmc CLI support from this project, moving it into a new GitHub project
This removes the following prerequisite Python packages for the zhmcclient package:
prompt_toolkit (from click-repl)
python-utils (from progressbar2)
wcwidth (from prompt-toolkit -> click-repl)
Fixed a flawed setup of setuptools in Python 2.7 on the Travis CI, where the metadata directory of setuptools existed twice, by adding a script remove_duplicate_setuptools.py that removes the moot copy of the metadata directory (issue #434).
11.18. Version 0.17.0¶
The zhmcclient mock support for Partitions no longer allows to stop a partition when it is in status ‘degraded’ or ‘reservation-error’. That is consistent with the real HMC as described in the HMC API book.
In the HTTPError exception class, args was set to the body argument, i.e. to the entore response body. Because by convention, args should be a human readable message, this has been changed to now set args to the ‘message’ field in the response body, or to None if not present.
Fixed the bug that aborting a confirmation question in the CLI (e.g. for “zhmc partition delete”) caused an AttributeError to be raised. It now prints “Aborted!” and in interactive mode, terminates only the current command. (issue #418).
Fixed an AttributeError when calling ‘zhmc vfunction update’. Access to a partition from nic and vfunction is done via the respective manager (issue #416).
In the zhmc CLI, fixed that creating a new session reused an existing session. This prevented switching between userids on the same HMC (issue #422).
Docs: In the “Introduction” chapter of the documentation, fixed the HMC API version shown for z14.
Docs: In the Appendix of the documentation, added IBM book number and link for the HMC API book of z14.
Avoided DeprecationWarning on Python 3 for invalid escape sequences in some places.
The zhmcclient mock support for various resource classes did not always check for invalid CPC status and for invalid Partition status as described in the HMC API book. It now does.
In the mock support, invalid input to faked resource classes (mainly when adding faked resources) is now handled by raising a new exception
ValueError). The URI handler of the mock support now converts that into an HTTP error 400 (Bad Request), consistent with the HMC API book.
datetime_from_timestamp()functions that convert between Python
datetimeobjects and HMC timestamp numbers.
Added mock support for Metrics resources.
Session.logoff(), consistent with
Session.logon(). This was needed as part of fixing issue #422.
Added a __repr__() function to the Session class, for debug purposes.
In the ParseError exception class, a message of None is now tolerated, for consistency with the other zhmcclient exception classes.
In the NotFound exception class, a filter_args parameter of None is now tolerated, for consistency with the NoUniqueMatch exception class.
Documented for the zhmcclient exception classes how args is set.
Clarified in the documentation that the manager and resources parameters of the NoUniqueMatch and NotFound exception classes must not be None.
Improved the unit test cases for the Client class and for the zhmcclient exception classes, and migrated them to py.test.
Migrated the unit tests for HBAs from unittest to py.test, and improved the test cases.
In the Hba.reassign_port() method, updated the Hba object with the changed port, consistent with other update situations.
Clarified in the description of HbaManager.list() that only the ‘element-uri’ property is returned and can be used for filtering.
The mock support for the “Create NIC” operation now performs more checking on the URIs specified in the ‘network-adapter-port’ or ‘virtual-switch-uri’ input properties, raising HTTP status 404 (Not Found) as specified in the HMC API book.
FakedNic.add()method of the mock support, the checking for the URIs specified in the ‘network-adapter-port’ or ‘virtual-switch-uri’ input properties was relaxed to only the minimum, in order to make the setting up of faked resources easier.
Migrated the unit tests for
NicManagerfrom unittest to py.test, and improved them.
Improved the way the named tuples
Added support for
Consoleresource and its child resources
LDAP Server Definition, both for the zhmcclient API and for the zhmcclient mock support.
As part of support for the
Consoleresource, added a new resource class
UnmanagedCpcwhich representd unmanaged CPCs that have been discovered by the HMC. The existing
Cpcclass continues to represent only managed CPCs; this has been clarified in the documentation.
As part of support for the
Consoleresource, added a method
Clientclass, which waits until the HMC is available again after a restart. This method is used by
Console.restart(), but it can also be used by zhmcclient users.
As part of support for the
Session.post()to allow for an empty response body when the operation returns with HTTP status 202 (Accepted). This status code so far was always assumed to indicate that an asynchronous job had been started, but it can happen in some
Consoleoperations as well.
Improved the error information in the
ParseErrorexception, by adding the “Content-Type” header in cases where that is interesting.
Add CLI commmands to mount and unmount an ISO to a Partition.
11.19. Version 0.16.0¶
Fixed CLI: Remove defaults for options for ‘partition update’ (issue #405).
Added Code Climate support.
11.20. Version 0.15.0¶
In case the user code was specifically processing the reason code 900 used for HTML-formatted error responses with HTTP status 500: This reason code has been split up into multiple reason codes. See the corresponding item in section “Enhancements”.
Fixed a TypeError: “‘odict_values’ object does not support indexing” on Python 3.x (issue #372).
Minor fixes in the documentation (e.g. fixed name of
Fixed the zhmc CLI for Python 3 where multiple commands raised AttributeError: “‘dict’ object has no attribute ‘iteritems’ in
zhmccli/_helper.py. (issue #396).
Added support for the HMC Metric Service. For details, see section ‘Metrics’ in the zhmcclient documentation. There is an example script
metrics.pydemonstrating the use of the metrics support. The metrics support caused an additional package requirement for the
Added support for a “metrics” command to the zhmc CLI.
Added support for the IBM z14 system (in internal machine type tables and in the documentation).
zhmccli: Support for ‘authorization controls’ of a Partition (issue #380)
Added CLI support for processing weights (issue #383)
The HTTPError raised at the API for HMC Web Services not enabled now has a simple error message and uses a specific reason code of 900. Previously, the returned HTML-formatted response body was used for the message and a generic reason code of 999. All other HTML-formatted error responses still use the generic reason code 999. That reason code 999 is now documented to be changed to more specific reason codes, over time. (issue #296).
Reduced the package requirements to only the direct dependencies of this package.
Changed the experimental
Cpc.get_free_crypto_domains()method to test only control-usage access to the specified adapters. Improved that method by supporting None for the list of adapters which means to inspect all crypto adapters of the CPC.
11.21. Version 0.14.0¶
Changed the return value of
TimeStatsKeeper.snapshot()from a list of key/value tuples to a dictionary. This is more flexible and reduces the number of data structure conversions in different scenarios. See issue #269.
Changed the arguments of
Partition.mount_iso_image()incompatibly, in order to fix issue #57.
Fixed the documentation of several asynchronous
Partitionmethods that incorrectly documented returning
Nonein case of synchronous invocation, to now document returning an empty dictionary:
All other asynchronous methods did not have this issue. See issue #248.
Clarified in the documentation of all exceptions that have a
detailsinstance variable, that it is never
Fixed using ‘–ssc-dns-servers’ option for the CLI commands ‘zhmc partition create/update’. See issue #310.
Fixed the incorrect parameters of
Partition.mount_iso_image(). See issue #57.
Reads the vlan-id as a integer instead as a string for the ‘zhmc nic create/update’ cli command. See issue #337.
Fixed the AttributeError that occurred when using zhmcclient in Jupyter notebooks, or in the python interactive mode. See issue #341.
Improved content of
zhmcclient.ParseErrormessage for better problem analysis.
Increased the default status timeout from 60 sec to 15 min, in order to accomodate for some large environments. The status timeout applies to waiting for reaching the desired LPAR status after the HMC operation ‘Activate LPAR’ or ‘Deactivate LPAR’ has completed.
Noneas a value for the
Lpar.load(), and changed the default to be
None(the latter change does not change the behavior).
Added actual status, desired statuses and status timeout as attributes to the
StatusTimeoutexception, for programmatic processing by callers.
In the zhmc CLI, added a
--allow-status-exceptionsoption for the
lpar activate/deactivate/loadcommands. Setting this option causes the LPAR status “exceptions” to be considered an additional valid end status when waiting for completion of the operation.
Improved documentation of CLI output formats.
Simplified the message of the
ServerAuthErrorthat are used depending on where the authentication issue is detected. Reason for the split was that the two subclasses have different instance variables. The
AuthErrorexception class is now an abstract base class that is never raised but can be used to catch exceptions.
Made error data available as instance variables of the following exceptions:
Improved unit test cases for
Added support to the zhmc CLI for an interactive session to the console of the operating system running in a partition (
zhmc partition console) or LPAR (
zhmc lpar console).
str_def()method to all exception classes, which returns a definition-style string for parsing by scripts.
In the zhmc CLI, added options
--error-formatfor controlling the format of error messages. The
-e defoption selects the format returned by the new
str_def()methods. This format provides for easier parsing of details of error messages by invoking scripts.
wait_for_status()methods to the
Partitionclasses, in order to ease the work for users that need to ensure that a particular LPAR or partition status is reached.
Added support for crypto-related methods on the
Adapterresource classes. Added zhmcclient mock support for the faked partition (not yet for the faked adapter).
Partition.start()waits for reaching the desired status ‘active’ or ‘degraded’, because it transitions through status ‘paused’ when starting a partition.
NoUniqueMatchexception so that the list of resources that did match the filter, are shown with their URIs in the error message, and are available as new
resource_urisattributes. This change adds a required argument
resourcesto the constructor of
NoUniqueMatch. However, since this exception is only supposed to be raised by the zhmcclient implementation, this change is compatible to zhmcclient users.
Moved the invocation of PyLint from the “make check” target into its own “make pylint” target, inorder to speed up the CI testing.
Added the ability for
Session.post()to support binary data as the payload. The
bodyargument may now be a dictionary which is represented as a JSON string, a binary string which is used directly, or a unicode string which is encoded using UTF-8. This was necessary to fix issue #57.
In the zhmcclient mock support, added a Python property
nameto all faked resources, which returns the value of the ‘name’ resource property.
Added a Python property
Adapterclass, which returns the maximum number of crypto domains of a crypto adapter.
Added a Python property
Cpcclass, which returns the maximum number of active LPARs or partitions of a CPC.
get_free_crypto_domains()method to the
Cpcclass, in order to find out free domain index numbers for a given set of crypto adapters. Note: This method is considered experimental in this version.
update_properties()method to the
Improved the description of the
Nic.create()methods to describe how the backing adapter port is specified.
Extended the zhmcclient mock support by adding support for all operations thet are supported at the zhmcclient API but were not yet supported for mocking, so far.
11.22. Version 0.13.0¶
In the CLI, changed the default for number of processors for the
zhmc partition createcommand to create 1 IFL by default, if neither IFLs nor CPs had been specified. Also, a specified number of 0 processors is now passed on to the HMC (and rejected there) instead of being removed by the CLI. This keeps the logic simpler and more understandable. See also issue #258.
BaseManager.flush()method in favor of the new
Fixed that the defaults for memory for the
zhmc partition createcommand were ignored (issue #246).
The default values for the retry / timeout configuration for a session has been changed to disable read retries and to set the read timeout to 1 hour. In addition, read retries are now restricted to HTTP GET methods, in case the user enabled read retries. See issue #249.
Fixed that resource creation, deletion, and resource property updating now properly updates the resource name-to-URI cache in the zhmcclient that is maintained in the *Manager objects. As part of that, the BaseManager init function got an additional required argument session, but because creation of manager objects is not part of the external API, this should not affect users. See issue #253.
In the unit testcases for the update_properties() and delete() methods of resource classes, fixed incorrect assumptions about their method return values. See issue #256.
In the unit testcases for the update_properties() and delete() methods of resource classes, fixed incorrectly returned response bodies for mocked DELETE and POST (for update), and replaced that with status 204 (no content). This came up as part of fixing issue #256.
NotFoundfor existing resources, for resource types that are elements (i.e. NICs, HBAs, VFs, Ports) (issue #264).
Fixed that the filter arguments for
list()for string properties when matched on the client side are matched using regular expressions instead of exact matching, consistent with the zhmcclient documentation, and with server-side matching on the HMC. See issue #263.
Fixed that the filter arguments for
list()when used with lists of match values incorrectly applied ANDing between the list items. They now apply ORing, consistent with the zhmcclient documentation, and with server-side matching on the HMC. See issue #267.
Fixed that the
Cpc.dpm_enabledproperty incorrectly returned
Trueon a z13 in classic mode. See issue #277.
Fixed errors in zhmcclient mock support related to DPM mode checking.
Fixed that filter arguments specifying properties that are not on each resource, resulted in raising KeyError. An example was when the “card-location” property was specified when finding adapters; that property does not exist for Hipersocket adapters, but for all other types. This situation is now handled by treating such resources as non-matching. See issue #271.
Fix when providing ‘load-parameter’ option. See issue #273
Added content to the “Concepts” chapter in the documentation.
The update_properties() method of all Python resource objects now also updates the properties of that Python resource object with the properties provided by the user (in addition to issuing the corresponding Update Properties HMC operation. This was done because that is likely the expectation of users, and we already store user-provided properties in Python resource objects when creating resources so it is now consistent with that. This came up as part of issue #253.
As part of fixing the name-to-URI cache, a new attribute name_uri_cache_timetolive was added to class RetryTimeoutConfig, which allows controlling after what time the name-to-URI cache is automatically invalidated. The default for that is set in a new DEFAULT_NAME_URI_CACHE_TIMETOLIVE constant. Also, the *Manager classes now have a new method invalidate_cache() which can be used to manually invalidate the name-to-URI cache, for cases where multiple parties (besides the current zhmcclient instance) change resources on the HMC. This came up as part of issue #253.
Improved the documentation of the lookup methods (list(), find(), findall()) and of the resource filtering concept in section ‘Filtering’. Related to issue #261.
Added zhmcclient mock support for the Create Hipersocket and Delete Hipersocket operations.
Added support for filtering in the zhmcclient mock support.
In order to improve the ability to debug the resource and manager objects at the API and the faked resource and manager objects of the mock support, the
__repr()__methods ahave been improved. Because these functions now display a lot of data, and because testing their string layout is not very interesting, all unit test cases that tested the result of
__repr()__methods have been removed.
Add basic Secure Service Container support to the CLI.
11.23. Version 0.12.0¶
The password retrieval function that can optionally be passed to
Session()has changed its interface; it is now being called with host and userid. Related to issue #225.
Added WWPN support in mocking framework (issue #212).
Fixed error in mock support where the operation_timeout argument to FakedSession.post() was missing.
Fixed a bug in the unit test for the mock support, that caused incomplete expected results not to be surfaced, and fixed the incomplete testcases.
Fixed in the CLI that the spinner character was part of the output.
Improved robustness of timestats tests by measuring the actual sleep time instead of going by the requested sleep time.
Added support for ‘error’ field in ‘job-results’ (fixes issue #228).
Fixed version mismatches in CI test environment when testing with the minimum package level by consistently using the latest released packages as of zhmcclient v0.9.0 (2016-12-27). This caused an increase in versions of packages needed for the runtime.
Improved the mock support by adding the typical attributes of its superclass FakedBaseResource to the FakedHmc class.
Improved the mock support by adding __repr__() methods to all Faked* classes that return an object representation suitable for debugging.
In the mock support, the following resource properties are now auto-set if not specified in the input properties:
‘dpm-enabled’ is auto-set to False, if not specified.
‘is-ensemble-member’ is auto-set to False, if not specified.
‘status’ is auto-set, if not specified, as follows: If the ‘dpm-enabled’ property is True, it is set to ‘active’; otherwise it is set to ‘operating’.
Partition: ‘status’ is auto-set to ‘stopped’, if not specified.
Lpar: ‘status’ is auto-set to ‘not-activated’, if not specified.
Adapter: ‘status’ is auto-set to ‘active’, if not specified.
In the CLI, added
-yas a shorter alternative to the existing
--yesoptions, that allow skipping confirmation prompts.
Added OS-X as a test environment to the Travis CI setup.
In the CLI, added a
--passwordoption for specifying the HMC password (issue #225).
Added logging support to the zhmc CLI (issue #113).
Added ‘load-parameter’ option to ‘zhmc lpar load’ (issue #226).
11.24. Version 0.11.0¶
Changed the return value of all methods on resource classes that invoke asynchronous operations (i.e. all methods that have a wait_for_completion parameter), as follows:
For wait_for_completion=True, the JSON object in the ‘job-results’ field is now returned, or None if not present (i.e. no result data). Previously, the complete response was returned as a JSON object.
For wait_for_completion=False, a new Job object is now returned that allows checking and waiting for completion directly on the Job object. Previously, the whole response of the ‘Query Job Status’ operation was returned as a JSON object, and the job completion was checked on the Session object, and one could not wait for completion.
Changed the default value of the wait_for_completion parameter of the Session.post() method from True to False, in order to avoid superfluos timestats entries. This method is not normally used by users of the zhmcclient package.
Removed the version strings from the
argsproperty of the
zhmcclient.VersionErrorexception class. They had been available as
argscontinues to be the error message, and the
api_versionproperties continue to provide the version strings.
Changed the names of the Python loggers as follows:
Logger ‘zhmcclient.api’ logs API calls made by the user of the package, at log level DEBUG. Internal calls to API functions are no longer logged.
Logger ‘zhmcclient.hmc’ logs HMC operations. Their log level has been changed from INFO to DEBUG.
Removed the log calls for the HMC request ID.
Added a minimum version requirement >=4.0.0 for the dependency on the “decorate” Python package (issue #199).
Increased minimum version of “click-spinner” package to 0.1.7, in order to pick up the fix for zhmcclient issue #116.
Fixed CLI help text for multiple commands, where the text was incorrectly flowed into a paragraph.
Added support for retry/timeout configuration of HTTP sessions, via a new
RetryTimeoutConfigclass that can be specified for the
Sessionobject. The retry/timeout configuration can specify:
HTTP connect timeout and number of retries.
HTTP read timeout (of HTTP responses), and number of retries.
Maximum number of HTTP redirects.
Added new exceptions
zhmcclient.ConnectTimeout(for HTTP connect timeout),
zhmcclient.ResponseReadTimeout(for HTTP response read timeout), and
zhmcclient.RequestRetriesExceeded(for HTTP request retry exceeded). They are all derived from
Fixed a discrepancy between documentation and actual behavior of the return value of all methods on resource classes that invoke asynchronous operations (i.e. all methods that have a wait_for_completion parameter). See also the corresponding incompatible change (issue #178).
In the CLI, added a ‘help’ command that displays help for interactive mode, and a one-line hint that explains how to get help and how to exit interactive mode (issue #197).
In the CLI, added support for command history. The history is stored in the file ~/.zhmc_history.
In the CLI, changed the prompt of the interactive mode to
Added support for tolerating HTML content in the response, instead of JSON. An HTML formatted error message may be in the response for some 4xx and 5xx HTTP status codes (e.g. when the WS API is disabled). Such responses are raised as
HTTPErrorexceptions with an artificial reason code of 999.
Fixed an incorrect use of the
zhmcclient.AuthErrorexception and unnecessary checking of HMC behavior, i.e. when the HMC fails with “API session token expired” for an operation that does not require logon. This error should never be returned for operations that do not require logon. If it would be returned, it is now handled in the same way as when the operation does require logon, i.e. by a re-logon.
Added support for deferred status polling to the Lpar.activate/deactivate/load() methods. The HMC operations issued by these methods exhibit “deferred status” behavior, which means that it takes a few seconds after successful completion of the asynchronous job that executes the operation, until the new status can be observed in the ‘status’ property of the LPAR resource. These methods will poll the LPAR status until the desired status value is reached. A status timeout can be specified via a new status_timeout parameter to these methods, which defaults to 60 seconds. If the timeout expires, a new StatusTimeout exception is raised (issue #191).
Added operation timeout support to Session.post() and to all resource methods with a wait_for_completion parameter (i.e. the asynchronous methods). The operation timeout on the asynchronous methods can be specified via a new operation_timeout parameter, which defaults to 3600 seconds. If the timeout expires, a new OperationTimeout exception is raised (issue #6).
Added a new module that defines public constants, and that defines default timeout and retry values.
Experimental: In the CLI, added more supported table formats (plain, simple, psql, rst, mediawiki, html, LaTeX).
Improved the content of the log messages for logged API calls and HMC operations to now contain the function call arguments and return values (for API calls) and the HTTP request and response details (for HMC operations). For HMC operations and API calls that contain the HMC password, the password is hidden in the log message by replacing it with a few ‘*’ characters.
11.25. Version 0.10.0¶
The support for server-side filtering caused an incompatibility for the find() and findall() methods: For String typed resource properties, the provided filter string is now interpreted as a regular expression that is matched against the actual property value, whereby previously it was matched by exact string comparison.
The parameter signatures of the __init__() methods of BaseResource and BaseManager have changed incompatibly. These methods have always been considered internal to the package. They are now explicitly stated to be internal and their parameters are no longer documented. If users have made themselves dependent on these parameters (e.g. by writing a mock layer), they will need to adjust to the new parameter signature. See the code for details.
Fixed a bug where the CLI code tries to access ‘cpc’ from the ‘partition’ directly without going via the manager property. This caused an AttributeError (issue #161).
Fixed unrecognized field (‘adapter-port’) during ‘HBA create’ (issue #163).
Added filter arguments to the list() method, and added support for processing as many filter arguments as supported on the server side via filter query parameters in the URI of the HMC List operation. The remaining filter arguments are processed on the client side in the list() method.
Changed the keyword arguments of the find() and findall() methods to be interpreted as filter arguments that are passed to the list() method.
Documented the authorization requirements for each method, and in total in a new section “Setting up the HMC”.
Added a method open_os_message_channel() on Partition and Lpar objects, that returns a notification token for receiving operating system messages as HMC notifications.
Experimental: Added a class NotificationReceiver that supports receiving and iterating through HMC notificationsi for a notification token, e.g. those produced by open_os_message_channel().
11.26. Version 0.9.0¶
Fixed a bug where accessing the ‘name’ property via the properties attribute caused KeyError to be raised (issue #137). Note that there is now a recommendation to use get_property() or the name or uri attributes for accessing specific properties. The properties attribute should only be used for iterating over the currently present resource properties, but not for expecting particular properties.
Fixing regression in findall(name=..) (issue #141).
Changed links to HMC API books in Bibliography to no longer require IBM ID (issue #131).
Added example shell script showing how to use the command line interface.
Improved the examples with better print messages, exception handling, access of resource properties, and refreshing of resources.
Added support for load-parameter field in lpar.load().
11.27. Version 0.8.0¶
Added support in CLI for remaining cmds; client improvements.
Added a tool ‘tools/cpcdata’ for gathering information about all CPCs managed by a set of HMCs. The data can optionally be appended to a CSV spreadsheet, for regular monitoring.
11.28. Version 0.7.0¶
IOError during click-spinner 0.1.4 install (issue #120)
Documentation for zhmc CLI
11.29. Version 0.6.0¶
Fixed typo in help message of cpcinfo.
Fixed KeyError: ‘status’ when running example5.py (issue #99).
Fixed documentation of field Partition.hbas (issue #101).
Fixed new Flake8 issue E305.
Started raising a ParseError exception when the JSON payload in a HTTP response cannot be parsed, and improved the definition of the ParseError exception by adding line and column information.
Improved the AuthError and ConnectionError exceptions by adding a details property that provides access to the underlying exception describing details.
For asynchronous operations that are invoked with wait_for_completion, added an entry in the time statistics for the overall operation from the start to completion of the asynchronous operation. That entry is for a URI that is the target URI, appended with “+completion”.
Added time statistics entry for overall asynchronous operations.
Improved VersionError exception class and removed number-of-args tests.
Added the option to create a session object with a given session id.
Added base implementation of a command line interface (zhmc) for the zhmcclient.
11.30. Version 0.5.0¶
Fixed that in Partition.dump_partition(), wait_for_completion was always passed on as True, ignoring the corresponding input argument.
Added a script named
tools/cpcinfothat displays information about CPCs. Invoke with
prop()method for resources that allows specifying a default value in case the property does not exist.
get_wwpns()which performs HMC operation ‘Export WWPN List’.
reassign_port()which performs HMC operation ‘Reassign Storage Adapter Port’.
Clarifications in the Resource model section.
dpm_enabledproperty to use ‘List Partitions’ and ‘List Logical Partitions’ operations, in order to avoid the ‘List CPC Properties’ operation.
11.31. Version 0.4.0¶
This is the base version for this change log.