From 2510697f039a9b8fbf091ed08241137fa64b4568 Mon Sep 17 00:00:00 2001 From: immarvin Date: Tue, 29 Nov 2016 01:16:03 -0500 Subject: [PATCH 1/6] refine the doc on raid --- .../common/deployment/raid_cfg.rst | 52 +++++-------------- 1 file changed, 12 insertions(+), 40 deletions(-) diff --git a/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst b/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst index cc90f1f4a..2374f13ae 100644 --- a/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst +++ b/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst @@ -6,59 +6,31 @@ Overview This section describes how to use xCAT to deploy diskful nodes with RAID1 setup, and the procedure for RAID1 maintainence activities such as replacing a failed disk. -All the examples in this section are based on three configuration scenarios: +xCAT provides an user interface :doc:`linuximage.partitionfile ` to specify the customized partition script for diskful provision, and provides some default partition scripts to configure RAID1 on system Power server. -#. RHEL6 on a system p machine with two SCSI disks sda and sdb - -#. RHEL6 on a system p machine with two SAS disks and multipath configuration. - -#. SLES 11 SP1 on a system p machine with two SCSI disks sda and sdb - -If you are not using the configuration scenarios listed above, you may need to modify some of the steps in this documentation to make it work in your environment. Deploy Diskful Nodes with RAID1 Setup on RedHat ----------------------------------------------- -xCAT provides two sample kickstart template files with the RAID1 settings, ``/opt/xcat/share/xcat/install/rh/service.raid1.rhel6.ppc64.tmpl`` is for the configuration scenario **1** listed above and ``/opt/xcat/share/xcat/install/rh/service.raid1.multipath.rhel6.ppc64.tmpl`` is for the configuration scenario **2** listed above. You can customize the template file and put it under ``/install/custom/install//`` if the default one does not match your requirements. +xCAT provides a partition script `raid1_rh.partscript `_ which setup RAID1 on 2 disks on Power8 LE server, "raid1_rh.partscript" is composed of 2 parts: -Here is the RAID1 partitioning section in ``service.raid1.rhel6.ppc64.tmpl``: :: +1) the logic to pickup the disks to setup RAID +2) the logic to generate raid/partition scheme file "/tmp/partitionfile". - #Full RAID 1 Sample - part None --fstype "PPC PReP Boot" --size 8 --ondisk sda --asprimary - part None --fstype "PPC PReP Boot" --size 8 --ondisk sdb --asprimary +In most cases, this partition script "raid1_rh.partscript" is suffice for you to create a basic 2-disk RAID1 on your server. If you have some specific requirements on disks or partition scheme of the RAID, you need to provide your own partition script, "raid1_rh.partscript" is self-explanation and can be a reference for you. To simplify the introduction here, "raid1_rh.partscript" will be used as the partition script, the steps is listed below: - part raid.01 --size 200 --fstype ext4 --ondisk sda - part raid.02 --size 200 --fstype ext4 --ondisk sdb - raid /boot --level 1 --device md0 raid.01 raid.02 +1. obtain the partition script: :: - part raid.11 --size 1024 --ondisk sda - part raid.12 --size 1024 --ondisk sdb - raid swap --level 1 --device md1 raid.11 raid.12 + wget -O /install/custom/raid1_rh.partscript - part raid.21 --size 1 --fstype ext4 --grow --ondisk sda - part raid.22 --size 1 --fstype ext4 --grow --ondisk sdb - raid / --level 1 --device md2 raid.21 raid.22 +2. specify the partition script for osimage: :: -Here is the RAID1 partitioning section in ``service.raid1.multipath.rhel6.ppc64.tmpl``: :: + chdef -t osimage -o rhels7.3-ppc64le-install-compute partitionfile="s:/install/custom/raid1_rh.partscript" - #Full RAID 1 Sample - part None --fstype "PPC PReP Boot" --size 8 --ondisk mpatha --asprimary - part None --fstype "PPC PReP Boot" --size 8 --ondisk mpathb --asprimary - - part raid.01 --size 200 --fstype ext4 --ondisk mpatha - part raid.02 --size 200 --fstype ext4 --ondisk mpathb - raid /boot --level 1 --device md0 raid.01 raid.02 - - part raid.11 --size 1024 --ondisk mpatha - part raid.12 --size 1024 --ondisk mpathb - raid swap --level 1 --device md1 raid.11 raid.12 - - part raid.21 --size 1 --fstype ext4 --grow --ondisk mpatha - part raid.22 --size 1 --fstype ext4 --grow --ondisk mpathb - raid / --level 1 --device md2 raid.21 raid.22 - -The samples above created one PReP partition, one 200MB ``/boot`` partition and one ``/`` partition on ``sda/sdb`` and ``mpatha/mpathb``. If you want to use different partitioning scheme in your cluster, modify this RAID1 section in the kickstart template file accordingly. +3. provision the node: :: + rinstall cn1 osimage=rhels7.3-ppc64le-install-compute + After the diskful nodes are up and running, you can check the RAID1 settings with the following commands: Mount command shows the ``/dev/mdx`` devices are mounted to various file systems, the ``/dev/mdx`` indicates that the RAID is being used on this node. :: From cc5dbb0930cb95a4d5526d6136c43f2e68837a6e Mon Sep 17 00:00:00 2001 From: immarvin Date: Wed, 30 Nov 2016 04:37:09 -0500 Subject: [PATCH 2/6] docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst refine the doc on raid on rh7 --- .../common/deployment/raid_cfg.rst | 59 ++++++++++--------- 1 file changed, 31 insertions(+), 28 deletions(-) diff --git a/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst b/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst index 2374f13ae..22fabc71d 100644 --- a/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst +++ b/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst @@ -1,12 +1,10 @@ -Configure RAID before Deploy OS -=============================== +Configure RAID before deploying the OS +====================================== Overview -------- -This section describes how to use xCAT to deploy diskful nodes with RAID1 setup, and the procedure for RAID1 maintainence activities such as replacing a failed disk. - -xCAT provides an user interface :doc:`linuximage.partitionfile ` to specify the customized partition script for diskful provision, and provides some default partition scripts to configure RAID1 on system Power server. +xCAT provides an user interface :doc:`linuximage.partitionfile ` to specify the customized partition script for diskful provision, and provides some default partition scripts. Deploy Diskful Nodes with RAID1 Setup on RedHat @@ -14,20 +12,20 @@ Deploy Diskful Nodes with RAID1 Setup on RedHat xCAT provides a partition script `raid1_rh.partscript `_ which setup RAID1 on 2 disks on Power8 LE server, "raid1_rh.partscript" is composed of 2 parts: -1) the logic to pickup the disks to setup RAID -2) the logic to generate raid/partition scheme file "/tmp/partitionfile". +# the logic to select the disks to setup RAID +# the logic to generate the partition scheme and save it to /tmp/partitionfile in the installer. -In most cases, this partition script "raid1_rh.partscript" is suffice for you to create a basic 2-disk RAID1 on your server. If you have some specific requirements on disks or partition scheme of the RAID, you need to provide your own partition script, "raid1_rh.partscript" is self-explanation and can be a reference for you. To simplify the introduction here, "raid1_rh.partscript" will be used as the partition script, the steps is listed below: +In most scenarios, the sample partitioning script is sufficient to create a basic RAID1 across two disks and is provided as a sample to build upon. -1. obtain the partition script: :: +1. Obtain the partition script: :: wget -O /install/custom/raid1_rh.partscript -2. specify the partition script for osimage: :: +2. Associate the partition script to the osimage: :: - chdef -t osimage -o rhels7.3-ppc64le-install-compute partitionfile="s:/install/custom/raid1_rh.partscript" + chdef -t osimage -o rhels7.3-ppc64le-install-compute partitionfile="s:/install/custom/partition/rhels7/raid1.partitionfile" -3. provision the node: :: +3. Provision the node: :: rinstall cn1 osimage=rhels7.3-ppc64le-install-compute @@ -36,28 +34,33 @@ After the diskful nodes are up and running, you can check the RAID1 settings wit Mount command shows the ``/dev/mdx`` devices are mounted to various file systems, the ``/dev/mdx`` indicates that the RAID is being used on this node. :: # mount - /dev/md2 on / type ext4 (rw) - proc on /proc type proc (rw) - sysfs on /sys type sysfs (rw) - devpts on /dev/pts type devpts (rw,gid=5,mode=620) - tmpfs on /dev/shm type tmpfs (rw) - /dev/md0 on /boot type ext4 (rw) - none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) + ... + /dev/md1 on / type xfs (rw,relatime,attr2,inode64,noquota) + /dev/md0 on /boot type xfs (rw,relatime,attr2,inode64,noquota) + /dev/md2 on /var type xfs (rw,relatime,attr2,inode64,noquota) The file ``/proc/mdstat`` includes the RAID devices status on the system, here is an example of ``/proc/mdstat`` in the non-multipath environment: :: # cat /proc/mdstat Personalities : [raid1] - md2 : active raid1 sda5[0] sdb5[1] - 19706812 blocks super 1.1 [2/2] [UU] + md2 : active raid1 sdk2[0] sdj2[1] + 1047552 blocks super 1.2 [2/2] [UU] + resync=DELAYED bitmap: 1/1 pages [64KB], 65536KB chunk - - md1 : active raid1 sda2[0] sdb2[1] - 1048568 blocks super 1.1 [2/2] [UU] - - md0 : active raid1 sda3[0] sdb3[1] - 204788 blocks super 1.0 [2/2] [UU] - + + md3 : active raid1 sdk3[0] sdj3[1] + 1047552 blocks super 1.2 [2/2] [UU] + resync=DELAYED + + md0 : active raid1 sdk5[0] sdj5[1] + 524224 blocks super 1.0 [2/2] [UU] + bitmap: 0/1 pages [0KB], 65536KB chunk + + md1 : active raid1 sdk6[0] sdj6[1] + 973998080 blocks super 1.2 [2/2] [UU] + [==>..................] resync = 12.8% (125356224/973998080) finish=138.1min speed=102389K/sec + bitmap: 1/1 pages [64KB], 65536KB chunk + unused devices: On the system with multipath configuration, the ``/proc/mdstat`` looks like: :: From 18d7251103cb3f02330050a57106fd16f8b3e61d Mon Sep 17 00:00:00 2001 From: immarvin Date: Wed, 30 Nov 2016 04:58:03 -0500 Subject: [PATCH 3/6] docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst refine the doc on raid on rh7 --- .../manage_clusters/common/deployment/raid_cfg.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst b/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst index 22fabc71d..35d75f89b 100644 --- a/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst +++ b/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst @@ -4,7 +4,7 @@ Configure RAID before deploying the OS Overview -------- -xCAT provides an user interface :doc:`linuximage.partitionfile ` to specify the customized partition script for diskful provision, and provides some default partition scripts. +xCAT provides an user interface :doc:`linuximage.partitionfile ` to specify the customized partition script for diskful provision, and provides some default partition scripts. Deploy Diskful Nodes with RAID1 Setup on RedHat @@ -12,8 +12,8 @@ Deploy Diskful Nodes with RAID1 Setup on RedHat xCAT provides a partition script `raid1_rh.partscript `_ which setup RAID1 on 2 disks on Power8 LE server, "raid1_rh.partscript" is composed of 2 parts: -# the logic to select the disks to setup RAID -# the logic to generate the partition scheme and save it to /tmp/partitionfile in the installer. +* the logic to select the disks to setup RAID +* the logic to generate the partition scheme and save it to /tmp/partitionfile in the installer. In most scenarios, the sample partitioning script is sufficient to create a basic RAID1 across two disks and is provided as a sample to build upon. From 8ec6065322f28d0fef27476c4ce0e5740b1b3400 Mon Sep 17 00:00:00 2001 From: immarvin Date: Thu, 1 Dec 2016 01:52:22 -0500 Subject: [PATCH 4/6] refine the doc for linuximage.partitionfile --- perl-xCAT/xCAT/Schema.pm | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/perl-xCAT/xCAT/Schema.pm b/perl-xCAT/xCAT/Schema.pm index 9605c5da8..47907ce0b 100755 --- a/perl-xCAT/xCAT/Schema.pm +++ b/perl-xCAT/xCAT/Schema.pm @@ -796,7 +796,14 @@ passed as argument rather than by table value', permission => 'The mount permission of /.statelite directory is used, its default value is 755', dump => qq{The NFS directory to hold the Linux kernel dump file (vmcore) when the node with this image crashes, its format is "nfs:///". If you want to use the node's "xcatmaster" (its SN or MN), can be left blank. For example, "nfs:///" means the NFS directory to hold the kernel dump file is on the node's SN, or MN if there's no SN.}, crashkernelsize => 'the size that assigned to the kdump kernel. If the kernel size is not set, 256M will be the default value.', - partitionfile => 'The path of the configuration file which will be used to partition the disk for the node. For stateful osimages,two types of files are supported: "" which contains a partitioning definition that will be inserted directly into the generated autoinst configuration file and must be formatted for the corresponding OS installer (e.g. kickstart for RedHat, autoyast for SLES, pressed for Ubuntu). "s:" which specifies a shell script that will be run from the OS installer configuration file %pre section; the script must write the correct partitioning definition into the file /tmp/partitionfile on the node which will be included into the configuration file during the install process. For statelite osimages, partitionfile should specify ""; see the xCAT Statelite documentation for the xCAT defined format of this configuration file. For Ubuntu, besides "" or "s:", the disk name(s) to partition must be specified in traditional, non-devfs format, delimited with space, it can be specified in 2 forms: "d:" which contains the disk name(s) to partition and "s:d:" which runs in pressed/early_command and writes the disk names into the "/tmp/xcat.install_disk" . To support other specific partition methods such as RAID or LVM in Ubuntu, some additional preseed values should be specified, these values can be specified with "c:" which contains the additional pressed entries in "d-i ..." form and "s:c:" which runs in pressed/early_command and set the preseed values with "debconf-set". The multiple values should be delimited with comma "," ', + partitionfile => 'Only available for diskful osimages and statelite osimages(localdisk enabled). The full path of the partition file or the script to generate the partition file. The valid value includes: + "": For diskful osimages, the partition file contains the partition definition that will be inserted directly into the template file for os installation. The syntax and format of the partition file should confirm to the corresponding OS installer of the Linux distributions(e.g. kickstart for RedHat, autoyast for SLES, pressed for Ubuntu). For statelite osimages, when the localdisk is enabled, the partition file with specific syntax and format includes the partition scheme of the local disk, please refer to the statelite documentation for details. + "s:": a shell script to generate the partition file "/tmp/partitionfile" inside the installer before the installation start. + "d:": only available for ubuntu osimages, includes the name(s) of the disks to partition in traditional, non-devfs format(e.g, /dev/sdx, not e.g. /dev/discs/disc0/disc), and be delimited with space. All the disks involved in the partition file should be specified. + "s:d:": only available for ubuntu osimages, a script to generate the disk name file "/tmp/xcat.install_disk" inside the debian installer. This script is run in the "pressed/early_command" section. + "c:": only availbe for ubuntu osimages, contains the additional pressed entries in "d-i ..." form. This can be used to specify some additional preseed options to support RAID or LVM in Ubuntu. + "s:c:": only available for ubuntu osimages, runs in pressed/early_command and set the preseed values with "debconf-set". The multiple values should be delimited with comma "," +', driverupdatesrc => 'The source of the drivers which need to be loaded during the boot. Two types of driver update source are supported: Driver update disk and Driver rpm package. The value for this attribute should be comma separated sources. Each source should be the format tab:full_path_of_source_file. The tab keyword can be: dud (for Driver update disk) and rpm (for driver rpm). If missing the tab, the rpm format is the default. e.g. dud:/install/dud/dd.img,rpm:/install/rpm/d.rpm', comments => 'Any user-written notes.', disable => "Set to 'yes' or '1' to comment out this row.", From fdb12ecf8f5c8caed3da129f8acc9c481197c185 Mon Sep 17 00:00:00 2001 From: immarvin Date: Thu, 1 Dec 2016 02:14:15 -0500 Subject: [PATCH 5/6] refine the doc on raid --- .../manage_clusters/common/deployment/raid_cfg.rst | 6 +++--- .../guides/admin-guides/references/man5/linuximage.5.rst | 9 ++++++++- 2 files changed, 11 insertions(+), 4 deletions(-) diff --git a/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst b/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst index 35d75f89b..82aa0bbd1 100644 --- a/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst +++ b/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst @@ -10,7 +10,7 @@ xCAT provides an user interface :doc:`linuximage.partitionfile `_ which setup RAID1 on 2 disks on Power8 LE server, "raid1_rh.partscript" is composed of 2 parts: +xCAT provides a partition script `./raid1_rh.sh `_ which setup RAID1 on 2 disks on Power8 LE server, ``raid1_rh.sh`` is composed of 2 parts: * the logic to select the disks to setup RAID * the logic to generate the partition scheme and save it to /tmp/partitionfile in the installer. @@ -19,11 +19,11 @@ In most scenarios, the sample partitioning script is sufficient to create a basi 1. Obtain the partition script: :: - wget -O /install/custom/raid1_rh.partscript + wget https://raw.githubusercontent.com/xcat2/xcat-extensions/master/partition/raid1_rh.sh -O /install/custom/raid1_rh.sh 2. Associate the partition script to the osimage: :: - chdef -t osimage -o rhels7.3-ppc64le-install-compute partitionfile="s:/install/custom/partition/rhels7/raid1.partitionfile" + chdef -t osimage -o rhels7.3-ppc64le-install-compute partitionfile="s:/install/custom/raid1_rh.sh" 3. Provision the node: :: diff --git a/docs/source/guides/admin-guides/references/man5/linuximage.5.rst b/docs/source/guides/admin-guides/references/man5/linuximage.5.rst index a8f7eb915..ad5715d86 100644 --- a/docs/source/guides/admin-guides/references/man5/linuximage.5.rst +++ b/docs/source/guides/admin-guides/references/man5/linuximage.5.rst @@ -173,7 +173,14 @@ linuximage Attributes: \ **partitionfile**\ - The path of the configuration file which will be used to partition the disk for the node. For stateful osimages,two types of files are supported: "" which contains a partitioning definition that will be inserted directly into the generated autoinst configuration file and must be formatted for the corresponding OS installer (e.g. kickstart for RedHat, autoyast for SLES, pressed for Ubuntu). "s:" which specifies a shell script that will be run from the OS installer configuration file %pre section; the script must write the correct partitioning definition into the file /tmp/partitionfile on the node which will be included into the configuration file during the install process. For statelite osimages, partitionfile should specify ""; see the xCAT Statelite documentation for the xCAT defined format of this configuration file. For Ubuntu, besides "" or "s:", the disk name(s) to partition must be specified in traditional, non-devfs format, delimited with space, it can be specified in 2 forms: "d:" which contains the disk name(s) to partition and "s:d:" which runs in pressed/early_command and writes the disk names into the "/tmp/xcat.install_disk" . To support other specific partition methods such as RAID or LVM in Ubuntu, some additional preseed values should be specified, these values can be specified with "c:" which contains the additional pressed entries in "d-i ..." form and "s:c:" which runs in pressed/early_command and set the preseed values with "debconf-set". The multiple values should be delimited with comma "," + Only available for diskful osimages and statelite osimages(localdisk enabled). The full path of the partition file or the script to generate the partition file. The valid value includes: + + * ````: For diskful osimages, the partition file contains the partition definition that will be inserted directly into the template file for os installation. The syntax and format of the partition file should confirm to the corresponding OS installer of the Linux distributions(e.g. kickstart for RedHat, autoyast for SLES, pressed for Ubuntu). For statelite osimages, when the localdisk is enabled, the partition file with specific syntax and format includes the partition scheme of the local disk, please refer to the statelite documentation for details. + * ``s:``: a shell script to generate the partition file "/tmp/partitionfile" inside the installer before the installation start. + * ``d:``: only available for ubuntu osimages, includes the name(s) of the disks to partition in traditional, non-devfs format(e.g, /dev/sdx, not e.g. /dev/discs/disc0/disc), and be delimited with space. All the disks involved in the partition file should be specified. + * ``s:d:``: only available for ubuntu osimages, a script to generate the disk name file "/tmp/xcat.install_disk" inside the debian installer. This script is run in the "pressed/early_command" section. + * ``c:``: only availbe for ubuntu osimages, contains the additional pressed entries in "d-i ..." form. This can be used to specify some additional preseed options to support RAID or LVM in Ubuntu. + * ``s:c:``: only available for ubuntu osimages, runs in pressed/early_command and set the preseed values with "debconf-set". The multiple values should be delimited with comma "," From 2911746a47abba1727c1de95a0e2d770ec8b5bce Mon Sep 17 00:00:00 2001 From: immarvin Date: Thu, 1 Dec 2016 20:57:25 -0500 Subject: [PATCH 6/6] refine the doc on soft raid1 setup during node provision --- .../common/deployment/raid_cfg.rst | 16 ++++++++-------- perl-xCAT/xCAT/Schema.pm | 2 +- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst b/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst index 82aa0bbd1..0acea9a4e 100644 --- a/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst +++ b/docs/source/guides/admin-guides/manage_clusters/common/deployment/raid_cfg.rst @@ -10,28 +10,28 @@ xCAT provides an user interface :doc:`linuximage.partitionfile `_ which setup RAID1 on 2 disks on Power8 LE server, ``raid1_rh.sh`` is composed of 2 parts: - -* the logic to select the disks to setup RAID -* the logic to generate the partition scheme and save it to /tmp/partitionfile in the installer. +xCAT provides a partition script `raid1_rh.sh `_ which configures RAID1 across 2 disks on RHEL 7.x operating systems. In most scenarios, the sample partitioning script is sufficient to create a basic RAID1 across two disks and is provided as a sample to build upon. 1. Obtain the partition script: :: - wget https://raw.githubusercontent.com/xcat2/xcat-extensions/master/partition/raid1_rh.sh -O /install/custom/raid1_rh.sh + mkdir -p /install/custom/partition/ + wget https://raw.githubusercontent.com/xcat2/xcat-extensions/master/partition/raid1_rh.sh \ + -O /install/custom/partition/raid1_rh.sh 2. Associate the partition script to the osimage: :: - chdef -t osimage -o rhels7.3-ppc64le-install-compute partitionfile="s:/install/custom/raid1_rh.sh" + chdef -t osimage -o rhels7.3-ppc64le-install-compute \ + partitionfile="s:/install/custom/partition/raid1_rh.sh" 3. Provision the node: :: rinstall cn1 osimage=rhels7.3-ppc64le-install-compute -After the diskful nodes are up and running, you can check the RAID1 settings with the following commands: +After the diskful nodes are up and running, you can check the RAID1 settings with the following process: -Mount command shows the ``/dev/mdx`` devices are mounted to various file systems, the ``/dev/mdx`` indicates that the RAID is being used on this node. :: +``mount`` command shows the ``/dev/mdx`` devices are mounted to various file systems, the ``/dev/mdx`` indicates that the RAID is being used on this node. :: # mount ... diff --git a/perl-xCAT/xCAT/Schema.pm b/perl-xCAT/xCAT/Schema.pm index 47907ce0b..228ab4770 100755 --- a/perl-xCAT/xCAT/Schema.pm +++ b/perl-xCAT/xCAT/Schema.pm @@ -799,7 +799,7 @@ passed as argument rather than by table value', partitionfile => 'Only available for diskful osimages and statelite osimages(localdisk enabled). The full path of the partition file or the script to generate the partition file. The valid value includes: "": For diskful osimages, the partition file contains the partition definition that will be inserted directly into the template file for os installation. The syntax and format of the partition file should confirm to the corresponding OS installer of the Linux distributions(e.g. kickstart for RedHat, autoyast for SLES, pressed for Ubuntu). For statelite osimages, when the localdisk is enabled, the partition file with specific syntax and format includes the partition scheme of the local disk, please refer to the statelite documentation for details. "s:": a shell script to generate the partition file "/tmp/partitionfile" inside the installer before the installation start. - "d:": only available for ubuntu osimages, includes the name(s) of the disks to partition in traditional, non-devfs format(e.g, /dev/sdx, not e.g. /dev/discs/disc0/disc), and be delimited with space. All the disks involved in the partition file should be specified. + "d:": only available for ubuntu osimages, includes the name(s) of the disks to partition in traditional, non-devfs format(e.g, /dev/sdx, not e.g. /dev/discs/disc0/disc), and be delimited with space. All the disks involved in the partition file should be specified. "s:d:": only available for ubuntu osimages, a script to generate the disk name file "/tmp/xcat.install_disk" inside the debian installer. This script is run in the "pressed/early_command" section. "c:": only availbe for ubuntu osimages, contains the additional pressed entries in "d-i ..." form. This can be used to specify some additional preseed options to support RAID or LVM in Ubuntu. "s:c:": only available for ubuntu osimages, runs in pressed/early_command and set the preseed values with "debconf-set". The multiple values should be delimited with comma ","