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

Remove trailing spaces in file xCAT-client/pods/man1/chhypervisor.1.pod

Browse Source
This commit is contained in:
GONG Jie 2017-12-31 23:59:59 +00:00
parent 144b9168a9
commit f83d5e0a19
1 changed files with 32 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

64
xCAT-client/pods/man1/chhypervisor.1.pod
View File

@ -52,10 +52,10 @@ B<chhypervisor> I<noderange> [B<--smcli> I<function> I<arguments>]
The B<chhypervisor> command can be used to configure the RHEV-h.
The rhev-h host will register to the rhev-m automatically, but admin needs to
The rhev-h host will register to the rhev-m automatically, but admin needs to
approve the host can be added to the 'cluster' with B<-a> flag .
After registering, the network interfaces of host need to be added to the 'network' of
After registering, the network interfaces of host need to be added to the 'network' of
RHEV. And the power management for the host should be configured so that
rhev-m could make proper decision when certain host encountered error.
@ -75,8 +75,8 @@ B<hypervisor.mgr> - The rhev manager (The FQDN of rhev-m server) for the host.
B<hypervisor.interface> - The configuration for the nics. Refer to B<-n>.
B<hypervisor.cluster> - The cluster that the host will be added to. The
default is 'Default' cluster if not specified.
B<hypervisor.cluster> - The cluster that the host will be added to. The
default is 'Default' cluster if not specified.
=back
@ -94,45 +94,45 @@ Before approve, the status of the host must be 'pending_approval'.
=item B<-n>
Configure the network interfaces for the host.
Note: This operation only can be run when host is in 'maintenance mode'.
Note: This operation only can be run when host is in 'maintenance mode'.
Use B<-d> to switch the host to 'maintenance' mode.
The interfaces which configured in hypervisor.interface will be added
to the network of RHEV.
The format of hypervisor.interface is multiple [network:interfacename:
protocol:IP:netmask:gateway] sections separated with '|'. For example:
protocol:IP:netmask:gateway] sections separated with '|'. For example:
[rhevm2:eth0:static:10.1.0.236:255.255.255.0:0.0.0.0].
=over 2
B<network> - The logic network which has been created by 'cfgve -t nw'
B<network> - The logic network which has been created by 'cfgve -t nw'
or the default management network 'rhevm'.
B<interfacename> - Physical network name: 'eth0','eth1'...
B<protocol> - To identify which boot protocol to use for the interface: dhcp
B<protocol> - To identify which boot protocol to use for the interface: dhcp
or static.
B<IP> - The IP address for the interface.
B<netmask> - The network mask for the interface.
B<gateway> - The gateay for the interface. This field only can be set when
the interface is added to 'rhevm' network.
B<gateway> - The gateay for the interface. This field only can be set when
the interface is added to 'rhevm' network.
=back
=item B<-p>
Configure the power management for the host.
The power management must be configured for the rhev-h host to make the
rhev-m to monitor the power status of the host, so that when certain host
The power management must be configured for the rhev-h host to make the
rhev-m to monitor the power status of the host, so that when certain host
failed to function, rhev-m will fail over certain role like SPM to other active host.
For rack mounted server, the bmc IP and user:password need to be set for the
power management (These parameters are gotten from ipmi table). rhev-m uses the
ipmi protocol to get the power status of the host.
For rack mounted server, the bmc IP and user:password need to be set for the
power management (These parameters are gotten from ipmi table). rhev-m uses the
ipmi protocol to get the power status of the host.
=item B<-e>
To activate the host.
@ -151,9 +151,9 @@ Display usage message.
=item B<--adddisk2pool> I<function> I<region> I<volume> I<group>
Add a disk to a disk pool defined in the EXTENT CONTROL. Function type can be
either: (4) Define region as full volume and add to group OR (5) Add existing
region to group. If the volume already exists in the EXTENT CONTROL, use
Add a disk to a disk pool defined in the EXTENT CONTROL. Function type can be
either: (4) Define region as full volume and add to group OR (5) Add existing
region to group. If the volume already exists in the EXTENT CONTROL, use
function 5. If the volume does not exist in the EXTENT CONTROL, but is attached
to SYSTEM, use function 4.
@ -171,15 +171,15 @@ Create a virtual switch.
=item B<--addzfcp2pool> I<pool> I<status> I<wwpn> I<lun> I<size> I<owner>
Add a zFCP device to a device pool defined in xCAT. The device must have been
carved up in the storage controller and configured with a WWPN/LUN before it
can be added to the xCAT storage pool. z/VM does not have the ability to
Add a zFCP device to a device pool defined in xCAT. The device must have been
carved up in the storage controller and configured with a WWPN/LUN before it
can be added to the xCAT storage pool. z/VM does not have the ability to
communicate directly with the storage controller to carve up disks dynamically.
=item B<--removediskfrompool> I<function> I<region> I<group>
Remove a disk from a disk pool defined in the EXTENT CONTROL. Function type can
be either: (1) Remove region, (2) Remove region from group, (3) Remove region
Remove a disk from a disk pool defined in the EXTENT CONTROL. Function type can
be either: (1) Remove region, (2) Remove region from group, (3) Remove region
from all groups, OR (7) Remove entire group .
=item B<--removescsi> I<device_number> I<persist (YES or NO)>
@ -200,11 +200,11 @@ Remove a zFCP device from a device pool defined in xCAT.
=item B<--smcli> I<function> I<arguments>
Execute a SMAPI function. A list of APIs supported can be found by using the
help flag, e.g. chhypervisor pokdev61 --smcli -h. Specific arguments associated
with a SMAPI function can be found by using the help flag for the function,
e.g. chhypervisor pokdev61 --smcli Image_Query_DM -h. Only z/VM 6.2 and older
SMAPI functions are supported at this time. Additional SMAPI functions will be
Execute a SMAPI function. A list of APIs supported can be found by using the
help flag, e.g. chhypervisor pokdev61 --smcli -h. Specific arguments associated
with a SMAPI function can be found by using the help flag for the function,
e.g. chhypervisor pokdev61 --smcli Image_Query_DM -h. Only z/VM 6.2 and older
SMAPI functions are supported at this time. Additional SMAPI functions will be
added in subsequent zHCP versions.
=back
@ -256,22 +256,22 @@ To deactivate the host 'host1', enter:
To add a disk to a disk pool defined in the EXTENT CONTROL, enter:
chhypervisor pokdev61 --adddisk2pool 4 DM1234 DM1234 POOL1
=item 2.
To add a zFCP device to a device pool defined in xCAT, enter:
chhypervisor pokdev61 --addzfcp2pool zfcp1 free 500501234567C890 4012345600000000 8G
=item 3.
To remove a region from a group in the EXTENT CONTROL, enter:
chhypervisor pokdev61 --removediskfrompool 2 DM1234 POOL1
=item 4.
To remove a zFCP device from a device pool defined in xCAT, enter:
chhypervisor pokdev61 --removezfcpfrompool zfcp1 4012345600000000 500501234567C890
=item 5.
To execute a SMAPI function (Image_Query_DM), enter: