mirror of
				https://github.com/xcat2/xcat-core.git
				synced 2025-11-04 05:12:30 +00:00 
			
		
		
		
	Remove trailing spaces in file xCAT-client/pods/man1/mkzone.1.pod
This commit is contained in:
		@@ -1,10 +1,10 @@
 | 
			
		||||
=head1 B<NAME>
 | 
			
		||||
 | 
			
		||||
B<mkzone> - Defines a new zone in the cluster. 
 | 
			
		||||
B<mkzone> - Defines a new zone in the cluster.
 | 
			
		||||
 | 
			
		||||
=head1 B<SYNOPSIS>
 | 
			
		||||
 | 
			
		||||
B<mkzone> I<zonename>  [B<--defaultzone>] [B<-k> I<full path to the ssh RSA private key>] [B<-a> I<noderange>] [B<-g>] [B<-f>] [B<-s> I<{yes|no}>] [B<-V>] 
 | 
			
		||||
B<mkzone> I<zonename>  [B<--defaultzone>] [B<-k> I<full path to the ssh RSA private key>] [B<-a> I<noderange>] [B<-g>] [B<-f>] [B<-s> I<{yes|no}>] [B<-V>]
 | 
			
		||||
 | 
			
		||||
B<mkzone> [B<-h> | B<-v>]
 | 
			
		||||
 | 
			
		||||
@@ -12,20 +12,20 @@ B<mkzone> [B<-h> | B<-v>]
 | 
			
		||||
 | 
			
		||||
The B<mkzone> command is designed to divide the xCAT cluster into multiple zones. The nodes in each zone will share common root ssh keys. This allows the nodes in a zone to be able to as root ssh to each other without password, but cannot do the same to any node in another zone. All zones share a common xCAT Management Node and database including the site table, which defines the attributes of the entire cluster.
 | 
			
		||||
The mkzone command is only supported on Linux ( No AIX support).
 | 
			
		||||
The nodes are not updated with the new root ssh keys by mkzone.  You must run updatenode -k  or xdsh -K to the nodes to update the root ssh keys to the new generated zone keys. This will also sync any service nodes with the zone keys, if you have a hierarchical cluster.   
 | 
			
		||||
The nodes are not updated with the new root ssh keys by mkzone.  You must run updatenode -k  or xdsh -K to the nodes to update the root ssh keys to the new generated zone keys. This will also sync any service nodes with the zone keys, if you have a hierarchical cluster.
 | 
			
		||||
Note: if any zones in the zone table, there must be one and only one defaultzone. Otherwise, errors will occur.
 | 
			
		||||
 | 
			
		||||
=head1 B<OPTIONS>
 | 
			
		||||
 | 
			
		||||
=over 5
 | 
			
		||||
 | 
			
		||||
=item B<-h>|B<--help> 
 | 
			
		||||
=item B<-h>|B<--help>
 | 
			
		||||
 | 
			
		||||
Displays usage information. 
 | 
			
		||||
Displays usage information.
 | 
			
		||||
 | 
			
		||||
=item B<-v>|B<--version> 
 | 
			
		||||
=item B<-v>|B<--version>
 | 
			
		||||
 | 
			
		||||
Displays command version and build date. 
 | 
			
		||||
Displays command version and build date.
 | 
			
		||||
 | 
			
		||||
=item B<-k | --sshkeypath> I<full path to the ssh RSA private key>
 | 
			
		||||
 | 
			
		||||
@@ -37,7 +37,7 @@ If -f is not used,  then it will generate a set of root ssh keys for the zone an
 | 
			
		||||
if --defaultzone is input, then it will set the zone defaultzone attribute to yes; otherwise it will set to no.
 | 
			
		||||
if --defaultzone is input and another zone is currently the default,
 | 
			
		||||
then the -f flag must be used to force a change to the new defaultzone.
 | 
			
		||||
If -f flag is not use an error will be returned and no change made. 
 | 
			
		||||
If -f flag is not use an error will be returned and no change made.
 | 
			
		||||
Note: if any zones in the zone table, there must be one and only one defaultzone. Otherwise, errors will occur.
 | 
			
		||||
 | 
			
		||||
=item B<-a | --addnoderange> I<noderange>
 | 
			
		||||
@@ -49,13 +49,13 @@ it will add the group name "zonename" to each node in the noderange.
 | 
			
		||||
=item B<-s| --sshbetweennodes> B<yes|no>
 | 
			
		||||
 | 
			
		||||
If -s entered, the zone sshbetweennodes attribute will be set to yes or no. It defaults to yes. When this is set to yes, then ssh will be setup
 | 
			
		||||
to allow passwordless root access between nodes.  If no, then root will be prompted for a password when running ssh between the nodes in the zone. 
 | 
			
		||||
to allow passwordless root access between nodes.  If no, then root will be prompted for a password when running ssh between the nodes in the zone.
 | 
			
		||||
 | 
			
		||||
=item B<-f | --force> 
 | 
			
		||||
=item B<-f | --force>
 | 
			
		||||
 | 
			
		||||
Used with the (--defaultzone) flag to override the current default zone.
 | 
			
		||||
 | 
			
		||||
=item B<-g | --assigngroup> 
 | 
			
		||||
=item B<-g | --assigngroup>
 | 
			
		||||
 | 
			
		||||
Used with the (-a) flag to create the group zonename for all nodes in the input noderange.
 | 
			
		||||
 | 
			
		||||
@@ -74,7 +74,7 @@ To make a new zone1 using defaults, enter:
 | 
			
		||||
 | 
			
		||||
 mkzone zone1
 | 
			
		||||
 | 
			
		||||
Note: with the first B<mkzone>, you will automatically get the xcatdefault zone created as the default zone.  This zone uses ssh keys from <roothome>/.ssh directory.  
 | 
			
		||||
Note: with the first B<mkzone>, you will automatically get the xcatdefault zone created as the default zone.  This zone uses ssh keys from <roothome>/.ssh directory.
 | 
			
		||||
 | 
			
		||||
=item 2.
 | 
			
		||||
To make a new zone2 using defaults and make it the default zone enter:
 | 
			
		||||
@@ -85,7 +85,7 @@ To make a new zone2 using defaults and make it the default zone enter:
 | 
			
		||||
 | 
			
		||||
To make a new zone2A using the ssh id_rsa private key in /root/.ssh:
 | 
			
		||||
 | 
			
		||||
 mkzone zone2A -k /root/.ssh 
 | 
			
		||||
 mkzone zone2A -k /root/.ssh
 | 
			
		||||
 | 
			
		||||
=item 4.
 | 
			
		||||
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user