PowerVC 2.3.2：仮想アプライアンス (PVCVA) 版の導入・初期設定の手順確認

Last updated at 2026-02-02Posted at 2026-02-01

はじめに

2025年12月にリリースされた PowerVC 2.3.2 からアプライアンス形式 (OS とソフトウェアが一緒に製品として提供される形態, ユーザーが簡単に起動して管理できる形式でパッケージ化されたプリインストール・ソフトウェア) が導入モジュールとして提供されるようになりました。

PowerVC for Private Cloud の新機能

PowerVC 仮想アプライアンス
新しいデプロイメントモデルである PowerVCPowerVC2.3.2 仮想アプライアンス（ PVCVA ）が導入されます。 PVCVA では、ベース Linux® オペレーティングシステムを含む事前構築済みイメージが仮想アプライアンスとして PowerVC 提供されます。このモデルは、完全にサポートされた制御されたカプセル化された IBM 環境を提供します。

PowerVC virtual appliance

引用画像：Architecture

2.3.2 では以前と同様の製品モジュールのみも提供されていますが、将来のバージョンではアプライアンス版のみの提供を予定しているそうです。

アプライアンスでは、導入が楽になる反面、独自のコマンド体系や、Linux コマンドは制限されたコマンドのみの使用など大きく操作が変わっています。

当記事ではPowerVC 2.3.2 アプライアンス版の導入方法を確認しました。

動画

当記事のご参考動画です。音声動画で理解の一助にお役立てください。

実行環境

IBM Power S824 LPAR (2 CPU, 32GB Memory)
　- 500GB SAN boot volume を接続
PowerVC Virtual Appliance (PVCVA) 2.3.2

requirement より 500GB のディスクを使用します。

モジュール入手

製品ダウンロードサイトで、以下のように、Appliance の iso ファイルをダウンロードします。

環境構築

導入準備

LPAR への iso 割り当てや、導入手順は下記と同様の流れで実施しています。

HMCから仮想端末を起動してブートする手順

Boot virtual machine by using vOPT

HMCにログインし vtmenu コマンドを実行し、対象筐体、対象LPARを選択して仮想端末を起動

SMS (c) Copyright IBM Corp. 2000,2016 All rights reserved.
-------------------------------------------------------------------------------
 Main Menu
 1.   Select Language
 2.   Setup Remote IPL (Initial Program Load)
 3.   I/O Device Information
 4.   Select Console
 5.   Select Boot Options









 -------------------------------------------------------------------------------
 Navigation Keys:5

                                             X = eXit System Management Services
 -------------------------------------------------------------------------------

5. Select Boot Options

 SMS (c) Copyright IBM Corp. 2000,2016 All rights reserved.
-------------------------------------------------------------------------------
 Multiboot
 1.   Select Install/Boot Device
 2.   Configure Boot Device Order
 3.   Multiboot Startup <OFF>
 4.   SAN Zoning Support










 -------------------------------------------------------------------------------
 Navigation keys:
 M = return to Main Menu
 ESC key = return to previous screen         X = eXit System Management Services
 -------------------------------------------------------------------------------
 Type menu item number and press Enter or select Navigation key:1

1. Select Install/Boot Device

 SMS (c) Copyright IBM Corp. 2000,2016 All rights reserved.
-------------------------------------------------------------------------------
Select Device Type
1.   Tape
2.   CD/DVD
3.   Hard Drive
4.   Network
5.   List all Devices









-------------------------------------------------------------------------------
Navigation keys:
M = return to Main Menu
ESC key = return to previous screen         X = eXit System Management Services
-------------------------------------------------------------------------------
Type menu item number and press Enter or select Navigation key:2

2. CD/DVD

 SMS (c) Copyright IBM Corp. 2000,2016 All rights reserved.
-------------------------------------------------------------------------------
Select Media Type
1.   SCSI
2.   SAN
3.   SAS
4.   SATA
5.   USB
6.   NVMe
7.   List All Devices







-------------------------------------------------------------------------------
Navigation keys:
M = return to Main Menu
ESC key = return to previous screen         X = eXit System Management Services
-------------------------------------------------------------------------------

1. SCSI

 SMS (c) Copyright IBM Corp. 2000,2016 All rights reserved.
-------------------------------------------------------------------------------
Select Media Adapter
1.          U8286.42A.xxxxxV-V7-C2-T1   /vdevice/v-scsi@30000002
2.          U8286.42A.xxxxxxV-V7-C3-T1   /vdevice/v-scsi@30000003
3.          U8286.42A.xxxxxxV-V7-C4-T1   /vdevice/v-scsi@30000004
4.   List all devices










