What's new in version 2.0.2

IBM® Power® Virtualization Center version 2.0.2 comes with many new features and enhancements. We are more than delighted to listen to our client requirements and implement the same along with our benchmark innovation strategies that take PowerVC to the next level every release.

PowerVC high availability and scale architecture

Earlier versions of PowerVC followed the All-in-One (AIO) deployment model that involved installing packages and setting up services corresponding to stateless (OpenStack based services like nova, cinder, etc.) and stateful services (MariaDB, RabbitMQetc) on a single system; thus, not following the distributed approach that OpenStack supports. While All-in-one deployment model keeps PowerVC deployment simple and highly manageable, the model denies PowerVC the scale and high availability that it might achieve with a multinode model. For details, see PowerVC high availability and scale architecture.

PowerVC support for P10

PowerVC version 2.0.2 supports managing a Power E1080 host via HMC or NovaLink.

Functional enhancements

PowerVC 2.0.2.1 updates

Listed below are the key features implemented in the 2.0.2.1 release.

Direct install or upgrade to 2.0.2.1
You can now directly install PowerVC 2.0.2.1 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.2.1.
Backup and restore on multinode
With PowerVC 2.0.2.1, you can perform restore directly on multinode (three nodes) from PowerVC version 2.0.1 to 2.0.2.1. For details, see Upgrading to PowerVC 2.0.2 or 2.0.2.1.
HMC host scaling with additional Compute plane node
Starting PowerVC version 2.0.2.1, Compute plane nodes are introduced to share the compute services load and allow managing more HMC managed hosts. For details, see Compute plane node and HMC host scaling.
Multinode on HMC
HMC managed hosts can be added to both single node setup as well as three node setup of PowerVC cluster. This ensures the Nova compute process for the host is configured in an Active-passive mode and monitored by Pacemaker.
Infoblox integration
You can manage the DNS records in Infoblox through PowerVC GUI. For details, see Automatically update DNS records.
Multinode support on SLES ppc64le
Installation is supported on SLES ppc64le for both single node and multinode environments.
Scheduled tasks

If you are assigned to self-service user role, you can schedule virtual machine operations such as start, stop, and restart of VM(s).

Select network order on GUI (RFE ID: 151694)

You can select the network order while deploying a VM on PowerVC GUI.

Compute plane node management API
The Compute plane node APIs allows you to register, view details, update, or deregister a Compute plane node from PowerVC. For details, see Compute plane node.
Scheduled tasks API
The scheduled tasks APIs can be executed by using curl commands. These APIs can be used for scheduling start, stop, restart, or deploy VMs. You can also choose to fetch list of tasks that are scheduled by users who are assigned to different roles. For details, see Scheduled tasks.

PowerVC version 2.0.2 features

PowerVC multinode (RFE ID: 111561)
  • PowerVC installation through operations manager

    The PowerVC operations manager (OpsMgr) is a collection of utilities and services that are designed to facilitate end-user operation of PowerVC clusters like install, upgrade, backup, and restore. Starting 2.0.2 release, you must install and configure PowerVC operations manager before installing PowerVC. For details, see Initiate installation through PowerVC operations manager.

  • PowerVC cluster management

    With one or more nodes of PowerVC now being deployed to work as a cluster, maintenance operations are handled through the PowerVC operations manager powervc-opsmgr CLI. This command provides you options to install, uninstall, add or replace nodes, and upgrade.

  • HMC

    HMC managed nodes can be used in a three-node PowerVC cluster when setting the hmc_multinode configuration in powervc-config. This ensures the Nova compute process for the host is configured in an Active-passive mode and monitored by Pacemaker. By default, the HMC managed hosts only work on a single node setup of PowerVC version 2.0.2.

  • NovaLink

    NovaLink managed hosts can be added to both one-node PowerVC cluster as well as the three-node PowerVC cluster. The Nova and Neutron agents on NovaLink communicate with the PowerVC by using a virtual IP. This means even if one of the PowerVC nodes is down, the requests will be routed to the appropriate nodes.

Scheduled tasks (RFE ID: 131441)
You can view details of tasks that are scheduled on a virtual machine in the Dashboard > Tasks > Scheduled tasks of the GUI.

If you are assigned to any of these roles - admin, admin_asst, or a vm_manager, you can schedule virtual machine operations such as start, stop, restart and deploy of VM(s). If you are assigned to a deployer role, you can schedule deploy of VM(s).

SR-IOV updates (RFE IDs: 144847, 143130, 148411, 130232)
  • Support for SR-IOV network in deploy template

    Starting PowerVC version 2.0.2, you can create deploy templates with SR-IOV networks. You can deploy virtual machines by using these deploy templates.

  • VIOS selection based on SCG for SR-IOV vNICs

    You can configure a new property in the default section of the nova conf file enabling VIOS selection based on instance SCG to create vNIC server during SR-IOV deployments. For details, see Commands.

  • Selection of two physical network names for SR-IOV vNIC redundancy

    Starting PowerVC version 2.0.2, you have the option to choose Redundant physical network name. When you deploy a virtual machine with vNIC redundancy option, the redundant adapter is used from the redundant physical network name selected. For details, see Redundancy support section in SR-IOV backed networks.

  • Onboarding of VMs with direct attached logical ports

    You can connect logical ports directly to a virtual machine and onboard them to PowerVC. However, mobility operations such as active and inactive migration, remote restart, and automatic remote restart are restricted on the virtual machine.

