xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-06-18 04:10:46 +00:00
Code Issues Releases Wiki Activity

modify some part depending on the comments

Browse Source
This commit is contained in:
huweihua
2015-09-08 22:54:12 -04:00
parent bcb954f8e4
commit a5d273b37e
2 changed files with 26 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
docs/source/guides/admin-guides/manage_clusters/common/deployment/create_img.rst
View File

@ -23,12 +23,26 @@ To see the attributes of a particular osimage, run
::
lsdef -t osimage <osimage-name>
Initially, some attributes of osimage is assigned to default value by xCAT, they all can work correctly, cause the files or templates invoked by those attributes are shipped with xCAT by default. If need to customize those attribute, refer to next section "Customize osimage".
Initially, some attributes of osimage is assigned to default value by xCAT, they all can work correctly, cause the files or templates invoked by those attributes are shipped with xCAT by default. If need to customize those attribute, refer to next section :doc:`Customize osimage </guides/admin-guides/manage_clusters/ppc64le/diskful/customize_image/index>`
Below is an example of osimage definitions created by 'copycds'
::
[root@server ~]# lsdef -t osimage
rhels7.2-ppc64le-install-compute (osimage)
rhels7.2-ppc64le-install-service (osimage)
rhels7.2-ppc64le-netboot-compute (osimage)
rhels7.2-ppc64le-stateful-mgmtnode (osimage)
In these osimage definitions shown above
* **<os>-<arch>-install-compute** is the default osimage definition used for diskfull installation
* **<os>-<arch>-netboot-compute** is the default osimage definition used for diskless installation
* **<os>-<arch>-install-service** is the default osimage definition used for service node deployment which shall be used in hierarchical environment
**[Below tips maybe helpful for you]**
**[Tips 1]**
If this is the same distro version as what your management node used, create a .repo file in /etc/yum.repos.d with content similar to:
::
[local-<os>-<arch>]
@ -40,7 +54,14 @@ If this is the same distro version as what your management node used, create a .
In this way, if you need install some additional RPMs into your MN later, you can simply install them by yum. Or if you are installing a software on your MN that depends some RPMs from the this disto, those RPMs will be found and installed automatically.
**[Tips 2]**
If need to change osimage name to your favorite name, below statement maybe help:
Sometime you can create/modify a osimage definition easily based on the default osimage definition. the general steps can be:
* lsdef -t osimage -z <os>-<arch>-install-compute > <filename>.stanza
* modify <filename>.stanza depending on your requirement
* cat <filename>.stanza| mkdef -z
For example, if need to change osimage name to your favorite name, below statement maybe helpful:
::
lsdef -t osimage -z rhels6.2-x86_64-install-compute | sed 's/^[^ ]\+:/mycomputeimage:/' | mkdef -z

5
docs/source/guides/admin-guides/manage_clusters/common/deployment/deploy_os.rst
View File

@ -6,6 +6,7 @@ Initialize the Compute for Deployment
XCAT use '**nodeset**' command to associate a specific image to a node which will be installed with this image.
::
nodeset <nodename> osimage=<osimage>
There are more attributes of nodeset used for some specific purpose or specific machines, for example:
@ -20,11 +21,11 @@ Start the OS Deployment
Start the deployment involves two key operations. First specify the boot device of the next boot to be network, then reboot the node:
For Power machine, those two operations can be completed by one command '**rnetboot**',
For **Power machine**, those two operations can be completed by one command '**rnetboot**'
::
rnetboot <node>
But for x server, those two operations need two independent commands.
But for **x86_64 server**, those two operations need two independent commands.
Specify the boot device boot from network next time, run
::
rsetboot <node> net