-------------------------------------------------------------------------------
Navigation keys:
M = return to Main Menu
ESC key = return to previous screen         X = eXit System Management Services
-------------------------------------------------------------------------------
Type menu item number and press Enter or select Navigation key:3

このLPARは vscsi 接続のため SCSI デバイスが多いのですが、仮想メディアは３番目で接続されていたので 3 を選択します。(環境によって選択肢は異なります)

3. U8286.42A.xxxxxxV-V7-C4-T1 /vdevice/v-scsi@30000004

 SMS (c) Copyright IBM Corp. 2000,2016 All rights reserved.
-------------------------------------------------------------------------------
Select Device
Device  Current  Device
Number  Position  Name
1.        -      SCSI CD-ROM
       ( loc=U8286.42A.848DB5V-V7-C4-T1-L8100000000000000 )










-------------------------------------------------------------------------------
Navigation keys:
M = return to Main Menu
ESC key = return to previous screen         X = eXit System Management Services
-------------------------------------------------------------------------------
Type menu item number and press Enter or select Navigation key:1

1. - SCSI CD-ROM

 SMS (c) Copyright IBM Corp. 2000,2016 All rights reserved.
-------------------------------------------------------------------------------
Select Task

SCSI CD-ROM
   ( loc=U8286.42A.848DB5V-V7-C4-T1-L8100000000000000 )

1.   Information
2.   Normal Mode Boot
3.   Service Mode Boot








-------------------------------------------------------------------------------
Navigation keys:
M = return to Main Menu
ESC key = return to previous screen         X = eXit System Management Services
-------------------------------------------------------------------------------
Type menu item number and press Enter or select Navigation key:2

2. Normal Mode Boot

 SMS (c) Copyright IBM Corp. 2000,2016 All rights reserved.
-------------------------------------------------------------------------------
Are you sure you want to exit System Management Services?
1.   Yes
2.   No












-------------------------------------------------------------------------------
Navigation Keys:

                                            X = eXit System Management Services
-------------------------------------------------------------------------------

1. Yes

IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM                         IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM    STARTING SOFTWARE    IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM       PLEASE WAIT...    IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM                         IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM

ブートしてきて、Welcome to the IBM PowerVC! が出てきました。

lapsed time since release of system processors: 1195917 mins 21 secs
error: ../../grub-core/kern/misc.c:503:unrecognized number.

Welcome to the IBM PowerVC!



      Install PowerVC (PowerVM)



      Use the ^ and v keys to change the selection.
      Press 'e' to edit the selected item, or 'c' for a command prompt.
   The selected entry will be started automatically in 0s.
OF stdout device is: /vdevice/vty@30000000
Preparing to boot Linux version 4.18.0-553.72.1.el8.ibm.1.ppc64le (mockbuild@832c977cdc8748d7be8440329c113adc) (gcc version 8.5.0 20210514 (Red Hat 8.5.0-23) (GCC)) #1 SMP Wed Sep 3 11:05:13 CDT 2025
Detected machine type: 0000000000000101
command line: BOOT_IMAGE=/ppc/ppc64le/img2a rd.dm=1 rd.lvm=1 rd.multipath=1 root=LABEL=PVC-2.3.2.0 rootfallback=/dev/sr0 rd.retry=15 rd.timeout=30 rd.shell rd.luks=0 rd.nomodeset plymouth.enable=0 media=media quiet insmodpost=usb_storage consoleblank=0 net.ifnames=0 biosdevname=0
Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
Calling ibm,client-architecture-support... done
memory layout at init:
  memory_limit : 0000000000000000 (16 MB aligned)
  alloc_bottom : 0000000015030000
  alloc_top    : 0000000020000000
  alloc_top_hi : 0000000020000000
  rmo_top      : 0000000020000000
  ram_top      : 0000000020000000
instantiating rtas at 0x000000001eca0000... done
prom_hold_cpus: skipped
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x0000000015040000 -> 0x00000000150416e1
Device tree struct  0x0000000015050000 -> 0x0000000015060000
Quiescing Open Firmware ...
Booting Linux via __start() @ 0x000000000e550000 ...
[    0.721580] vas: API is supported only with radix page tables
[    0.784226] vas: HCALL(39c) error -2, query_type 0, result buffer 0x628752000
[    0.784454] NX-GZIP is not supported. Returned=-524
[    1.476110] vio vio: uevent: failed to send synthetic uevent: -19
[    1.476267] vio 4000: uevent: failed to send synthetic uevent: -19
[    1.476292] vio 4001: uevent: failed to send synthetic uevent: -19
[    1.476324] vio 4002: uevent: failed to send synthetic uevent: -19
[    1.476352] vio 4004: uevent: failed to send synthetic uevent: -19
[   14.610389] dracut-pre-mount[981]: mount: /media/cdrom: WARNING: device write-protected, mounted read-only.
         Stopping Device-Mapper Multipath Device Controller...
