Revision aa279109 NEWS

b/NEWS
11 11 
  opcode from Ganeti. This lead to incompatible changes in the format of
12 12 
  the JSON file. It's now not a custom dict anymore but a dict
13 13 
  compatible with the ``OpInstanceCreate`` opcode.
14 
- Parent directories for file storage need now to be listed in
15 
  ``$sysconfdir/ganeti/file-storage-paths``. ``cfgupgrade`` will write
16 
  the file automatically based on old configuration values, but it can
17 
  not distribute it across all nodes and the file contents should be
14 
- Parent directories for file storage need to be listed in
15 
  ``$sysconfdir/ganeti/file-storage-paths`` now. ``cfgupgrade`` will
16 
  write the file automatically based on old configuration values, but it
17 
  can not distribute it across all nodes and the file contents should be
18 18 
  verified. Use ``gnt-cluster copyfile
19 19 
  $sysconfdir/ganeti/file-storage-paths`` once the cluster has been
20 20 
  upgraded. The reason for requiring this list of paths now is that
......
24 24 
  Ganeti does not permit arbitrary paths to be passed.
25 25 
- The parsing of the variants file for OSes (see
26 26 
  :manpage:`ganeti-os-interface(8)` has been slightly changed: now empty
27 
  lines and comment lines are ignored for better readability.
28 
- The ``setup-ssh`` tool added in Ganeti 2.2 has been replaced.
29 
  ``gnt-node add`` now invokes a new tool on the destination node, named
30 
  ``prepare-node-join``, to configure the SSH daemon. Paramiko is no
31 
  longer necessary to configure nodes' SSH daemons via ``gnt-node add``.
27 
  lines and comment lines (starting with ``#``) are ignored for better
28 
  readability.
29 
- The ``setup-ssh`` tool added in Ganeti 2.2 has been replaced and is no
30 
  longer available. ``gnt-node add`` now invokes a new tool on the
31 
  destination node, named ``prepare-node-join``, to configure the SSH
32 
  daemon. Paramiko is no longer necessary to configure nodes' SSH
33 
  daemons via ``gnt-node add``.
32 34 
- A new user option, :pyeval:`rapi.RAPI_ACCESS_READ`, has been added
33 35 
  for RAPI users. It allows granting permissions to query for
34 36 
  information to a specific user without giving
......
40 42 
- Draining (``gnt-cluster queue drain``) and un-draining the job queue
41 43 
  (``gnt-cluster queue undrain``) now affects all nodes in a cluster and
42 44 
  the flag is not reset after a master failover.
45 
- Instance creations now support the use of opportunistic locking,
46 
  potentially speeding up the (parallel) creation of multiple instances.
47 
  This feature is currently only available via the :doc:`RAPI
48 
  <rapi>` interface and when an instance allocator is used. If the
49 
  ``opportunistic_locking`` parameter is set the opcode will try to
50 
  acquire as many locks as possible, but will not wait for any locks
51 
  held by other opcodes. If the not enough resources can be found to
52 
  allocate the instance, the temporary error code
53 
  :pyeval:`errors.ECODE_TEMP_NORES` is returned. The operation can be
54 
  retried thereafter, with or without opportunistic locking.
43 55 

  		





  44
  56
  
    

  		





  45
  57
  
    
Version 2.6.1


  		












Also available in:
  Unified diff