15 Specify_the_disk_partitions_during_diskfull_install

ligc edited this page 2015-07-30 04:22:49 -04:00

Table of Contents

• overview
• External Interface
• use partition definition file
• use script to create partition definition
• Internal implementation
• Limitation
• Other Design Considerations

Table of Contents

• overview
• External Interface
  • use partition definition file
  • use script to create partition definition
• Internal implementation
• Limitation
• Other Design Considerations

Design_Warning

overview

xCAT use "nodeset <noderange> install" to create the install configure file(RHEL/CentOS/Fedora/SL/ESXI call kickstart file, SLES/SUSE/WINDOWS use xml file, Debian/Ubuntu call squeeze file) for each node. Command nodeset use *.tmpl file as a template and create each node's configure file. Currently the partition part in the *.tmpl file are hard code. There is a new requirement which from PCM is "Ability to specify the disk partitions that should be setup during diskfull install".

External Interface

use partition definition file

1. Write a file contains the partition definition. The definition format should be based on the OS type.

for RHEL/CentOS/Fedora/SL/ESXI likes:

 part swap --size 2048
 part / --size 1 --grow --fstype ext3

for SLES/SUSE likes:

   <drive>
     <device>/dev/sda</device>
     <initialize config:type="boolean">true</initialize>
     <use>all</use>
   </drive>

for Windows likes:

 <DiskConfiguration>
   <WillShowUI>OnError</WillShowUI>
   <Disk>
     <DiskID>0</DiskID>
     <WillWipeDisk>true</WillWipeDisk>
     <CreatePartitions>
       <CreatePartition>
         <Order>1</Order>
         <Type>Primary</Type>
         <Extend>true</Extend>
         </CreatePartition>
        </CreatePartitions>
   </Disk>
 </DiskConfiguration>

for Debian/Ubuntu likes:

 d-i partman-auto/expert_recipe string               \
     boot-root ::                                    \
             40 50 100 ext3                          \
             $primary{ } $bootable{ }                \
             method{ format } format{ }              \
             use_filesystem{ } filesystem{ ext3 }    \
             mountpoint{ /boot }                     \

2. use "chdef -t osimage <imagename> partitionfile=<definition file absolute path>" to modify the osimage object.

3. run "nodeset <noderange> install". The install configure file will contains the partition definition in the specified file.

use script to create partition definition

1. write a script file, which can create a partition definition, and save the definition into /tmp/partitionfile (this file name can not be changed). Like:

 echo "part swap --size 1024" > /tmp/partitionfile
 echo "part / --size 1 --grow --fstype ext3" >> /tmp/partitionfile

2. use "chdef -t osimage <imagename> partitionfile=s:<script file absolute path>" to modify the osimage object.

3. run "nodeset <noderange> install". The install configure file will contains the script which contained in %pre part and use "%include /tmp/partitionfile" to define the partition strategy.

Internal implementation

1. Database change: add an attribute partitionfile into osimage object. Put the partitionfile attribute into the linuximage schema. The user can use the chdef command to set/change the partitionfile attribute for the image.

2. *.tmpl file change: find out the partition definition subset in all *.tmpl files, use special comment line embrace the subset.

• for non-xml format .tmpl file, use #XCAT_PARTITION_START# and #XCAT_PARTITION_END# to embrace the subset.
• for xml format .tmpl file, useandto embrace the subset.

3. template.pm :

• In mkinstall():

  a. get the osimage's partitionfile attribute. b. call subvars(), use the partitionfile attribute value as a parameter.

• In subvars();

  a. if the partitionfile is not exist: do not do any operations (will use the default definition in our *.tmpl file). b. if the partitionfile is exist, i. If the partitionfile is start with s:... , add the content in the partitionfile into %pre part in the kickstartfile, use %include /tmp/partitionfile to replace the subset witch embrace by comment line ii. else, If partitionfile is readable, use the content in the partition file to replace the subset witch embrace by comment line(will use the specified definition).

Limitation

• only the .tmpl files from xCAT-server package can work.
• use script to create partition definition only works on redhat and sles linux. other version linux is still under design.

Other Design Considerations

• Required reviewers: Bruce Potter, Li Guang Cheng
• Required approvers: Bruce Potter
• Database schema changes: N/A
• Affect on other components: N/A
• External interface changes, documentation, and usability issues: add the document how to use this function
• Packaging, installation, dependencies: N/A
• Portability and platforms (HW/SW) supported: N/A
• Performance and scaling considerations: N/A
• Migration and coexistence: N/A
• Serviceability: N/A
• Security: N/A
• NLS and accessibility: N/A
• Invention protection: N/A

News

• Apr 22, 2016: xCAT 2.11.1 released.
• Mar 11, 2016: xCAT 2.9.3 (AIX only) released.
• Dec 11, 2015: xCAT 2.11 released.
• Nov 11, 2015: xCAT 2.9.2 (AIX only) released.
• Jul 30, 2015: xCAT 2.10 released.
• Jul 30, 2015: xCAT migrates from sourceforge to github
• Jun 26, 2015: xCAT 2.7.9 released.
• Mar 20, 2015: xCAT 2.9.1 released.
• Dec 12, 2014: xCAT 2.9 released.
• Sep 5, 2014: xCAT 2.8.5 released.
• May 23, 2014: xCAT 2.8.4 released.
• Jan 24, 2014: xCAT 2.7.8 released.
• Nov 15, 2013: xCAT 2.8.3 released.
• Jun 26, 2013: xCAT 2.8.2 released.
• May 17, 2013: xCAT 2.7.7 released.
• May 10, 2013: xCAT 2.8.1 released.
• Feb 28, 2013: xCAT 2.8 released.
• Nov 30, 2012: xCAT 2.7.6 released.
• Oct 29, 2012: xCAT 2.7.5 released.
• Aug 27, 2012: xCAT 2.7.4 released.
• Jun 22, 2012: xCAT 2.7.3 released.
• May 25, 2012: xCAT 2.7.2 released.
• Apr 20, 2012: xCAT 2.7.1 released.
• Mar 19, 2012: xCAT 2.7 released.
• Mar 15, 2012: xCAT 2.6.11 released.
• Jan 23, 2012: xCAT 2.6.10 released.
• Nov 15, 2011: xCAT 2.6.9 released.
• Sep 30, 2011: xCAT 2.6.8 released.
• Aug 26, 2011: xCAT 2.6.6 released.
• May 20, 2011: xCAT 2.6 released.
• Feb 14, 2011: Watson plays on Jeopardy and is managed by xCAT!
• xCAT Release Notes Summary
• xCAT OS And Hw Support Matrix
• xCAT Test Environment Summary

History

• Oct 22, 2010: xCAT 2.5 released.
• Apr 30, 2010: xCAT 2.4 is released.
• Oct 31, 2009: xCAT 2.3 released.
  xCAT's 10 year anniversary!
• Apr 16, 2009: xCAT 2.2 released.
• Oct 31, 2008: xCAT 2.1 released.
• Sep 12, 2008: Support for xCAT 2
  can now be purchased!
• June 9, 2008: xCAT breaths life into
  (at the time) the fastest
  supercomputer on the planet
• May 30, 2008: xCAT 2.0 for Linux
  officially released!
• Oct 31, 2007: IBM open sources
  xCAT 2.0 to allow collaboration
  among all of the xCAT users.
• Oct 31, 1999: xCAT 1.0 is born!
  xCAT started out as a project in
  IBM developed by Egan Ford. It
  was quickly adopted by customers
  and IBM manufacturing sites to
  rapidly deploy clusters.