[  OK  ] Stopped Device-Mapper Multipath Device Controller.
         Starting Device-Mapper Multipath Device Controller...
[  OK  ] Started Device-Mapper Multipath Device Controller.

選択肢を確認して導入を続けます。

Next

Installing Base Operating System... とあり、今はOS導入段階であることがわかります。

10分程度経ったのちに下記の画面に遷移しました。

Finish を選択し、ブートシークエンスが続きます。

[  755.713137] dracut-pre-mount[20445]: mount: /sysroot: /dev/mapper/360050763808106d7d8000000000005bc2 already mounted on /sysroot.
[  OK  ] Started dracut pre-mount hook.
         Starting File System Check on /dev/disk/by-label/PVC-2.3.2.0...
[  OK  ] Reached target Initrd Root File System.
         Starting Reload Configuration from the Real Root...
[  OK  ] Started File System Check on /dev/disk/by-label/PVC-2.3.2.0.
         Stopping Device-Mapper Multipath Device Controller...
[  OK  ] Started Reload Configuration from the Real Root.
[  OK  ] Reached target Initrd File Systems.
[  OK  ] Reached target Initrd Default Target.
         Starting dracut mount hook...
[  OK  ] Stopped Device-Mapper Multipath Device Controller.
[  OK  ] Started dracut mount hook.
         Starting dracut pre-pivot and cleanup hook...
[  OK  ] Started dracut pre-pivot and cleanup hook.
         Starting Cleaning Up and Shutting Down Daemons...
[  OK  ] Stopped target Timers.
[  OK  ] Stopped dracut pre-pivot and cleanup hook.
[  OK  ] Stopped target Initrd Default Target.
[  OK  ] Stopped target Basic System.
[  OK  ] Stopped target Paths.
[  OK  ] Stopped target System Initialization.
[  OK  ] Stopped udev Wait for Complete Device Initialization.
[  OK  ] Stopped target Swap.
[  OK  ] Stopped Apply Kernel Variables.
[  OK  ] Stopped target Slices.
[  OK  ] Stopped target Sockets.
[  OK  ] Stopped target Initrd Root Device.
[  OK  ] Stopped target Remote File Systems.
[  OK  ] Stopped target Remote File Systems (Pre).
[  OK  ] Stopped dracut mount hook.
[  OK  ] Stopped dracut pre-mount hook.
[  OK  ] Stopped target Local Encrypted Volumes.
[  OK  ] Stopped Dispatch Password Requests to Console Directory Watch.
[  OK  ] Stopped dracut initqueue hook.
         Stopping Open-iSCSI...
[  OK  ] Stopped udev Coldplug all Devices.
[  OK  ] Stopped dracut pre-trigger hook.
         Stopping udev Kernel Device Manager...
[  OK  ] Stopped Create Volatile Files and Directories.
[  OK  ] Stopped target Local File Systems.
[  OK  ] Stopped target Local File Systems (Pre).
[  OK  ] Stopped Open-iSCSI.
         Stopping iSCSI UserSpace I/O driver...
[  OK  ] Closed Open-iSCSI iscsid Socket.
[  OK  ] Stopped iSCSI UserSpace I/O driver.
[  OK  ] Started Cleaning Up and Shutting Down Daemons.
[  OK  ] Closed Open-iSCSI iscsiuio Socket.
[  OK  ] Stopped udev Kernel Device Manager.
[  OK  ] Stopped dracut pre-udev hook.
[  OK  ] Stopped dracut cmdline hook.
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Stopped Create list of required sta…vice nodes for the current kernel.
[  OK  ] Closed udev Kernel Socket.
[  OK  ] Closed udev Control Socket.
         Starting Cleanup udevd DB...
[  OK  ] Started Cleanup udevd DB.
[  OK  ] Reached target Switch Root.
         Starting Switch Root...
[  758.309318] vio vio: uevent: failed to send synthetic uevent: -19
[  758.310027] vio 4000: uevent: failed to send synthetic uevent: -19
[  758.310042] vio 4001: uevent: failed to send synthetic uevent: -19
[  758.310057] vio 4002: uevent: failed to send synthetic uevent: -19
[  758.310071] vio 4004: uevent: failed to send synthetic uevent: -19
[  766.405605] cloud-init[21085]: Cloud-init v. 23.4-7.el8_10.9 running 'init-local' at Fri, 30 Jan 2026 15:05:10 +0000. Up 766.16 seconds.

~ 省略 ~

