|
Direct install or upgrade to 2.0.3
|
|
|
You can now directly install PowerVC 2.0.3, unlike earlier releases where you had to first install the major version and then update to the available fix pack version of PowerVC. Similarly, if you have any previous version of PowerVC 2.0.x installed, take a backup, copy the backup file to a custom location, and then uninstall the existing version. Reboot the system and install or upgrade to PowerVC 2.0.3.
|
|
|
Scale up to 5 node cluster
|
|
|
By using PowerVC Operations Manager, you can create a single node or multinode (3 nodes) PowerVC cluster and then extend the cluster up to 5 nodes.
|
|
|
Backup and restore on multinode
|
|
|
With PowerVC 2.0.3, you can perform restore directly on multinode (three nodes) from PowerVC version 2.0.1 to 2.0.2.1 and then add two nodes for a five node cluster if needed.
|
|
|
Compute plane node support on SLES
|
|
|
Compute plane nodes share the compute services load and allow managing more HMC managed hosts. Starting PowerVC version 2.0.3, this feature is also supported on SLES (ppc64le).
|
|
|
Rolling upgrade to PowerVC 2.0.3
|
|
|
PowerVC rolling upgrade can be performed on PowerVC 2.0.2 or 2.0.2.1 installed nodes. Rolling upgrade targets very minimal downtime where you can continue to use the cluster with limited features while an upgrade is happening at the backend.
|
|
|
Scheduled tasks for self_service users
|
|
|
If you are assigned to self_service user role, you can schedule deploy of virtual machines starting PowerVC 2.0.3.
|
|
|
UI performance enhancement
|
|
|
Removed periodic syncing of resources from MariaDB to MongoDB. The onClick background syncing is adopted to maintain data consistency for out-of-band operations. Introduced Node.js clustering to improve the fast loading of UI pages.
|
|
|
Select alternate fabrics for SCG (RFE ID: 149761)
|
|
|
PowerVC will now select alternate fabrics when an SCG with exactly-one configuration and multiple fabrics registered is used.
|
|
|
Image list page design enhancements
|
|
|
Enhanced image list page design, adhering to the IBM Carbon guidelines.
|
|
|
Brocade fabric registration (RFE ID: 109582)
|
|
|
SSH key support is enabled for Brocade fabric registration.
|
|
|
Support for SVC child pools (RFE ID: 152947)
|
|
|
SVC child pools are now supported during registration and template creation.
|
|
|
Support for registration when a node is down
|
|
|
Registration or deregistration of a host, storage, or a fabric is supported even when a node goes down. After the node is up, you can run powervc-opsmgr resync_node -s <source_host> -d <dest_host> to sync the conf files on the source host and destination host.
|
|
|
Update compute plane node IP address
|
|
|
When the IP address or hostname of the management system changes, run powervc-opsmgr config changecomputeplaneip command to automatically update these values in PowerVC.
|
|
|
Update node IP address
|
|
|
When the IP address or hostname of the management system changes, run powervc-opsmgr config changenodeip command to automatically update these values in PowerVC.
|
|
|
Update VIP address
|
|
|
Starting PowerVC 2.0.3, you can update virtual IP (VIP) settings by using PowerVC operations manager (OpsMgr).
|
|
|
Changes in guest OS support |
|
|
Support for RHEL 8.6 and RHEL 9.0 guest OS has been added. For details, see Guest operating system support.
|