Skip to main content

What's new in version 2.2

Lenovo XClarity Orchestrator management software version 2.2 supports new hardware, software enhancements, and fixes.

Additional hardware support

XClarity Orchestrator supports ThinkSystem V4 devices that are managed only through Lenovo XClarity Administrator. XClarity Orchestrator does not support ThinkSystem V4 devices that are managed through Lenovo XClarity Management Hub 2.0.

XClarity Orchestrator supports devices that can be managed by XClarity Management Hub 2.0, XClarity Administrator, and XClarity Management Hub. You can find a complete list of supported devices and options (such as I/O, DIMM, and storage adapters), minimum required firmware levels, and limitations considerations from the Lenovo XClarity Support website by clicking the Compatibility tab and then clicking the link for the appropriate device types.

Fixes

Refer to the change history file (*.chg) that is provided in the update package for information about fixes.

Software enhancements

This version supports the following enhancements to the management software.
FunctionDescription
Resource managersOnly XClarity Management Hub 2.0 v1.0.2 – v1.3 is supported. Later versions are not supported.
Provisioning resources

You can deploy these operation systems: Red Hat® Enterprise Linux (RHEL) Server 9.x and VMware vSphere® Hypervisor (ESXi) 8.0.x and 9.0.x (see Supported operating systems).

You can configure ThinkEdge SE350 and SE450 servers using configuration patterns (see Provisioning server configurations).

Service and support

You can delete selected service tickets that are in the canceled, closed, error, rejected, or resolved state (see Viewing service tickets and status).

Terraform integrationFor information about changes to the Terraform toolkit, see Summary of changes in the XClarity Orchestrator provider for Terraform.
PowerShell toolkitFor information about new and updated Summary of changes in the PowerShell toolkit.
REST APIFor information about new and updated Summary of changes in the REST API.