From 568016956e8f6ce5bd0ce84cfb6fb812c8a28ee4 Mon Sep 17 00:00:00 2001
From: GONG Jie <gongjie@linux.vnet.ibm.com>
Date: Sun, 31 Dec 2017 23:59:59 +0000
Subject: [PATCH] Remove trailing spaces in file
 xCAT-client/pods/man1/nodeimport.1.pod

---
 xCAT-client/pods/man1/nodeimport.1.pod | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/xCAT-client/pods/man1/nodeimport.1.pod b/xCAT-client/pods/man1/nodeimport.1.pod
index 2c3b670f7..b471eb436 100644
--- a/xCAT-client/pods/man1/nodeimport.1.pod
+++ b/xCAT-client/pods/man1/nodeimport.1.pod
@@ -74,7 +74,7 @@ To import nodes using a profile, follow the following steps:
   "__NetworkProfile_default_mn","static","static",,,,
   "__NetworkProfile_default_cn","static",,,,,
   "__ImageProfile_rhels6.2-x86_64-install-compute","static","static",,,,
-   
+
   # lsdef -t group __NetworkProfile_default_cn
   Object name: __NetworkProfile_default_cn
       grouptype=static
@@ -86,9 +86,9 @@ To import nodes using a profile, follow the following steps:
       nictypes=eth0:Ethernet
       primarynic=eth0
 
-2. Prepare a node information file. 
+2. Prepare a node information file.
 
-  Example of a node information file, a blade and a rack server defined: 
+  Example of a node information file, a blade and a rack server defined:
   # hostinfo begin
   # This entry defines a blade.
   __hostname__:
@@ -116,7 +116,7 @@ To import nodes using a profile, follow the following steps:
      slotid=1
   # hostinfo end.
 
-  Example of a node information file, a switch auto discovery node defined: 
+  Example of a node information file, a switch auto discovery node defined:
   # hostinfo begin
   # This entry defines a blade.
   __hostname__:
@@ -128,15 +128,15 @@ To import nodes using a profile, follow the following steps:
   __hostname__:
      mac=b8:ac:6f:37:59:28
      cec=mycec
-  
+
   __hostname__:
      mac=b8:ac:6f:37:59:28
      cec=mycec
      lparid=2
   # Node information file ends.
-  
+
   Example of a node information file that specifies a PowerKVM Guest node that uses KVM management:
-  
+
   # Node information file begins
   # This entry defines a PowerKVM Guest node.
   # Make sure the node 'vm01' is already created on Hypervisor
@@ -179,7 +179,7 @@ B<nicips=<nics-ip>> This is an optional item.
 
 Description: Lists the IP address for each network interface configuration (NIC) used by the node, excluding the provisioning network, where <nics-ip> is in the form <nic1>!<nic-ip1>,<nic2>!<nic-ip2>,.... For example, if you have 2 network interfaces configured, the nicips attribute should list both network interfaces:  nicips=eth1!10.10.10.11,bmc!192.168.10.3. If the nicips attribute is not specified, the IP addresses are generated automatically according to the network profile.
 
-B<rack=<rack-name>> This is an optional item. 
+B<rack=<rack-name>> This is an optional item.
 
 Description: node location info. Specify the rack name which this node will be placed into. If not specify this item, there will be no node location info set for this node. this item must be specified together with height + unit.
 
@@ -197,7 +197,7 @@ Description: node location info, for rack server only. Specify the node's start
 
 B<vmhost=<PowerKVM Hypervisior Host Name>>  This is a mandatory option for defining PowerKVM Guest nodes.
 
-Description: Specifies the vmhost of a Power KVM Guest node, where <vmhost> is the host name of PowerKVM Hypervisior. 
+Description: Specifies the vmhost of a Power KVM Guest node, where <vmhost> is the host name of PowerKVM Hypervisior.
 
 3. Import the nodes, by using the following commands. Note: If we want to import PureFlex X/P nodes, hardware profile must be set to a PureFlex hardware type.