[  875.816996] cloud-init[21347]: Cloud-init v. 23.4-7.el8_10.9 running 'modules:final' at Fri, 30 Jan 2026 15:07:00 +0000. Up 875.61 seconds.
[  875.817252] cloud-init[21347]: Cloud-init v. 23.4-7.el8_10.9 finished at Fri, 30 Jan 2026 15:07:00 +0000. Datasource DataSourceNone.  Up 875.80 seconds
[  875.817411] cloud-init[21347]: 2026-01-30 15:07:00,530 - cc_final_message.py[WARNING]: Used fallback datasource
[  OK  ] Started Execute cloud user/final scripts.
[  OK  ] Reached target Cloud-init target.

Red Hat Enterprise Linux 8.10 (Ootpa)
Kernel 4.18.0-553.72.1.el8.ibm.1.ppc64le on an ppc64le

localhost login:

CLI ログイン

ログイン・プロンプトが出てきました。
デフォルト・パスワードはマニュアルに記載があり、abcd1234 を使用します。

Note: The default username is pvcroot and the default password is abcd1234.

localhost login: pvcroot
Password:
pvcroot@localhost:~>

ログインできました。

HMCのようにシェルは制限されており、実行できるコマンドが決まっています。

cli commands

ネットワーク・インターフェースを確認します。
IP アドレスは設定されていません。

pvcroot@localhost:~> ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UNKNOWN group default qlen 1000
    link/ether fa:61:9a:46:b7:20 brd ff:ff:ff:ff:ff:ff
    altname env32

IPアドレス設定

chpvc コマンドという PowerVC 仮想アプライアンス独自のコマンドでネットワークを設定します。

まずは help を確認。

pvcroot@localhost:~> chpvc network add -h
usage: chpvc network add [-h] --interface INTERFACE --ip IP --netmask NETMASK
                         [--gateway GATEWAY]

options:
  -h, --help            show this help message and exit
  --interface INTERFACE
                        Interface to assign IP to
  --ip IP               IP address to assign
  --netmask NETMASK     Netmask (e.g., 255.255.255.0)
  --gateway GATEWAY     Default gateway (optional)

IPアドレスの設定を実行

コマンド： chpvc network add --ip <IPアドレス> --netmask <ネットマスク> --gateway <ゲートウェイ> --interface <ネットワーク・デバイス名>

pvcroot@localhost:~> chpvc network add --ip xxx.xx.xx.xx --netmask 255.255.0.0 --gateway xxx.xx.xx.x --interface eth1

Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/3)

+--------------------------------------------------------------------------------+
   INFO
	Configured Wired connection 1 with xxx.xx.xx.xx/16, gateway=xxx.xx.xx.x
+--------------------------------------------------------------------------------+
|                          *** End of chpvc network ***                          |
+--------------------------------------------------------------------------------+

もしインターフェース設定で下記のエラーが出る場合には、メッセージの通り NetworkManager を再起動します。

+--------------------------------------------------------------------------------+
   ERROR
	Verify if the correct active network interface is configured or Try restarting the NetworkManager service using systemctl restart NetworkManager
+--------------------------------------------------------------------------------+
|                          *** End of chpvc network ***                          |
+--------------------------------------------------------------------------------+

pvcroot@localhost:~> systemctl restart NetworkManager

ホスト名設定

続いて、chpvc コマンドで hostname を設定します。
最初は localhost で設定されていました。

コマンド： chpvc hostname modify <FQDN>

pvcroot@localhost:~> chpvc hostname modify testvm1.test.com

+--------------------------------------------------------------------------------+
   INFO
	Hostname changed to 'testvm1.test.com'.
+--------------------------------------------------------------------------------+
|                         *** End of chpvc hostname ***                          |
+--------------------------------------------------------------------------------+

DNS サーバー設定

PowerVC 構成の際に名前解決が必要であるため、DNSサーバーを設定しています。

クローズド環境のDNS設定は以下ご参考ください。

これまでの構築環境では/etc/hosts で実施していることがほとんどだったのですが、仮想アプライアンスで/etc/hosts を直接編集することができず、DNS 設定を行いました。

コマンド： chpvc network_dns add -ns <DNSサーバーIPアドレス> -ds <ドメイン名>

pvcroot@localhost:~> chpvc network_dns add -ns xxx.xx.xx.xx -ds test.com

+--------------------------------------------------------------------------------+
   INFO
	Added nameserver 'xxx.xx.xx.xx' in /etc/resolv.conf
+--------------------------------------------------------------------------------+
|                        *** End of chpvc network_dns ***                        |
+--------------------------------------------------------------------------------+

+--------------------------------------------------------------------------------+
   INFO
	Added search 'test.com' in /etc/resolv.conf
+--------------------------------------------------------------------------------+
|                        *** End of chpvc network_dns ***                        |
+--------------------------------------------------------------------------------+

DNS 稼働確認

