2025.1 Series Release Notes¶
2025.1-eom¶
Bug Fixes¶
Fixes getting the supported reset types from services that publish them in an
ActionInforesource, referenced by the system reset action’s@Redfish.ActionInfoannotation, instead of annotating them inline. On such systems every reset type was previously assumed to be supported.
5.5.1¶
Bug Fixes¶
Improve Redfish VirtualMedia
InsertMediaerror handling on BMCs that require credentials but return unstructured errors (e.g., responses that omiterror.codeand reportActionParameterMissingonly via@Message.ExtendedInfoor free-text messages). Sushy now detects these cases and retries withUserName/Passwordparameters, allowing ISO mounting to proceed. This also preserves compatibility with legacyerror.code == *GeneralErrorresponses that mention missing parameters.
5.4.0¶
New Features¶
Adds support for the
Portresource to the library.
Upgrade Notes¶
Support for Python 3.8 has been removed. Now the minimum python version supported is 3.9 .
Bug Fixes¶
Provides dummy vmedia username and password if required by BMC
5.3.0¶
New Features¶
Adds EthernetInterfaces property support to the Redfish Manager instance.
Bug Fixes¶
PATCH ‘HttpBootUri’ against SettingsURI if present. If not, fall back to System URI.
5.2.0¶
Bug Fixes¶
Adds the ability to retry an attempt to determine a Manager for a System when ManagedBy attribute is missing but Managers attribute is present. This resolves issues with certain hardware models such as Huawei 1288H.
Some hardware vendors set MAC addresses to the empty string which is not valid so skip including those ethernet_interfaces.
The
Namefield of a StorageControllers sub-field of a Storage resource is no longer mandatory.
5.1.0¶
Bug Fixes¶
Adds a work-around for cases where
Accept-Encoding: identityis not accepted.
5.0.0¶
Bug Fixes¶
Correctly handles error code
Base.1.12.ActionParameterMissingwhen dealing with hardware that requiresTransferProtocolTypefor virtual media operations and has different message in RelatedProperties response.
4.8.0¶
New Features¶
Adds a
boot_progressmapped object to the System object. Inside of this object, alast_statevalue maps to values provided by thesushy.BootProgressStateenum. Also exposes, for information purposes, thelast_boot_seconds_count,last_state_updated_at, andoem_last_statevalues, which map to the DMTF Redfish valuesLastBootTimeSeconds,LastStateTime, andOemLastStatefields for theBootProgressobject.
Adds support for virtual media via
Systemresource. For more information, see bug 2039458.
Bug Fixes¶
Correctly handles errors on a request that is re-tried after refreshing an authentication token.
4.7.0¶
New Features¶
Adds functionality to the
set_system_boot_optionsmethod permitting anhttp_boot_urioption to be set.
Adds an
http_boot_urioption to the System boot object, permitting an API client user to view what the BMC’s redfishHttpBootUrisetting is.
4.6.0¶
Bug Fixes¶
Fixes missing ETag in PATCH operation against Redfish resources with backward compatibility for Redfish implementation which doesn’t work with ETag in header.
4.5.1¶
Bug Fixes¶
Fixes bug where sushy would not pass a read/connect timeout through to requests when making requests to a redfish service. This means that an ill-timed failure could cause python processes calling sushy to freeze indefinitely.
4.5.0¶
Bug Fixes¶
Add TransferMethod for any general error that mentions it.
Add TransferProtocolType for any general error that mentions it
In some cases registries might not be available because the our check for the registry language did not account for a possible country suffix. The logic was improved to take it into account.
An issue was encountered on some HPE iLO supported machines where the Baseboard Management Controller would respond with a HTTP 400 error and an error message indicating the requested operation was invalid for the then system state. For example, attempting to change the power state via the BMC shortly after previously changing the power state. We now attempt to retry within the permitted number of retries when this error is encountered.
4.4.2¶
Bug Fixes¶
Fixes exceeding retries. Before this fix running sushy for longer it no longer retried for temporary failures when it should.
Fixes ‘Unsupported parameter name @Redfish.OperationApplyTime’ error on iDRAC firmware version 6.00.02.00 or newer when deleting volumes.
Workaround for https://github.com/psf/requests/issues/3829 If the env
REQUESTS_CA_BUNDLEis set therequests.Session()ignores the verify parameter. Therefore the verify parameter is moved directly into the function call of requests.
4.4.1¶
Bug Fixes¶
Adds an extra check for cases where the BMC provides a SettingsObject URI through @Redfish.Settings but this URI does not allow setting boot related attributes. Prior to sending a PATCH request to SettingsURI, a GET request is issued to verify if it contains the attributes to be updated. In case these attributes are missing, the request is made against System URI instead. Issues such as the one addressed with this change usually manifest themselves with a Redfish response containing an error message similar to the following:
MessageId: Base.1.8.PropertyNotWritable, Message: The property BootSourceOverrideEnabled is a read only property and cannot be assigned a value.
Add retries on iDRAC error with code SYS518 and message “iDRAC is currently unable to display any information because data sources are unavailable.” for all request types in addition to existing GET methods. This helps to fix a known intermittent issue when deleting set of volumes one after another and iDRAC is reloading after deleting each volume.
Correctly handles error code
Base.1.5.PropertyMissingwhen dealing with hardware that requiresTransferProtocolTypefor virtual media operations.
4.4.0¶
New Features¶
Adds two new configuration options:
server_side_retriesallows to set a custom value for the number of times we should retry a GET request in case of a server error, defaults to 10;server_side_retries_delayallows to customize the time in seconds between the request retries, defaults to 3.
Bug Fixes¶
To avoid timeouts with recent versions of firmwares we need to increase the number of server side retries. For example, in idrac firmware series 5.x the time gap between operations is almost 20 seconds instead of the 10 seconds in the 4.x series.
Alters eTag handling in PATCH requests: First, the original eTag is used. In case of a failure, if the eTag provided was weak, it is converted to a strong format by removing the weak prefix. If this approach is not applicable or fails, the final attempt is made omitting the eTag entirely. By taking this approach, no workarounds are applied if BMC is handling eTags as expected and in case of failures, known workarounds are attempted, improving overall resiliency.
4.3.0¶
New Features¶
Adds
controllersproperty ofStorageclass that was introduced in Redfish v1.9 to replacestorage_controllersdeprecated in Redfish v1.13.
Bug Fixes¶
Fixes potential cases where exceptions from the underlying
requestslibrary may be raised up throughsushy, resulting in client applications possibly not understanding that an error has occurred. The sushyConnectionErrorexception is now returned upon any exception falling underRequestExceptionfrom therequestslibrary.
4.2.2¶
Bug Fixes¶
Fixes unreliable behavior with ETag interactions with some BMCs as opportunistic use of compressed responses may cause the BMC to change an ETag response to “Weak”, which is to be expected as an ETag represents an absolute byte-by-byte response consistency, and compression cannot reliably honor that contract. Introduction of a client perceiving a “Weak” ETag may not be expected by the server, and the server may reject responses because the ETag is not a “Strong” ETag when we respond or interact with a resource.
As a result, requests no longer offer oppurtunistic compression of responses as an acceptable possibility, which overall has minimal impact, espescially when compared to the value of consistent BMC behavior and interaction.
4.2.1¶
Bug Fixes¶
Fixes an issue in the sushy connector object handling where a Sushy client utilizing
basicauthentication would not raise an AccessError exception once the credentials stopped working. We now explicitly check to see ifbasicauthentication is in use, and raise the exception if an AccessError is encountered.
4.2.0¶
Bug Fixes¶
Fixes issues with the refresh of
Sessionbased authentication where a previous refresh attempt failing could result in a fallback toBasicauthentication and would silently fail. The client library now attempts to re-authenticate.
Fixes silent failures when a refresh of an authentication
Sessionfails and was unable to be re-established due to anAccessError. Should this occur, now theAccessErrorexception is explicitly raised as opposed to attempting to fall back toBasicauthentication.
Fixes issues where the
SessionandBasicauth interface would fallback toBasicauthentication should aConnectionErrorexception occur while attempting to perform an authentication action.ConnectionErrorexceptions are signs of networking transport issues, and should be investigated. AConnectionErrorexception is now raised.
Prevents the combined
SessionandBasicauthentication support from falling back toBasicauthentication onceSessionbased authentication has been established. This should be considered a potential security issue or an environmental change requiring potential client re-initialization. This is exposed as anAccessErrorexception. Continued operations against the Sushy library will attempt to reauthenticate, if possible.
4.1.1¶
Bug Fixes¶
Resolved virtualmedia attach failures caused by the lack of TransferProtocolType parameter in the request payload which is required by certain BMCs (e.g. on Nokia servers). This is done by adding capability to retry virtualmedia InsertMedia with the updated payload in such cases.
Fixes incompatibility with BMCs that require use of a specific SettingsObject URI specified in @Redfish.Settings resource in order to set BootSourceOverride or similar attributes. For example, this is required on Nokia servers.
4.1.0¶
New Features¶
Adds support for creating and deleting virtual media TLS certificates.
Bug Fixes¶
Makes the unstripped version of an Etag available in addition to the stripped one in order to support vendor implementations which require one or the other.
If available, uses headers with an Etag to set the boot options.
The large
MessageRegistryobjects are no longer logged.
4.0.0¶
Prelude¶
Sushy now exposes Python enums instead of simple string constants. Please check the upgrade notes before updating to this version.
New Features¶
Adds the
Revisionproperty to theDriveresource.
Adds support for the NetworkAdapter resource to the library.
Adds support for the NetworkDeviceFunction and NetworkPort resource to the library.
Adds basic support for
CertificateService.
Allows reading and changing the virtual media fields
TransferMethodandVerifyCertificate.
Allows reading the virtual media field
UserName.
Upgrade Notes¶
Python enumerations are now used instead of strings for all Sushy constants. The old names are kept but now point to enumerated values, so e.g.
sushy.POWER_STATE_ONis an alias forsushy.PowerState.ON. Consumers of the library may see breakages in two cases:Relying on literal values of the old constants. Use constants instead.
Relying on the fact that Sushy constants are strings (e.g. storing them in a database). You can either use the
valueattribute to get the underlying string or create your own mapping.
Deprecation Notes¶
The old constant names (not based on enumerations) are now deprecated. For example, use
sushy.PowerState.ONinstead ofsushy.POWER_STATE_ON.
resources.task_monitor.TaskMonitorandresources.taskservice.taskmonitor.TaskMonitorthat were deprecated in Wallaby are now removed. Usetaskmonitor.TaskMonitorinstead.
Methods
create_volume,delete_volume,initialize_volumein volume module that were deprecated in Wallaby are now removed. Usecreate,deleteandinitializeinstead.
Bug Fixes¶
Changing boot device string for virtual media from “Cd” to “UsbCd” on SuperMicro machines to match their specific naming convention.
3.12.0¶
New Features¶
The
VirtualMedia.insert_mediacall now supports credentials for theimageURI.
Bug Fixes¶
Changes the default value of “WriteProtected” parameter in in VirtualMedia::insert_media() from False to True. This is to match Redfish schema 2021.1 and VirtualMedia.v1_3_0: https://redfish.dmtf.org/schemas/v1/VirtualMedia.v1_3_0.json
3.11.0¶
New Features¶
Adds
rootproperty to Sushy resources to link to main Sushy object. Empty for Sushy root itself.
Upgrade Notes¶
“Inserted” and “WriteProtected” optional attributes are no longer present in the InsertMedia API call payload when default values {“Inserted”: True, “WriteProtected”: True} are specified by the consumer (e.g. Ironic) and PATCH method of configuring virtual media is not used. Behaviour is unchanged if PATCH method is used.
Bug Fixes¶
Removing “Inserted” and “WriteProtected” parameters from the Redfish VirtualMedia::insert_media() API call payload when default values {“Inserted”: True, “WriteProtected”: True} are set and PATCH method is not used. Those parameters are optional as per Redfish schema 2021.1. Some BMCs (e.g. SuperMicro X11/X12 platforms) treat these fields as read-only and setting them causes vMedia insert failures. These attributes should default to True on the BMC side. Some BMCs using PATCH method of configuring virtual media (e.g. Lenovo SD530) still require “Inserted” attribute, so only changing this for non-PATCH methods of configuring virtual media such as InsertMedia action.
Fixes OEM resource attribute parsing for OEM resources with required fields. Before the fix an error such as “The attribute <attribute name> is missing from the resource <resource path>” occurred.
3.10.0¶
New Features¶
Adds
Drive.volumesproperty for list of volumes that drive is part of.
Bug Fixes¶
Removes the requirement from Context to be present when requesting a subscription, some BMCs do not report Context when the subscription is created with empty string and would cause MissingAttributeError.
Fixes
Processor.sub_processorsfor “‘Processor’ object has no attribute ‘conn’” error.
3.9.0¶
New Features¶
Adds support for the Redfish EventService resource. EventService is responsible for managing event subscriptions and generates the events sent to subscribers.
3.8.0¶
New Features¶
Add support for caching Redfish Attribute Registries. In particular, cache the BIOS Attribute Registry and provide a function to return it if it matches the AttributeRegistry field in System BIOS.
Bug Fixes¶
Adds a fallback for inserting and ejecting virtual media using the PATCH HTTP request instead of the explicit action URIs. The fallback is required for Lenovo ThinkSystem machines (i.e. SD530, ..) that only implement the PATCH method.
3.7.0¶
New Features¶
Adds new method
get_task_monitorto retrieve TaskMonitor instance by task monitor URI.
Adds support for fetching and resetting individual UEFI secure boot databases.
Deprecation Notes¶
Existing two
TaskMonitor-s are deprecated and replaced with onetaskmonitor.TaskMonitor.For
resources.task_monitor.TaskMonitorusers changes include:in_progressis replaced with methodcheck_is_processinglocation_headeris replaced with methodtask_monitor_urithere is no replacement for
set_retry_after,taskmonitor.TaskMonitorsets this internally from Retry-After header
For
resources.taskservice.taskmonitor.TaskMonitorusers changes include:check_is_processing,sleep_forand staticget_task_monitoradded.in
__init__parameterfield_datais deprecated, useresponsein
__init__parametertask_monitoris renamed totask_monitor_uritask_monitoris deprecated, usetask_monitor_uriretry_afteris deprecated, usesleep_for
Methods
create_volume,delete_volume,initialize_volumein volume module are deprecated and replaced with ones namedcreate,deleteandinitialize. New methods for asynchronous operations returntaskmonitor.TaskMonitorinstead of deprecatedresources.task_monitor.TaskMonitor.Method
resources.updateservice.UpdateService.get_task_monitoris deprecated, useSushy.get_task_monitorinstead.
Bug Fixes¶
Automatically retries internal server errors from GET requests.
3.6.1¶
Bug Fixes¶
Fixes
AttributeError: 'str' object has no attribute 'get'during error handling. This occurs when BMC does not return a list of messages inside@Message.ExtendedInfo, but a single item. This has been observed with iDRAC.
Fixes issues in the
volumemodule where the first parameter passed to theTaskMonitorconstructor was incorrect. The parameter passed was the resource object (self), but it should have been the connector object (self._conn). This affected thecreate_volume()anddelete_volume()methods.
3.6.0¶
New Features¶
Adds initial support for the TaskService resource to the library. TaskService is responsible for managing tasks.
Update the
create_volumemethod in theVolumeCollectionclass and thedelete_volumeandinitialize_volumemethods in theVolumeclass to take optionalapply_timeandtimeoutkeyword parameters. This allows the caller of those volume methods to specify a preferredOperationApplyTimeannotation and a maximum timeout for synchronous operations. For asynchronous operations, those three methods will now return aTaskMonitorinstance that the caller can use to monitor the state of the task.
Adding a new attribute task_uri to monitor redfish firmware update since some vendors(ilo) does not provide appropriate response with task_monitor uri.
Adds support for UEFI secure boot: reading the current status, enabling or disabling secure boot, resetting keys.
Deprecation Notes¶
The
supported_valuesproperty in theOperationApplyTimeSupportFieldclass is deprecated. Use themapped_supported_valuesproperty instead. Themapped_supported_valuesproperty uses theMappedListFieldtype to map the Redfish schema-defined enumeration values to constants exposed by the Sushy package.
Bug Fixes¶
Fixes an issue in the
Connectorclass where an exception is not raised when an asynchronous operations fails.
3.5.0¶
Bug Fixes¶
Fixes an issue in performing action
#Bios.ResetBioswhen no body in POST request provided and BMC responds with HTTP 400 Bad request, for example, Dell R630 having iDRAC 2.75.75.75. See story 2008198 for details.
The
Actionsfield in theVolumeresource was incorrectly specified as being required. This fix makes the field optional.
Makes message parsing more resilient by handling the case where the message ID only contains a message key and no registry name. In this case, fall back to the
Messagesmessage registry file and then to theBaseMessagesmessage registry file. If the message ID cannot be found, then set the message tounknown. When parsing messages, if not enough arguments were supplied, then fill in the remaining arguments withunknown.
Reduce the logging from sushy by logging only attributes and values set in the redfish response, not the entire json.
3.4.0¶
New Features¶
Adds support for
biosresource to allow specifying BIOS attribute update time and maintenance window when updating BIOS attributes usingset_attributeorset_attributes.The update is backward compatible and when new parameters not passed, they default to
None.Also adds
maintenance_windowforbiosresource to expose default maintenance window set by the system if any.
Added the ability to monitor the progress of a firmware update by changing the
simple_updateoperation to return a task monitor object.
Bug Fixes¶
Instead of trying to GET /redfish/v1/SessionService, which is usually reachable via authentication, fail, and then guess /redfish/v1/SessionService/Sessions as Sessions URL, we try first to use directly the Sessions URL provided by the root service, if available.
3.3.1¶
Security Issues¶
No longer logs passwords and auth tokens in DEBUG mode when using SessionService for authentication.
Bug Fixes¶
Fixes bugs in the
UpdateService.software_inventoryandUpdateService.firmware_inventoryproperties making them operational.
3.3.0¶
New Features¶
Add RAIDType property to the Volume resource and SupportedRAIDTypes property to the Storage resource.
Make POST and DELETE operations in Volume and VolumeCollection blocking.
Bug Fixes¶
Fixes Sushy OEM extension loading when using multiple servers that caused loaded extensions to point to server for which the extension was loaded first.
3.2.0¶
New Features¶
Adds optional
response_callbackparameter toConnectorclass that can be used by the application to receive vanilla HTTP messages in the course of running Redfish call. The intention is to facilitate Redfish exchange debugging.
Bug Fixes¶
Adds a new
set_system_boot_optionsmethod to theSystemobject superseding theset_system_boot_sourcemethod. The new method has all boot parameters optional to allow for more atomicity when PATCH’ing RedfishBootobject. The new method will only include those items in the PATCH document, that are explicitly passed by the user. This change might improve interoperability with BMCs that do not handle certain attributes of theBootobject.
Postpones (potentially very large) Redfish message registries download and processing up to the first access by the client. The goal is to reduce the amount of unnecessary traffic and CPU cycles.
3.1.0¶
New Features¶
The
get_system,get_managerandget_chassismethods modified not to require theidentityparameter referring to a particular resource instance. Ifidentityis omitted, sushy will default to the only available resource for as long as it’s single and therefore deterministic. The intent is to simplify user API by not requiring the consumer to discover available resources prior to requesting one.
Add support for a Task Monitor resource to be able to monitor the state of asynchronous operations.
Bug Fixes¶
Fixes bug in
SimpleStorageCollection.disks_sizes_byteswhich assumed the type of a disk’sCapacityBytesproperty isinteger. According to the Distributed Management Task Force (DMTF) Redfish standard schema [1], it can benull, which is converted toNonein Python. For more information, see story 2006918.[1] https://redfish.dmtf.org/schemas/SimpleStorage.v1_2_3.json
Handles incomplete messages in MessageRegistry that are not having fields like ‘Description’ and ‘Severity’. See story 2007216 for more information.
3.0.0¶
Upgrade Notes¶
Python 2.7 support has been dropped. Last release of sushy to support Python 2.7 is OpenStack Train. The minimum version of Python now supported by sushy is Python 3.6.
2.0.0¶
New Features¶
Exposes the
endpointsub-resource from thefabricresource.endpointrepresents the properties of an entity that sends or receives protocol defined messages over a transport.
Adds a new field called
MappedListFieldwhich supports a list of mapped instances.
Adds the ability to conditionally match sushy fields against received JSON object. The conditional matching is performed by a user-supplied callable which gets the key to consider (along with the value and potentially other details) and should indicate the the caller if the match occurred. The motivation behind this change is to accommodate malformed Redfish resource properties as observed in the OEM wilderness.
Update the Storage, Volume, and Drive models to support RAID configuration management.
Exposes
UpdateServiceconstants tosushynamespace.
Upgrade Notes¶
OEM resource class hierarchy has been redesigned to allow for non-terminal sub-resources (e.g. Links) to be handled within OEM resource model. As a consequence, backward compatibility with previously existing OEM extension framework (anything based on
OEMExtensionResourceBaseclass) is not preserved. User OEM code migration would involve switching fromOEMExtensionResourceBasetoOEMResourceBase(note__init__call signature change) and replacingOEMField-based classes with their generic sushyFieldcounterparts.
Bug Fixes¶
Improve interoperability by including the recommended OData-Version header in outgoing Redfish requests.
Disable HTTP connection pooling by asking HTTP server to close our connection right upon use. The rationale is that some BMC observed in the wild seem to close persistent connections abruptly upon eventual reuse failing completely unrelated operation. So in
sushywe just try not to maintain persistent connections with BMC at all.
Makes
Manager->Actionsfield optional as Redfish Manager schema defines it. Otherwise sushy fails hard at parsing response from a Redfish agent that does not includeActionsfield in its document tree.
Fixes bug in
UpdateService.simple_updatemethod making it operational.
The
transfer_protocolparameter of theUpdateService.simple_updatemethod should be given one of the newly exposed constants rather than a string literal. This is a breaking change.
Fixes an issue in performing action
#Bios.ResetBioswhen BMC expects the POST request with empty body instead of no body. See story 2006246 for details.
1.9.0¶
New Features¶
Biosresource introducesupdate_statusproperty that exposes the status and any errors of last BIOS attribute update.
Adds the
IndicatorLEDproperty to theDriveresource. The state of the LED can be read and can be changed via the.set_indicator_led()method of theDrivesushy class.
Adds support for the Fabric resource to the library.
Adds the Power resource to the Library.
Adds mappings and constants for possible values of System Type in System resource. This represents the type of the computer system.
Adds the Thermal resource to the Library.
Adds
CapacityBites,Manufacturer,Model,PartNumber,SerialNumberandStatusproperties to theDriveresource.
The
IndicatorLEDproperty ofSystemandChassisresources made settable with the introduction of the.set_indicator_led()method to the respective sushy classes.
Update sushy models to support the Redfish SettingsApplyTime and OperationApplyTimeSupport annotations.
Deprecation Notes¶
Deprecates system-specific indicator LEDs as redundant. The
SYSTEM_INDICATOR_LED_LIT,SYSTEM_INDICATOR_LED_BLINKING,SYSTEM_INDICATOR_LED_OFFandSYSTEM_INDICATOR_LED_UNKNOWNconstants should not be used. Generic indicator LED constants should be used instead. Those areINDICATOR_LED_LIT,INDICATOR_LED_BLINKING,INDICATOR_LED_OFFandINDICATOR_LED_UNKNOWNrespectively.
The
operation_apply_time_supportandmaintenance_windowproperties in theSettingsFieldclass are deprecated. TheSettingsFieldclass represents the@Redfish.Settingsannotation and those properties cannot appear within this annotation. Instead use theapply_time_settingsproperty in the target resource (e.g.Biosresource).
Other Notes¶
Includes Redfish standard message registry files that are licensed under Creative Commons Attribution 4.0 License: https://creativecommons.org/licenses/by/4.0/
1.8.0¶
New Features¶
Establishes linkage between Chassis and ComputerSystem/Managers resources as references at sushy data abstraction level. That makes it possible to look up Chassis by Manager/ComputerSystem or any other way around.
Adds support for the Chassis resource to the library.
Adds foundation for supporting resource extensibility proposed as OEM extensibility in Redfish specification [1] to the library.
Provides an attribute ‘oem_vendors’ in Resource classes to discover the available OEM extensions.
Provides a method ‘get_oem_extension()’ in Resource classes to get the vendor defined resource OEM extension object, if discovered.
[1] http://redfish.dmtf.org/schemas/DSP0266_1.1.html#resource-extensibility
Establishes ComputerSystem->Managers and Manager->ComputerSystems references at sushy data abstraction level what make it possible to look up Manager(s) responsible for a ComputerSystem and vice versa.
Adds support for the CompositionService resource to the library.
The CompositionService is the top level resource for all things related to Composability. If a Redfish service supports Composability, the Service Root resource will contain the CompositionService property.
Adds support for the UpdateService resource to the library. UpdateService is responsible for managing firmware updates.
Unifies sushy models by Redfish schema bundle.
These changes introduce and update currently implemented sushy models to comply with the most recent schema bundle[1]. [1]https://www.dmtf.org/documents/redfish-spmf/redfish-schema-bundle-20181
Bug Fixes¶
Some vendors like HPE iLO has this kind of implementation that for eject virtual media need to pass empty dictionary otherwise throws Unsupported media type error.
1.7.0¶
New Features¶
Exposes the
simple_storageandstorageproperties from system resource in sushy.simple_storageproperty indicates a collection of storage controllers and their directly-attached devices associated with the system.storageproperty refers to a collection of storage subsystem associated with system. Resources such as drives and volumes can be accessed from that subsystem.
Adds the Storage resource to the library. It also provides the max size available (in bytes) of drives and volumes that can be accessed from storage.
Adds support for the virtual media resource to the library.
Adds functionality to pass different requests library session arguments to sushy connector.
Adds Product and ProductFeaturesSupported properties support to the Redfish Root Service
Bug Fixes¶
Tries to terminate authenticated Redfish session at BMC Session Service on the event of
Sushyobject deallocation. This should reduce the chance of authenticated sessions pool exhaustion at some BMCs.
1.6.0¶
New Features¶
Adds support for the BIOS resource to the library.
Adds the “SimpleStorage” to the library. It also provides the max size available (in bytes) among all its directly attached devices.
1.5.0¶
New Features¶
Adds mappings and constants for possible values of the Indicator LED value in the System class.
Bug Fixes¶
Fixes malformed value of the
BootSourceOverrideModeelement which goes against the Redfish schema and causes some of the boot mode calls to fail.
1.4.0¶
New Features¶
Adds the processor status and id fields to the
Processorclass.
Adds the system status field to show the system status.
Critical Issues¶
Fixes authentication failure when SessionService attribute is not present in the root resource.
1.3.0¶
New Features¶
Adds the ability to specify user-defined connector object on creation of a root Sushy instance.
New
forceargument to therefreshmethod on resources can be set toFalseto prevent refreshing of resources that are not stale. Resources can be marked as stale by calling a newinvalidatemethod.
Other Notes¶
Changes the values for the constants
HEALTH_STATE_ENABLED,HEALTH_STATE_DISABLED,HEALTH_OK,HEALTH_WARNINGandHEALTH_CRITICAL. These could be correctly used with their mapped values in mappings.py.
1.2.0¶
New Features¶
Adds the “EthernetInterfaces” to the library. It also returns the list of connected MACs.