Revision e0897adf man/gnt-cluster.sgml

b/man/gnt-cluster.sgml
2 2

  
3 3
  <!-- Fill in your name for FIRSTNAME and SURNAME. -->
4 4
  <!-- Please adjust the date whenever revising the manpage. -->
5
  <!ENTITY dhdate      "<date>February 12, 2009</date>">
5
  <!ENTITY dhdate      "<date>June 08, 2010</date>">
6 6
  <!-- SECTION should be 1-8, maybe w/ subsection other parameters are
7 7
       allowed: see man(7), man(1). -->
8 8
  <!ENTITY dhsection   "<manvolnum>8</manvolnum>">
......
30 30
    &dhucpackage;
31 31

  
32 32
    &dhsection;
33
    <refmiscinfo>ganeti 2.0</refmiscinfo>
33
    <refmiscinfo>Ganeti 2.2</refmiscinfo>
34 34
  </refmeta>
35 35
  <refnamediv>
36 36
    <refname>&dhpackage;</refname>
37 37

  
38
    <refpurpose>ganeti administration, cluster-wide</refpurpose>
38
    <refpurpose>Ganeti administration, cluster-wide</refpurpose>
39 39
  </refnamediv>
40 40
  <refsynopsisdiv>
41 41
    <cmdsynopsis>
......
50 50

  
51 51
    <para>
52 52
      The <command>&dhpackage;</command> is used for cluster-wide
53
      administration in the ganeti system.
53
      administration in the Ganeti system.
54 54
    </para>
55 55

  
56 56
  </refsect1>
......
293 293

  
294 294
      <para>
295 295
        The <option>-g</option> option will let you specify a volume group
296
        different than 'xenvg' for ganeti to use when creating instance disks.
296
        different than "xenvg" for Ganeti to use when creating instance disks.
297 297
        This volume group must have the same name on all nodes. Once the
298 298
        cluster is initialized this can be altered by using the
299 299
        <command>modify</command> command. If you don't want to use lvm
......
564 564
      <para>
565 565
        The <option>--no-voting</option> option skips the remote node agreement
566 566
        checks. This is dangerous, but necessary in some cases (for example
567
        failing over the master role in a 2 node cluster with the original master
568
        down). If the original master then comes up, it won't be able to start
569
        its master daemon because it won't have enough votes, but so won't the
570
        new master, if the master daemon ever needs a restart. You can pass
571
        --no-voting to ganeti-masterd on the new master to solve this problem,
572
        and gnt-cluster redist-conf to make sure the cluster is consistent again.
567
        failing over the master role in a 2 node cluster with the original
568
        master down). If the original master then comes up, it won't be able to
569
        start its master daemon because it won't have enough votes, but so
570
        won't the new master, if the master daemon ever needs a restart. You
571
        can pass <option>--no-voting</option> to
572
        <command>ganeti-masterd</command> on the new master to solve this
573
        problem, and run <command>gnt-cluster redist-conf</command> to make
574
        sure the cluster is consistent again.
573 575
      </para>
574 576

  
575 577
    </refsect2>
......
900 902
      </para>
901 903

  
902 904
      <para>
903
        If the <option>--no-nplus1-mem</option> option is given, ganeti won't
905
        If the <option>--no-nplus1-mem</option> option is given, Ganeti won't
904 906
        check whether if it loses a node it can restart all the instances on
905 907
        their secondaries (and report an error otherwise).
906 908
      </para>

Also available in: Unified diff