pvcroot@localhost:~> nslookup xxx.xx.xx.bb
bb.xx.xx.xxx.in-addr.arpa	name = testvm1.test.com.

pvcroot@localhost:~> nslookup xxx.xx.xx.cc
cc.xx.xx.xxx.in-addr.arpa	name = testvm2.test.com.

対象 IP アドレスで名前解決ができています。

インベントリ設定

Create inventory and configure the virtual machine

ここからは以前のバージョン同様に、インベントリ作成と導入を実施します。

インベントリ作成では次の内容を入力します。

　・ライセンスの確認
　・導入ノード数
　・Node 1 の IP アドレスまたはホスト名
　・実行ユーザー
　・パスワード
　・Virtual IPアドレス

コマンド： powervc-opsmgr inventory -c <クラスター名>

pvcroot@localhost:~> powervc-opsmgr inventory -c powervc232

LICENSE INFORMATION

The Programs listed below are licensed under the following
License Information terms and conditions in addition to the
Program license terms previously agreed to by Client and
IBM. If Client does not have previously agreed to license
terms in effect for the Program, the International Program
License Agreement (i125-3301-15) applies.

Program Name (Program Number):
IBM PowerVC for Private Cloud 2.3.2 (5765-VC2)

The following standard terms apply to Licensee's use of the
Program.

Press Enter to continue viewing the license agreement, or
enter "1" to accept the agreement, "2" to decline it, "3"
to print it, "4" to read non-IBM terms, or "99" to go back
to the previous screen.
1
License accepted
+--------------------------------------------------------------------------------+
|                               PowerVC Inventory                                |
+--------------------------------------------------------------------------------+
   PowerVC Nodes
	Enter the number of nodes           : 1
+--------------------------------------------------------------------------------+
   INFO:
     Primary/Bootstrap Node
  	* First node specified will be considered as primary or bootstrap node.
+--------------------------------------------------------------------------------+
   PowerVC Node(s) Information
     Node 1
	Enter IP/Hostname for Node 1        : xxx.xx.xx.bb
	Enter Username for all nodes        : pvcroot
	Enter Password for all nodes        :
+--------------------------------------------------------------------------------+
   Virtual IP
	Enter Virtual IP                    : xxx.xx.xx.cc
+--------------------------------------------------------------------------------+

~ 省略~

省略部分ログ (クリックして展開)

+--------------------------------------------------------------------------------+
|                         PowerVC Inventory - powervc232                         |
+--------------------------------------------------------------------------------+
	Cluster Name              : powervc232
	Cluster ID                : 2cb8fc03-fea2-45bf-8831-930906672efb
	Mode                      : Appliance
	Virtual IP                : xxx.xx.xx.cc
	Primary/Bootstrap Host    : xxx.xx.xx.bb
	Hosts                     : xxx.xx.xx.bb
	Edition                   : private_cloud
+--------------------------------------------------------------------------------+
|                 *** End of PowerVC Inventory - powervc232 ***                  |
+--------------------------------------------------------------------------------+

Establishing passwordless connection
    Cloud-init check successful for host xxx.xx.xx.bb
    Successfully created ssh keys for host xxx.xx.xx.bb
    Successfully fetched ssh keys for host xxx.xx.xx.bb
    Successfully fetched ip address, hostname and fqdn for host xxx.xx.xx.bb
    Successfully added ssh keys to authorized keys for host xxx.xx.xx.bb
    Successfully updated /etc/hosts and /etc/resolv.conf for host xxx.xx.xx.bb
    Successfully updated known hosts for host xxx.xx.xx.bb
Inventory generated successfully at /powervcdata/opsmgr/inventory/powervc232

+--------------------------------------------------------------------------------+
|                         PowerVC Inventory - powervc232                         |
+--------------------------------------------------------------------------------+
	Cluster Name              : powervc232
	Cluster ID                : 2cb8fc03-fea2-45bf-8831-930906672efb
	Mode                      : Appliance
	Virtual IP                : xxx.xx.xx.cc
	Primary/Bootstrap Host    : xxx.xx.xx.bb
	Hosts                     : xxx.xx.xx.bb
	Edition                   : private_cloud
	Inventory Directory       : /powervcdata/opsmgr/inventory/powervc232
+--------------------------------------------------------------------------------+
|                 *** End of PowerVC Inventory - powervc232 ***                  |
+--------------------------------------------------------------------------------+
[WARNING]: Could not match supplied host pattern, ignoring: active_hosts

PLAY [{{ playbook_task_names.get_active_hosts }}] ******************************

TASK [{{ playbook_task_names.check_for_active_hosts }}] ************************
Saturday 31 January 2026  01:12:04 +0000 (0:00:00.228)       0:00:00.228 ******
ok: [xxx.xx.xx.bb]

