###################################################################################################################################
###################################################################################################################################
##
## The purpose of this file is to define the server-specific configuration information for an automated installation via AutoYaST.
##
##
## Individual fields are seperated by ";". Fields can contain single values or multiple values seperated by ":" (list fields).
## If fields are optional they can be left empty resulting in two consecutive field separators ";;".
##
## As of November 5, 2012 this file has 14 fields per server which means there should be 13 semicolons per line.

## To jump to the ";" after a certain field, e. g. field 8 execute the following sequence of commands in vi:
##
## 1. leave insert mode by typing <ESC>
## 2. use cursor to go to a particular line
## 3. type 0 (number 0) to go to beginning of the line
## 4. type "8", type "f", type ";" - your cursor will jump to the semicolon after the 8th field
##
## The following command determines the number of occurences of ";" in the current line: "s/;/&/ng"


## Detailed field description 
## Field 01 - HOST_NAME 	- mandatory - short name of the server being installed; e.g. machine01
## Field 02 - IP_ADDRESS/CIDR	- mandatory - IP address and net mask of the server being installed; used as system identifier.
##				  Net mask in CIDR notation:
##				  255.255.240.0 = 20
##				  255.255.248.0 = 21
##				  255.255.252.0 = 22
##				  255.255.254.0 = 23
##				  255.255.255.0 = 24
## - OR -   - MAC_ADRESS        - If AY_MACHINE_IDENTIFIER="MAC" is set in AY_MAIN.txt this field accomodates the MAC address
##                                of the server being installed
## Field 03 - GATEWAY		- optional - IP address of the default gateway
## Field 04 - SERVER_TYPE	- mandatory - pure SLES or OES systems including version, feature pack (level FP, OES11 only
##				  and support pack level;
##				  "ovl" at the end of the identifier denotes that the system will be installed from the combined
##				  SLES/OES installation medium (no longer used with OES2018 and later).
##				  Examples for valid server types are: sles11sp4, sles12p5, sels15sp4, oes11sp3, oes11sp3ovl,
##				  oes2015sp1, oes2015sp1ovl, oes2018sp3, oes2023.
##				  Server types for different environments can be created by appending them with identifiers such as
##				  "-DEV", "-TST", etc.
##				  !!! IMPORTANT !!!
##				  There always needs to be a corresponding addon_products-$SERVER_TYPE.xml file in the ../files/addon
##				  directory, even when installing a pure SLES system.
## Field 05 - DEVICE_NAME0	- mandatory name of the 1st system disk device; e.g. /dev/sda|/dev/hda|/dev/vmx|/dev/cciss/c0d0|...
## Field 06 - DEVICE_NAME1	- optional  name of the 2nd system disk device; e.g. /dev/sdb|/dev/hdb|/dev/vmx|/dev/cciss/c0d1|...
##			  	  Use "ssh $SERVER -C 'sfdisk -l'" to determine device names if unsure.
## Field 07 - PART_FILE		- mandatory partitioning class file; must be located in .../files/partitioning
##			  	  The file name should identify the type and the number and size of the device(s) for which it defines
##				  the partitioning. The file name can also give an indiation for which type of server it is intended.
##				  e. g. part-vmware-GPT-btrfs-lvm-50G.xml, part-vmware-GPT-btrfs-lvm-50G_2nd-HDD_ZCMSat.xml, etc.  
## Field 08 - SOFT_FILE		- mandatory software class file; must be located in .../files/software  
##			  	  The file name should identify the SERVER_TYPE and the purpose of the server for which the software
##				  selection is valid;
##			          e.g. soft-oes2018_branch.xml; soft-sles15_basci.xml, etc.
## Field 09 - ZCM_KEY_LIST	- optional keys for the registration of the new device with a ZENworks Management Zone.
## 				  Multiple keys are possible separated by ':'; the first key will be used for registration with the
## 				  ZCM server, all other keys will be used for subscribing to device groups in ZCM used to manage
##				  configuration and software updates.
##				  Examples for valid ZCM keys for a production environment are:
## 				  PRD_<location>_EDIR (location), TST_EDIR_GRP (config) and DEV_OES2018SP2 (update) etc.
## Field 10 - TREE_NAME		- mandatory for OES servers - eDirectory tree name 
##				  There must be a configuration file <TREE_NAME>.txt in .../configs; the file name is case sensitive!
## Field 11 - TREE_TYPE		- mandatory for OES servers - existing|new
## Field 12 - SERVER_CONTEXT	- mandatory for OES servers - server context in LDAP syntax, e.g. ou=servers,ou=services,ou=DUS,o=Novell
## Field 13 - SERVER_LOCATION	- optional configuration file determining all aspects of the physical server location such as the following:
##				  default gateway, LDAP server list, NTP server list, etc.
##				  There must be a configuration file <SERVER_LOCATION[.txt]> in .../configs; the file name is case sensitive!
## 				  In smaller environments all this information can be provided in the configuration file corresponding
##				  to the tree name or in CUSTOMER.txt
## Field 14 - SERVICE_TYPE	- mandatory XML profile as defined in CUSTOMER.txt; the file names are case sensitive!
## 				  The XML files identified by the profile must exist in .../files/services/oes|sles


## Field overview
## 01: HOST_NAME; 02: IP_ADDRESS/NETMASK; 03 GATEWAY; 04: SERVER_TYPE; 05: DEVICE_NAME0; 06: DEVICE_NAME1; 07: PART_FILE;
## 08: SOFT_FILE; 09: ZCM_KEY_LIST; 10: TREE_NAME; 11: TREE_TYPE; 12: SERVER_CONTEXT; 13: SERVER_LOCATION; 14: SERVICE_TYPE

#######################################################################
###                   AutoYaST test installations                   ###
#######################################################################

#Server1;10.10.10.101/24;;oes2023-TST;/dev/sda;;part-vmware-UEFI-btrfs-lvm-30G.xml;soft-oes2023_edir-iman.xml;;<Your_Tree>;new;<Your_ServerContext>;<Your_Location.txt>;OES2023_EDIR_IMAN
#Server2;10.10.10.102/24;;oes2023-TST;/dev/sda;;part-vmware-UEFI-btrfs-lvm-30G.xml;soft-oes2023_branch.xml;;<Your_Tree>;existing;<Your_ServerContext>;<Your_Location.txt>;OES2023_BRANCH

#################################################################
###     DEVELOPMENT environment eDirectory Tree <TreeName>    ###
#################################################################




#################################################################
###        TEST environment eDirectory Tree <TreeName>        ###
#################################################################




#################################################################
###     PRODUCTION environment eDirectory Tree <TreeName>     ###
#################################################################
