Legacy install of PowerVC
Using OpsMgr, perform legacy install of version 2.2.1 on a system in which RHEL HA license is not required.
Legacy install feature is not recommended for production environments and is meant for test and
PoC environments.
Notes:
- Legacy install is deprecated and support will be removed in a future release.
- Legacy install of PowerVC is not supported for upgrade from 2.2.1 to 2.2.1.1.
Example:
Inventory creation for PowerVC on
a single
node
[root@<Hostname> ~]# powervc-opsmgr inventory -c <clustername_legacy>
+--------------------------------------------------------------------------------+
| PowerVC Inventory |
+--------------------------------------------------------------------------------+
Configure Firewall (y/n) (Default: y):
Legacy Installation (y/n) (Default: y):
+--------------------------------------------------------------------------------+
INFO:
Legacy Method option
* Only one node will be part of PowerVC.
* No cluster will be installed during PowerVC installation.
Sudo User
* Sudo user with same username and password across all nodes is required.
+--------------------------------------------------------------------------------+
PowerVC Node(s) Information
Node 1
Enter IP/Hostname for Node 1 : <IP or Hostname>
Enter Username for all nodes : root
Enter Password for all nodes :
+--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+
| PowerVC Inventory - <clustername_legacy> |
+--------------------------------------------------------------------------------+
Cluster Name : <clustername_legacy>
Cluster ID : 071bb404-26c8-4eaf-aeb5-292e3b4490f1
Install Method : legacy
Firewall Config : True
Login User : root
Virtual IP : <IP>
Hosts : <IP or Hostname>
Edition : private_cloud
+--------------------------------------------------------------------------------+
| *** End of PowerVC Inventory - <clustername_legacy> *** |
+--------------------------------------------------------------------------------+
Establishing passwordless connection
PLAY [{{ playbook_task_names.configure_ssh_keys }}] ****************************
TASK [Gathering Facts] *********************************************************
<Date> 01:55:02 -0400 (0:00:00.168) 0:00:00.168 *********
[DEPRECATION WARNING]: Distribution rhel 8.7 on host should use
/usr/libexec/platform-python, but is using /usr/bin/python for backward
compatibility with prior Ansible releases. A future Ansible release will
default to using the discovered platform python for this host. See https://docs
.ansible.com/ansible/2.9/reference_appendices/interpreter_discovery.html for
more information. This feature will be removed in version 2.12. Deprecation
warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
ok: [<IP or Hostname>]
TASK [command] *****************************************************************
<Date> 01:55:05 -0400 (0:00:02.962) 0:00:03.131 *********
changed: [<IP or Hostname>]
TASK [include_vars] ************************************************************
<Date> 01:55:07 -0400 (0:00:01.377) 0:00:04.508 *********
ok: [<IP or Hostname>]
.
.
.
.
SSH Key exchange successfully completed at,
<Date> 01:55:12.,
Refer to
/opt/ibm/powervc-opsmgr/ansible/artifacts/powervc-opsmgr_<clustername_legacy>_ssh_key_xchg_20240430_015459/stdout
for more details.
Inventory file generated successfully at /opt/ibm/powervc-opsmgr/ansible/inventory/<clustername_legacy>
+--------------------------------------------------------------------------------+
| PowerVC Inventory - <clustername_legacy> |
+--------------------------------------------------------------------------------+
Cluster Name : <clustername_legacy>
Cluster ID : 071bb404-26c8-4eaf-aeb5-292e3b4490f1
Install Method : legacy
Firewall Config : True
Login User : root
Virtual IP : <IP>
Hosts : <IP or Hostname>
Edition : private_cloud
Inventory Directory : /opt/ibm/powervc-opsmgr/ansible/inventory/<clustername_legacy>
+--------------------------------------------------------------------------------+
| *** End of PowerVC Inventory - <clustername_legacy> *** |
+--------------------------------------------------------------------------------+
After generation of inventory file, you can validate by running powervc-opsmgr inventory -l command.
Example:
[root@controller ~]# powervc-opsmgr inventory -l
+--------------------------------------------------------------------------------+
| PowerVC Inventory - <clustername_legacy> |
+--------------------------------------------------------------------------------+
Cluster Name : <clustername_legacy>
Cluster ID : 071bb404-26c8-4eaf-aeb5-292e3b4490f1
Install Method : legacy
Firewall Config : True
Login User : root
Virtual IP : <IP>
Hosts : <IP or Hostname>
Edition : private_cloud
+--------------------------------------------------------------------------------+
| *** End of PowerVC Inventory - <clustername_legacy> *** |
+--------------------------------------------------------------------------------+
Start the installation by using the following method:
- To verify that your environment meets all of the prerequisites, run
powervc-opsmgr install -c <clustername> -p
before starting the actual install. - Run
powervc-opsmgr install -c <clustername>
to start installation.To use your RHSM subscription and enable repos on all nodes, you can use -s option. However, you can also choose to manually add repos by using your RHEL subscription.
You can use the below command to run the install CLI as a backgroundnohup powervc-opsmgr install -c <cluster_name> -s &
The installation log file can be found in the following location:
/opt/ibm/powervc-opsmgr/ansible/artifacts/powervc-opsmgr_<cluster_name>_install_<time_stamp>/stdout
.
After installation is complete, run powervc-opsmgr install -c <cluster_name> -s --validate-install to check the complete health status of all services.
Limitations
- This feature is not supported for add node, replace node, change VIP and compute plane node IPs, and resync_node.
- Legacy install is supported only on 8.8 (x86_64 and ppc64le), SLES 15 SP3 SAP, SLES 15 SP5, and SLES 15 SP5 SAP Edition.