Revision 7322bf7b man/gnt-cluster.rst

b/man/gnt-cluster.rst
27 27

  
28 28
Activates the master IP on the master node.
29 29

  
30
ADD-TAGS
31
~~~~~~~~
32

  
33
**add-tags** [\--from *file*] {*tag*...}
34

  
35
Add tags to the cluster. If any of the tags contains invalid
36
characters, the entire operation will abort.
37

  
38
If the ``--from`` option is given, the list of tags will be
39
extended with the contents of that file (each line becomes a tag).
40
In this case, there is not need to pass tags on the command line
41
(if you do, both sources will be used). A file name of - will be
42
interpreted as stdin.
43

  
44 30
COMMAND
45 31
~~~~~~~
46 32

  
......
522 508
For details about how to use ``--hypervisor-state`` and ``--disk-state``
523 509
have a look at **ganeti**(7).
524 510

  
525
LIST-TAGS
526
~~~~~~~~~
527

  
528
**list-tags**
529

  
530
List the tags of the cluster.
531

  
532 511
MASTER-FAILOVER
533 512
~~~~~~~~~~~~~~~
534 513

  
......
680 659
See **ganeti(7)** for a description of ``--submit`` and other common
681 660
options.
682 661

  
683
REMOVE-TAGS
684
~~~~~~~~~~~
685

  
686
**remove-tags** [\--from *file*] {*tag*...}
687

  
688
Remove tags from the cluster. If any of the tags are not existing
689
on the cluster, the entire operation will abort.
690

  
691
If the ``--from`` option is given, the list of tags to be removed will
692
be extended with the contents of that file (each line becomes a tag).
693
In this case, there is not need to pass tags on the command line (if
694
you do, tags from both sources will be removed). A file name of - will
695
be interpreted as stdin.
696

  
697 662
RENAME
698 663
~~~~~~
699 664

  
......
760 725
output. Otherwise it will log details about the inconsistencies in
761 726
the configuration.
762 727

  
763
SEARCH-TAGS
764
~~~~~~~~~~~
765

  
766
**search-tags** {*pattern*}
767

  
768
Searches the tags on all objects in the cluster (the cluster
769
itself, the nodes and the instances) for a given pattern. The
770
pattern is interpreted as a regular expression and a search will be
771
done on it (i.e. the given pattern is not anchored to the beggining
772
of the string; if you want that, prefix the pattern with ^).
773

  
774
If no tags are matching the pattern, the exit code of the command
775
will be one. If there is at least one match, the exit code will be
776
zero. Each match is listed on one line, the object and the tag
777
separated by a space. The cluster will be listed as /cluster, a
778
node will be listed as /nodes/*name*, and an instance as
779
/instances/*name*. Example:
780

  
781
::
782

  
783
    # gnt-cluster search-tags time
784
    /cluster ctime:2007-09-01
785
    /nodes/node1.example.com mtime:2007-10-04
786

  
787 728
VERIFY
788 729
~~~~~~
789 730

  
......
857 798

  
858 799
Show the cluster version.
859 800

  
801
Tags
802
~~~~
803

  
804
ADD-TAGS
805
^^^^^^^^
806

  
807
**add-tags** [\--from *file*] {*tag*...}
808

  
809
Add tags to the cluster. If any of the tags contains invalid
810
characters, the entire operation will abort.
811

  
812
If the ``--from`` option is given, the list of tags will be
813
extended with the contents of that file (each line becomes a tag).
814
In this case, there is not need to pass tags on the command line
815
(if you do, both sources will be used). A file name of - will be
816
interpreted as stdin.
817

  
818
LIST-TAGS
819
^^^^^^^^^
820

  
821
**list-tags**
822

  
823
List the tags of the cluster.
824

  
825
REMOVE-TAGS
826
^^^^^^^^^^^
827

  
828
**remove-tags** [\--from *file*] {*tag*...}
829

  
830
Remove tags from the cluster. If any of the tags are not existing
831
on the cluster, the entire operation will abort.
832

  
833
If the ``--from`` option is given, the list of tags to be removed will
834
be extended with the contents of that file (each line becomes a tag).
835
In this case, there is not need to pass tags on the command line (if
836
you do, tags from both sources will be removed). A file name of - will
837
be interpreted as stdin.
838

  
839
SEARCH-TAGS
840
^^^^^^^^^^^
841

  
842
**search-tags** {*pattern*}
843

  
844
Searches the tags on all objects in the cluster (the cluster
845
itself, the nodes and the instances) for a given pattern. The
846
pattern is interpreted as a regular expression and a search will be
847
done on it (i.e. the given pattern is not anchored to the beggining
848
of the string; if you want that, prefix the pattern with ^).
849

  
850
If no tags are matching the pattern, the exit code of the command
851
will be one. If there is at least one match, the exit code will be
852
zero. Each match is listed on one line, the object and the tag
853
separated by a space. The cluster will be listed as /cluster, a
854
node will be listed as /nodes/*name*, and an instance as
855
/instances/*name*. Example:
856

  
857
::
858

  
859
    # gnt-cluster search-tags time
860
    /cluster ctime:2007-09-01
861
    /nodes/node1.example.com mtime:2007-10-04
862

  
860 863
.. vim: set textwidth=72 :
861 864
.. Local Variables:
862 865
.. mode: rst

Also available in: Unified diff