xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-05-29 09:13:08 +00:00
Code Issues Releases Wiki Activity

update the rst file about the rscan

Browse Source
This commit is contained in:
penguhyang 2016-01-21 22:39:43 -05:00
parent 7e3817fe5f
commit 6dce0200d9
1 changed files with 53 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

53
docs/source/guides/admin-guides/references/man1/rscan.1.rst
View File

@ -35,6 +35,8 @@ The rscan command lists hardware information for each node managed by the hardwa
For the management module of blade, if the blade server is a Flex system P node, the fsp belongs to the blade server also will be scanned.
For the KVM host, all the KVM guests on the specified KVM host will be scanned. Note: currently rscan can only get the information of the "disk" device on the kvm guest with the underlying source as a "file" on the KVM host.
Note: The first line of the output always contains information about the hardware control point. When using the rscan command to generate output for HMC or IVM hardware control points, it provides the FSPs and BPAs as part of the output. The only exception is the rscan -u flag which provides updates made hardware control point in the xCAT database.
@ -53,10 +55,16 @@ OPTIONS
For the Flex system manager, both the blade server and fsp object of xCAT will be updated if the mpa and slot id are matched to the object which has been defined in the xCAT database.
For the KVM host, the information of the KVM guests which have been defined in xCAT database will be updated.
Note: only the matched object will be updated.
\ **-n**\ For KVM host, the information of the KVM guests, which are not defined in xCAT database yet, will be written into xCAT database.
\ **-w**\ Writes output to xCAT database.
For KVM host, updates the information of the KVM guests which have been defined in xCAT database with the same node name and KVM host, creates the definition of the KVM guests which do not exist in xCAT database , and notifies user about the conflicting KVM guests that the name exist in xCAT database but the kvm host is different.
\ **-x**\ XML format.
\ **-z**\ Stanza formated output.
@ -279,6 +287,51 @@ Output is similar to:
blade [SN#YL10JH184079] Matched To =>[cmm01node03]
8. To scan the KVM host "hyp01", list all the KVM guest information on the KVM host in stanza format and write the KVM guest information into xCAT database:
\ *rscan hyp01 -z -w*\
Output is similar to:
.. code-block:: perl
kvm1
arch=x86_64
mac=
mgt=kvm
vmcpus=1
vmhost=hyp01
vmmemory=1024
vmnicnicmodel=virtio
vmnics=virbr0
vmstorage=/install/vms/kvm1.hda.qcow2
kvm2
arch=x86_64
mac=
mgt=kvm
vmcpus=2
vmhost=hyp01
vmmemory=1024
vmnicnicmodel=virtio
vmnics=virbr0
vmstorage=/install/vms/kvm2.hda.qcow2
9. To update definitions of kvm guest, which is managed by hypervisor hyp01, enter:
\ *rscan hyp01 -u*\
Output is similar to:
.. code-block:: perl
type name hypervisor id cpu memory nic disk
kvm kvm2 hyp01 12 2 1024 virbr0 /install/vms/kvm2.hda.qcow2
kvm kvm1 hyp01 10 1 1024 virbr0 /install/vms/kvm1.hda.qcow2
*****
FILES