Ansible Role: nim_alt_disk_migration

The IBM Power Systems AIX collection provides an Ansible role, referred to as nim_master_migration, which assists in automating migration of NIM master machine.

For guides and reference, see the Docs Site.

Requirements

None.

Role Variables

Available variables are listed below, along with default values:

Role Variables
Variable Suboptions Required Default Choices Comments
nim_master_migration_master_a true NIM Master that will be used in migrating the required Master machine. Controller node would be connected to this node.
nim_master_migration_master_b true Specifies the NIM Master machine that is supposed to be migrated using another NIM Master (nim_master_migration_master_a) as its master.
nim_master_migration_alt_disk true Specifies the alternate disk on which NIM Alt Disk Migration will take place.
nim_master_migration_db_filename false Specifies the filename, where the database backup will be created on nim_master_migration_master_b machine.
nim_master_migration_lpp_source_v true Specifies a NIM object name associated to a LPP resource for the desired level of migration.
nim_master_migration_spot_v true Specifies a NIM object name associated to a spot resource for the desired level of migration.
nim_master_migration_nim_master_fileset_src true Specifies the location and filename, where the NIM master fileset (nos.sysmgt) is located.
nim_master_migration_nim_master_fileset_dest true Specifies the location wher NIM master fileset will be copied to/located on the NIM master mahine (nim_master_migration_master_b)
nim_master_migration_db_file_controller false Specifies the location where the database backup file will be copied to from the NIM master machine (nim_master_migration_master_b)
nim_master_migration_phase true backup_and_migration, db_restore Specifies the phase of operations that need to be performed so as to accomplish the broader task of Migrating NIM Master machine.

NOTES:

  • This role requires another machine having NIM master setup (nim_master_migration_master_a), nim_master_migration_master_a should be able to establish SSH connection with the master machine that needs to be migrated.

  • This machine (nim_master_migration_master_a) should be on the level to which you want your master machine (nim_master_migration_master_b) to be migrated.

  • Controller node’s primary target is nim_master_migration_master_a, but It should be able to establish SSH connection with nim_master_migration_master_b (The machine that needs to be migrated) as well.

  • To completely migrate the required machine and bring it back to the original state, you need to run the role twice. Once, with nim_master_migration_phase = “backup_and_migration” and second time with nim_master_migration_phase = “db_restore”

  • backup_and_migration will initialise the setup required and perform the migration of nim_master_migration_master_b using nim_master_migration_master_a as master.

  • db_restore will restore the database and bring the machine (nim_master_migration_master_b) to previous state.

Dependencies

  • nim_alt_disk_migration role

Example Playbook

# Use C(nim_master_migration_phase) = backup_and_migration to perform the following tasks:
# Creating database backup file
# Unconfiguring nim_master_migration_master_b (NIM master machine that needs to be migrated)
# Setting up nim_master_migration_master_b as client of nim_master_migration_master_a
# Perform Nim Alt disk migration operation
# Rebooting the machine (nim_master_migration_master_b)

- name: "nim_master_migration demo"
  hosts: all
  gather_facts: false
  remote_user: root
  collections:
    - ibm.power_aix
  tasks:
    - import_role:
        name: ibm.power_aix.nim_master_migration
      vars:
        nim_master_migration_master_a: p9zpa-ansible-nim1.aus.stglabs.ibm.com
        nim_master_migration_master_b: "fvtfleet1-lp1.aus.stglabs.ibm.com"
        nim_master_migration_alt_disk: "hdisk1"
        nim_master_migration_db_filename: "db_backupfile"
        nim_master_migration_lpp_source_v: "2317A_73D"
        nim_master_migration_spot_v: "2317A_73D_spot"
        nim_master_migration_nim_master_fileset_src: "~/bos.sysmgt"
        nim_master_migration_nim_master_fileset_dest: "~/bos.sysmgt"
        nim_master_migration_phase: backup_and_migration

# Use C(nim_master_migration_phase) = db_restore to perform the following tasks:
# Copy and install nim master fileset (bos.sysmgt.nim.master) on NIM master (nim_master_migration_master_b)
# Transfer and restore database backup on NIM master (nim_master_migration_master_b)
- name: "nim_master_migration demo"
  hosts: all
  gather_facts: false
  remote_user: root
  collections:
    - ibm.power_aix
  tasks:
    - import_role:
        name: ibm.power_aix.nim_master_migration
      vars:
        nim_master_migration_master_a: p9zpa-ansible-nim1.aus.stglabs.ibm.com
        nim_master_migration_master_b: "fvtfleet1-lp1.aus.stglabs.ibm.com"
        nim_master_migration_alt_disk: "hdisk1"
        nim_master_migration_db_filename: "db_backupfile"
        nim_master_migration_lpp_source_v: "2317A_73D"
        nim_master_migration_spot_v: "2317A_73D_spot"
        nim_master_migration_nim_master_fileset_src: "~/bos.sysmgt"
        nim_master_migration_nim_master_fileset_dest: "~/bos.sysmgt"
        nim_master_migration_phase: db_restore
        nim_master_migration_db_file_controller: "~/db_backupfile"