TASK [{{ playbook_task_names.group_active_hosts }}] ****************************
Saturday 31 January 2026  01:12:04 +0000 (0:00:00.836)       0:00:01.065 ******
changed: [xxx.xx.xx.bb]

PLAY [{{ playbook_task_names.set_primary_host }}] ******************************

TASK [Gathering Facts] *********************************************************
Saturday 31 January 2026  01:12:04 +0000 (0:00:00.033)       0:00:01.098 ******
ok: [xxx.xx.xx.bb]

TASK [debug] *******************************************************************
Saturday 31 January 2026  01:12:16 +0000 (0:00:11.957)       0:00:13.056 ******
ok: [xxx.xx.xx.bb] => {
    "msg": "['xxx.xx.xx.bb'] , xxx.xx.xx.bb"
}

TASK [set_fact] ****************************************************************
Saturday 31 January 2026  01:12:16 +0000 (0:00:00.032)       0:00:13.088 ******
skipping: [xxx.xx.xx.bb]

PLAY [{{ playbook_task_names.sync_inventory }}] ********************************

TASK [command] *****************************************************************
Saturday 31 January 2026  01:12:16 +0000 (0:00:00.034)       0:00:13.123 ******
changed: [xxx.xx.xx.bb]

TASK [include_vars] ************************************************************
Saturday 31 January 2026  01:12:17 +0000 (0:00:00.930)       0:00:14.054 ******
ok: [xxx.xx.xx.bb]

TASK [include_vars] ************************************************************
Saturday 31 January 2026  01:12:17 +0000 (0:00:00.040)       0:00:14.094 ******
ok: [xxx.xx.xx.bb]

TASK [{{ pvc_utils_task_names.store_locale_variable }}] ************************
Saturday 31 January 2026  01:12:17 +0000 (0:00:00.053)       0:00:14.148 ******
ok: [xxx.xx.xx.bb]

TASK [include_vars] ************************************************************
Saturday 31 January 2026  01:12:17 +0000 (0:00:00.032)       0:00:14.181 ******
ok: [xxx.xx.xx.bb]

TASK [Error Message for utils nls] *********************************************
Saturday 31 January 2026  01:12:18 +0000 (0:00:00.083)       0:00:14.265 ******
skipping: [xxx.xx.xx.bb]

TASK [include_vars] ************************************************************
Saturday 31 January 2026  01:12:18 +0000 (0:00:00.031)       0:00:14.297 ******
ok: [xxx.xx.xx.bb]

TASK [include_vars] ************************************************************
Saturday 31 January 2026  01:12:18 +0000 (0:00:00.105)       0:00:14.403 ******
ok: [xxx.xx.xx.bb]

TASK [pvc_lock : include_vars] *************************************************
Saturday 31 January 2026  01:12:18 +0000 (0:00:00.065)       0:00:14.468 ******
skipping: [xxx.xx.xx.bb]

TASK [pvc_lock : Acquire lock - Check for Lock file] ***************************
Saturday 31 January 2026  01:12:18 +0000 (0:00:00.027)       0:00:14.496 ******
ok: [xxx.xx.xx.bb]

TASK [pvc_lock : Display lock found message] ***********************************
Saturday 31 January 2026  01:12:18 +0000 (0:00:00.427)       0:00:14.923 ******
skipping: [xxx.xx.xx.bb]

TASK [pvc_lock : Configure lock facts based on file] ***************************
Saturday 31 January 2026  01:12:18 +0000 (0:00:00.026)       0:00:14.949 ******
ok: [xxx.xx.xx.bb]

TASK [pvc_lock : Configure lock facts based on all node] ***********************
Saturday 31 January 2026  01:12:18 +0000 (0:00:00.029)       0:00:14.979 ******
ok: [xxx.xx.xx.bb]

TASK [pvc_lock : End the play if lock found] ***********************************
Saturday 31 January 2026  01:12:18 +0000 (0:00:00.043)       0:00:15.023 ******
skipping: [xxx.xx.xx.bb]

TASK [pvc_lock : Acquire lock - Create PowerVC Lock file] **********************
Saturday 31 January 2026  01:12:18 +0000 (0:00:00.030)       0:00:15.053 ******
changed: [xxx.xx.xx.bb -> localhost]

TASK [Create directory] ********************************************************
Saturday 31 January 2026  01:12:19 +0000 (0:00:00.416)       0:00:15.470 ******
ok: [xxx.xx.xx.bb]

TASK [Sync License accepted file] **********************************************
Saturday 31 January 2026  01:12:19 +0000 (0:00:00.302)       0:00:15.773 ******
changed: [xxx.xx.xx.bb]

