# IBM_PROLOG_BEGIN_TAG 
# This is an automatically generated prolog. 
#  
# bos72L src/bos/usr/ios/cli/viosupgrade.inst 1.1 
#  
# Licensed Materials - Property of IBM 
#  
# Restricted Materials of IBM 
#  
# COPYRIGHT International Business Machines Corp. 2018 
# All Rights Reserved 
#  
# US Government Users Restricted Rights - Use, duplication or 
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 
#  
# IBM_PROLOG_END_TAG 
# VIOSUPGRADE Utility file
# 
# This file can be used as a input file for the "viosupgrade" tool ("-f" option) 
# in order to initiate the installation of multiple VIO Servers in parallel. 
# For the viosupgrade tool, input arguments are expected to be in specific order. 
# This file has definitions of all the mandatory / optional arguments and examples
# for users reference. All teh arguments for any given VIOS upgrade process are
# expected to be in the same line. 
# This file can also be used to verify the installation of all the VIO servers
# specified here.
#
######################### Trigger installation ###################################
#
# viosupgrade tool accept two types of installation,
# TYPE1 = bosinst(indicates new and fresh installation on the current rootvg
#			disk or on the provided disks)
# TYPE2 = altinst(indicates new and fresh installation on the alternate disk 
#			only)
#
# Fields description:
# -------------------
# NODE_NAME 		- Target VIOS hostname to perform VIOS upgrade operation.
#
# MKSYSB_NAME 		- The MKSYSB resource name.
#
# SPOT_NAME			- The SPOT resource name.
#
# TARGET_INSTALL_DISKS - Target rootvg disks(other then current rootvg)
#							to install new image.						
#
# ALT_ROOTVG_PVS	- The alternate physical volume to take
#						backup of current rootvg(in TYPE1 case) or install(in TYPE2 case).
#
# VIOS_CONFIG_BACKUP_FILE - Specifies the already exist VIOS configuration
#							backup resource.
#
# CLUSTER_NODE		- Specify if the given VIOS is part of the cluster.
#
# NIM_RESOURES		- Specifies configuration resource(s) to apply as part of the installation. 
#					  supported resources are resolv_conf, script, fb_script, file_res, image_data, log.
#--------------------
#
# NOTE: File format is comma-separated values(CSV), for multiple values	
#		in particular field pass colon(:) separated values.
#
# -----------------------------------------------------------------------------
# TYPE1 file format:
# ------------------
# NODE_NAME, MKSYSB_NAME, SPOT_NAME, TARGET_INSTALL_DISKS, ALT_ROOTVG_PVS, VIOS_CONFIG_BACKUP_FILE, CLUSTER_NODE, NIM_RESOURES
# 
# NOTE: Mandatory fields are NODE_NAME, MKSYSB_NAME, SPOT_NAME.
#		CLUSTER_NODE field requires either character 'c'(if node is a part of the cluster)
#			or empty(if node is not a part of the cluster).
#
# Examples:
# ---------
# Lets say user wants to install 4 VIOS in a single execution of the command,
# 		 In that case user needs to add entries in the file as below,
# 
# vios1, vios_mksysb_1, vios_spot_1, hdisk1:hdisk2, 			 , viosbr_backup_resource_1, c, 
# vios2, vios_mksysb_2, vios_spot_2, 			  , hdisk4:hdisk5, viosbr_backup_resource_2,  ,
# vios3, vios_mksysb_1, vios_spot_1, 			  , 			 , 						   , c, my_resolv_conf:my_script:my_fb_script:my_file_res:my_image_data:my_log
# vios4, vios_mksysb_2, vios_spot_2, 			  , 			 , 						   ,  , my_resolv_conf:my_script:my_file_res
#
# NOTE: 1) More than one value – Colon separated – ':' .
#       2) For cluster level operation specify only 'c' character.
#		3) Maximum number of nodes supported for installation through file option is 30. 
#		4) Data needs to be entered in the file always in the same format. 
#		5) Empty fields in place of 'TARGET_INSTALL_DISKS' and 'ALT_ROOTVG_PVS' 
#		   specifies 'SKIP' option from the user.
#		6) Empty fields in place of 'VIOS_CONFIG_BACKUP_FILE' specifies that 
#		   VIOS configuration backup has to be taken from VIOS.
#		7) 'CLUSTER_NODE' field requires either character 'c' (if node is a part of the cluster)
#		   or empty(if node is not a part of the cluster).
# -----------------------------------------------------------------------------		
# TYPE2 file format:
# ------------------
# NODE_NAME, MKSYSB_NAME, SPOT_NAME, TARGET_INSTALL_DISKS, ALT_ROOTVG_PVS, VIOS_CONFIG_BACKUP_FILE, CLUSTER_NODE, NIM_RESOURES
# 
#
# NOTE: 1) Mandatory fields are NODE_NAME, MKSYSB_NAME, SPOT_NAME.
# 		2) In TYPE2 installation, SPOT_NAME and TARGET_INSTALL_DISKS fields will always be empty.
#		3) CLUSTER_NODE field requires either character 'c'(if node is a part of the cluster)
#			or empty(if node is not a part of the cluster).
#
# Examples:
# ---------
# Lets say user wants to install 4 VIOS in a single execution of the command,
# 		 In that case user needs to add entries in the file as below,
# 
# vios1, vios_mksysb_1, , , hdisk1:hdisk2:hdisk3 , viosbr_backup_resource_1, c,
# vios2, vios_mksysb_2, , , hdisk4:hdisk5		 , viosbr_backup_resource_2,  ,
# vios3, vios_mksysb_1, , , 					 , 						   , c,
# vios4, vios_mksysb_2, , , 					 , 						   , c, my_resolv_conf:my_script:my_file_res
# 
#
# -----------------------------------------------------------------------------		
######################### Check status ####################################
#
# User can provide the input file which was provided at the time of triggering installation operation
# (i.e. TYPE1 and TYPE2 input file can be provided as an input).
# Exmaple:
# --------
# vios1, vios_mksysb_1, , , hdisk1:hdisk2:hdisk3 , viosbr_backup_resource_1, c,
# vios2, vios_mksysb_2, , , hdisk4:hdisk5     , viosbr_backup_resource_2,  ,
#
#
# User can also choose to provide only VIOS hostname to verify the installation status
# Example:
# ---------
# Lets say user wants to check the status of 4 VIOS in a single execution of the command,
# 		 In that case user needs to add entries in the file as below,
# 
# vios1
# vios2
# vios3
# vios4
#
######################### Add your entries below this line ################