Revision 7322bf7b
| 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 |
| b/man/gnt-node.rst | ||
|---|---|---|
| 78 | 78 |
# gnt-node add -g group2 -s 192.0.2.9 node9.group2.example.com |
| 79 | 79 |
|
| 80 | 80 |
|
| 81 |
ADD-TAGS |
|
| 82 |
~~~~~~~~ |
|
| 83 |
|
|
| 84 |
**add-tags** [\--from *file*] {*nodename*} {*tag*...}
|
|
| 85 |
|
|
| 86 |
Add tags to the given node. If any of the tags contains invalid |
|
| 87 |
characters, the entire operation will abort. |
|
| 88 |
|
|
| 89 |
If the ``--from`` option is given, the list of tags will be |
|
| 90 |
extended with the contents of that file (each line becomes a tag). |
|
| 91 |
In this case, there is not need to pass tags on the command line |
|
| 92 |
(if you do, both sources will be used). A file name of - will be |
|
| 93 |
interpreted as stdin. |
|
| 94 |
|
|
| 95 | 81 |
EVACUATE |
| 96 | 82 |
~~~~~~~~ |
| 97 | 83 |
|
| ... | ... | |
| 274 | 260 |
Lists available fields for nodes. |
| 275 | 261 |
|
| 276 | 262 |
|
| 277 |
LIST-TAGS |
|
| 278 |
~~~~~~~~~ |
|
| 279 |
|
|
| 280 |
**list-tags** {*nodename*}
|
|
| 281 |
|
|
| 282 |
List the tags of the given node. |
|
| 283 |
|
|
| 284 | 263 |
MIGRATE |
| 285 | 264 |
~~~~~~~ |
| 286 | 265 |
|
| ... | ... | |
| 372 | 351 |
# gnt-node remove node5.example.com |
| 373 | 352 |
|
| 374 | 353 |
|
| 375 |
REMOVE-TAGS |
|
| 376 |
~~~~~~~~~~~ |
|
| 377 |
|
|
| 378 |
**remove-tags** [\--from *file*] {*nodename*} {*tag*...}
|
|
| 379 |
|
|
| 380 |
Remove tags from the given node. If any of the tags are not |
|
| 381 |
existing on the node, the entire operation will abort. |
|
| 382 |
|
|
| 383 |
If the ``--from`` option is given, the list of tags to be removed will |
|
| 384 |
be extended with the contents of that file (each line becomes a tag). |
|
| 385 |
In this case, there is not need to pass tags on the command line (if |
|
| 386 |
you do, tags from both sources will be removed). A file name of - will |
|
| 387 |
be interpreted as stdin. |
|
| 388 |
|
|
| 389 | 354 |
VOLUMES |
| 390 | 355 |
~~~~~~~ |
| 391 | 356 |
|
| ... | ... | |
| 645 | 610 |
output lines. ``--sync`` forces the opcode to acquire the node lock(s) |
| 646 | 611 |
in exclusive mode. |
| 647 | 612 |
|
| 613 |
Tags |
|
| 614 |
~~~~ |
|
| 615 |
|
|
| 616 |
ADD-TAGS |
|
| 617 |
^^^^^^^^ |
|
| 618 |
|
|
| 619 |
**add-tags** [\--from *file*] {*nodename*} {*tag*...}
|
|
| 620 |
|
|
| 621 |
Add tags to the given node. If any of the tags contains invalid |
|
| 622 |
characters, the entire operation will abort. |
|
| 623 |
|
|
| 624 |
If the ``--from`` option is given, the list of tags will be |
|
| 625 |
extended with the contents of that file (each line becomes a tag). |
|
| 626 |
In this case, there is not need to pass tags on the command line |
|
| 627 |
(if you do, both sources will be used). A file name of - will be |
|
| 628 |
interpreted as stdin. |
|
| 629 |
|
|
| 630 |
LIST-TAGS |
|
| 631 |
^^^^^^^^^ |
|
| 632 |
|
|
| 633 |
**list-tags** {*nodename*}
|
|
| 634 |
|
|
| 635 |
List the tags of the given node. |
|
| 636 |
|
|
| 637 |
REMOVE-TAGS |
|
| 638 |
^^^^^^^^^^^ |
|
| 639 |
|
|
| 640 |
**remove-tags** [\--from *file*] {*nodename*} {*tag*...}
|
|
| 641 |
|
|
| 642 |
Remove tags from the given node. If any of the tags are not |
|
| 643 |
existing on the node, the entire operation will abort. |
|
| 644 |
|
|
| 645 |
If the ``--from`` option is given, the list of tags to be removed will |
|
| 646 |
be extended with the contents of that file (each line becomes a tag). |
|
| 647 |
In this case, there is not need to pass tags on the command line (if |
|
| 648 |
you do, tags from both sources will be removed). A file name of - will |
|
| 649 |
be interpreted as stdin. |
|
| 650 |
|
|
| 648 | 651 |
.. vim: set textwidth=72 : |
| 649 | 652 |
.. Local Variables: |
| 650 | 653 |
.. mode: rst |
Also available in: Unified diff