TASK [pvc_sync_inv : include_vars] *********************************************
Saturday 31 January 2026  01:12:20 +0000 (0:00:00.617)       0:00:16.391 ******
fatal: [xxx.xx.xx.bb]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}
...ignoring

TASK [pvc_sync_inv : include_vars] *********************************************
Saturday 31 January 2026  01:12:20 +0000 (0:00:00.026)       0:00:16.417 ******
fatal: [xxx.xx.xx.bb]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}
...ignoring

TASK [{{ pvc_sync_inv_task_names.check_for_lock_file }}] ***********************
Saturday 31 January 2026  01:12:20 +0000 (0:00:00.029)       0:00:16.447 ******
ok: [xxx.xx.xx.bb -> 127.0.0.1]

TASK [{{ pvc_sync_inv_task_names.set_fact }}] **********************************
Saturday 31 January 2026  01:12:20 +0000 (0:00:00.272)       0:00:16.720 ******
ok: [xxx.xx.xx.bb]

TASK [{{ pvc_sync_inv_task_names.set_fact_for_lock_file_based_on_all_node }}] ***
Saturday 31 January 2026  01:12:20 +0000 (0:00:00.030)       0:00:16.751 ******
ok: [xxx.xx.xx.bb]

TASK [{{ pvc_sync_inv_task_names.synchronize_inventory }}] *********************
Saturday 31 January 2026  01:12:20 +0000 (0:00:00.046)       0:00:16.797 ******
skipping: [xxx.xx.xx.bb]

TASK [pvc_lock : include_vars] *************************************************
Saturday 31 January 2026  01:12:20 +0000 (0:00:00.025)       0:00:16.822 ******
skipping: [xxx.xx.xx.bb]

TASK [pvc_lock : Release lock - Remove lock file] ******************************
Saturday 31 January 2026  01:12:20 +0000 (0:00:00.029)       0:00:16.852 ******
changed: [xxx.xx.xx.bb -> localhost]

TASK [pvc_lock : Display Failed nodes if case of failure] **********************
Saturday 31 January 2026  01:12:20 +0000 (0:00:00.287)       0:00:17.140 ******
ok: [xxx.xx.xx.bb] => {
    "msg": [
        "Number of nodes        : 1",
        "List of Nodes          : ['xxx.xx.xx.bb']",
        "Number of failed nodes : 0",
        "List of failed nodes   : [] "
    ]
}

TASK [pvc_lock : Success message for play] *************************************
Saturday 31 January 2026  01:12:20 +0000 (0:00:00.046)       0:00:17.187 ******
ok: [xxx.xx.xx.bb] => {
    "msg": "Play completed successfully in all '1' hosts '['xxx.xx.xx.bb']'."
}
xxx.xx.xx.bb               : ok=25   changed=5    unreachable=0    failed=0    skipped=7    rescued=0    ignored=2


PLAY RECAP *********************************************************************
xxx.xx.xx.bb               : ok=25   changed=5    unreachable=0    failed=0    skipped=7    rescued=0    ignored=2

Saturday 31 January 2026  01:12:20 +0000 (0:00:00.020)       0:00:17.208 ******
===============================================================================
Gathering Facts -------------------------------------------------------- 11.96s
command ----------------------------------------------------------------- 0.93s
{{ playbook_task_names.check_for_active_hosts }} ------------------------ 0.84s
Sync License accepted file ---------------------------------------------- 0.62s
pvc_lock : Acquire lock - Check for Lock file --------------------------- 0.43s
pvc_lock : Acquire lock - Create PowerVC Lock file ---------------------- 0.42s
Create directory -------------------------------------------------------- 0.30s
pvc_lock : Release lock - Remove lock file ------------------------------ 0.29s
{{ pvc_sync_inv_task_names.check_for_lock_file }} ----------------------- 0.27s
include_vars ------------------------------------------------------------ 0.11s
include_vars ------------------------------------------------------------ 0.08s
include_vars ------------------------------------------------------------ 0.07s
include_vars ------------------------------------------------------------ 0.05s
pvc_lock : Display Failed nodes if case of failure ---------------------- 0.05s
{{ pvc_sync_inv_task_names.set_fact_for_lock_file_based_on_all_node }} --- 0.05s
pvc_lock : Configure lock facts based on all node ----------------------- 0.04s
include_vars ------------------------------------------------------------ 0.04s
set_fact ---------------------------------------------------------------- 0.03s
{{ playbook_task_names.group_active_hosts }} ---------------------------- 0.03s
{{ pvc_utils_task_names.store_locale_variable }} ------------------------ 0.03s
Inventory sync is successful
pvcroot@localhost:~>

PowerVC クラスター構成 (PowerVC インストール)

PowerVC 構成(インストール)を実行します。

コマンド： powervc-opsmgr configure -c <クラスター名>

