Revision 2a50e2e8

b/doc/walkthrough.rst
478 478
      - initrd_path: default ()
479 479
    Hardware:
480 480
      - VCPUs: 1
481
      - memory: 128MiB
481
      - maxmem: 256MiB
482
      - minmem: 512MiB
482 483
      - NICs:
483 484
        - nic/0: MAC: aa:00:00:78:da:63, IP: None, mode: bridged, link: xen-br0
484 485
    Disks:
......
857 858

  
858 859
  node1# gnt-instance modify -B memory=4G instance1
859 860
  Modified instance instance1
860
   - be/memory -> 4096
861
   - be/maxmem -> 4096
862
   - be/minmem -> 4096
861 863
  Please don't forget that these parameters take effect only at the next start of the instance.
862 864
  node1# gnt-instance modify …
863 865

  
......
915 917

  
916 918
- try to manually move instances around (but this can become complicated
917 919
  for any non-trivial cluster)
918
- try to reduce memory of some instances to accommodate the available
919
  node memory
920
- try to reduce the minimum memory of some instances on the source node
921
  of the N+1 failure (in the example above ``node1``): this will allow
922
  it to start and be failed over/migrated with less than its maximum
923
  memory
924
- try to reduce the runtime/maximum memory of some instances on the
925
  destination node of the N+1 failure (in the example above ``node2``)
926
  to create additional available node memory (check the :doc:`admin`
927
  guide for what Ganeti will and won't automatically do in regards to
928
  instance runtime memory modification)
920 929
- if Ganeti has been built with the htools package enabled, you can run
921 930
  the ``hbal`` tool which will try to compute an automated cluster
922 931
  solution that complies with the N+1 rule

Also available in: Unified diff