Revision e23cb7ca man/gnt-network.rst
b/man/gnt-network.rst | ||
---|---|---|
14 | 14 |
DESCRIPTION |
15 | 15 |
----------- |
16 | 16 |
|
17 |
The **gnt-network** command is used for network definition administration
|
|
18 |
in the Ganeti system. |
|
17 |
The **gnt-network** command is used for network definition |
|
18 |
administration in the Ganeti system.
|
|
19 | 19 |
|
20 | 20 |
COMMANDS |
21 | 21 |
-------- |
... | ... | |
38 | 38 |
initially. To connect it to a node group, use ``gnt-network connect``. |
39 | 39 |
``--network`` option is mandatory. All other are optional. |
40 | 40 |
|
41 |
The ``--network`` option allows you to specify the network in a CIDR notation. |
|
41 |
The ``--network`` option allows you to specify the network in a CIDR |
|
42 |
notation. |
|
42 | 43 |
|
43 |
The ``--gateway`` option allows you to specify the default gateway for this
|
|
44 |
network. |
|
44 |
The ``--gateway`` option allows you to specify the default gateway for |
|
45 |
this network.
|
|
45 | 46 |
|
46 | 47 |
The ``--network-type`` can be none, private or public. |
47 | 48 |
|
48 | 49 |
IPv6 semantics can be assigned to the network via the ``--network6`` and |
49 |
``--gateway6`` options. IP pool is meaningless for IPV6 so those two values
|
|
50 |
can be used for EUI64 generation from a NIC's MAC address. |
|
50 |
``--gateway6`` options. IP pool is meaningless for IPV6 so those two |
|
51 |
values can be used for EUI64 generation from a NIC's MAC address.
|
|
51 | 52 |
|
52 |
See **ganeti(7)** for a description of ``--submit`` and other common options. |
|
53 |
See **ganeti(7)** for a description of ``--submit`` and other common |
|
54 |
options. |
|
53 | 55 |
|
54 | 56 |
MODIFY |
55 | 57 |
~~~~~~ |
... | ... | |
67 | 69 |
|
68 | 70 |
Modifies parameters from the network. |
69 | 71 |
|
70 |
Unable to modify network (IP address range). Create a new network if you want |
|
71 |
to do so. All other options are documented in the **add** command above. |
|
72 |
Unable to modify network (IP address range). Create a new network if you |
|
73 |
want to do so. All other options are documented in the **add** command |
|
74 |
above. |
|
72 | 75 |
|
73 |
See **ganeti(7)** for a description of ``--submit`` and other common options. |
|
76 |
See **ganeti(7)** for a description of ``--submit`` and other common |
|
77 |
options. |
|
74 | 78 |
|
75 | 79 |
REMOVE |
76 | 80 |
~~~~~~ |
... | ... | |
87 | 91 |
| **list** [--no-headers] [--separator=*SEPARATOR*] [-v] |
88 | 92 |
| [-o *[+]FIELD,...*] [network...] |
89 | 93 |
|
90 |
Lists all existing networks in the cluster. If no group names are given, then |
|
91 |
all groups are included. Otherwise, only the named groups will be listed. |
|
94 |
Lists all existing networks in the cluster. If no group names are given, |
|
95 |
then all groups are included. Otherwise, only the named groups will be |
|
96 |
listed. |
|
92 | 97 |
|
93 | 98 |
The ``--no-headers`` option will skip the initial header line. The |
94 |
``--separator`` option takes an argument which denotes what will be |
|
95 |
used between the output fields. Both these options are to help |
|
96 |
scripting. |
|
99 |
``--separator`` option takes an argument which denotes what will be used |
|
100 |
between the output fields. Both these options are to help scripting. |
|
97 | 101 |
|
98 | 102 |
The ``-v`` option activates verbose mode, which changes the display of |
99 | 103 |
special field states (see **ganeti(7)**). |
100 | 104 |
|
101 |
The ``-o`` option takes a comma-separated list of output fields. |
|
102 |
If the value of the option starts with the character ``+``, the new
|
|
103 |
fields will be added to the default list. This allows to quickly
|
|
104 |
see the default list plus a few other fields, instead of retyping
|
|
105 |
the entire list of fields.
|
|
105 |
The ``-o`` option takes a comma-separated list of output fields. If the
|
|
106 |
value of the option starts with the character ``+``, the new fields will
|
|
107 |
be added to the default list. This allows to quickly see the default
|
|
108 |
list plus a few other fields, instead of retyping the entire list of
|
|
109 |
fields. |
|
106 | 110 |
|
107 | 111 |
The available fields and their meaning are: |
108 | 112 |
|
... | ... | |
144 | 148 |
|
145 | 149 |
**remove-tags** [\--from *file*] {*networkname*} {*tag*...} |
146 | 150 |
|
147 |
Remove tags from the given network. If any of the tags are not |
|
148 |
existing on the network, the entire operation will abort.
|
|
151 |
Remove tags from the given network. If any of the tags are not existing
|
|
152 |
on the network, the entire operation will abort. |
|
149 | 153 |
|
150 | 154 |
If the ``--from`` option is given, the list of tags to be removed will |
151 | 155 |
be extended with the contents of that file (each line becomes a tag). In |
... | ... | |
166 | 170 |
|
167 | 171 |
| **connect** {*network*} {*mode*} {*link*} [*groups*...] |
168 | 172 |
|
169 |
Connect a network to given node groups (all if not specified) with the network
|
|
170 |
parameters *mode* and *link*. Every network interface will inherit those
|
|
171 |
parameters if assigned in a network. |
|
173 |
Connect a network to given node groups (all if not specified) with the |
|
174 |
network parameters *mode* and *link*. Every network interface will
|
|
175 |
inherit those parameters if assigned in a network.
|
|
172 | 176 |
|
173 | 177 |
DISCONNECT |
174 | 178 |
~~~~~~~~~~ |
175 | 179 |
|
176 | 180 |
| **disconnect** {*network*} [*groups*...] |
177 | 181 |
|
178 |
Disconnect a network from given node groups (all if not specified). This is |
|
179 |
possible only if no instance is using the network. |
|
182 |
Disconnect a network from given node groups (all if not specified). This |
|
183 |
is possible only if no instance is using the network. |
|
184 |
|
|
185 |
.. vim: set textwidth=72 : |
|
186 |
.. Local Variables: |
|
187 |
.. mode: rst |
|
188 |
.. fill-column: 72 |
|
189 |
.. End: |
Also available in: Unified diff