pvcroot@localhost:~> powervc-opsmgr configure -c powervc232

PLAY [PowerVC Configuration] ***************************************************
Saturday 31 January 2026  03:03:42 +0000 (0:00:00.249)       0:00:00.249 ******

TASK [Gathering Facts] *********************************************************
ok: [xxx.xx.xx.bb]
Saturday 31 January 2026  03:03:44 +0000 (0:00:01.659)       0:00:01.908 ******

TASK [include_vars] ************************************************************
ok: [xxx.xx.xx.bb]
Saturday 31 January 2026  03:03:44 +0000 (0:00:00.080)       0:00:01.989 ******


~ (省略) ~ 


TASK [pvc_main : synchronize inventory] ****************************************
ok: [xxx.xx.xx.bb -> xxx.xx.xx.bb] => (item=xxx.xx.xx.bb)
Saturday 31 January 2026  03:53:07 +0000 (0:00:04.335)       0:49:25.293 ******
ok: [xxx.xx.xx.bb] => {
    "msg": "Play completed successfully"
}

TASK [pvc_main : Success message for play] *************************************
ok: [xxx.xx.xx.bb] => {
    "msg": "Play completed successfully"
}
Saturday 31 January 2026  03:53:07 +0000 (0:00:00.072)       0:49:25.365 ******
xxx.xx.xx.bb               : ok=2387 changed=1175 unreachable=0    failed=0    skipped=1956 rescued=0    ignored=33

PLAY RECAP *********************************************************************
xxx.xx.xx.bb               : ok=2387 changed=1175 unreachable=0    failed=0    skipped=1956 rescued=0    ignored=33

Saturday 31 January 2026  03:53:07 +0000 (0:00:00.068)       0:49:25.433 ******
===============================================================================
pvc_bootstrap_keystone : Wait for keystone service to be active ------- 131.55s
pvc_firewalld : Pause until the firewalld comes up -------------------- 100.45s
pvc_reverse_proxy : restart proxyserver -------------------------------- 91.45s
pvc_firewalld : Open TCP ports on Firewall ----------------------------- 44.67s
pvc_pacemaker : Configure Pacemaker resources -------------------------- 31.93s
powervc_galera_new : Wait for 30 seconds for WSREP become prepared state -- 30.51s
powervc_galera_new : Wait for 30 seconds for WSREP become prepared state -- 30.41s
pvc_bootstrap_keystone : Check for port status after restart ----------- 30.35s
pvc_main : {{ playbook_task_names.wait_for_30_seconds_to_have_galera_as_resource_active }} -- 30.32s
pvc_main : Httpd service restart --------------------------------------- 29.77s
pvc_reg_services : openstack create endpoints -------------------------- 26.92s
pvc_pacemaker : Configure Pacemaker resources -------------------------- 25.60s
pvc_main : Apply permissions to files (0644) --------------------------- 25.39s
pvc_pacemaker : Wait untill cluster is online and ready ---------------- 25.08s
pvc_bootstrap_keystone : Create predefined roles ----------------------- 24.93s
powervc_utils : Set file permissions for components -------------------- 23.75s
powervc_db_conn : Datamanager Calls for DB Sync ------------------------ 15.83s
powervc_ui : restart ui server ----------------------------------------- 15.64s
powervc_galera_new : Wait for 15 seconds to fully stop galera service -- 15.57s
powervc_galera_new : Wait for 15 seconds to fully stop galera service -- 15.53s
IBM PowerVC configuration successfully completed at 2026-01-31 03:53:08.
 Refer to
 /powervclog/opsmgr/artifacts/powervc-opsmgr_powervc232_configure_20260131_030338/stdout
 for more details.
Access PowerVC UI at https://xxx.xx.xx.cc
+--------------------------------------------------------------------------------+
|                        *** End of PowerVC Inventory ***                        |
+--------------------------------------------------------------------------------+
pvcroot@localhost:~>

この環境では PowerVC 構成(導入)はおよそ 50 分弱でした。

Web UI ログイン

インベントリで設定したユーザー (pvcroot) でログインします。

Web UI は PowerVC 2.3.1 からは大きな変更はないようです。(多分細かな修正が入っていると思います)

エンタープライズ・ポリシーや、ボリューム・スナップショットの画面もあります。
(2.3.1にも存在していたかもしれませんが、おそらく 2.3.0 には未実装だった機能かと思われます。)

おわりに

PowerVC 2.3.2 から新しくリリースされたアプライアンスの導入を確認しました。
Web UI には大きな違いはないようですが、CLI ではこれまでとコマンド体系も変わっていますので少々慣れが必要です。

ご参考になれば幸いです。

以上です。

You get articles that match your needs
You can efficiently read back useful information
You can use dark theme

What you can do with signing up