PowerVC

 View Only

PowerVC 2.0.2 - With all new installation technique

By Rajni Kumari posted Thu September 30, 2021 08:15 AM

  
PowerVC 2.0.2 is released in Sept 2021 with all new high availability and scale architecture. This blog explains the new install procedure for the PowerVC version 2.0.2. The new PowerVC installer supports cluster and HA. PowerVC installation is supported on one-node and three-node. Read 'Multinode architecture overview' blog to understand the new architecture implemented in PowerVC.

Before you start installing PowerVC

Configure yum repository for PowerVC install on RHEL and make sure that the following repos are enabled.

  • AppStream
  • BaseOS
  • Supplementary
  • High Availability
  • Ansible

For SLES, PowerVC 2.0.2 installation is supported only on single node.

PowerVC installer does not support enabling sle-module-public-cloud repository on SLES 15 SP3 management server. Also, enabling sle-module-public-cloud repository on SLES 15 SP3 management server after installing PowerVC and performing system updates might affect PowerVC functionality. Make sure that sle-module-public-cloud is disabled.

Notes:

  • For SLES, ensure that all SELinux components are installed by using YaST. Refer to corresponding SLES version SELinux configuration documentation for instructions. For example, see Configuring SELinux for SLES 15 SP3.
  • After installing the SELinux packages and enabling the SELinux GRUB 2 boot parameters, reboot virtual machine to activate the configuration.

Installation procedure

