Revision acd9fa11 man/hspace.rst

b/man/hspace.rst
250 250 
  are reported by RAPI as such, or that have "?" in file-based input
251 251 
  in any numeric fields.
252 252 

  		





  253
  
  
    
-t *datafile*, --text-data=*datafile*


  		





  254
  
  
    
  The name of the file holding node and instance information (if not


  		





  255
  
  
    
  collecting via RAPI or LUXI). This or one of the other backends must


  		





  256
  
  
    
  be selected.


  		





  257
  
  
    

  		





  258
  253
  
    
-S *filename*, --save-cluster=*filename*


  		





  259
  254
  
    
  If given, the state of the cluster at the end of the allocation is


  		





  260
  255
  
    
  saved to a file named *filename.alloc*, and if tiered allocation is


  		





  261
  256
  
    
  enabled, the state after tiered allocation will be saved to


  		





  262
  257
  
    
  *filename.tiered*. This allows re-feeding the cluster state to


  		





  263
  258
  
    
  either hspace itself (with different parameters) or for example


  		





  264
  
  
    
  hbal.


  		





  
  259
  
    
  hbal, via the ``-t`` option.


  		





  
  260
  
    

  		





  
  261
  
    
-t *datafile*, --text-data=*datafile*


  		





  
  262
  
    
  Backend specification: the name of the file holding node and instance


  		





  
  263
  
    
  information (if not collecting via RAPI or LUXI). This or one of the


  		





  
  264
  
    
  other backends must be selected. The option is described in the man


  		





  
  265
  
    
  page **htools**(1).


  		





  265
  266
  
    

  		





  266
  267
  
    
-m *cluster*


  		





  267
  
  
    
 Collect data directly from the *cluster* given as an argument via


  		





  268
  
  
    
 RAPI. If the argument doesn't contain a colon (:), then it is


  		





  269
  
  
    
 converted into a fully-built URL via prepending ``https://`` and


  		





  270
  
  
    
 appending the default RAPI port, otherwise it's considered a


  		





  271
  
  
    
 fully-specified URL and is used as-is.


  		





  
  268
  
    
  Backend specification: collect data directly from the *cluster* given


  		





  
  269
  
    
  as an argument via RAPI. The option is described in the man page


  		





  
  270
  
    
  **htools**(1).


  		





  272
  271
  
    

  		





  273
  272
  
    
-L [*path*]


  		





  274
  
  
    
  Collect data directly from the master daemon, which is to be


  		





  275
  
  
    
  contacted via the luxi (an internal Ganeti protocol). An optional


  		





  276
  
  
    
  *path* argument is interpreted as the path to the unix socket on


  		





  277
  
  
    
  which the master daemon listens; otherwise, the default path used by


  		





  278
  
  
    
  ganeti when installed with *--localstatedir=/var* is used.


  		





  
  273
  
    
  Backend specification: collect data directly from the master daemon,


  		





  
  274
  
    
  which is to be contacted via LUXI (an internal Ganeti protocol). The


  		





  
  275
  
    
  option is described in the man page **htools**(1).


  		





  279
  276
  
    

  		





  280
  277
  
    
--simulate *description*


  		





  281
  
  
    
  Instead of using actual data, build an empty cluster given a node


  		





  282
  
  
    
  description. The *description* parameter must be a comma-separated


  		





  283
  
  
    
  list of five elements, describing in order:


  		





  284
  
  
    

  		





  285
  
  
    
  - the allocation policy for this node group (*preferred*, *allocable*


  		





  286
  
  
    
    or *unallocable*, or alternatively the short forms *p*, *a* or *u*)


  		





  287
  
  
    
  - the number of nodes in the cluster


  		





  288
  
  
    
  - the disk size of the nodes (default in mebibytes, units can be used)


  		





  289
  
  
    
  - the memory size of the nodes (default in mebibytes, units can be used)


  		





  290
  
  
    
  - the cpu core count for the nodes


  		





  291
  
  
    

  		





  292
  
  
    
  An example description would be **preferred,B20,100G,16g,4**


  		





  293
  
  
    
  describing a 20-node cluster where each node has 100GB of disk


  		





  294
  
  
    
  space, 16GiB of memory and 4 CPU cores. Note that all nodes must


  		





  295
  
  
    
  have the same specs currently.


  		





  296
  
  
    

  		





  297
  
  
    
  This option can be given multiple times, and each new use defines a


  		





  298
  
  
    
  new node group. Hence different node groups can have different


  		





  299
  
  
    
  allocation policies and node count/specifications.


  		





  
  278
  
    
  Backend specification: similar to the **-t** option, this allows


  		





  
  279
  
    
  overriding the cluster data with a simulated cluster. For details


  		





  
  280
  
    
  about the description, see the man page **htools**(1).


  		





  300
  281
  
    

  		





  301
  282
  
    
--tiered-alloc *spec*


  		





  302
  283
  
    
  Besides the standard, fixed-size allocation, also do a tiered


  		












Also available in:
  Unified diff