Storage enhancements (RFE IDs: 113249, 140505, 120025, 135375)
  • SVC HyperSwap®

    HyperSwap is a high availability feature for IBM Storwize® that provides dual-site, active-active access to a volume. PowerVC version 2.0.2 provides the capability to register and manage HyperSwap volumes. One of the main objectives of this support is to leverage Storwize dual site cluster management capability to build high available workloads. For details, see HyperSwap feature on IBM Storwize.

  • Additional storage properties

    Storage details page is updated to have additional properties to show total allocated capacity, overprovisioning and warning threshold.

  • Support for Pure Storage

    Clone virtual machine and clone volumes operations are now supported for Pure Storage.

  • Support for Hitachi
    • Retype for available volume are supported as storage assisted migration.
    • Snapshot and restore is supported for Hitachi GAD Volumes.
  • Volume set template CLI set-template

    Allows you to update a template if the volume already has template assigned using force option.

  • Storwize Global Mirror Change Volumes (GMCV) enablement

    Now, you can create a storage template for GMCV using API or CLI, which enables you to manage IBM Storwize GMCV volume replication using PowerVC. For details, see Global Mirror feature on IBM Storwize.

Updates on export and import images (RFE ID: 146507)
  • Standalone remote backup node for export or import images

    Starting PowerVC version 2.0.2, you can register a standalone backup node that has the required Fibre Channel connectivity and which is responsible to perform import or export operation. To achieve more concurrency, you can choose to have multiple backup nodes. For details, see Registering a backup node.

  • IBM Cloud Object Storage integration

    Starting release 2.0.2, you can directly upload and download images packaged as an OVA tar to and from an IBM Cloud Object Storage (COS) using PowerVC user interface. For details, see Registering IBM Cloud Object Storage in PowerVC.

  • Backup images OVA tars are created uses pigz for smaller size and fast compression

    The OVA tar for the image is created using pigz level 9 (best) compression for the backup files which ensures a smaller file size and faster compression. By default pigz compression is enabled. If the cinder config option use_fast_compression is set to False, the regular gzip compression is used.

    For details, see Exporting and importing images.
  • powervc-image CLI now allows to override and update os-type metadata during OVA import.
UI enhancements (RFE IDs: 131441, 142636)
  • Feedback option

    The feedback dialog is removed, and you can now provide feedback about PowerVC from help panel manually.

  • Auto-refresh

    Auto-refresh enhancements are updated for Deploy templates, SSH Keypairs, VM tab of Host edit page, Network tab of VM edit page and Volume tab, Storage templates, Volume tab of Storage template edit page, SCG, Consistency groups, Projects, Enterprise policies, Email templates, Users, and Compute templates.

  • Actions menu

    Actions menu is added to the resource edit pages of Storage providers, Boot volumes, Data volumes, and Hosts.

  • Pagination

    Pagination is now enabled for the pages - Projects, Boot volumes, Data volumes, and DRO logs.

  • powervc-config web options

    powervc-config web options for idle timeout and inactivity timeout are implemented for the new UI.

  • Selective login

    You can now login to a particular project from the Projects page.

Changes in hardware and software support

Export and import image API
The image export or import APIs let you export or import images from a backup node registered in PowerVC. You can also choose whether you want to upload an image to the IBM Cloud Object Storage along with export. Similarly, the import image API allows you to import an image to PowerVC from a backup node registered in PowerVC. You can also choose whether you want to download an image from IBM Cloud Object Storage and then import it. For details, see Export or import image.
Backup node registration API
The backup node registration APIs allow you to register a remote or a local backup node in PowerVC. You can also choose to discover existing image OVAs. For details, see Backup node registration.
Registering IBM Cloud Object Storage API
The Cloud Object Storage (COS) registration APIs allows you to register an existing COS bucket in PowerVC which helps you to upload or download image OVAs. For details, see Registering IBM Cloud Object Storage API.
Tag redundant network API
This API allows you to tag the redundant network name for the SR-IOV based network. For details, see Supported OpenStack Networks (Neutron) APIs.
Register and enable HyperSwap storage for IBM Storwize API
HyperSwap storage registration uses existing storage registration API. For details, see Storage controller registration.
Host site assignment API
The API allows you to map the host port WWPNs with the Storwize site information. You can select the hosts and assign the site ID based on the preferred path to perform data I/O transfer. For details, see Storage controller registration.
Role permissions for backup node and IBM Cloud Object Storage features
Add, view, edit, or delete permissions for backup node and Cloud Object Storage might vary based on the user role permissions. For details, see Managing roles.
Changes in guest OS support
Support for SLES 15 SP1, SLES 15 SP2, SLES 15 SP3, RHEL 7.9, RHEL 8.0, RHEL 8.1, RHEL 8.2, and RHEL 8.4 guest OS has been added. For details, see Guest operating system support.