Let's see the installation procedure for PowerVC 2.0.2.

  1. Download PowerVC 2.0.2 installer. 
    Extract the tar file that matches your environment to the location where you want to run the installation script for ppc64le powervc-opsmgr-rhel-ppcle-2.0.2.tgz for x86 powervc-opsmgr-rhel-x86-2.0.2.tgz.
    [root@test ~]# tar -xvf powervc-opsmgr-rhel-ppcle-2.0.2.tgz
    powervc-opsmgr/
    powervc-opsmgr/images/
    powervc-opsmgr/images/RPM-GPG-KEY-PowerVC
  2. Install PowerVC Operations Manager (opsmgr). 
    cd powervc-opsmgr
    [root@ powervc-opsmgr]# ls
    images  lap  lib  license  opsmgr-version.properties  packages  setup_opsmgr.sh  uninstall-opsmgr.sh  version.properties
    [root@powervc-opsmgr]# ./setup_opsmgr.sh
    ################################################################################
    Starting the PowerVC:setup_prepnode 2.0.2 installation on:
    2021-09-28T05:34:24-04:00
    ################################################################################
    <skipping lines>
    2021-09-28T05:35:49.10-04:00 [INFO]:[INSTALL_ANSIBLE] Ansible version 2.9 not available in repo.
    2021-09-28T05:35:49.11-04:00 [INFO]:[INSTALL_ANSIBLE] Ansible version 2.9 is not in repo, finding in additional repo of RHEL8
    2021-09-28T05:36:01.70-04:00 [INFO]:[INSTALL_ANSIBLE] Ansible 2.9 installation started .....
    2021-09-28T05:36:42.07-04:00 [INFO]:[INSTALL_ANSIBLE] Ansible packages installed successfully.
    2021-09-28T05:36:51.56-04:00 [INFO]:[INSTALL_ANSIBLE] Ansible 2.9 installation completed .....
    2021-09-28T05:36:51.56-04:00 [INFO]:[INSTALL_ANSIBLE] Installing PowerVC Ops. Manager...
    2021-09-28T05:36:51.57-04:00 [INFO]:[INSTALL_POWERVC_OPSMGR] POWERVC OPSMGR PACKAGES : sshpass python3-netaddr rsync python3-oslo-i18n python3-powervc-opsmgr
    2021-09-28T05:37:18.36-04:00 [INFO]:[INSTALL_POWERVC_OPSMGR] PowerVC Opsmgr packages installed successfully.
    <skipping lines>
  3. Create inventory.

    Following is the example shown for PowerVC installation on single node. For three-node deployment, you must provide node2 and node3 IP/hostname. Make sure that all nodes have the same architecture and password. A virtual IP will also be required for the installer to proceed – this is an IP which is not active and in the same subnet as the nodes.

    [root@powervc-opsmgr]# powervc-opsmgr inventory -c powervc
    *********************************************************
    Install Private cloud edition(y/n): y
    Enable Monitoring (y/n): y
    Configure Firewall (y/n): y
    *********************************************************
    Enter the number of nodes: 1
    *********************************************************
    INFO: First node specified will be considered as primary host/node
    *******************************************************
    Enter IP/Hostname for Node 1: test.pok.stglabs.ibm.com
    Enter Username for Node 1: root
    Enter Password for Node 1:
    *********************************************************
    Enter Virtual IP/Hostname: 9.x.x.x
    Establishing passwordless connection
    PLAY [Configure SSH Keys] ******************************************************
    << skipping lines>>
    SSH Key exchange successfully completed at, 2021-09-28 05:42:30.,
    Refer to
    /opt/ibm/powervc-opsmgr/ansible/artifacts/powervc-opsmgr_powervc_ssh_key_xchg_20210928_054221/stdout
    for more details.
    Inventory file generated successfully at /opt/ibm/powervc-opsmgr/ansible/inventory/powervc

    Notes:

    • Firewall configuration is similar to the older versions, if specified as yes, installer will configure the firewall.
    • All nodes and the Virtual IP must belong to the same subnet. The Virtual IP should not correspond to an active system.
    • While using a pre-defined inventory, it is important to process it with the -i option so that it doesn’t become non-coherent.
    • Installation, uninstallation and other operations in powervc-opsmgr are logically idempotent. If the operation is stuck at some point for any reason, it is expected to launch the operation again. The operation resumes from the last checkpoint.
    • Installation takes a while, and if you expect the connection to the machine to drop, using nohup is recommended.

    List Inventory

    [root@test powervc-opsm
    [root@test ~]# powervc-opsmgr inventory -l
    Cluster name: powervc
    Hosts: ['test.pok.stglabs.ibm.com']
    Edition: private_cloud
    Firewall Config: True
    Monitoring: True
    Primary host: test.pok.stglabs.ibm.com
    Virtual IP: 9.x.x.x
    ---End of cluster powervc---
  4. Install PowerVC.
    [root@test powervc-opsmgr]# powervc-opsmgr install -c powervc -s
    PLAY [Precheck] ****************************************************************
    Tuesday 28 September 2021  05:44:35 -0400 (0:00:00.097)       0:00:00.097 *****
    ok: [test.pok.stglabs.ibm.com]
    TASK [pvc_main : synchronize inventory] ****************************************
    ok: [test.pok.stglabs.ibm.com -> test.pok.stglabs.ibm.com] => (item=test.pok.stglabs.ibm.com)
    <<skipping lines>>
    TASK [pvc_main : Success message for play] *************************************
    ok: [test.pok.stglabs.ibm.com] => {
       "msg": "Play completed successfully"
    }
    Tuesday 28 September 2021  07:25:08 -0400 (0:00:00.531)       1:37:29.161 *****
    PLAY RECAP *********************************************************************
    test.pok.stglabs.ibm.com : ok=2621 changed=1251 unreachable=0    failed=0    skipped=1783 rescued=0    ignored=2 
    <<skipping lines>>
    IBM PowerVC installation successfully completed at 2021-09-28 07:25:09.
    Refer to
     /opt/ibm/powervc-opsmgr/ansible/artifacts/powervc-opsmgr_powervc_install_20210928_054737/stdout
    for more details.
    Access PowerVC UI at https://9.x.x.x
    RUNNING HANDLER [../roles/filebeat : service] **********************************
    << skipping lines>>
    IBM PowerVC monitoring install successfully completed at 2021-09-28 07:36:03.
    Refer to
    /opt/ibm/powervc-opsmgr/ansible/monitoring/run/artifacts/0515b551-c40b-45bd-9a79-3fbc7eb95ddd/stdout
     for more details.

    Validate version  

    [root@test ~]# cat /opt/ibm/powervc/version.properties
    [2.0.2 Install]
    name = IBM PowerVC
    version = 2.0.2
    build = 20210911-0351
    oem = no
    install-date = 2021-09-28
    cloud_enabled = yes
    offering = private_cloud
    cluster = powervc

    Validate powervc-services after installation of PowerVC using powervc-services status .

    [root@test ~]# powervc-services status
    clerk-api
    Started: test.pok.stglabs.ibm.com
    ttv-validation-api
    Started: test.pok.stglabs.ibm.com
    panko-api
    Started: test.pok.stglabs.ibm.com
    openstack-gnocchi-metricd
    Started: test.pok.stglabs.ibm.com
    openstack-swift-account
    Started: test.pok.stglabs.ibm.com
    openstack-swift-object
    Started: test.pok.stglabs.ibm.com
    openstack-swift-proxy
    Started: test.pok.stglabs.ibm.com
    openstack-swift-container
    Started: test.pok.stglabs.ibm.com
    openstack-swift-object-replicator
    Started: test.pok.stglabs.ibm.com
    memcached
    Started: test.pok.stglabs.ibm.com
    placement-api
    Started: test.pok.stglabs.ibm.com
    powervc-ui-server
    Started: test.pok.stglabs.ibm.com
    mongod
    Started: test.pok.stglabs.ibm.com
    powervc-bumblebee
    Started: test.pok.stglabs.ibm.com
    powervc-cinder-ibm-health
    Started: test.pok.stglabs.ibm.com
    powervc-nova-ibm-health
    Started: test.pok.stglabs.ibm.com
    powervc-neutron-ibm-health
    Started: test.pok.stglabs.ibm.com
    openstack-ceilometer-notification
    Started: test.pok.stglabs.ibm.com
    openstack-ceilometer-polling
    Started: test.pok.stglabs.ibm.com
    openstack-nova-api
    Started: test.pok.stglabs.ibm.com
    openstack-nova-conductor
    Started: test.pok.stglabs.ibm.com
    openstack-nova-scheduler
     Started: test.pok.stglabs.ibm.com
    openstack-nova-novncproxy
     Started: test.pok.stglabs.ibm.com
    neutron-server
     Started: test.pok.stglabs.ibm.com
    openstack-nova-ibm-notification
     Started: test.pok.stglabs.ibm.com
    openstack-nova-ibm-ego-ha-service
     Started: test.pok.stglabs.ibm.com
    openstack-nova-ibm-ego-resource-optimization
     Started: test.pok.stglabs.ibm.com
    openstack-cinder-api
     Started: test.pok.stglabs.ibm.com
    openstack-cinder-scheduler
     Started: test.pok.stglabs.ibm.com
    powervc-cinder-conductor
     Started: test.pok.stglabs.ibm.com
    zookeeper
     Started: test.pok.stglabs.ibm.com
    openstack-glance-api
     Started: test.pok.stglabs.ibm.com
    httpd
     Started: test.pok.stglabs.ibm.com
    memcached
     Started: test.pok.stglabs.ibm.com
    rabbitmq-server
     Started: test.pok.stglabs.ibm.com
    galera
     Started: test.pok.stglabs.ibm.com
    [root@test ~]#

Now, enjoy using PowerVC 2.0.2!! Please reach out to us if you have any queries or comments regarding this blog.

Knowledge center link: PowerVC
Keep watching our social outlets for more interesting information about PowerVC! Find and follow us on FacebookLinkedInYouTube, and Twitter.

Blog Authors:

Rajni Kumari
Shyama Venugopal

0 comments
67 views

Permalink